Hi,

have to copy files multiple times around 2 TB between 2 environments . the destination volume is a CIFS share and NFS mount.

we thought of using winSCP . but SFTP is not supported on Netapp CDOT. 

any workaround??

thanks

So im looking at setting up fpolicy to add in another layer to hopefully prevent Ransomware.

Netapp has a good blog article about it.

https://blog.netapp.com/fighting-ransomware-tools

My question is looking around there seems to be about 4000 rough known

extensions now.

looking a the command to add in extensions 

vserver fpolicy policy scope create -vserver svm1 -policy-name blacklist_-file-extensions-to-include WNCRY,locky

is there a way we could tell FPolicy to use a file as the list ??

Hello,

My customer is monitoring FAS using SCOM with OnCommand Plug-in for Microsoft. However, OnCommand Plugi-in for Microsoft became EOVS on 6/30/2020.

Are there any alternatives to OCPM in monitoring FAS by SCOM?

Best Regards,

Chigusa

Hi all !  

I'll have to upgrade a FAS2552 which is currently running  7MOD 8.2.5P2. By checking HWU, I could upgrade to ONTAP 9.6 (even 9.7). What's the process to do so ? Data have already been migrated, so i'll first erase everything (option 4), no need of 7MTT. 

Thanks for your answers. 

Regards. 

Hello Guys,

I'm migrating from old FAS system to FAS8300 using 7MTT. The copying is done and I'm about to cutover only to realize the login to the 7MTT is failing. I have tried several and I'm 100% certain the login details is the same and haven't changed since I installed the 7MTT. Has anyone experienced this? Please I need help urgently.

Regards.

Updated to ontap 9.6P9 from ontap 9.5  directly after I notice my PRTG (https based) sensors  going down for this cluster

short time after i found out that storage based snapshot backup with veeam backup also stopped working

also seems to use the https api.  Can't find what's stopping this , when i use either program i get a " The remote server returned an error: (408) Request Timeout. "  but from both servers I can connect to the https of the ontap system and I can run a curl command to query the api with successful output:

C:\curl\bin>curl -X GET -u admin:*** https://10.1.0.100/api/cluster?fields=version -v -k
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying 10.1.0.100:443...
* Connected to 10.1.0.100 (10.1.0.100) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=SAN; C=US
* start date: Jul 25 19:39:11 2020 GMT
* expire date: Jul 23 19:39:11 2030 GMT
* issuer: CN=SAN; C=US
* SSL certificate verify result: self signed certificate (18), continuing anyway.
* Server auth using Basic with user 'admin'
> GET /api/cluster?fields=version HTTP/1.1
> Host: 10.1.0.100
> Authorization: Basic YWRtaW46KlN5c3RlbTAxKg==
> User-Agent: curl/7.71.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 29 Jul 2020 11:33:35 GMT
< Server: libzapid-httpd
< X-Content-Type-Options: nosniff
< Cache-Control: no-cache,no-store,must-revalidate
< Content-Length: 208
< Content-Type: application/hal+json
<
{
"version": {
"full": "NetApp Release 9.6P9: Wed Jul 08 09:07:16 UTC 2020",
"generation": 9,
"major": 6,
"minor": 0
},
"_links": {
"self": {
"href": "/api/cluster"
}
}
}* Connection #0 to host 10.1.0.100 left intact

any one else have seen this or have some suggestions ? have cases running with netapp support , prtg support and veeam support , but the process is going very slow and I need to get my backup back running again.

All help appreciated.

JWH

Good Morning,

i am new to the forum and a novice to NetApp.

I have a network with Vmware and NetApp storage. We had a folder deleted which we thought were old files which were no longer used but after deleting our DFS/Print vm server will not Power on. Says it need a .vmdk file that was one of the deleted files.

We tried looking in the backup tapes but could not find the files. I have been researching and there is mentioning of a snapshot directory that may retain these files but it is hidden. 

Long story short is we need to restore these files to return access to NFS file shares and print services.

Is there any way to do so?

Thanks for any help.

Ed

Hello, 

I'd like to know what's happening when simulating a failed disk in ADP configuration on an AFF C190 with the following sysconfig -r : 

===== SYSCONFIG-R =====
Aggregate c190_01_root (online, raid_dp, fast zeroed) (block checksums)
  Plex /c190_01_root/plex0 (online, normal, active, pool0)
    RAID group /c190_01_root/plex0/rg0 (normal, block checksums)

RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------        ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity         0b.00.18P3        0b    0   18  SA:A   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)
      parity          0b.00.19P3        0b    0   19  SA:A   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)
      data            0b.00.20P3        0b    0   20  SA:A   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)
      data            0b.00.21P3        0b    0   21  SA:A   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)
      data            0b.00.22P3        0b    0   22  SA:A   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

