toasters

toasters@lists.teaparty.net

13514 discussions

The system's root volume does not meet the minimum required size.
by Randy Rue 28 Aug '23

28 Aug '23

Getting this warning in the "Active IQ Suggestions" since our last upgrade. It has a link under Corrective Action that leads to the top of NA's Hardware Universe site. The root volumes for our three vservers are all only 0% or 1% used (1GB each). But the "vol0" volumes show: scarab::> vol show Vserver Volume Aggregate State Type Size Available Used% --------- ------------ ------------ ---------- ---- ---------- ---------- ----- scarab-a vol0 aggr0_scarab_01 online RW 151.3GB 78.82GB 45% scarab-b vol0 aggr0_scarab_02 online RW 124.6GB 61.74GB 47% I think I recall trying to resize a node's root volume from the CLI in the past and getting an error along the lines of "don't mess with this volume."

2 1

fg.space.member.nearlyFull: Constituent 1317 in FlexGroup
by Randy Rue 28 Aug '23

28 Aug '23

Getting this error in Events for several flexgroups. I've familiarized myself with checking for FlexGroup imbalances in System Manager and from the CLI. Since upgrading to 9.13.1 I see there are options in SM and the CLI to "rebalance" an FG. But launching a rebalance never seems to finish. The default is to give it six hours before timing out. It then gives up with no work done. Right now I'm running it on a ~8TB FG with 12 Constituent Volumes, ranging from 122GiB to 2.44TiB in size. It's been running for over two weeks now and it's still "Scanning" with 0 bytes moved. I think I gave it 60 days. Imbalance Percentage: 43% Moved Data Size: - Maximum Constituent Imbalance Percentage: 344% Rebalance Start Time: Thu Aug 10 12:30:37 2023 Rebalance Stop Time: - Rebalance Runtime: 428h12m10s Rebalance Maximum Runtime: 1440h0m0s Maximum Imbalance Threshold per Constituent: 20% Minimum Imbalance Threshold per Constituent: 5% Maximum Concurrent File Moves per Constituent: 25 Minimum File Size: 100MB Exclude Files Stuck in Snapshot Copies: true scarab::> Is this new "rebalance" feature just vaporware?

1 0

Multiple SRA (OTV) / SRM instances per vSphere
by Chris Hague 28 Jul '23

28 Jul '23

Following a change which took place to upgrade NetApp OTV to 9.12, we experienced issues with our "many to one" SRM setup which is in place for various migrations. Effectively it will now only run in a "one to one" setup. This worked before. But now it seems that only the last OTV you register will work, overwriting the previous one. (We need to upgrade OTV to 9.12 in order to support bringing our clusters ONTAP versions to 9.12 so there is no option to rollback). NetApp support have directed us to this KB: Storage Replication Adapter: How to configure SRA in a SRM Shared Recovery Site - NetApp Knowledge Base<https://kb.netapp.com/mgmt/OTV/SRA/Storage_Replication_Adapter%3A_How_to_co…> Which suggests that to support this configuration the 2nd OTV needs to be run in VCF mode. However, in the guide for configuring VCF: VMware Cloud Foundation mode of deployment for ONTAP tools (netapp.com)<https://docs.netapp.com/us-en/ontap-tools-vmware-vsphere/deploy/vmware_clou…> It states: "You can only work with vVols datastores in the VCF deployment mode." We are using NFS datastores, not vVols. Does anyone have experience of this set up? Will it work as they have suggested? Or is there another way to register multiple OTV's to the one VC? TIA Chris. This email is being sent by a subsidiary of the Arthur J. Gallagher & Co. global group of companies. For details of the registered office, company number and, where applicable, regulated status of our subsidiaries, please visit https://www.ajg.com/uk/legal-and-regulatory-information. Your account executive will make clear at the beginning of the relationship which entity is providing services to you, or please refer to your Terms of Business Agreement. For information on how we use your personal data and how you may exercise your rights in respect of that information, please refer to our Privacy Notice https://www.ajg.com/uk/privacy-policy/. If you are providing us with personal data of another individual, you must tell them you are providing this to us and show them a copy of this notice. Please contact me if you do not want to receive direct marketing information from us. This e-mail and any attachments are CONFIDENTIAL and may contain legally privileged information. If you are not the intended recipient of this e-mail message, please telephone or e-mail us immediately, delete this message and do not copy, distribute or use the information in this message or any attachments.

1 0

LDAP timeout errors since upgrade to 9.13.1
by Randy Rue 27 Jul '23

27 Jul '23

