Product Support Notice

Transcription

1 PSN # PSN003403r2 Product Support Notice 2012 Avaya Inc. All Rights Reserved. Avaya Proprietary Use pursuant to the terms of your signed agreement or company policy. Original publication date: 23-Aug-11. This is Issue 2, published date: 16- Severity/risk level Medium Urgency Optional May-12. Name of problem Avaya Common Server HP DL360 G7 End of Life for 146GB Hard Disk Drive. Products affected Avaya Common Server HP DL360 G7 Avaya Aura SIP Enablement Services (SES): Releases Avaya Aura Communication Manager (CM): Releases and 6.x Application Server 5300 (AS5300) Avaya Aura Messaging: Release 6.x Media Processing Server (MPS) Avaya Aura Session Boarder Controller: Release 6.0.x Multiservice Access Switch (MAS) Midsize Business Template (MBT) Avaya Aura Session Manager: Release 6.x Avaya Aura System Manager: Release 6.x Communication Server 1000 (CS1000) Avaya Agile Communication Environment (ACE) Hospitality Messaging Server 400 (HMS) Voice Portal (Avaya Aura Experience Portal) Avaya one-x Speech Avaya Modular Messaging Proactive Contact Avaya one-x Client Enablement Services Problem description HP has announced End of Life for the 2.5 SAS 146GB 10K RPM Hard Disk Drives (146GB HDD) used in the majority of HP DL360 G7 server configurations sold by Avaya. The last ship date of servers from HP with this HDD is November 30, Resolution Overview Issue 2 of this PSN covers all product server transitions that occurred after the original publication. The 146GB HDD will be replaced by the 2.5 SAS 300GB 10K RPM HDD (300GB HDD) which is being qualified by all Avaya applications impacted by this change. Avaya applications will transition to the 300GB HDD servers in two phases. The first phase will transition to the 300GB HDD by September The remaining Avaya applications will transition to the 300GB HDD by October Actual shipment of the new server configurations from Avaya for both phases depends on existing inventory levels. After qualification, the new configurations will be ordered on a case-by-case basis as existing inventory is sufficiently depleted. In some cases the servers will also transition from a 3x 146GB HDD RAID 5 configuration to a 2x 300GB HDD RAID 1 configuration due to the added capacity of the replacement HDD. In other cases, the number of disk drives and RAID configuration will not change. Since server capacity and functionality are essentially unchanged, none of the server material codes will change regardless of the before and after HDD/RAID configuration. Since material codes will not change, Avaya may have mixed inventory of old and new configurations for any particular product during this transition, and either or both could ship on the same order. In the case of duplicated systems, it is possible and acceptable that one server has146gb HDDs and the other has 300GB HDDs. In general, no product software updates are required to support the new server configurations. However, there may be minor enhancements to optimize RAID status command output or other non-critical functionality. Refer to product specific documentation and release notes for additional information.

