#Hi all I have a question about the a

1 messages · Page 1 of 1 (latest)

iron vapor
#

firmware_type: service-processor for SP firmware upgrade.

earnest heath
#

Hallo @iron vapor thank you for your reply. With that the upgrade will be directly started or it will take some time, like when you upload the zip over the system manager?

iron vapor
#

na_ontap_firmware_upgrade will help download the SP firmware package but to make the update take effect, node reboot is required.

from module doc:

  • Update ONTAP service-prosessor firmware
    • The recommend procedure is to
      1. download the firmware package from the NetApp Support site
      2. copy the package to a web server
      3. download the package from the web server using this module
    • Once a disk qualification, disk, shelf, or ACP firmware package is downloaded, ONTAP will automatically update the related resources in background.
    • It may take some time to complete.
    • For service processor, the update requires a node reboot to take effect.

playbook to download SP firmware from web server

  • name: sp firmware download on node node1
    na_ontap_firmware_upgrade:
    state: present
    package_url: "{{ web_server }}/308-03917_A0-AFF_FAS80XX_3.9_SP_FW.zip"
    # package: 308-03917_A0-AFF_FAS80XX_3.9_SP_FW.zip
    firmware_type: service-processor
    node: node1
    hostname: "{{ hostname }}"
    username: "{{ username }}"
    password: "{{ password }}"
    https: true
    validate_certs: false
earnest heath
#

Hmm the SP was updated without a node reboot

#

So that means the only way to enforce the SP Upgrade without waiting around 30min would be to reboot a node

pearl agate
#

only the SP needs to reboot, obviously... sometimes one has to reboot the SP in advance to get it to update... sometimes you just give up and hope the next OS release and SP firmware release will update

tranquil pagoda
#

The preferred way is to let ONTAP decide when to do the upgrade. It will try to make it as less disruptive as possible. We added some options for force a sp_reboot before and after downloading the firmware. It is actually recommended to reboot the SP before upgrading.

Doing an ONTAP node reboot will also force a firmware upgrade, but that's generally the less preferred way.

earnest heath
#

Ah ok, then we will loop through the nodes to get the right FW version and the let ONTAP upgrade the SP when its good

gaunt lily
#

na_ontap_voolume size_change_threshold - can someone explain what this does? it seems to say that if the size requested is less than the threshold value percentage, nothing is done. However, if it is met sometimes the new volume size is smaller than before.