Hi All, Since upgrading to 9.13.1 our AFF/FAS on-premise cluster has an alert in the System Manager dashboard and shows us receiving these errors every hour or two: secd.ldap.noServers: None of the LDAP servers configured for Vserver (vfiler_name) are currently accessible via the network for LDAP service type (Service: LDAP (Active Directory), Operation: SiteDiscovery). We run a redundant pair of slapd LDAP servers presented via an F5 BigIP at a single IP. The SVMs LDAP settings include of a list of the F5's highly available IP and then the two back end servers. Nothing has changed with our LDAP service. The LDAP servers don't seem to be distressed and no other systems/services that touch our LDAP are complaining. Our NetApp SVMs don't seem to be dropping or bouncing any filer traffic. Has anything changed from 9.9 to 9.13 in the way ONTAP talks to LDAP? Is it chattier? More sensitive to lags? Randy

2 4

Microsoft CVE-2022-38023 and NTLMv2
by Randy Rue 17 Jul '23

17 Jul '23

Hello All, We've upgraded our AFF-A220 to 9.13.1 as per https://kb.netapp.com/Support_Bulletins/Customer_Bulletins/SU530 and should be all good to go for next Tuesday's closing of the door on NTLMv2 authentication. However, scrb::> vserver cifs session show -vserver sdata -fields auth-mechanism,address,windows-user node vserver session-id connection-id address auth-mechanism windows-user -------- ---------- -------------------- ------------- --------------- -------------- ------------ scrb-a sdata 12223613813613660030 4271015427 10.6.154.156 NTLMv2 FHC\rgrasdue still shows all of our CIFS connections using NTLMv2 to authenticate (one line is shown of hundreds of connections) Are we ready for next week's update? Will the auth-mechanism change after we patch our DCs? Or will all our CIFS connections break? Let u s know, Randy Rue

3 3

Re: Strange errors when inserting used X302A-R5 BSAS disk into DS4246 shelf
by John Stoffel 08 Jul '23

08 Jul '23

>>>>> "Florian" == Florian Schmid via Toasters <toasters(a)teaparty.net> writes: > we have an old NetApp dev cluster containing a pair of FAS 8060 > nodes and several DS4246 shelves with 1TB X302A-R5 BSAS disk. Those are rock solid heads for sure! I've still got a pair in production here. > I have replaced several disks already over the last years and never > had issues to do so, but this time, I have tried 2 disks and both > have reported the same strange issues on this shelf port. The port > of the shelf I would think, is fine, because NetApp has reported a > broken spare disk on this port, but nothing special. How many shelves do you have? And have you tried putting the disk into a different slot? And when you say "broken spare disk on this port" are you talking about the SAS port on the disk shelf, or about the disk slot in the disk shelf? > When I look on NetApp site, I don't find a real solution here, so I > hope someone of you can help me here? > This errors I'm getting: > 2/14/2023 18:24:45 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(9997). > 2/14/2023 18:22:06 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:20:01 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:19:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:17:56 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:16:06 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:15:51 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:14:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:13:46 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:11:41 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:09:36 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:09:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:07:31 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:05:26 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:04:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > 2/14/2023 18:03:21 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). > disk show -disk 2.11.10 > There are no entries matching your query. This strongly implies to me that the physical slot in the disk shelf is going bad, or has a bad connector. Or that you just got a bad disk from the vendor. I'd have them replace it with a known good one. If you have another spare disk working in the system, I'd move it to this slot and see what happens. And of course move the un-recognized disk there to check whether it's the shelf disk slot, or the disk itself is bad. > The disk is not recognized and NetApp is throwing this errors... > Both disks have been bought from a known second hand shop, where we > never had issues in the past with "used" parts. Bad disks happen. > We are running 9.7 on the cluster with a relatively new disk > qualification package. I would also say, that those old disks > haven't got any firmware updates for the last 3 years or so... We're still running 9.3... ugh.

3 3

Strange errors when inserting used X302A-R5 BSAS disk into DS4246 shelf
by Florian Schmid 17 Feb '23

17 Feb '23