2 All HP DL360 G7 servers sold by Avaya will be supported identically through the end of manufacturer support regardless of these hardware variations. Product Server Transitions The server material codes and using applications that have transitioned are shown in Table 1 which also indicates the before and after HDD/RAID configuration. Table 1. Product Server Transitions to 300GB HDD Material ID SAP Description Where Used Application DL360G7 SRVR AA EXPERIENCE PORTAL Voice Portal NORTEL RESERVED AS5300 HP SW EXPERT AC AS5300 AC DL360G7 SRVR 2CPU MID MPS AC DL360G7 SRVR 2CPU MID MAS AC DL360G7 SERVER SESSION MANAGER Session Manager DL360G7 SERVER SES SES NORTEL RESERVED AS5300 HP SW EXPERT DC AS5300 DC DL360G7 SRVR 2CPU MID MPS DC DL360G7 SRVR 2CPU MID MAS DC HDD/RAID configuration 2x 146GB HDD RAID DL360G7 SRVR 1CPU MID BASE One-X speech DL360 MM ONE-X SPEECH SRVR DUAL PT One-X Speech DUAL PT DL360 MM ONE-X SPEECH SRVR QUAD PT One-X Speech Quad PT DL360 MM ONE-X SPEECH SRVR CLUSTER One-X Speech Cluster DL360G7 SRVR 1CPU MID BASE MM MAS DL360 MAS SRVR MM AVSTR MM MAS AVSTR changed to 2x 300GB HDD RAID DL360 MAS SRVR MM EXC/DOMSTR MM MAS EXC/DOMSTR DL360 MAS MM AVSTR SUP/OLA MM MAS AVSTR SUP/OLA DL360 MAS MM EXDOM SUP/OLA/WC/WSO MM MAS EXDOM SUP/OLA/WC/WSO DL360G7 SRVR 1CPU MID Proactive Contact DL360G7 SERVER CM HIGH DUPLEX CM 5.2.1/6.0.1 Duplex DL360G7 SERVER SYSTEM MANAGER System Manager DL360G7 SRVR 2CPU MID ACE (Old) DL360G7 SRVR 1CPU MID CS HMS DL360G7 SERVER CM S/D/MBT/SBC CM 5.2.1/6.0.1 Simplex/Duplex DL360G7 SERVER CM S/D/MBT/SBC MBT DL360G7 SERVER CM S/D/MBT/SBC Session Border Controller Messaging Standard DL360G7 AVAYA ONE-X CES R6.X SRVR One-X CES DL360G7 SRVR ACE ACE (New) 3x 146GB HDD RAID 5 changed to 2x 300GB HDD RAID 1 4x 146GB HDD RAID 5 changed to 3x 300GB HDD RAID Avaya Inc. All Rights Reserved. Page 2

3 FRU Server Transitions The following Field Replaceable Unit (FRU) servers have also transitioned to the 300GB HDD. Table 2. FRU Server Transitions to 300GB HDD Material ID SAP Description Where Used HDD/RAID configuration DL360G7 SRVR 1CPU HI FRU DL360G7 SRVR 2CPU MID DC FRU DL360G7 SRVR 2CPU MID FRU x 146GB HDD RAID 1 changing to 2x 300GB HDD RAID DL360G7 SRVR 1CPU MID FRU HDD FRU The existing 300GB HDD FRU (below) should be used for all HP DL360 G7 Server variations since it can be used to replace failed 146GB or 300GB HDDs. When a failed 146GB HDD is replaced with a 300GB HDD, the 300GB HDD is treated as if it were a 146GB HDD by the RAID array and the same virtual drive size is presented to the operating system. To simplify the logistics of HDD field replacement, Avaya will discontinue the 146GB HDD FRU since it obviously cannot be used for servers with the 300GB HDDs. Material ID FRU Description DL360G7 SRVR 300GB 10K SAS 2.5" HDD Visual Identification of HDD Type The Hard Disk Drives are assessable on the front panel of all HP DL360 G7 Servers and the number and size of HDDs present can be readily determined (there is a label with the HDD type and size on the left front of each drive as shown below). DL360 G7 Server with 3x 2.5 SAS 146 GB HDDs 2012 Avaya Inc. All Rights Reserved. Page 3

4 Further, HP DL360 G7 server configurations shipped from Avaya that have transitioned to the 300GB HDD will have a B suffix added to the Material ID on both the product label that is applied to the server and to the packaging label as pictured below for Communication Manager. This makes it possible to identify the server HDD size before they are unboxed. Sample Communication Manager HP DL360 G7 Server Product label Sample Communication Manager HP DL360 G7 Packaging label Workaround or alternative remediation Remarks Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Download Patch install instructions Verification Service-interrupting? No 2012 Avaya Inc. All Rights Reserved. Page 4

5 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 For additional support, contact your Authorized Service Provider. Depending on your coverage entitlements, additional support may incur charges. Support is provided per your warranty or service contract terms unless otherwise specified. Avaya Support Contact Telephone U.S. Remote Technical Services Enterprise U.S. Remote Technical Services Small Medium Enterprise U.S. Remote Technical Services BusinessPartners for Enterprise Product BusinessPartners for Small Medium Product Please contact your distributor. Canada Caribbean and Latin America Europe, Middle East, and Africa Asia Pacific 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. Avaya Notes 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. Additional information for Tier 3, Tier 4, and development HDD Replacement The HP 146GB 10K SAS HDD (CC ) has gone end-of-life (EOL). Because of the EOL situation AVAYA HP DL360G7 systems in the field may receive a 300GB 10K SAS HDD (CC ) as a replacement for a failed 146GB HDD. The 300GB HDD is interchangeable with the 146GB HDD. RAID Systems originally configured with 146GB HDDs are compatible with a 300GB HDD replacement. For example a Qty=3 146GB HDD RAID 5 system presents a 273GB Virtual Drive to the operating system. When one of the 146GB HDDs is replaced with a 300GB HDD the RAID 5 system will continue to present a 273GB Virtual drive to the operating system. The following procedure describes replacing a failed 146GB HDD with a 300GB HDD. Example RAID status commands for this procedure are shown below. 1. Remove the failed 146GB HDDs from a running system. Application should continue to run unaffected Avaya Inc. All Rights Reserved. Page 5

