Alright, thanks – I’ve openend a case (#2006815752) now, cannot see the details of the BURT, though, but have refered support to it. Will update everyone in here on the outcome!
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: tmac [mailto:tmacmd@gmail.com] Gesendet: Samstag, 8. April 2017 14:05 An: Alexander Griesser AGriesser@anexia-it.com Cc: toasters@teaparty.net Betreff: Re: Switching to ACP inband connectivity
I have seen this! Support was unable to reproduce for me. I will dig up a case number later if you like.
I will give you two options: 1. Open a support case with netapp and refer to the BURT 1050364 / Case 2006580487 2. The ultimate fix that I did was this: -> Downgrade *all* IOM firmware to 2.09. Wait for it to stabilize. -> Convert to in-band. Wait for it to stabilize and confirm IN-Band -> Convert to out-of-band and upgrade to 2.10 firmware. -> Wait for it to stabilize and then convert to out-of-band
I got to believe there may be some race condition where the 2.08 -> 2.10 firmware is not completing 100%. If you use the out-of-band, all looks ok, but switch to in-band and not so much.
The thought is something special happens on 2.09 that fixes everything allowing the upgrade to 2.10
If possible, please open a case and refer to the data above. I think it is in everyones best interest NetApp gets to the bottom of this to fix.
Thanks
--tmac
Tim McCarthy, Principal Consultant
Proud Member of the #NetAppATeamhttps://twitter.com/NetAppATeam
I Blog at TMACsRackhttps://tmacsrack.wordpress.com/
[ my initial post stripped due to size limitations on this mailing list… ]