Hi, we have an old NetApp dev cluster containing a pair of FAS 8060 nodes and several DS4246 shelves with 1TB X302A-R5 BSAS disk. I have replaced several disks already over the last years and never had issues to do so, but this time, I have tried 2 disks and both have reported the same strange issues on this shelf port. The port of the shelf I would think, is fine, because NetApp has reported a broken spare disk on this port, but nothing special. When I look on NetApp site, I don't find a real solution here, so I hope someone of you can help me here? This errors I'm getting: 2/14/2023 18:24:45 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(9997). 2/14/2023 18:22:06 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:20:01 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:19:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:17:56 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:16:06 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:15:51 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:14:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:13:46 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:11:41 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:09:36 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:09:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:07:31 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:05:26 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:04:01 node-01 ERROR scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). 2/14/2023 18:03:21 node-02 ERROR scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request - (0x5 - 0x20 0x0 0x0)(0). disk show -disk 2.11.10 There are no entries matching your query. The disk is not recognized and NetApp is throwing this errors... Both disks have been bought from a known second hand shop, where we never had issues in the past with "used" parts. We are running 9.7 on the cluster with a relatively new disk qualification package. I would also say, that those old disks haven't got any firmware updates for the last 3 years or so... Thank you very much in advance. Best regards, Florian

1 0

Service-Policies does not restrict SSH...
by Heino Walther 05 Jan '23

05 Jan '23

Hi there I am trying to restrict which IP addresses can reach the SSH port on the default cluster management interface… I first cloned the default-management service-policy to a new policy… I then restrict the service “management-ssh” to a specific range, say 10.0.2.0/24 I then modify the cluster lif and the two node management interfaces, so that they use my new service-policy. But… I am still able to ssh into the system from 10.10.10.0/24… which makes no sense at all… If I do the same to the management-https it _does_ work as expected… The “old” firewall is enabled, and all policies are set to 0.0.0.0/0 (I think this old firewall is depreciated… ) So it there something specific about ssh? (ONTAP 9.12.1) Personally I think the “firewall” features are a mess on ONTAP at the moment… also the fact that you can only open up for IP ranges, and not specific IP addresses… so the “best” you can do is /30 I guess? Why not just allow specific IP or even ranges.. like 10.10.10.5, 10.10.10.5-10, and 10.10.20.0/24 Any help or input is appreciated 😊 /H

2 1

Two node MetroCluster performance issues?
by Heino Walther 21 Dec '22

21 Dec '22

Hi there I have a setup with a two node Fabric MetroCluster with A300 nodes and four Brocade 6510 switches places about 10KM from each other. Our ESXi 7.0 hosts connects via 16G FC using another four frontend Brocade 6510 switches. Our ESXi hosts can see four paths for each LUN they are presented from the SVMs. ESXi show all four paths as Active (I/O) which I find a bit odd, because two of the paths are remote to the ESXi hosts… Both the ESXi and the igroup on the NetApp is configured for ALUA… but I have googled that there can be issues with this, and maybe we have those issues… The main issue is that if we do a few performance tests across different datastores (local and remote to the ESXi host), we see OK performance for the local datastores (800+MB/sec.) but if we try to test against a datastore that is remote to the ESXi host we see 50-60MB/sec. which is a huge difference and leads us to question the setup… We are aware that especially writing to a remote datastore will involve a transfer to the remote controller (10KM) this controller then has to write this to it’s peer (remote) controller (10KM) the remote peer than has to send an ack. back to the peer (10KM) which then sends an ack. to the ESXi host (10KM) so all in all 40KM plus waiting for the systems… it is not ideal, but is this kind of performance normal? The two nodes does have an ethernet based cluster interconnect which is currently linked at 1Gb, and I am beginning to suspect that the data between the two nodes is going via this link? But the more I think about it, the more it does not make sense? Our FC interswitch links are running 8Gb, but on the switches we see nothing near saturation of any ports… and we of cause also checked for port errors of any kind… If anyone has a similar setup, any help would be great… we are doing a few more tests, but we are close to opening a case with NetApp… /B

2 1

Migration to DS4486 shelf?
by Heino Walther 05 Dec '22

05 Dec '22

Hi there Because of space constraints I am planning to move my 3 pcs. DS212C into a DS4486. But I have a few questions 😊 My existing disks are X318 (8TB NL-SAS), and I think the caddies for the DS4486 are also SAS, so that should technically fit? Does the NetApp see 24 or 48 disks from the DS4486? Because I plan to reuse existing disks with aggregates on them… I can see the DS4486 use special PN as spare disks because the caddy has two disks installed. How does NetApp handle the replacement when one disk of the two dies? I know the healthy disk is also copied to a spare before you can replace the caddy, but do you then replace both disks, or do you just replace the broken disk of the two? I also have plans on replacing the IOM6 modules with IOM12 just as you can in the DS4246 shelfs.. any issues with that? I know this is close if not far beyond what is supported 😉 /Heino Heino Walther<https://www.linkedin.com/in/heinowalther/> Beardmann ApS<http://beardmann.dk/> Jellingvej 9 - 7100 Vejle<https://goo.gl/maps/xQVPFMHXpXu> D: 7199 9060 M: 2075 7501

4 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters