Avaya Pod Fx Troubleshooting Manual Download Page 3

indicated in the order provided that the performance capacity of the

Server(s) does not exceed the performance capacity specified for the

Software. End User may not re-install or operate the Software on

Server(s) with a larger performance capacity without Avaya’s prior

consent and payment of an upgrade fee.

Named User License (NU). You may: (i) install and use each copy or

Instance of the Software on a single Designated Processor or Server

per authorized Named User (defined below); or (ii) install and use

each copy or Instance of the Software on a Server so long as only

authorized Named Users access and use the Software. “Named

User”, means a user or device that has been expressly authorized by

Avaya to access and use the Software. At Avaya’s sole discretion, a

“Named User” may be, without limitation, designated by name,

corporate function (e.g., webmaster or helpdesk), an e-mail or voice

mail account in the name of a person or corporate function, or a

directory entry in the administrative database utilized by the Software

that permits one user to interface with the Software.

Shrinkwrap License (SR). You may install and use the Software in

accordance with the terms and conditions of the applicable license

agreements, such as “shrinkwrap” or “clickthrough” license

accompanying or applicable to the Software (“Shrinkwrap License”).

Heritage Nortel Software

“Heritage Nortel Software” means the software that was acquired by

Avaya as part of its purchase of the Nortel Enterprise Solutions

Business in December 2009. The Heritage Nortel Software is the

software contained within the list of Heritage Nortel Products located

at 

https://support.avaya.com/LicenseInfo

 under the link “Heritage

Nortel Products” or such successor site as designated by Avaya. For

Heritage Nortel Software, Avaya grants Customer a license to use

Heritage Nortel Software provided hereunder solely to the extent of

the authorized activation or authorized usage level, solely for the

purpose specified in the Documentation, and solely as embedded in,

for execution on, or for communication with Avaya equipment.

Charges for Heritage Nortel Software may be based on extent of

activation or use authorized as specified in an order or invoice.

Copyright

Except where expressly stated otherwise, no use should be made of

materials on this site, the Documentation, Software, Hosted Service,

or hardware provided by Avaya. All content on this site, the

documentation, Hosted Service, and the product provided by Avaya

including the selection, arrangement and design of the content is

owned either by Avaya or its licensors and is protected by copyright

and other intellectual property laws including the sui generis rights

relating to the protection of databases. You may not modify, copy,

reproduce, republish, upload, post, transmit or distribute in any way

any content, in whole or in part, including any code and software

unless expressly authorized by Avaya. Unauthorized reproduction,

transmission, dissemination, storage, and or use without the express

written consent of Avaya can be a criminal, as well as a civil offense

under the applicable law.

Virtualization

The following applies if the product is deployed on a virtual machine.

Each product has its own ordering code and license types. Note that

each Instance of a product must be separately licensed and ordered.

For example, if the end user customer or Avaya Channel Partner

would like to install two Instances of the same type of products, then

two products of that type must be ordered.

Third Party Components

“Third Party Components” mean certain software programs or

portions thereof included in the Software or Hosted Service may

contain software (including open source software) distributed under

third party agreements (“Third Party Components”), which contain

terms regarding the rights to use certain portions of the Software

(“Third Party Terms”). As required, information regarding distributed

Linux OS source code (for those products that have distributed Linux

OS source code) and identifying the copyright holders of the Third

Party Components and the Third Party Terms that apply is available

in the products, Documentation or on Avaya’s website at: 

https://

support.avaya.com/Copyright

 or such successor site as designated

by Avaya. The open source software license terms provided as Third

Party Terms are consistent with the license rights granted in these

Software License Terms, and may contain additional rights benefiting

You, such as modification and distribution of the open source

software. The Third Party Terms shall take precedence over these

Software License Terms, solely with respect to the applicable Third

Party Components to the extent that these Software License Terms

impose greater restrictions on You than the applicable Third Party

Terms.

The following applies only if the H.264 (AVC) codec is distributed with

the product. THIS PRODUCT IS LICENSED UNDER THE AVC

PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A

CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE

REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH

THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC

VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A

PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO

PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS

GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.

ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,

L.L.C. SEE 

HTTP://WWW.MPEGLA.COM

.

Service Provider

THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S

HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT

OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS

SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE

PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM

THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S

HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN

WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE

OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING

BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,

THE AVAYA CHANNEL PARTNER IS REQUIRED TO

INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE

AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,

DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.

WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL

PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED

THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE

AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES

THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY

AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729

CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE 

WWW.SIPRO.COM/CONTACT.HTML

. THE H.264 (AVC) CODEC IS

LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR

THE PERSONAL USE OF A CONSUMER OR OTHER USES IN

WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE

VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC

VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED

BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR

WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO

PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE

IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION

FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE

OBTAINED FROM MPEG LA, L.L.C. SEE 

HTTP://

WWW.MPEGLA.COM

.

Compliance with Laws

You acknowledge and agree that it is Your responsibility for

complying with any applicable laws and regulations, including, but not

limited to laws and regulations related to call recording, data privacy,

intellectual property, trade secret, fraud, and music performance

rights, in the country or territory where the Avaya product is used.

Preventing Toll Fraud

“Toll Fraud” is the unauthorized use of your telecommunications

system by an unauthorized party (for example, a person who is not a

corporate employee, agent, subcontractor, or is not working on your

company's behalf). Be aware that there can be a risk of Toll Fraud

associated with your system and that, if Toll Fraud occurs, it can

result in substantial additional charges for your telecommunications

services.

Avaya Toll Fraud intervention

If You suspect that You are being victimized by Toll Fraud and You

need technical assistance or support, call Technical Service Center

Toll Fraud Intervention Hotline at +1-800-643-2353 for the United

States and Canada. For additional support telephone numbers, see

the Avaya Support website: 

https://support.avaya.com

 or such

successor site as designated by Avaya.

Summary of Contents for Pod Fx

Page 1: ...Troubleshooting the Avaya Pod Fx Release 3 1 NN47204 700 Issue 05 01 October 2017...

Page 2: ...BIND SUCH ENTITY TO THESE TERMS OF USE IF YOU DO NOT HAVE SUCH AUTHORITY OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS...

Page 3: ...the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products Documentation or on Avaya s website at https support avaya com Copyright or such...

Page 4: ...such successor site as designated by Avaya scroll to the bottom of the page and select Contact Avaya Support Trademarks Avaya Aura is a registered trademark of Avaya Inc The trademarks logos and serv...

Page 5: ...General troubleshooting 24 Quick Fixes 28 Troubleshooting with PVM 31 Chapter 5 Troubleshooting software issues 34 Troubleshooting Avaya Aura Communication Manager in an Avaya Aura Virtualized Enviro...

Page 6: ...7 Resources 60 Support 60 Documentation reference 62 Training 63 Avaya Mentor videos 63 Searching a documentation collection 64 Subscribing to e notifications 65 Contents October 2017 Troubleshooting...

Page 7: ...Services also performs product registration on your behalf Avaya Partner and Customer implementation For information about the step by step registration process see the Avaya Classic Global Registrati...

Page 8: ...vaya 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 2 In t...

Page 9: ...hestration Suite POS is a bundle of visualization and management applications required to configure orchestrate manage and monitor your Avaya Pod Fx POS Release 3 1 applications include the following...

Page 10: ...ed before starting any component upgrades To perform an Avaya Pod Fx upgrade update the following components to the Release 3 1 software baseline Avaya Aura System Manager Avaya Pod Orchestration Suit...

Page 11: ...es not require additional resources in the Avaya Pod Fx such as additional storage or servers To schedule a design review email podfxsales avaya com HPE Nimble CS1000 Array Release 3 1 introduces the...

Page 12: ...tab 2 Enter the management IP address of the storage array 3 Log in to the management interface with the Administrator credentials 4 Select Administration Alerts and Monitoring Diagnostics from the m...

Page 13: ...ation is sent from the array This does not have to be a valid email address However the address should provide enough information to be clearly identifiable to the recipient For example a corporation...

Page 14: ...p LANGUAGE EN_US Valid EMC support credentials Customer s SMTP IP address alias Important You must schedule EMC support to complete these tasks Procedure 1 Access EMC Unisphere by opening the IP addre...

Page 15: ...stem must be registered in the EMC database by the EMC support team Work with the customer to ensure the port requirements described here are met HTTPS SUPPORT EMC COM DOCU55301_EMC_SECURE_REMOTE_SERV...

Page 16: ...ystem_Serial_Number customer_domain f Click OK 11 Click Manage ESRS 12 In the Support Credentials section enter the customer EMC credentials 13 Click OK 14 Ensure the Credentials Type is set to EMC On...

Page 17: ...onitoring and alerts on page 12 Configuring VPFM to monitor Avaya Pod Fx elements on page 17 Creating an email action on page 18 Configuring SNMP traps for the SAL Gateway on page 21 Configuring VPFM...

Page 18: ...d 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 Procedure 1 Navigate to Configura...

Page 19: ...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 Click OK 2 In These Elements click Everything The syst...

Page 20: ...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 Sent Thursday April 21 2016 2 16 PM To Pod Fx...

Page 21: ...n g End the SSH session h Logout 2 Configure Avaya Virtual Services Platform 7200 Series switches to send SNMP traps a Start an SSH session with the switch b Log in as the admin user c Use the enable...

Page 22: ...SNMP receivers f Enter the SAL Gateway IP address in the next available receiver field g Verify that it is enabled h Click OK i Logout 6 Configure the EMC VNXe3200 to send SNMP traps a Log in as the...

Page 23: ...he Global Alerting Enable checkbox d Select Generate PET for each of the filter names e Click Apply Changes f Select Server Information Event Management Trap Settings from the menu g Enter and enable...

Page 24: ...hat the IST is up and running Check that SMLT is up and running Check the autotopology table for possible loops EMC storage array EMC recommends that you enable Connect EMC support service This featur...

Page 25: ...a discovery is run on a VPFM domain The message is a low priority level 4 and warns the NOC operator of potential MLT misconfigurations To understand the reason for the message click the Attribute ta...

Page 26: ...e 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 curr...

Page 27: ...ot have any limits on the file size and can grow until it is the size of the partition Delete the file and restart all services if this file has consumed all resources on the partition The vCenter inv...

Page 28: ...heck for status and restart jboss using the following commands as root user On the PVM VM check the jboss status using the command service jboss status Restart jboss using the command service jboss re...

Page 29: ...screen Pod Visualization Manager PVM discovery is not operating as expected You can stop or restart the Serviceability Agent SA using the Administrative toolbar Diagnostics Stop SA and Diagnostics Res...

Page 30: ...bled on the ESXi host clusters by default Avaya Pod Fx that have been expanded with additional compute servers of different make and type can experience issues migrating VMs between hosts in the clust...

Page 31: ...es 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 disp...

Page 32: ...D an orange LED next to a blinking LED Faulty disk Note Hovering the mouse over an LED presents more information EMC VNXe 3200 Storage Server Disk LED no LED shown The disk is missing Note Hovering th...

Page 33: ...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 sol...

Page 34: ...vironment 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...

Page 35: ...erministic behavior Solution The duplication link must have a total capacity of 1Gbps that is dedicated to CM duplication The duplication link interface should be a separate and dedicated interface Se...

Page 36: ...nce the migration could be service impacting 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...

Page 37: ...Log in to the vCenter web interface located at https vCenter_ip_address 5480 2 Click Summary 3 In the vCenter Server section click Start to restart the Server process 4 Verify that the status changes...

Page 38: ...ult Gateway address for the ESXi host because it is a highly available IP address The das isolationaddress is queried to determine if an isolation response has occurred on the host If you change this...

Page 39: ...erElection ChangeState SlaveConnecting Startup SlaveConnectingStateFunc ClusterManagerImpl IsBadIP 10 x x x is bad ip The following situations are observed as a result of the timeout High Availability...

Page 40: ...encounter issues with High Availability configuration Both devices must be configured to have an MTU setting of 1950 to ensure proper operation 1 Connect to the switch 2 Enter Global Configuration mod...

Page 41: ...file using the command cat etc vmware vpx embedded_db cfg 9 Note the value of EMB_DB_INSTANCE and EMB_DB_USER 10 Create the vCenter backup using the command pg_dump EMB_DB_INSTANCE U EMB_DB_USER Fp c...

Page 42: ...oyment Host connection Reverting to VCSA snapshots Procedure 1 Backup and restore the failed upgrade to a new 5 5 instance a Backup the vPostgres database from the failed 5 5 upgrade b Note the IP add...

Page 43: ...t complete the action when all hosts lose power When the hosts are powered on again vCenter attempts to restart all hosts but cannot successfully reconnect the VMs to the network This issue impacts SM...

Page 44: ...Related links Troubleshooting software issues on page 34 Troubleshooting software issues October 2017 Troubleshooting the Avaya Pod Fx 44 Comments on this document infodev avaya com...

Page 45: ...n this scenario the issue is cosmetic and does not affect power supply or system functionality Cause False PSU alert errors are a known issue with Lenovo BMC firmware prior to version 20 00 Solution 1...

Page 46: ...sole on the Avaya Pod Fx open vCenter and place the host that requires the BMC update into maintenance mode Troubleshooting hardware issues October 2017 Troubleshooting the Avaya Pod Fx 46 Comments on...

Page 47: ...TALLATION INSTRUCTIONS section to extract the bmc_xxx ast file upload the file to the server and apply the update Note The default username and password for the ThinkServer Management Module TMM is ty...

Page 48: ...struction steps in the readme the firmware update proceeds You can check the status by watching the status column Troubleshooting hardware issues October 2017 Troubleshooting the Avaya Pod Fx 48 Comme...

Page 49: ...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 Lenovo compute server power supply alarm troublesh...

Page 50: ...rrors 236 or 239 The server may also reboot unexpectedly and display POST error 207 Cause These POST error conditions are a known issue with some HP ProLiant Gen8 servers Use the following procedure t...

Page 51: ...tor and keyboard to the server b Log in using root credentials c Navigate to Troubleshooting Options using the keyboard d Enable ESXi Shell and SSH Support 11 Copy the downloaded file to a temporary d...

Page 52: ...st 4 Select BIOS in the Component list 5 Select BIOS Update Utility for BMC Web GUI ThinkServer RDXXX where RDXXX represents the specific server model 6 Verify that the update version shown is version...

Page 53: ...ower Distribution Unit Refer to the following manufacturer documentation for specific instructions on installation and use ServerTech https www servertech com support Important Ensure there is no stra...

Page 54: ...les Remove all cables from the faulty PDU 8 Remove PDU from enclosure Remove the PDU from the Avaya Pod Fx enclosure ensuring not to bump or disconnect any cords from active PDUs 9 Locate PDU serial n...

Page 55: ...Installer or technician must return the faulty PDU to Avaya using standard equipment return procedures Related links Troubleshooting hardware issues on page 45 Configuring switched PDUs over Ethernet...

Page 56: ...switched PDUs over Console Connection on page 58 for a procedure to use a Console connection to configure the PDU 4 Open a browser window and connect to the PDU management software at http 192 168 1 2...

Page 57: ...led Sentry3_SMART_PDU_1_EXT 22 Change the SysLocation field to Main Pod or Extension Pod depending on the installation type 23 Click Apply 24 Select Tools Restart from the menu 25 Select Restart from...

Page 58: ...ection PDU configuration is required after installing a new PDU See Configuring switched PDUs over Ethernet on page 55 for the procedure to configure a switched PDU using an Ethernet connection Proced...

Page 59: ...rect port on the switch See the Customer Lifecycle Workbook for port information 14 Use the browser provided with the MSC to connect to the PDU management software 15 Log into the management software...

Page 60: ...ing by the Avaya Pod Fx product management team Documentation for specific Avaya products can be found on the Avaya website at http support avaya com Important If you deviate from an Avaya Pod Fx rele...

Page 61: ...y Matrix at https support avaya com CompatibilityMatrix Index aspx You must ensure that automatic software updates are disabled for applications Avaya tests updates to determine compatibility and Avay...

Page 62: ...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...

Page 63: ...aylist categories include Unified Communications tested on Internet Explorer and Firefox Contact Centers Networking Small and Midsize Business Uploaded videos A composite of all available Avaya Mentor...

Page 64: ...ad the documentation collection zip file to your local computer You must have Adobe Acrobat or Adobe Reader installed on your computer Procedure 1 Extract the document collection zip file into a folde...

Page 65: ...on for a specific product for example 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...

Page 66: ...select the product name 9 Select a release version 10 Select the check box next to the required documentation types 11 Click Submit Resources October 2017 Troubleshooting the Avaya Pod Fx 66 Comments...

Reviews: