Product Support Notice

Transcription

1 PSN # PSN005154u Product Support Notice 2018 Avaya Inc. All Rights Reserved. Original publication date: 23 March This is Issue #02, published date: 13 April Severity/risk level High Urgency Immediately Name of problem Pod Fx (CPOD) New HP_Firmware_PodFx_31_2.zip file Products affected Pod Fx 3.0.2, Pod Fx 3.1 Problem description In order to keep up with the latest updates provided by Hewlett Packard, a new firmware zip package is being published to supersede the existing HP_Firmware_PodFx_31.zip file under the Avaya Pod Fx v3.1 software line up. This new firmware package contains the following updates and fixes: New HP SSP custom ISO image built from release Unconnected Fibre Channel Port Reported As "Degraded" in ilo 4 System Information Page. Missing HPE Broadcom tg3 Ethernet driver from the 3.1 software line up content when upgrading 2400 Pods to Pod Fx 3.1. Missing procedure to update the HPE Broadcom tg3 Ethernet card on HP Gen 9 servers in 2400 Pods in existing Pod Fx 3.1documentation. Updated driver for the HPE Broadcom Qlogic Ethernet cards. Resolution For 4200 and 2400 Pods with HP Gen 8 and Gen 9 servers, as part of the infrastructure upgrade, when going from CPOD 2.x.x Pod Fx 3.0.x to Pod Fx 3.1 to upgrade the compute server firmware, users should use the bp-avaya-dl360g9-g8-spp ISO image that comes with the new firmware zip package available at support.avaya.com under the Avaya Pod fx v3.1 software line up. For 4200 Pods with VSP 7200 switches, as part of the infrastructure upgrade, when going from Pod Fx 3.0.x to Pod Fx 3.1 to upgrade the HPE Broadcom Qlogic Ethernet driver, users should use the new QLG-bnx-6.0-offline_bundle zip file that comes with the new firmware zip package available at support.avaya.com under the Avaya Pod fx v3.1 software line up. For 4200 legacy Pods with VSP 7028XLS and VSP 4850 switches and 2400 Pods with HP Gen 8 and Gen 9 servers, as part of the infrastructure upgrade, when going from CPOD 2.x.x Pod Fx 3.0.x to Pod Fx 3.1 to upgrade the HPE Broadcom tg3 Ethernet driver, users should use the nx1_tg l.v60.1-offline_bundle zip file that comes with the new firmware zip package available at support.avaya.com under the Avaya Pod fx v3.1 software line up. As part of the customer advisory published by HPE on March 09, 2018, Document ID: a en_us, it is recommended that you update the HP Agentless Management Service to release or later. Version for VMware vspehre 6.0 was the latest available release at the time this PSN was issued. Users should use the ams-esxi6.0-bundle offline bundle to update the HP ams to release The DL360G9/DL360PG8 Firmware update image contains: Device Information Firmware package release Firmware Version ilo 4 hp-firmware-ilo i386.rpm v2.55 Power Management Controller P89 BIOS (DL380/360G9) P71 BIOS (DL380/360pG8) P420i SMART ARRAY Cntrl (RAID Controller) hp-firmware-powerpic-gen i386.rpm firmware-system-p _2017_10_ i386.rpm hp-firmware-system-p i386.rpm hp-firmware-smartarray-46a4d957a x86_64.rpm v3.3 v /25/ /01/2015 v8.32

2 P440ar SMART ARRAY Cntrl (RAID Controller) HPE QLogic NX2 Online Firmware Upgrade Utility HPE Broadcom NX1 Online Firmware Upgrade Utility firmware-smartarray-ea3138d8e x86_64.rpm firmware-nic-qlogic-nx x86_64 firmware-nic-broadcom x86_64.rpm v6.06 v / v / Workaround or alternative remediation Remarks Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Execute PSN with one host at a time during an approved maintenance windows. Download PLDS Download ID: CPOD Patch install instructions Using the new HP SPP ISO image to upgrade server compute firmware. Service-interrupting? No 1. From support.avaya.com, download the new HP_Firmware_PodFx_v31-2.zip package and transfer it to the MSC VM. 2. Unzip the firmware package file. 3. Follow the existing procedure documented in the latest Using the Management Server Console for Avaya Pod Fx document for release 3.1 to boot up each ESXi host using the new bp-avaya- DL360G9-G8-SPP iso image. 4. When upgrading HP Gen 9 compute servers, the automatic firmware update version will be auto selected. No user intervention is needed at this point.

3 5. When upgrading HP Gen 8 compute servers, the interactive mode will be the default setting regardless that the Automatic firmware update version is being shown as highlighted in the console screen. a. Press the space bar to interrupt automatic selection. b. Use the Down arrow key to select Interactive Firmware Update version. c. Press the Up arrow key to select Automatic firmware Update Version. d. Press Enter. No further user intervention is required at this point. The automatic update process starts. Driver Updates Driver Updates for Pods with Release 3.1 software Note: For Pod Fx move to the next section. Using vsphere Update Manager to update: - HP Agent Management server - HP Broadcom Qlogic Ethernet card - HP Broadcom tg3 Ethernet card 1. If not yet installed, follow the existing procedure documented in the latest Using the Management Server Console for Avaya Pod Fx document for release 3.1 to install vsphere Update Manager. 2. Log in to vcenter by using the Administrator credentials. 3. On the menu, click Home> Solutions and Applications> Update Manager.