6 2. With the failed 146GB HDDs removed the RAID subsystem will report that the subsystem is running in degraded or interim recovery mode depending on your RAID monitoring software. 3. Insert the replacement 300GB HDD. 4. Within 10sec. the lower green LED on the newly inserted 300GB HDD should start flashing at a 1 second rate, indicating a rebuild of the array. 5. RAID subsystem should report rebuild of the array with a status of recovering or rebuild with a percentage of rebuild progress. 6. Once the rebuild is complete (approximately 25 minutes) the status will change to good or OK. Green LED will indicate the drive activity similar to other HDDs in the system. 7. The RAID array size will report the same amount of virtual drive space. RAID Status Command Examples Examples of possible RAID configurations that may be encountered in the field are shown below. The commands included in these examples can be used to view the RAID Configuration and HDDs that make up the array. For systems that support the raid_status command type the following commands from root login: A RAID 5 System with Qty=3 146 GB HDD RAID 5 system with one HDD failed/removed: Example commands and output: [root@dl360g7hw1 sbin]# raid_status -s logicaldrive 1 (273.4 GB, RAID 5): Interim Recovery Mode /* logical drive degraded and attempting to recover */ [root@dl360g7hw1 sbin]# raid_status -p physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 146 GB): OK /* drive in slot 1 is 146GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 146 GB): Failed /* drive in slot 2 has failed or has been removed */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, 146 GB): OK /* drive in slot 3 is 146GB */ A RAID 5 System with Qty=3 146 GB HDD RAID 5 system with one 300GB HDD installed during rebuild: Example commands and output: [root@dl360g7hw1 sbin]# raid_status -s logicaldrive 1 (273.4 GB, RAID 5): Recovering, 7% complete /* logical drive rebuilding */ [root@dl360g7hw1 sbin]# raid_status -p physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 146 GB): OK /* drive in slot 1 is 146GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 300 GB): Rebuilding /* 300GB drive has been inserted and is rebuilding */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, 146 GB): OK /* drive in slot 3 is 146GB */ Within 10sec. of insertion of replacement HDD the lower green LED on the newly inserted 300GB HDD should start flashing at a one second rate, indicating a rebuild of the array. Once the rebuild is complete (approximately 25 minutes) the status will change to good or OK Green LED will indicate drive activity similar to other HDDs in the system. A RAID 5 System with Qty=3 146 GB HDD RAID 5 system with one 300GB HDD installed and rebuilt: Example commands and output: [root@dl360g7hw1 sbin]# raid_status -s logicaldrive 1 (273.4 GB, RAID 5): OK /* logical drive healthy */ 2012 Avaya Inc. All Rights Reserved. Page 6

