We have an aging 3270 HA Pair running 7-mode that is only used as a backup target for a handful of remote offices still running 2220s with 7-mode, which we hope to decommission in the next few months. As the first step of our last round of patching on these systems, I patched the 3270s from 8.2.5P1 to 8.2.5P3. Upon completion, all SnapMirror jobs stopped working and our PowerShell scripts abruptly stopped working. They are critical because they force bandwidth drops during business hours on any SnapMirror jobs still running when offices open. In addition, we lost System Manager access. We can still access the system through the command line and CIFS. We have 3rd party support but I'm not hopeful that a solution will come from there. Any suggestions on where to look? I'm at a loss as to how a simple patch could break these items.
I have been unable to find a way to refresh the network of an ESX hypervisor in On Tap Select Deploy host without completly removing the host. This of course requires that no On Tap Select Cluster is running on the host (s). Basically once the esx host is added to onTap Select Deploy any further network changes on the host are not and can not be recognized by the Deploy appliance. There is clearly a refresh button but it has not effect on refreshing the networks.
Hello,
Does anyone know how to get Write I/O block size for a volume/LUN by way of System Manager, Unified Manager or CLI for a NAS filer?
I would assumne it should be pretty easy within Unified Manager but I'm not finding the data.
Thanks in advance!
We have a PowerShell script that reports on the top 50 consumers on one of our volumes. The volume has tracing quotas enabled so we are using Get-NcQuotaReport to get the information. The username returned from Get-NcQuotaReport comes back as DomainName\Username via $_QuotaUsers.QuotaUserName. Is there a way via an inline expression to remove the "DomainName\" from the output? Here is how we get the output.
$diskused = Get-NcQuotaReport | Where-Object {$_.Volume -eq 'OurVolume'} | Where-Object {$_.QuotaUsers.QuotaUserName -notlike '*Admin*'} | select QuotaUsers,DiskUsed
$diskused | Sort-Object -Unique -Descending { [int64]$_.DiskUsed} |
Format-Table @{Name='Username';Expression={$_.QuotaUsers.QuotaUserName}}, @{Name='GigaBytes';Expression={($_.DiskUsed -shr 20)};align='right'; Width=10} |
Select-Object -First 50 | Out-String -Width 80 |
Out-File $reportfile -Append
When running Get-NcQuotaReport we get numerous entries where the QuotaUserName and QuotaTarget are empty or blank. How do we find out which files are contributing to these?
Get-NcQuotaReport -Volume Our_Volume | Select-Object diskused,QuotaUsers,Quotatarget | Where-Object {$_.QuotaUsers.QuotaUserName -like ''}DiskUsed QuotaUsers QuotaTarget
-------- ---------- -----------
4 {}
33426292 {}
40 {}
3026624 {}
115472068 {}
4 {}
24859292 {}
44 {}
41184 {}
5140 {}
32 {}
19480 {}
34232 {}
159148 {}
4 {}
32619876 {}
Hi,
can someone help me with the routing? I have the following network configuration:
Filer 1: Group e0a, e0c Ip: 10.140.11 .......
Group e0b, 0ed Ip: 10.140.21 .......
Mgmt e0m Ip: 10.140.15 .......
Filer 2: same config, only other IP
Default Gateway: 10.140.11.254
Client 1: ip: 10.140.15 ........ netapp on MGMT ping successfully
- ping on 10.140.21 ....... not successful
- ping to 10.140.11 ....... not successful
Client 2: ip: 10.140.31 ........ ping to 10.140.15 ..... not successful
ping to 10,140.21 ..... not successful
ping on 10.140.11 ..... not successful
I can ping the MGMT from client 1, I realize. Both are in the same subnet. But why do not I reach the others? Does something have to be stored in the Netapp routing table?
Please help.
Hello,
I guess that there no issue but I would like to be sure that it's supprted to have the MC Tiebreaker in the Cloud?
Best regards.
Nordin.
Behavior of "delete_on_close" with FPolicy notifications
Please refer the belwo article for step by step solution
https://kb.netapp.com/app/answers/answer_view/a_id/1086884
Note: If you are unable to view the entire content of this article please log in to kb.netapp.com
We are running in to a problem when copying files to a CIFS share running on CDOT 9.4. All files that contains 'special' characters in the file name is rejected. We need to store forensics dumps of cell phone data with emojis and other off the wall characters. As these are evidence, we cannot alter the files to comply with the base UTF character set that NetApp uses
The email alert (see below) that gets generated has some steps to enable UTF surrogate pairs, but the syntax isn't valid (as far as I can tell) for CDOT 9.4. So, I have two/three questions:
1. What is the ramification of enabling UTF surrogate pairs (should we do it)?
2. What is the proper syntax to implement the change?
2.a. How do we make the change persistent across reboots?
Subject: NODE_2: wafl.dir.surrpair.filename [LOG_ERR]
Filer: NODE_2
Time: Fri, Sep 20 09:50:41 2019 -0400
Severity: LOG_ERR
Message: wafl.dir.surrpair.filename: Failed to create a file with surrogate pair characters in the name in the directory /vol/<redacted>.
Description: This message occurs as a warning when a file name with surrogate pair characters in UTF-16 encoding fails to be created in a parent directory.
Action: To allow names with surrogate pairs to be created, use the following
command: "setflag wafl_reject_surrogate_pair 0". If the option needs to be set across reboots, set the bootarg 'wafl-accept-surrogate-pair?' to "true" at the LOADER prompt.
Source: wafl_exempt00
Index: 14321181
Is anyone out there familar enough with AWS Snowball to tell me if I can use a Snowball to perform seeding to a CVO? Has anyone actually done it?
We are looking at methods to seed data from an on-prem FAS to a CVO, and some folks think this would work but I can't find any documentation on it.
The idea is to seed the transport storage (snowball), then use it to seed the CVO, and resync with the On-Prem system via Snapmirror.
Hello everyone,
I have some x315A drives that im trying to use. I know they're encrypted and was trying to figure out how to return them to their original state. So far I am not having any luck. This is not the orginal system they were in. I no longer have the FAS system with the Keys. Does this mean these drives are completely uses less ? If so let me know so I could stop wasting my time trying to figure this out. Any explaination will be helpful.
The disk were autoassigned using some weired format. I tried unfailing them = no luck. I tried reassigning them = no luck.
TestCluster::storage*> encryption disk revert-to-original-state -disk TestCluster-01:0b.01.3 -psid 37FUU7QLD00000000LVCX6V53WE8YW1Z
Info: Starting revert-to-original-state on 1 disk on node TestCluster-01.
View the status of the operation by using the "storage encryption disk show-status" command.
Error: Could not send revert-to-original-state request to node TestCluster-01. Reason: resource limit exceeded
TestCluster::storage disk*> show
Usable Disk Container Container
Disk Size Shelf Bay Type Type Name Owner
---------------- ---------- ----- --- ------- ----------- --------- --------
1.0.0 546.9GB 0 0 SAS shared aggr0_TestCluster_02
TestCluster-02
1.0.1 546.9GB 0 1 SAS shared aggr0_TestCluster_01
TestCluster-01
1.0.2 546.9GB 0 2 SAS shared aggr0_TestCluster_02
TestCluster-02
1.0.3 546.9GB 0 3 SAS shared aggr0_TestCluster_01
TestCluster-01
1.0.4 546.9GB 0 4 SAS shared aggr0_TestCluster_02
TestCluster-02
1.0.5 546.9GB 0 5 SAS shared aggr0_TestCluster_01
TestCluster-01
1.0.6 546.9GB 0 6 SAS shared aggr0_TestCluster_02
TestCluster-02
1.0.7 546.9GB 0 7 SAS shared aggr0_TestCluster_01
TestCluster-01
1.0.8 546.9GB 0 8 SAS shared aggr0_TestCluster_02
TestCluster-02
1.0.9 546.9GB 0 9 SAS shared aggr0_TestCluster_01
TestCluster-01
1.0.10 546.9GB 0 10 SAS shared - TestCluster-02
1.0.11 546.9GB 0 11 SAS shared - TestCluster-01
TestCluster-01:0b.01.5 - 1 5 FSAS broken - -
TestCluster-02:0b.01.1 - 1 1 FSAS broken - -
TestCluster-02:0b.01.2 - 1 2 FSAS broken - -
TestCluster-02:0b.01.3 - 1 3 FSAS broken - -
TestCluster-02:0b.01.4 - 1 4 FSAS broken - -
TestCluster-02:0b.01.6 - 1 6 FSAS broken - -
TestCluster-02:0b.01.7 - 1 7 FSAS broken - -
TestCluster-02:0b.01.8 - 1 8 FSAS broken - -
TestCluster-02:0b.01.12 - 1 12 FSAS broken - -
21 entries were displayed.TestCluster::*> security config show
Cluster Cluster Security
Interface FIPS Mode Supported Protocols Supported Ciphers Config Ready
--------- ---------- ------------------- --------------------- ----------------
SSL true TLSv1.2, TLSv1.1 ALL:!LOW:!aNULL:!EXP: yes
!eNULL:!3DES:!kDH:
!kECDHTestCluster::storage disk*> unfail TestCluster-01:0b.01.5
Warning: Failed disk "TestCluster-01:0b.01.5" may have aggregate labels and file system data present. In that case, this command will attempt to bring this disk back into
the aggregate with which this disk had formerly been associated and preserve file system data. Are you sure you want to continue with disk unfail?
{y|n}: y
Error: command failed: Failed to unfail the disk. Reason: Disk 0b.01.5 does not exist.
TestCluster::storage disk*>
TestCluster::storage disk*>
TestCluster::storage disk*> unfail 0b.01.5
Error: command failed: Disk "0b.01.5" does not exist.
TestCluster::storage disk*>TestCluster-01> sysconfig -v
NetApp Release 9.6P1: Thu Jul 18 22:31:23 EDT 2019
System ID: 123025260 (TestCluster-01); partner ID: 123455246 (TestCluster-02)
System Serial Number: 71234300021 (TestCluster-01)
System Rev: D1
System Storage Configuration: Multi-Path HA
System ACP Connectivity: Additional Connectivity
All-Flash Optimized: false
Capacity Optimized: false
Backplane Part Number: DS212
Backplane Rev:
Backplane Serial Number: 4591503044
slot 0: System Board 1.7 GHz (System Board XIX D1)
Model Name: FAS2520
Part Number: 111-01323
Revision: D1
Serial Number: 031541000089
BIOS version: 8.3.0
Loader version: 4.3
Processors: 4
Processor type: Intel(R) Xeon(R) CPU C3528 @ 1.73GHz
Memory Size: 18432 MB
Memory Attributes: Hoisting
Normal ECC
NVMEM Size: 1280 MB of Main Memory Used
Controller: A
Service Processor Status: Online
Firmware Version: 2.9
Mgmt MAC Address: 00:A0:98:8B:A9:39
Ethernet Link: up, 100Mb, full duplex, auto-neg complete
Using DHCP: no
IPv4 configuration:
IP Address: 3.112.169.151
Netmask: 255.255.255.128
Gateway: 3.112.169.129
IPv6 configuration: Disabled
[Service Processor cached network information determined at Wed Oct 2 22:57:02 GMT 2019]
slot 0: Internal 10/100/1000 Ethernet Switch
Wrench: auto-100tx-fd-up
Locked-wrench: auto-100tx-fd-up
Device Type: 88E6176
slot 0: Gigabit Ethernet Controller 82580
e0a MAC Address: 00:a0:98:8b:a9:35 (auto-100tx-fd-up)
e0b MAC Address: 00:a0:98:8b:a9:36 (auto-unknown-fd-down)
e0M MAC Address: 00:a0:98:8b:a9:37 (auto-1000t-fd-up)
e0P MAC Address: 00:a0:98:8b:a9:38 (auto-1000t-fd-up)
Device Type: 150E
Firmware Version: 3.22 0x80000101
slot 0: 1/10 Gigabit Ethernet Controller IX2-T
e0c MAC Address: 00:a0:98:8b:a9:3b (auto-unknown-fd-down)
e0d MAC Address: 00:a0:98:8b:a9:3c (auto-10g_t-fd-up)
e0e MAC Address: 00:a0:98:8b:a9:3d (auto-unknown-fd-down)
e0f MAC Address: 00:a0:98:8b:a9:3e (auto-10g_t-fd-up)
Device Type: X540
Firmware Version: 4.4-0
slot 0: Interconnect HBA: Mellanox IB MT25204
Port Name: ib0a
GUID: 0x100000a0988ba935
Base LID: 0x4
Remote LID: 0x5
Firmware rev: 1.0.800
Hardware rev: 160
Command rev: 1
Interconnect Port: 1x
slot 0: SAS Host Adapter 0a (PMC-Sierra PM8001 rev. C, SAS, <UP>)
Firmware rev: 01.12.09.00
Base WWN: 5:00a098:00659db:b0
Phy State: [0] Enabled, 6.0 Gb/s
[1] Enabled, 6.0 Gb/s
[2] Enabled, 6.0 Gb/s
[3] Enabled, 6.0 Gb/s
ID Vendor Model FW Size
00.0 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.1 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.2 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.3 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.4 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.5 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.6 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.7 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.8 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.9 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.10: NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.11: NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
01.0 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.1 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.2 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.3 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.4 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.5 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.6 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.7 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.8 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.12: NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
Shelf 0: DS2126 Firmware rev. IOM6E A: 0172 IOM6E B: 0172
Shelf ?: unsupported DS4243, IOM3
slot 0: SAS Host Adapter 0b (PMC-Sierra PM8001 rev. C, SAS, <UP>)
Firmware rev: 01.12.09.00
Base WWN: 5:00a098:00659db:b4
Phy State: [4] Enabled, 3.0 Gb/s
[5] Enabled, 3.0 Gb/s
[6] Enabled, 3.0 Gb/s
[7] Enabled, 3.0 Gb/s
QSFP Vendor: Molex Inc.
QSFP Part Number: 112-00177+A0
QSFP Type: Passive Copper 2m ID:01
QSFP Serial Number: 326020990
ID Vendor Model FW Size
00.0 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.1 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.2 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.3 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.4 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.5 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.6 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.7 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.8 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.9 : NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.10: NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
00.11: NETAPP X487_SLTNG600A10 NA02 560.0GB (1147307696 520B/sect)
01.0 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.1 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.2 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.3 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.4 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.5 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.6 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.7 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.8 : NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
01.12: NETAPP X315_SMEGA04TA07 NA00 3807.8GB (7814037168 520B/sect) (Failed)
Shelf 0: DS2126 Firmware rev. IOM6E A: 0172 IOM6E B: 0172
Shelf ?: unsupported DS4243, IOM3
slot 0: Intel USB EHCI Adapter u0a (0xdf301000)
boot0 Micron Technology 0x655, class 0/0, rev 2.00/11.10, addr 2 1936MB 512B/sect (devproto=0x00)
What is the procedure for graceful shutdown and power up of a storage system during scheduled power outage?
https://kb.netapp.com/app/answers/answer_view/a_id/1003836
Note: If you are unable to view the entire content of this article please log in to kb.netapp.com
Top 10 Disk Issues and Solutions
https://kb.netapp.com/app/answers/answer_view/a_id/1002671
Note: If you are unable to view the entire content of this article please log in to kb.netapp.com
How to identify a broken or defective disk.
https://kb.netapp.com/app/answers/answer_view/a_id/1035597
Note: If you are unable to view the entire content of this article please log in to kb.netapp.com
Is it possible to run IP Metrocluster in Asynchronous mode?
I want to be able to live vMotion my VMs (not disks) to another site with asynchronously replicated storage with 15ms latency.
Hi guys.
I have some few question about upgrading ONTAP Firmware on FAS8040 platform. (now using Clusted ONTAP 8.3.2)
when i selecting the FAS8040 on the NetApp Support System Firmware & Diagnostics Download page i can see BIOS FW 9.6. is this ONTAP 9.6?
And can i upgrade one way to ONTAP 8.3.2 to ONTAP 9.6?
ONTAP 8.3.2 -> ONTAP 9.1 -> ONTAP 9.6 = correct ?
ONTAP 8.3.2 -> ONTAP 9.6 = corecct ?
give me something best practice guide book please thx.
regards.
Hello All,
Quick question. Is there a way within my ONTAP 9.3 environment to see if there are a certain set of Volumes/LUNS that have been historically "idle" on my array.
My goal is to see what volumes/LUNS I can go to the end-user on and say "hey, since you don't use these, we are taking them and re-allocating".
Thanks in advance!
Hi,
I would like to know if Aggregate level deduplication will be available for disk based aggregates, as opposed to AFF systems.
Thanks
Henry
We have a cluster that is running OnTap 9.6 P2 and we have DNS servers configured:
Oriole::> dns show
Name
Vserver Domains Servers
--------------- ----------------------------------- ----------------
Oriole omni.domain.com xxx.yyy.zzz.252,
xxx.yyy.zzz.253
oriole-svm omni.domain.com xxx.yyy.zzz.252,
xxx.yyy.zzz.253
2 entries were displayed.
Oriole::>We didn't realize that the cluster was configured to lookup server names, so we would run this command below before adding a server to an export policy:
Oriole::> vserver services dns hosts create -vserver oriole-svm -address 172.22.15.6 -hostname servername
When I run "dns hosts show" I see lots of entries and have a couple of questions:
1) Why would there be entries in this list for servers that do not currently (nor have ever had) an entry in our domain DNS? In the example below, that is an entry for the MPLS router at a remote office that has no entry on our DNS servers nor did we manually add it to the cluster.
Vserver Address Hostname Aliases ---------- -------------- --------------- ---------------------- oriole-svm xxx.yyy.zzz.114 mpls-rv-cl_side -
2) Why are there entries in this list that have both a "hostname" and an "Alias" when we always just added devices with a hostname? Is the cluster populating the alias field of a matching hostname based on what it finds on the DNS servers (in the code below, only the "hostname" was added to the cluster via the command above; how did the alias get populated)?
Oriole::> dns hosts show Vserver Address Hostname Aliases ---------- -------------- --------------- ---------------------- oriole-svm xxx.yyy.zzz.134 app02 app02.domain.com
3) Is there a way to automatically purge entries from the host list of servers that don't have entries in our domain DNS?