Table of Contents

Advertisement

Quick Links

Troubleshooting the Avaya Pod Fx
Release 3.1
NN47204-700
Issue 05.01
October 2017

Advertisement

Table of Contents
loading

Summary of Contents for Avaya Pod Fx

  • Page 1 ™ Troubleshooting the Avaya Pod Fx Release 3.1 NN47204-700 Issue 05.01 October 2017...
  • Page 2 Software at any given time. A “Unit” means the unit on which CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE Avaya, at its sole discretion, bases the pricing of its licenses and can FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA...
  • Page 3 IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION transmission, dissemination, storage, and or use without the express FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE written consent of Avaya can be a criminal, as well as a civil offense OBTAINED FROM MPEG LA, L.L.C. SEE HTTP:// under the applicable law.
  • Page 4 See the Avaya Support website: https://support.avaya.com product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: https://support.avaya.com...
  • Page 5: Table Of Contents

    ........ 15 Configuring EMC VNX5300 monitoring and EMC Secure Remote Support ....................17 Configuring alarm notifications ............17 Configuring VPFM to monitor Avaya Pod Fx elements ....................18 Creating an email action ..................19 Creating a response configuration ..............21 Configuring SNMP traps for the SAL Gateway Chapter 4: Troubleshooting general issues.................
  • Page 6 Chapter 7: Resources......................60 ..........................60 Support ....................... 62 Documentation reference ..........................63 Training ......................63 Avaya Mentor videos ..................64 Searching a documentation collection ....................65 Subscribing to e-notifications ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 7: Chapter 1: Introduction

    Chapter 1: Introduction Purpose This document contains advice, solutions, and procedures for dealing with common issues encountered while using the Avaya Pod Fx. This document is intended for the following audience: • end users • Avaya certified technicians • Avaya partners •...
  • Page 8 Note: If you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Example 1. Go to the Avaya Support website at http://support.avaya.com.
  • Page 9: Chapter 2: New In This Document

    The following sections outline what is new in Troubleshooting the Avaya Pod Fx (NN47204–700). VMware vSphere 6.0 Update 3B Avaya Pod Fx Release 3.1 uses VMware vSphere 6.0 vCenter Server Appliance Update 3B for all Avaya Pod Fx platforms. Compute servers are the physical servers, operating as VMware ESXi hosts. Avaya Pod Fx component applications are virtualized and run on a VMware High Availability (HA) cluster of ESXi hosts.
  • Page 10: Avaya Pod Fx Upgrades To Release 3.1

    Preexisting Avaya Pod Fx platforms can upgrade to Release 3.1 software. The following software upgrade scenarios are supported: • One step upgrade path for all Avaya Pod Fx platforms from Release 2.0.1, 2.1.1, 3.0, 3.0.1, or 3.0.2 to Release 3.1.
  • Page 11: Hpe Nimble Cs1000 Array

    Avaya Pod Fx Select certified Business Partners only). It is recommended that you perform the Avaya Pod Fx Configurator Design Review process in the event of an upgrade. This is recommended to validate the updated software line up for the applications does not require additional resources in the Avaya Pod Fx such as additional storage or servers.
  • Page 12: Chapter 3: Configuring Monitoring And Alerts

    Management IP and Controller Support IP addresses. Run the test once again. Troubleshoot and run the test until all items in the test pass. 8. Click Send Diagnostics for Nimble Analytics. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 13: Nimble Cs1000 And Vpfm Alarms

    10. Enter the information for your corporate SMTP server SMTP Server section. 11. Set the level at which alarms and notifications are sent in the Alert Options section. 12. Click Test to test the settings. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 14: Configuring Emc Vnxe3200 Monitoring And Emc Secure Remote Support

    7. In the Email Alerts section, add the email addresses of the individuals that will receive email notifications. 8. In the Severity level of alerts to send field, set the severity level that will trigger emails to be sent. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 15: Configuring Emc Vnx5300 Monitoring And Emc Secure Remote Support

    1. Access EMC Unisphere by opening the IP address of the device in a browser tab or from the PVM storage component view. 2. Log in with the required username and password credentials. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 16 22. Select the latest version of the Call_Home_Template from the provided list. 23. Select Explicit Events from the Events section. 24. Select the ConnectEMC tab. 25. Select Connect Home. 26. Click OK. 27. Select the Distributed Monitors tab. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 17: Configuring Alarm Notifications

    The following section contains procedures required to allow Avaya Pod Fx element events to trigger a response in VPFM. In this example, the response will be to send an email message to the Avaya Pod Fx operator(s) when IP availability is lost to an Avaya Pod Fx element. The Avaya Pod Fx operator can specify which element events will trigger an alert, and configure the trigger requirements.
  • Page 18: Creating An Email Action

    Creating an email action About this task Use this procedure to create an email action that will inform the Avaya Pod Fx operator of any alarms that are triggered during VPFM monitoring of the Avaya Pod Fx network elements. Before you begin Configure VPFM to monitor network elements.
  • Page 19: Creating A Response Configuration

    17 Creating a response configuration About this task Use this procedure to create a response configuration for all Avaya Pod Fx managed devices. Procedure 1. Navigate to Actions > By Event Response. Click Add a new response. Enter the name Pod Fx IP Availability Response.
  • Page 20 9. Click Apply your changes button. Example After you have completed all of the previous configuration steps, if an Avaya Pod Fx managed element is polled and does not respond, the operator(s) will receive an email similar to the following example: From: vpfm@company.com [mailto:vpfm@company.com]...
  • Page 21: Configuring Snmp Traps For The Sal Gateway

    Configuring SNMP traps for the SAL Gateway About this task Use this task to configure elements of the Avaya Pod Fx to send SNMP traps to the SAL Gateway. Procedure 1. Configure Avaya Virtual Services Platform 4000 Series switches to send SNMP traps.
  • Page 22 7. Configure HP iLO to send SNMP traps. a. Log in to the web interface of the HP iLO. The web interface is located at: https:// HP_iLO_IP_ADDRESS. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 23 Enter and enable the next available destination. Note: A test trap can be sent to verify it is enabled. h. Click Apply Changes. i. Logout. Related links Configuring alarm notifications on page 17 ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 24: Chapter 4: Troubleshooting General Issues

    You can also enable the service from the Alert Settings page. Tip: Booting up and shutting down the EMC VNXe 3200 can take approximately 30 minutes. Please be patient. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 25 As a general warning that an IP address was found in the SONMP, LLDP, or CDP table of a discovered device, but the IP object did not respond, VPFM displays the following message: potential managed device <IPO: 172.30.10.23> was not explored during ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 26 Pod Visualization Manager (PVM) discovers all physical components and builds a view of the Avaya Pod Fx. If you change a component or physically move a component to another rack, ensure that you update the PVM profile to reflect those changes and then use the Rediscover function. This updates the profile with the current component information.
  • Page 27 This represents the agreed design of the Avaya Pod Fx and is the documentation used to build it. If the applications currently running on the Avaya Pod Fx outstrip the originally designed capabilities of it, performance will be effected.
  • Page 28: Quick Fixes

    • Restart spirit agent using the following commands: service spiritAgent stop service snmpd restart service spiritAgent start Table continues… ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 29 4. In the Terminal window: a. Restart jboss: • # service jbossd {start|stop|status| restart} b. Restart Serviceability Agent: service • spiritAgent stop service snmpd restart service spiritAgent start Table continues… ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 30 EVC mode are disabled on the Mitigation of this requires creation ESXi host clusters by default. of a new host cluster with the EVC Avaya Pod Fx that have been mode enabled, moving hosts to expanded with additional compute the EVC mode cluster, manual...
  • Page 31: Troubleshooting With Pvm

    24 Troubleshooting with PVM Pod Visualization Manager (PVM) provides access to the visualization and management applications required to configure, orchestrate, manage, and monitor your Avaya Pod Fx. The following table lists some common troubleshooting information displayed in PVM. Symptom...
  • Page 32 PVM. Unusual power fluctuations are a sign of a consumption of power is shown. malfunctioning device or too much power is drawn by the Avaya Pod Fx. Either circumstance requires further investigation. Red thresholds are reached in...
  • Page 33 Threshold values are initially set to default values. They are configurable through the PVM to suit individual situations and preferences. PVM is a consolidated launch pad for all elements in the Avaya Pod Fx solution. Related links Troubleshooting general issues on page 24 ™...
  • Page 34: Chapter 5: Troubleshooting Software Issues

    Communication Manager in ® an Avaya Aura Virtualized Environment ® The issues in the following section are encountered when running Avaya Aura Communication ® Manager in an Avaya Aura Virtualized Environment such as the Avaya Pod Fx. Servers are temporarily in an active / active state Condition ®...
  • Page 35 See PSN003556u on the ® Avaya Support website for additional information. See Duplicated Avaya Aura Communication Manager on VMware for best practices on deploying duplicated CM servers in a VE configuration. It should be referenced for any duplicated CM VE deployment.
  • Page 36: Esxi Host Alarm After Vmware 6.0 Update 3A Upgrade

    If vMotion DRS automation is used, it is recommended that the DRS automation level be set to the most conservative level possible, such as level 2 or level 1. See PSN20151u on the Avaya Support website for more information.
  • Page 37: Vcenter Server Inaccessible After Server Failure Or Unexpected Server Reboot

    34 Reconfiguring a cluster About this task This procedure is used to reconfigure a cluster after an unexpected shutdown of the Avaya Pod Fx. Procedure 1. On the Management Server Console, launch the vCenter vSphere Client, and log in.
  • Page 38 5. Assign the licenses to the vCenter and hosts, as applicable. 6. In vCenter, click the address for the Avaya Pod Fx settings you want to administer, select the Turn On vSphere HA and Turn On vSphere DRS check boxes, and click OK.
  • Page 39: Timeout Error Configuring High Availability In Vcenter

    2. Click the Configuration tab. 3. Click Networking. 4. Click Properties for the Management Network on vSwitch0 on Release 3.0 Pods and vSwitch1 on pre-Release 3.0 Pods. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 40 16. Right-click the cluster and attempt to configure High Availability. Verify the MTU settings of the Avaya Virtual Services Platform 4850GTS switches if you continue to encounter issues with High Availability configuration. Both devices must be configured to have an MTU setting of 1950 to ensure proper operation.
  • Page 41: Backing Up And Restoring Vcenter Configuration

    16. Note the value of EMB_DB_PASSWORD and EMB_DB_INSTANCE. 17. Navigate to the vPostgres utility directory using the command cd /opt/vmware/ vpostgres/current/bin. 18. Stop the VMware vCenter Server service using the command service vmware-vpxd stop. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 42: Recovering From A Failed Vcsa 5.5 Upgrade

    Revert back to the 5.1 snapshot. b. Perform a fresh upgrade from 5.1 to 5.5. c. Proceed to the next step if the 5.5 upgrade does not complete successfully. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 43: Avaya Aura ® Vms Do Not Recover

    • vCenter is not able to complete the process of powering on the VM after the outage. ® • An event is displayed indicating the Ethernet interfaces associated with the Avaya Aura will start disconnected. • An error message is displayed if an attempt is made to manually reconnect the network adapter.
  • Page 44 Troubleshooting software issues Related links Troubleshooting software issues on page 34 ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 45: Chapter 6: Troubleshooting Hardware Issues

    3. Select the BMC Update utility for Web GUI that is applicable to your ThinkServer model. 4. Verify that the update version shown is version 20.00 or higher. Download both of the update files (the .tgz update utility and the readme). ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 46 Troubleshooting hardware issues 5. Using the Management Server Console on the Avaya Pod Fx, open vCenter and place the host that requires the BMC update into maintenance mode. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 47 Note: The default username and password for the ThinkServer Management Module (TMM) is typically: • Username: lenovo • Password: len0vO (len<zero>v<capital O>) ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 48 Troubleshooting hardware issues 7. After you perform the installation instruction steps in the readme, the firmware update proceeds. You can check the status by watching the status column. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 49 8. Open a new browser session to the ThinkServer Management Module (TMM) and login. Confirm the firmware update by viewing the Properties page. 9. Using the Management Server Console on the Avaya Pod Fx, open vCenter and exit the host from maintenance mode.
  • Page 50: Upgrading Hp Proliant Gen8 Server Bios For Post Errors

    BIOS to the latest version to correct this error. Important: The host server must be in maintenance mode to perform a BIOS upgrade. Ensure that the server is in maintenance mode before beginning this procedure. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 51 16. Use vCenter client to log in directly to the server when the update completes. 17. Confirm the BIOS was upgraded, the server is fully functional, and there are no major hardware alarms. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 52: Upgrading Lenovo Server Bios For Fan Alarm

    13. Log into the ThinkServer Management Module (TMM). Note: The default username and password for the TMM is typically: • Username: lenovo • Password: len0VO (len<zero>v<capital O>) or lenovo ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 53: Checklist For Replacing A Power Distribution Unit

    Always allow adequate strain relief at the PDU end of the cables. Task Description Notes PDU arrives on site. PDU arrives at the site of Avaya Pod Fx with faulty PDU. Mark defective PDU. Defective PDU is marked in the support ticket. Note shipped PDU serial The technician or installer number.
  • Page 54 Customer Lifecycle Workbook. Replace it with the serial number of the replacement PDU. Install PDU in enclosure. Install the replacement PDU in the Avaya Pod Fx enclosure. Power replacement PDU. Plug the replacement PDU into the customer power source. Configure PDU.
  • Page 55: Configuring Switched Pdus Over Ethernet

    Configuring switched PDUs over Ethernet About this task This procedure provides the information necessary to configure a switched PDU using the internal Avaya Pod Fx network. PDU configuration is required after installing a new PDU. See Configuring switched PDUs over Console Connection on page 58 for the procedure to configure a switched PDU using a DB9 connection.
  • Page 56 13. Perform the following steps if the PDU is vertically mounted with the exit line and cord in the UP position: a. Select Configuration > System from the menu. b. Select Inverted from the Display Orientation dropdown list. c. Click Apply. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 57 21. Change the SysName field to Sentry3_SMART_PDU_#_type where # is the PDU number and type is either MAIN or EXT. MAIN denotes a PDU in a main Avaya Pod Fx and EXT denotes a PDU in an extension Avaya Pod Fx.
  • Page 58: Configuring Switched Pdus Over A Console Connection

    This action only restarts the administrative interface. It does not reboot the power outlets or remove power from the outlets. 8. Confirm by pressing Y when prompted. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 59 15. Log into the management software to confirm connectivity. 16. Repeat these steps for the next PDU if more than one requires configuration. Related links Checklist for replacing a Power Distribution Unit on page 53 ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...
  • Page 60: Chapter 7: Resources

    Avaya is responsible only for support of the Avaya and third-party hardware and software within the Avaya Pod Fx that has been purchased through Avaya as part of the Avaya Pod Fx, or that has been explicitly approved in writing by the Avaya Pod Fx product management team.
  • Page 61 System Manager. This can only be done as a whole, with upgrade from one Avaya Pod Fx baseline release to another, unless approved by a PSN or PCN issued by the Avaya Pod Fx product team. This is as per the defined Lifecycle Policy for Avaya Pod Fx release ®...
  • Page 62: Documentation Reference

    Resources on page 60 Documentation reference The following provides a high-level list of links to the Avaya support website and third-party websites. Go to the following websites to obtain documentation for the components supported on Avaya Pod Fx. • Avaya: support.avaya.com–Contains documentation and downloads for networking, management, and applications for Avaya Pod Fx.
  • Page 63: Training

    Training For a detailed list of documentation for Avaya Pod Fx and specific components, see the following document: • Avaya Pod Fx Documentation Reference (NN47204–113) Related links Resources on page 60 Training Product training is available on the Avaya Learning website. For more information or to register, see http://avaya-learning.com.
  • Page 64: Searching A Documentation Collection

    60 Searching a documentation collection On the Avaya Support website, you can download the documentation library for a specific product and software release to perform searches across an entire document collection. For example, you can perform a single, simultaneous search across the collection to quickly find all occurrences of a particular feature.
  • Page 65: Subscribing To E-Notifications

    Application & Technical Notes for Virtual Services Platform 7000. Procedure 1. In an Internet browser, go to https://support.avaya.com. 2. Type your username and password, and then click Login. 3. Under My Information, select SSO login Profile.
  • Page 66 8. Scroll through the list, and then select the product name. 9. Select a release version. 10. Select the check box next to the required documentation types. 11. Click Submit. ™ October 2017 Troubleshooting the Avaya Pod Fx Comments on this document? infodev@avaya.com...

Table of Contents