radiant escarp
we have been getting this for a while now on our A700 systems (even with 9.15.1). Can someone who knows how to write shell scripts maybe fix that update script? 😂
I mean I know there is a workaround (setting a bootloader variable to skip the update) but this should be simple enough to fix so that it doesn't need any workarounds ...
nimble ferry
Just curious. What’s the “sysconfig -ac”? What nic cats are in there trying to be updated?
radiant escarp
this is the 4-port RJ45 one:
a700cl2::*> node run -node n1 sysconfig -ac
sysconfig: slot 1 OK: X91143A: Qlogic EP8324 Quad-Port 16Gb FC/10GbE PCIe CNA
sysconfig: slot 2 OK: X91143A: Qlogic EP8324 Quad-Port 16Gb FC/10GbE PCIe CNA
sysconfig: slot 3 OK: X91120A: quad-port 10G
sysconfig: slot 4 OK: X91440A: 40G high performance
sysconfig: slot 5 OK: X91143A: Qlogic EP8324 Quad-Port 16Gb FC/10GbE PCIe CNA
sysconfig: slot 6 OK: X93140A: NetApp NVRAM10
sysconfig: slot 8 OK: X91440A: 40G high performance
sysconfig: slot 9 OK: X92071A: PMC PM8072; PCI-E quad-port SAS (PM8072)
sysconfig: slot 10 OK: X91143A: Qlogic EP8324 Quad-Port 16Gb FC/10GbE PCIe CNA
sysconfig: No shelf configuration errors detected.
sysconfig: There are no configuration errors.
this is the current FW for the adapter in question:
a700cl2::*> node run -node n1 sysconfig -av 3
slot 3: 1/10 Gigabit Ethernet Controller IX4-T
e3d MAC Address: 00:a0:98:cc:22:c5 (auto-unknown-fd-down)
e3c MAC Address: 00:a0:98:cc:22:c4 (auto-unknown-fd-down)
e3b MAC Address: 00:a0:98:cc:22:c3 (auto-unknown-fd-down)
e3a MAC Address: 00:a0:98:cc:22:c2 (auto-1000t-fd-up)
Device Type: X550(0x1563) (BSD99) rev1
Firmware Version: 1.0-96.21 etid 800004c0
Part Number: 111-02399
Hardware Revision: A1
Serial Number: 031731000836
root cause(?) seems to be this:
netapp_intel_fw_helper: D1563-S1-P45 etid 800004c0 needs to update FW using D1563-S1-P45_P62-80001154.cfg
D1563-S1-P64-8000174D.cfg for location 0:24 0:23.
cp: /platform/etc/nic//D1563-S1-P45_P62-80001154.cfg
D1563-S1-P64-8000174D.cfg: No such file or directory
Note that it says:
needs to update FW using foo.cfg bar.cfg for location ...
There are two filenames in there. Whatever the script uses to determine the config file name to apply, it looks like it gets 2 values back (the P45_62 one and the P64 one) where it expects only one. This is why the copy fails and everything else after that.
For example the intel fw update binary needs a single filename after -c and it gets two file names, i.e. -c foo.cfg bar.cfg and that is why it spits out "Bad command line parameter" for the (second) file name
it's hard to debug since I cannot simply edit /etc/netapp_intel_fw_helper due to the root fs being read-only
it's nothing critical, and I cannot open a case as these two systems are from our test lab (without support) but I thought I'd bring it up anyways