toasters July 2023

toasters@lists.teaparty.net

6 participants
4 discussions

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

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 July 2023