Aggregate c190_01_SSD_1 (online, raid_dp, fast zeroed) (block checksums)
  Plex /c190_01_SSD_1/plex0 (online, normal, active, pool0)
    RAID group /c190_01_SSD_1/plex0/rg0 (normal, block checksums)

RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------        ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity         0b.00.18P1        0b    0   18  SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      parity          0b.00.19P1        0b    0   19  SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.20P1        0b    0   20  SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.21P1        0b    0   21  SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.22P1        0b    0   22  SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.0P1        0b    0   0   SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.1P1        0b    0   1   SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.2P1        0b    0   2   SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.3P1        0b    0   3   SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.4P1        0b    0   4   SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.5P1        0b    0   5   SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)
      data            0b.00.23P1        0b    0   23  SA:A   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

Pool1 spare disks (empty)

Pool0 spare disks

RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------        ------          ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block checksum
spare           0b.00.23P3        0b    0   23  SA:A   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

Partner disks

RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------        ------          ------------- ---- ---- ---- ----- --------------    --------------
partner         0b.00.4P3        0b    0   4   SA:A   0   SSD   N/A 0/0               63857/130780672
partner         0b.00.5P3        0b    0   5   SA:A   0   SSD   N/A 0/0               63857/130780672
partner         0b.00.3P2        0b    0   3   SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.3P3        0b    0   3   SA:A   0   SSD   N/A 0/0               63857/130780672
partner         0b.00.19P2        0b    0   19  SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.20P2        0b    0   20  SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.0P3        0b    0   0   SA:A   0   SSD   N/A 0/0               63857/130780672
partner         0b.00.0P2        0b    0   0   SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.2P3        0b    0   2   SA:A   0   SSD   N/A 0/0               63857/130780672
partner         0b.00.2P2        0b    0   2   SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.18P2        0b    0   18  SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.4P2        0b    0   4   SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.1P3        0b    0   1   SA:A   0   SSD   N/A 0/0               63857/130780672
partner         0b.00.1P2        0b    0   1   SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.5P2        0b    0   5   SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.23P2        0b    0   23  SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.22P2        0b    0   22  SA:A   0   SSD   N/A 0/0               425793/872025088
partner         0b.00.21P2        0b    0   21  SA:A   0   SSD   N/A 0/0               425793/872025088

===== SYSCONFIG-R =====

Aggregate c190_02_SSD_1 (online, raid_dp, fast zeroed) (block checksums)

  Plex /c190_02_SSD_1/plex0 (online, normal, active, pool0)

    RAID group /c190_02_SSD_1/plex0/rg0 (normal, block checksums)

      RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

      ---------        ------          ------------- ---- ---- ---- ----- --------------    --------------

      dparity         0b.00.0P2        0b    0   0   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      parity          0b.00.1P2        0b    0   1   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.2P2        0b    0   2   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.3P2        0b    0   3   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.4P2        0b    0   4   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.18P2        0b    0   18  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.19P2        0b    0   19  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.20P2        0b    0   20  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.21P2        0b    0   21  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.22P2        0b    0   22  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.5P2        0b    0   5   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

      data            0b.00.23P2        0b    0   23  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

Aggregate c190_02_root (online, raid_dp, fast zeroed) (block checksums)

  Plex /c190_02_root/plex0 (online, normal, active, pool0)

    RAID group /c190_02_root/plex0/rg0 (normal, block checksums)

      RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

      ---------        ------          ------------- ---- ---- ---- ----- --------------    --------------

      dparity         0b.00.0P3        0b    0   0   SA:B   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

      parity          0b.00.1P3        0b    0   1   SA:B   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

      data            0b.00.2P3        0b    0   2   SA:B   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

      data            0b.00.3P3        0b    0   3   SA:B   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

      data            0b.00.4P3        0b    0   4   SA:B   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

Pool1 spare disks (empty)

Pool0 spare disks

RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

---------        ------          ------------- ---- ---- ---- ----- --------------    --------------

Spare disks for block checksum

spare           0b.00.5P3        0b    0   5   SA:B   0   SSD   N/A 63849/130764288   63857/130780672 (fast zeroed)

Partner disks

RAID Disk        Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

---------        ------          ------------- ---- ---- ---- ----- --------------    --------------

