Patch NIC firmware

A script must be executed to fix a problem when StorNext VMs are not recognizing the onboard NIC ports which causes the StorNext networking page on the GUI to not allow configuration of the StorNext IPs. In the screen shot below, the "No data available" notification displays under the Configuration section where fields are supposed to be present for entering network configuration details. This GUI detail is a symptom of not having executed the script described below.

The following must be run on hypervisor node 1 as a root user, after the system is booted and the StorNext VMs are up and running. The script will automatically transfer itself to node 2 and run on that node as well so both StorNext VMs are updated.

  1. Download the autoconfigpatch.sh script from the ProDev FTP site: ftp://prodev@ftp.grassvalley.com/GV-AMS-Express/AMS-39
  2. Place the script in /tmp directory on the AMS Express unit's hypervisor node 1.
  3. Log in to hypervisor node 1 and get root access.
  4. Verify that both StorNext VMs are online by viewing the VM status on the GUI.
  5. Run the patch script on hypervisor node 1 as below.

    [root@d3-hv-n1 /tmp]$ chmod +x /tmp/autoconfigpatch.sh

    [root@d3-hv-n1 /tmp]$ sh /tmp/autoconfigpatch.sh

    Successful run will result in the following messages being displayed:

    Transferring patch script to node 2
    Running patch script on node 2
              Successfully applied patch on node 2
              No autoconfig errors found on node 2
    Running patch script on node 1
              Successfully applied patch on node 1
              No autoconfig errors found on node 1
  6. Proceed to the next task: Configure StorNext Network

Copyright © 2021 - 2022 GVBB Holdings SARL and Grass Valley USA, LLC. All rights reserved. Specifications are subject to change without notice. AMS Express 1.5 gvtp_20220429_09:58:17
Other Topic Library Versions