I have a netapp system that was never sending Autosupport. I configured all the emails, smtp, DNS stuff and am at the point where one node is working, but the other node keeps failing. One node reports the status as DOWN. I am getting a bit lost in IPs, and articles trying to understand what to check and what commands to run. I have a feeling its a simple fix. Does anyone have suggestions what to check?    NETAPPCLU01::vserver services name-service> dns check -vserver NETAPP02 Name Server Vserver Name Server Status Status Details ------------- --------------- ------------ -------------------------- NETAPPSVM02 10.10.10.20 up Response time (msec): 125 NETAPPSVM02 10.10.10.25 up Response time (msec): 0 2 entries were displayed. NETAPPCLU01::vserver services name-service> dns check -vserver NETAPP01 Name Server Vserver Name Server Status Status Details ------------- --------------- ------------ -------------------------- NETAPPSVM01 10.10.10.20 down Operation timed out. NETAPPSVM01 10.10.10.25 down Operation timed out. 2 entries were displayed. ... View more

This post is for those who see the below error. "Error: The "-hwassist-partner-ip" parameter is not supported on this platform." I have recently come across this error when working on a NetApp AFF A400. So what is Hardware Assisted takeover? Further details are here https://docs.netapp.com/us-en/ontap/high-availability/ha_how_hardware-assisted_takeover_works.html NetApp have streamlined this feature as now there is no configuration, but the documentation is yet to catch up. There are a number of elements within newer platforms that you should be aware of: 1) Hwassist IP address is set to 192.0.2.84 and 192.0.2.85 - https://kb.netapp.com/onprem/ontap/hardware/Hwassist_IP_address_is_set_to_192.0.2.84_and_192.0.2.85 - The applicable storage systems implement HW-assisted storage failover by using a private and internal Ethernet network with statically assigned IP addresses. - IP addressing for HW-assisted storage failover is not configurable on the applicable storage systems 2) New e0S interface on newer FAS and AFF storage systems - https://kb.netapp.com/onprem/ontap/hardware/What_is_the_ONTAP_e0S_interface - A private and internal Ethernet-switched subnet exists between both ONTAP HA partners and both BMCs - Features such as HW-assisted failover, ONTAP <-> BMC communications (IPMI), and BMC FW updates are performed over this private network 3) New e0M-16 interface on newer FAS and AFF storage systems - https://kb.netapp.com/onprem/ontap/hardware/What_is_the_ONTAP_e0M-16_interface - e0M-16 is a hidden, internal ONTAP interface on a node that is used for communication with its service processor (SP) or baseboard management controller (BMC) - e0M-16 (specifically using VLAN tag 16) is sharing the same physical internal Ethernet port as e0M, but is restricted to only communicate with its local SP or BMC, also on VLAN tag 16 - HW-assisted failover does not use e0M-16 when communicating with the partner's SP or BMC I hope that this post will help people when searching for this error. ... View more

Hi      I have configure my svm and create some volume for share AD domain user... it seem work fine. but some time netAPP simulator show EMERGENCY MESSAGE: None of the LSA servers configured for Vserver (svm0) are current accessible via the network.    But when I reboot simulator server....it could work fine for let user access these volume. it has occur some time one day. Whether it is simularot issue or which command that I must be set , OR I must add second Domain Controller for svm ?   Thanks!!   Wencheng   ... View more

Hello, we have started to deploy Ansible for backup /clone of EPIC environment. The refresh-hook script is supposed to run daily and keep 30 snapshots  /var/netapp_refresh/bin/eeod-refresh-hook.sh -e rdcepbkp -o eeod_snap_only   but only retains the one most recent snap, others are purged Have anyone else seen similar behavior? ... View more