7 sbin]# raid_status -p physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 146 GB): OK /* drive in slot 1 is 146GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 300 GB): OK /* drive in slot 2 is 300GB */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, 146 GB): OK /* drive in slot 3 is 146GB */ A RAID 1 System with Qty=2 300GB HDD RAID 5 system presents a 279.4GB Virtual Drive to the OS. Example commands and output: [root@spdl360g7300gb ~]# raid_status -s logicaldrive 1 (279.4 GB, RAID 1): OK /* logical drive healthy and correct capacity */ [root@spdl360g7300gb ~]# raid_status -p physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 300 GB): OK /* drive in slot 1 is 300GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 300 GB): OK /* drive in slot 2 is 300GB */ A RAID 5 System with Qty=3 146 GB HDD RAID 5 system presents a 273.4GB Virtual Drive to the OS. Example commands and output: [root@dl360g7hw1 ~]# raid_status -s logicaldrive 1 (273.4 GB, RAID 5): OK /* logical drive healthy and correct capacity */ [root@dl360g7hw1 ~]# raid_status -p physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 146 GB): OK /* drive in slot 1 is 146GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 146 GB): OK /* drive in slot 2 is 146GB */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, 146 GB): OK /* drive in slot 3 is 146GB */ For systems that do not support the raid_status command but have the hpacucli utilty installed: hpacucli command is typically installed in /usr/sbin A RAID 5 System with Qty=3 146 GB HDD RAID 5 system presents a 273.4GB Virtual Drive to the OS. Example command and output: [root@dl360g7hw1 sbin]# hpacucli ctrl all show config Smart Array P410i in Slot 0 (Embedded) (sn: A87580) array A (SAS, Unused Space: 0 MB) logicaldrive 1 (273.4 GB, RAID 5, OK) /* logical drive healthy and correct capacity */ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK) /* drive in slot 1 is 146GB */ 2012 Avaya Inc. All Rights Reserved. Page 7

8 physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 146 GB, OK) /* drive in slot 2 is 146GB */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 146 GB, OK) /* drive in slot 3 is 146GB */ A RAID 5 System with Qty=3 146 GB HDD RAID 5 system with one HDD failed/removed: Example command and output: [root@dl360g7hw1 sbin]# hpacucli ctrl all show config Smart Array P410i in Slot 0 (Embedded) (sn: A87580) array A (SAS, Unused Space: 0 MB) logicaldrive 1 (273.4 GB, RAID 5, Interim Recovery Mode) /* logical drive degraded and attempting to recover */ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK) /* drive in slot 1 is 146GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 146 GB, Failed) /* drive in slot 2 has failed or has been removed */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 146 GB, OK) /* drive in slot 3 is 146GB */ sep 250 (WWID: A8758F) A RAID 5 System with Qty=3 146 GB HDD RAID 5 system with one 300GB HDD installed during rebuild: Example command and output: [root@dl360g7hw1 sbin]# hpacucli ctrl all show config Smart Array P410i in Slot 0 (Embedded) (sn: A87580) array A (SAS, Unused Space: 0 MB) logicaldrive 1 (273.4 GB, RAID 5, Recovering, 3% complete) /* logical drive rebuilding */ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK) physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 300 GB, Rebuilding) /* 300GB drive has been inserted and is rebuilding */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 146 GB, OK) sep 250 (WWID: A8758F) Within 10sec. of insertion of replacement HDD the lower green LED on the newly inserted 300GB HDD should start flashing at a 1 second rate, indicating a rebuild of the array. Once the rebuild is complete (approximately 25 minutes) the status will change to good or OK Green LED will indicate drive activity similar to other HDDs in the system. A RAID 5 System with Qty=3 146 GB HDD RAID 5 system with one 300GB HDD installed and rebuilt: Example command and output: [root@dl360g7hw1 sbin]# hpacucli ctrl all show config Smart Array P410i in Slot 0 (Embedded) (sn: A87580) 2012 Avaya Inc. All Rights Reserved. Page 8