partner         0b.00.23P1        0b    0   23  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.5P1        0b    0   5   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.4P1        0b    0   4   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.3P1        0b    0   3   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.2P1        0b    0   2   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.1P1        0b    0   1   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.0P1        0b    0   0   SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.22P1        0b    0   22  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.21P1        0b    0   21  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.20P1        0b    0   20  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.19P1        0b    0   19  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.18P1        0b    0   18  SA:B   0   SSD   N/A 425785/872008704  425793/872025088 (fast zeroed)

partner         0b.00.18P3        0b    0   18  SA:B   0   SSD   N/A 0/0               63857/130780672 (fast zeroed)

partner         0b.00.20P3        0b    0   20  SA:B   0   SSD   N/A 0/0               63857/130780672 (fast zeroed)

partner         0b.00.19P3        0b    0   19  SA:B   0   SSD   N/A 0/0               63857/130780672 (fast zeroed)

partner         0b.00.21P3        0b    0   21  SA:B   0   SSD   N/A 0/0               63857/130780672 (fast zeroed)

partner         0b.00.22P3        0b    0   22  SA:B   0   SSD   N/A 0/0               63857/130780672 (fast zeroed)

partner         0b.00.23P3        0b    0   23  SA:B   0   SSD   N/A 0/0               63857/130780672 (fast zeroed)

If you have any idea ? 

Regards.

Hi Team,

Kindly advice and suggest.As we are getting alerts as per attached doc.

RUH-PS-######::> network interface show -failover
Logical Home Failover Failover
Vserver Interface Node:Port Policy Group
-------- --------------- --------------------- --------------- ---------------
Cluster
RUH-PS-DM5###H-01_clus1 RUH-PS-DM5000H-01:e0a
local-only Cluster
Failover Targets: RUH-PS-DM5000H-01:e0a,
RUH-PS-DM5###H-01:e0b
RUH-PS-DM5000H-01_clus2 RUH-PS-DM5000H-01:e0b
local-only Cluster
Failover Targets: RUH-PS-DM5000H-01:e0b,
RUH-PS-DM5000H-01:e0a
RUH-PS-DM5000H-02_clus1 RUH-PS-DM5000H-02:e0a
local-only Cluster
Failover Targets: RUH-PS-DM5000H-02:e0a,
RUH-PS-DM5000H-02:e0b
RUH-PS-DM5000H-02_clus2 RUH-PS-DM5000H-02:e0b
local-only Cluster
Failover Targets: RUH-PS-DM5000H-02:e0b,
RUH-PS-DM5000H-02:e0a
RUH-PS-DM5000H
RUH-PS-DM5000H-01_mgmt1 RUH-PS-DM5000H-01:e0M
local-only Management
Failover Targets: RUH-PS-DM5000H-01:e0M
RUH-PS-DM5000H-02_mgmt1 RUH-PS-DM5000H-02:e0M
local-only Management
Failover Targets: RUH-PS-DM5000H-02:e0M
cluster_mgmt RUH-PS-DM5000H-01:e0M broadcast-domain-wide
Management
Failover Targets: RUH-PS-DM5000H-01:e0M,
RUH-PS-DM5000H-02:e0M
SVM_iSCSI
RUH-PS-DM5000H-01_iscsi_lif_1 RUH-PS-DM5000H-01:e0c
disabled
Failover Targets: RUH-PS-DM5000H-01:e0c
RUH-PS-DM5000H-01_iscsi_lif_2 RUH-PS-DM5000H-01:e0d
disabled
Failover Targets: RUH-PS-DM5000H-01:e0d
RUH-PS-DM5000H-02_iscsi_lif_1 RUH-PS-DM5000H-02:e0c
disabled -
Failover Targets: RUH-PS-DM5000H-02:e0c
RUH-PS-DM5000H-02_iscsi_lif_2 RUH-PS-DM5000H-02:e0d
disabled -
Failover Targets: RUH-PS-DM5000H-02:e0d
11 entries were displayed.

Hi Guys,

When we perform internal scans on our NetApp Cluster mode storage systems, we found below vulnerabilities.

ISC BIND Denial of service

ISC BIND Service downgrade/reflected DOS

We found these issues on all Netapp clusters except one cluster. Now my task is to  compare the configurations on the clusters with one cluster where these vulnerabilities are not found. 

What are all the configurations I need to check on my clusters to resolve this ISC BIND issues?

Any help on this is appreciated.

