I thought it was per HA-pair since those are the ones actually talking to the disks. Someone can certainly correct me on that....but on the surface, that sounds incorrect (ACP the same across 4 nodes, not a HA pair)
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at TMACsRack https://tmacsrack.wordpress.com/*
On Fri, Apr 14, 2017 at 1:30 PM, Alexander Griesser <AGriesser@anexia-it.com
wrote:
Yah, I’d love to stay with OOB if possible, but AFAIK, you’re not allowed to mix ACP modes within a 4-node cluster f.ex. and I have to add a pair of AFF-A300s to this existing 2-node cluster and they do not have OOB-ACP anymore :-/
Will try to revert on the second controller, let’s see if that helps. Can’t hurt.
*Alexander Griesser*
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@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:* Freitag, 14. April 2017 19:28
*An:* Alexander Griesser AGriesser@anexia-it.com *Cc:* toasters@teaparty.net *Betreff:* Re: Switching to ACP inband connectivity
Well, thats a bummer!
I was fooling around on 9.0. The shipping version for ACP was 2.09, I was able to go back.
I would say...don't spend a lot of time with it. Your best bet is to simply leave ACP out-of-band.
I was not at all successful in doing anything until I got the FW back to 2.09.
I guess you could try running the "storage download acp –R" on both nodes to make sure?
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at **TMACsRack https://tmacsrack.wordpress.com/*
On Fri, Apr 14, 2017 at 12:56 PM, Alexander Griesser < AGriesser@anexia-it.com> wrote:
The thing is, they wanted to close the issue already telling me to subscribe to the BURT and get the info from there once it’s solved.
Anyways, I talked with support on the phone and he was reading your instructions down there and said that we should try that.
I’m not really sure how to downgrade ACP to a specific version, I’ve downloaded 2.09 and installed it, but it’s not really using it for the installation.
What I can do is I can revert to the version shipped with Ontap 9.1P2, which is what I did now by running:
storage download acp –R
but it did only install FW 2.10 again, but afterwards, it looked like this:
Node Module Name State
nodeA 1.22.B firmware-update-required
1.22.A firmware-update-required 2.11.A active 2.11.B firmware-update-required 2.14.B active 2.14.A active 2.12.A active 2.12.B firmware-update-required 2.13.A active 2.13.B firmware-update-required 1.21.B active 1.21.A activenodeB 1.22.B firmware-update-required
1.22.A firmware-update-required 2.11.A active 2.11.B firmware-update-required 2.14.B active 2.14.A active 2.12.A active 2.12.B firmware-update-required 2.13.A active 2.13.B firmware-update-required 1.21.B active 1.21.A active24 entries were displayed.
So I thought let’s do this again and it will fix the other half of the ACPs too, but it didn’t.
But at least half of them are fixed now J
Best,
*Alexander Griesser*
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@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:* toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] *Im Auftrag von *Alexander Griesser *Gesendet:* Samstag, 8. April 2017 19:20 *An:* tmac tmacmd@gmail.com *Cc:* toasters@teaparty.net *Betreff:* AW: Switching to ACP inband connectivity
Yah, no worries, I have time and endurance for things like that J No rush here on my end.
*Alexander Griesser*
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@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 tmacmd@gmail.com] *Gesendet:* Samstag, 8. April 2017 19:17 *An:* Alexander Griesser AGriesser@anexia-it.com *Cc:* toasters@teaparty.net *Betreff:* Re: Switching to ACP inband connectivity
Yep. internal burt, but a burt none the less. save them from digging it up.
Let us know how you make out. I was under a crunch putting a system into production and could not fool around with it any more.
Thanks
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at **TMACsRack https://tmacsrack.wordpress.com/*
On Sat, Apr 8, 2017 at 12:29 PM, Alexander Griesser < AGriesser@anexia-it.com> wrote:
Alright, thanks – I’m opening a case now, cannot see the details of the BURT, though, but will refer support to it.
Best,
*Alexander Griesser*
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@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:
- Open a support case with netapp and refer to the BURT 1050364 / Case
2006580487
- 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 #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at **TMACsRack https://tmacsrack.wordpress.com/*
[ stripping my own post due to size limitations on this mailing list ]