4 4. Click the Patch Repository tab. For Pods with HP Gen 9 servers using 10 Gib network cards: a) Click Import Patches. b) Browse to the location where the new firmware package was unzipped. c) Select the ams-esxi6.0-bundle zip file and select Open. d) Click Next. e) Click Finish to import the bundle to your repository. f) Repeat Steps a. to e. to import the QLG-bnx-6.0-offline_bundle zip file to your repository. For HP Gen8 servers & HP Gen9 servers using 1 GB network cards: a) Click Import Patches. b) Browse to the location where the new firmware package was unzipped. c) Select the ams-esxi6.0-bundle zip file and select Open. d) Click Next. e) Click Finish to import the bundle to your repository. f) Repeat Steps a. to e. to import the nx1_tg l.v60.1-offline_bundle zip file to your repository. 5. Click the Baselines and Groups tab. 6. Click Create to create a new Baseline. For Pod with HP Gen 9 servers using 10 Gib network cards: a) Name: Avaya Pod Fx 3.1- HPE Updates. b) Description: HPE Patches for Pod Fx 3.1 baseline. c) Click Hosts Patch. d) Click Next. e) Click Fixed. f) Click Next. g) Press the CTRL key and select the following patches to include: bnx2 driver for ESX bnx2fc driver for ESX bnx2i driver for ESX bnx2x driver for ESX ESXi Agentless Management Service Bundle h) Move the selected patches to the fixed patches to add list.

5 i) Click Next. j) Expand the Patches list to validate the selections. k) Click Finish to create a new baseline. For HP Gen 8 servers & HP Gen 9 servers using 1 Gib network cards: a) Name: Avaya Pod Fx 3.1- HPE Updates. b) Description: HPE Patches for Pod Fx 3.1 baseline. c) Click Hosts Patch. d) Click Next. e) Click Fixed. f) Click Next. g) Press the CTRL key and select the following patches to include: ESXi Agentless Management Service Bundle NetXtreme Broadcom Network Driver set [nx1_tg v60.1] h) Click Next. i) Expand the Patches list to validate the selections.

6 j) Click Finish to create the new baseline. 7. Click Compliance View in the upper-right corner to go back to the Hosts and Cluster view. 8. Select the first host from the cluster. 9. Click the Update Manager tab. 10. Click Attach. 11. Select the newly created baseline: HPE Patches for Pod Fx 3.1 baseline 12. Click Attach. 13. Select scan. 14. Validate that the check mark is with Patches and extensions only. 15. Select Scan. Host is ready to be remediated. Warning: Ensure the compute servers have been upgraded to ESXi 6.0 update 3 before continuing. Note: This new baseline can also be used at the same time with the existing VMware ESXi 6.0 Patches when remediating the hosts to avoid having to reboot each server twice, once for the ESXi patches and once for the HPE patches. 16. Click Remediate to install patches to the select hosts. This activity must only be conducted during an approved maintenance windows. Proceed with one server at a time. 17. Repeat Steps 8 to 17 with the remaining hosts. Driver Updates for Pods with Release software Using the vsphere command-line interface to update: - HP Agent Management server - HP Broadcom Qlogic Ethernet card - HP Broadcom tg3 Ethernet card Warning: Ensure the compute servers have been upgraded to ESXi 6.0 update 3 before continuing. Note: Validate you can access to each server s ilo remote console. For Pods with HP Gen9 servers using 10 Gib network cards: 1. Log in to vcenter using the Administrator credentials. 2. From the Hosts and Clusters view, select the first host within the cluster and place it in

7 maintenance mode. 3. Using winscp, connect to the ESXi host in maintenance mode using the root credentials and transfer the nx1_tg l.v60.1-offline_bundle zip & ams-esxi6.0-bundle zip file to /var/log/vmware. 4. With Putty, SSH to the ESXi hosts in maintenance mode using the root credentials. 5. Move to the location where the offline bundle was transferred to: cd /var/log/vmware 6. Execute the following commands to apply updates: - esxcli software vib update d nx1_tg l.v60.1-offline_bundle zip - esxcli software vib update d ams-esxi6.0-bundle zip - reboot 7. Optional: Follow boot up process from the ilo remote console. 8. From the Hosts and Clusters view, select the host from Step 2 and exit it out of maintenance mode once it gets connected to the cluster. 9. Proceed with remaining hosts repeating Steps from 2 to 7. Always perform the drivers update with one host at a time. 10. Driver validation: From the ESXi command-line interface esxcli software vib list grep amsd esxcli software vib list grep net-bnx2x For HP Gen 8 servers & HP Gen 9 servers using 1 Gib network cards: 1. Log in to vcenter using the Administrator credentials. 2. From the Hosts and Clusters view, select the first host within the cluster and place it into maintenance mode. 3. Using winscp, connect to the ESXi host in maintenance mode using the root credentials and transfer the QLG-bnx-6.0-offline_bundle zip & ams-esxi6.0-bundle zip file to /var/log/vmware. 4. With Putty, SSH to the ESXi hosts in maintenance mode using the root credentials. 5. Move to the location where the offline bundle was transferred to: cd /var/log/vmware 6. Execute the following commands to apply updates: - esxcli software vib update d QLG-bnx-6.0-offline_bundle zip - esxcli software vib update d ams-esxi6.0-bundle zip - reboot 7. Optional: Follow the boot up process from the ilo remote console. 8. From the Hosts and Clusters view, select the host from Step 2 and exit it out of maintenance mode once it gets connected to the cluster. 9. Proceed with remaining hosts repeating Steps 2 to 7. Always perform updates with one host at a time to avoid performance impacts. 10. Driver validation: From the ESXi command-line interface

8 esxcli software vib list grep amsd esxcli software vib list grep net-bnx2x Verification Failure Patch uninstall instructions Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks Avaya Security Vulnerability Classification Not Susceptible Mitigation If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use. Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED AS IS. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS AVAYA ), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.