CVE: CVE-2020-8616
Plugin Name Severity IP Address Protocol Port
ISC BIND Denial of
Service High IP Address UDP 53
Plugin Text:
Plugin Output:
Installed version : 9.6.2-P2
Fixed version : 9.11.19
Synopsis: The remote name server is affected by an assertion failure vulnerability.
Description: A denial of service (DoS) vulnerability exists in ISC BIND versions 9.11.18 / 9.11.18-S1 / 9.12.4-P2 / 9.13 / 9.14.11 / 9.15 / 9.16.2 / 9.17 /
9.17.1 and earlier. An unauthenticated, remote attacker can exploit this issue, via a specially-crafted message, to cause the service to stop responding.
Solution: Upgrade to the patched release most closely related to your current version of BIND.
See Also: https://kb.isc.org/docs/cve-2020-8617
CVE: CVE-2020-8617
Plugin Name Severity IP Address Protocol Port
ISC BIND Service
Downgrade / Reflected
DoS
Medium IP Address UDP 53
Plugin Text:
Plugin Output:
Installed version : 9.6.2-P2
Fixed version : 9.11.19
Synopsis: The remote name server is affected by Service Downgrade / Reflected DoS vulnerabilities.
Description: According to its self-reported version, the instance of ISC BIND 9 running on the remote name server is affected by performance
downgrade and Reflected DoS vulnerabilities. This is due to BIND DNS not sufficiently limiting the number fetches which may be performed while
processing a referral response.
An unauthenticated, remote attacker can exploit this to cause degrade the service of the recursive server or to use the affected server as a reflector in
a reflection attack.
Solution: Upgrade to the ISC BIND version referenced in the vendor advisory.
See Also: https://kb.isc.org/docs/cve-2020-8616

We recently had NetApp install a two-node FAS8700 cluster, but when we checked - we can only connect to 1 out of the service-processors. We can connect to the management lifs of both nodes.

Any help appreciated troubleshooting this...

Both showing online and with correct IPs, but I can only connect to the first one 10.7.190.14 - the second one says connection refused:

pnl0004scpr1655::> system service-processor show -instance

Node: pnl0004scpr1655-01
Type of Device: BMC
Status: online
Is Network Configured: true
Public IP Address: 10.7.190.14
MAC Address: d0:39:ea:13:0c:e1
Firmware Version: 13.2
Part Number: NA
Serial Number: NA
Device Revision: 13.2
Is Firmware Autoupdate Enabled: true

Node: pnl0004scpr1655-02
Type of Device: BMC
Status: online
Is Network Configured: true
Public IP Address: 10.7.190.15
MAC Address: d0:39:ea:13:16:36
Firmware Version: 13.2
Part Number: NA
Serial Number: NA
Device Revision: 13.2
Is Firmware Autoupdate Enabled: true
2 entries were displayed.

I came across this command, but it is not accepted:

pnl0004scpr1655::> system service-processor ssh show

Error: show failed: This command is not supported in this platform.

This is the detailed network setup which seems correct:

pnl0004scpr1655::> system service-processor network show -instance

Node: pnl0004scpr1655-01
Address Family: IPv4
Interface Enabled: true
Type of Device: BMC
Status: online
Link Status: up
DHCP Status: none
IP Address: 10.7.190.14
MAC Address: d0:39:ea:13:0c:e1
Netmask: 255.255.255.0
Prefix Length of Subnet Mask: -
Router Assigned IP Address: -
Link Local IP Address: -
Gateway IP Address: 10.7.190.1
Time Last Updated: 2020:08:03.22:49:35
Subnet Name: -
Enable IPv6 Router Assigned Address: -
SP Network Setup Status: succeeded
SP Network Setup Failure Reason: -

Node: pnl0004scpr1655-01
Address Family: IPv6
Interface Enabled: false
Type of Device: BMC
Status: online
Link Status: disabled
DHCP Status: none
IP Address: -
MAC Address: d0:39:ea:13:0c:e1
Netmask: -
Prefix Length of Subnet Mask: 0
Router Assigned IP Address: -
Link Local IP Address: -
Gateway IP Address: -
Time Last Updated: 2020:08:03.22:49:35
Subnet Name: -
Enable IPv6 Router Assigned Address: -
SP Network Setup Status: not-setup
SP Network Setup Failure Reason: -

Node: pnl0004scpr1655-02
Address Family: IPv4
Interface Enabled: true
Type of Device: BMC
Status: online
Link Status: up
DHCP Status: none
IP Address: 10.7.190.15
MAC Address: d0:39:ea:13:16:36
Netmask: 255.255.255.0
Prefix Length of Subnet Mask: -
Router Assigned IP Address: -
Link Local IP Address: -
Gateway IP Address: 10.7.190.1
Time Last Updated: 2020:08:03.22:42:47
Subnet Name: -
Enable IPv6 Router Assigned Address: -
SP Network Setup Status: succeeded
SP Network Setup Failure Reason: -