9 array A (SAS, Unused Space: 0 MB) logicaldrive 1 (273.4 GB, RAID 5, OK) /* logical drive healthy */ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK) /* drive in slot 1 is 146GB */ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 300 GB, OK) /* drive in slot 2 is 300GB */ physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 146 GB, OK) /* drive in slot 3 is 146GB */ sep 250 (WWID: A8758F) For users that do not have root access viewing /var/log/messages should report the following entries for indication of Logical drive status when removing and installing HDDs: Jul 28 20:01:41 dl360g7hw1 cmaidad[6965]: Logical Drive Status Change: Slot 0, Drive: 1. Status is now Interim Recovery. Jul 28 20:01:41 dl360g7hw1 cmaidad[6965]: Physical Drive Status Change: Slot 0 Port 1I Box 1 Bay 2. Status is now Failed. Jul 28 20:01:43 dl360g7hw1 cmaeventd[6917]: Hot-plug drive removed: Port 1I Box 1 Bay 2 of Embedded Array Controller. Jul 28 20:01:43 dl360g7hw1 cmaeventd[6917]: Physical drive failed: Port 1I Box 1 Bay 2 of Embedded Array Controller. Jul 28 20:06:27 dl360g7hw1 cmaidad[6965]: Logical Drive Status Change: Slot 0, Drive: 1. Status is now Rebuilding. Jul 28 20:06:27 dl360g7hw1 cmaidad[6965]: Physical Drive Status Change: Slot 0 Port 1I Box 1 Bay 2. Status is now OK. Jul 28 20:06:33 dl360g7hw1 cmaeventd[6917]: Hot-plug drive inserted: Port 1I Box 1 Bay 2 of Embedded Array Controller. Jul 28 20:06:57 dl360g7hw1 cmaeventd[6917]: Logical drive 1 of Embedded Array Controller, has changed from status Interim Recovery to Ready For Rebuild Jul 28 20:06:57 dl360g7hw1 cmaeventd[6917]: Logical drive 1 of Embedded Array Controller, has changed from status Ready For Rebuild to Rebuilding Jul 28 20:17:57 dl360g7hw1 cmaeventd[6917]: Logical drive 1 of Embedded Array Controller, has changed from status Rebuilding to OK System Platform RAID Status Command Example For System Platform based products, RAID status commands can also be run as root from dom0: raid_status p v It s output looks like the following on a RAID 1 system with two 146GB HDD installed: [root@strachur1 ~]# raid_status -p v Smart Array P410i in Slot 0 (Embedded) array A physicaldrive 1I:1:1 Port: 1I Box: 1 Bay: 1 Status: OK Drive Type: Data Drive Interface Type: SAS Size: 146 GB Rotational Speed: Firmware Revision: HPDE Serial Number: 6SD0DA3A0000B04537A Avaya Inc. All Rights Reserved. Page 9

10 Model: HP EG0146FAWHU PHY Count: 2 PHY Transfer Rate: 6.0GBPS, Unknown physicaldrive 1I:1:2 Port: 1I Box: 1 Bay: 2 Status: OK Drive Type: Data Drive Interface Type: SAS Size: 146 GB Rotational Speed: Firmware Revision: HPDE Serial Number: 6SD0CQ8H0000B045421E Model: HP EG0146FAWHU PHY Count: 2 PHY Transfer Rate: 6.0GBPS, Unknown Refer to Avaya product specific documentation for other methods of determining RAID/HDD status if root access is not available or the raid_status or hpacucli commands are not supported. Server Replacement Avaya s maintenance strategy is that FRU servers ship with the required non-fru components such as processors and RAID controllers for the products they are used for. However, they may be minimally configured with FRU components such as HDDs, memory and NIC cards, and may require reuse of these components from the failed server or additional FRU components to match the required configuration. A typical example is a product that requires 3 HDDs in a RAID 5 configuration and a dual port NIC card but is replaced by a FRU server with 2 HDDs in a RAID 1 configuration, less memory and no NIC card. In this situation, if the HDDs from the failed server are still good, the RAID array can be imported into the new server avoiding the necessity of restoring customer data from backup. If a server with a mixed RAID array of 146GB and 300GB HDDs fails for some other reason (e.g. system board failure), the mixed RAID array can also be imported into the new FRU server, replacing the blank HDDs that came in the FRU. After powering down both servers, the HDDs should be moved to the same position in the FRU server that they occupied in the failed server. Upon power up the RAID array will automatically be imported into the new server. The additional memory and other components required can also be moved from the failed server to the FRU server during the power down. Insure that DIMMS and any expansion cards are populated in the same slots as the original failed server. Additional steps to accept new NIC MAC addresses may be required. Check application specific documentation. In the situation that a FRU server needs to be built up to product specifications using blank HDDs instead of importing an existing RAID array, the HP DL360 G7 RAID Configuration Tool and instructions available at can be used (available under the Common Server product downloads). This tool will automatically configure the RAID depending on the number of drives found in the system (2 hard drives will be configured as RAID 1; and 3 or 4 hard drives will be configured as RAID 5). As noted above the most likely use of this tool is when the product requires 3 or 4 HDDs in a RAID 5 configuration and the FRU comes with 2 HDDs in a RAID 1 configuration Avaya Inc. All Rights Reserved. Page 10