Node: pnl0004scpr1655-02
Address Family: IPv6
Interface Enabled: false
Type of Device: BMC
Status: online
Link Status: disabled
DHCP Status: none
IP Address: -
MAC Address: d0:39:ea:13:16:36
Netmask: -
Prefix Length of Subnet Mask: 0
Router Assigned IP Address: -
Link Local IP Address: -
Gateway IP Address: -
Time Last Updated: 2020:08:03.22:42:47
Subnet Name: -
Enable IPv6 Router Assigned Address: -
SP Network Setup Status: not-setup
SP Network Setup Failure Reason: -
4 entries were displayed.

Where can customers provide positive/negative feedback on the new user interface? 

I am in the process of doing a controller swap from a FAS2620 to a FAS8200 using the Upgrading Controller Express Guide.   The instructions say to netboot the new controllers to install the new Ontap version to match the version on the current controllers.  I am netbooting to Ontap 9.7P5 and it has been over an hour and still loading the rootfs.img.    It is proceeding as their are dots spewing across the screen slowly.    I am direct connected to e0M on the controllers from my Mac at 1Gb speed.   How long would I expect the netboot to take?  Is there something I am missing?

Hello,

Does anyone has ever seen this?

- I am able to resolve any name in the domain using ping command on ONTAP (9.7P3);

- dns check command fails with server down and Operation Timed Out:

It smells like a bug. I am almost opening a case with NetApp to check.

Regards,

Pedro Rocha

Hello!

In the following extract, what accounts for System-Default?

STG::> qos statistics workload resource cpu show -node STG-01 -rows 20
Workload ID CPU
--------------- ----- -----
-total- (100%) - 93%
System-Default 1 37%
User-Default 2 24%
_WAFL 7 11%
_Efficiency_B.. 7501 5%
_SIS_CLONE_SP.. 20 1%
_SNAPMIRROR 15 1%
_WAFL_SCAN 19 1%

Kind regards, 

Pedro Rocha

Hi all,

we run a Powershell script to create snapshots from Windows 2012 R2 machine on a FAS2554. It ran flawlessly until last week when we upgraded the FAS Ontap Version. Upgrade path was as follows: 9.3P12 -> 9.5P18 -> 9.6P9.

Now the script fails and as I found it can't even connect to the FAS. A simple Connect-NcController fails with error "API invoke failed". Other facts are:

- Authentication works, because when I type wrong credentials, I get a corresponding error message

- I tried https and http and both are enable on the target FAS

- A "Test-Connection" either to port 80 or 443 is successful

- Certificates have been renewed and are not expired

After trying everything I can think of, I am completely at a loss. Any help would be greatly appreciated.

Thanks

Dan

I read through the manuals but it seems I dont quite understand how to properly set up an NFS Storage with no_root_squash and Name Mapping for my Domain Admins to Root.

Goal:
Have NFS Storage that I can mount on my Linux Box. Linux Box is connected with AD. I want to be able to create Folders/Files as root:root and also with my domain users domuser@domain:domgroup@domain. Preferably with NFS4.0 so I can use ACL and set multiple permission Groups on Folders/Files.

Set Up is now as following
Cluster: 10.0.0.5
Client: 10.0.0.10
SVM: SMB

Volume: nfs_sftp
QTree: qtree_nfs_sftp

My Issue now is:

With NFS4.1 activated and a Standard Domain User set im able to mount and list everything in it but when I create a Folder its owner is shown as root but reroutet to nobody.

With NFS4.0 activated im not able to mount the Share.

With NFS3 activated I can mount the share but have no permission to list whats in it, I also created the "exp_NFS_SFTP" file to refer to the Export Policy as suggested in the Manual.

I def did not quite understand how to properly configure it so Im full of hope someone can point me in the right directions.

Hello,

Our customer is currently using CIFS from Ontap 9.5 and  8.2.4 (7-mode) and he is going to change some user's UPN attributes (userPrincipalName ) on his Microsoft Active Directory.  He asked me if there is any point of care in doing so.

I'm trying to find any related information on NetApp's KB and didn't find anything related to this matter.

Would you guys have any document or comments about using this AD Attribute to access shares from NetApp  and possible issues that may arise on changing it on AD side?

Thanks!

My English is not good, please try to understand

I have two Storages with 7-mode, one storage is online and 2nd is not in production/free. One drive found faulty in online storage. So we removed disk from free storage with "disk fail -i" command then installed it in online storage and found on error that the "fail disk detect".  The disk is only shown in GUI "broken" and when use command line the disk is not found anywhere.

Please help to resolve this issue.

how do we get the 7-mode controller details via powershell/REST api?

details such as model, serial number...etc

In cluster mode, we can use Get-NcNode, is there such an api in 7-mode?