Avaya Pod Fx Troubleshooting Manual

Troubleshooting the Avaya Pod Fx

™

Release 3.1

NN47204-700

Issue 05.01

October 2017

2012-2017, A

vaya Inc.

Notice

While reasonable efforts have been made to ensure that the

information in this document is complete and accurate at the time of

printing, Avaya assumes no liability for any errors. Avaya reserves

the right to make changes and corrections to the information in this

document without the obligation to notify any person or organization

of such changes.

Documentation disclaimer

“Documentation” means information published in varying mediums

which may include product information, operating instructions and

performance specifications that are generally made available to users

of products. Documentation does not include marketing materials.

Avaya shall not be responsible for any modifications, additions, or

deletions to the original published version of Documentation unless

such modifications, additions, or deletions were performed by or on

the express behalf of Avaya. End User agrees to indemnify and hold

harmless Avaya, Avaya's agents, servants and employees against all

claims, lawsuits, demands and judgments arising out of, or in

connection with, subsequent modifications, additions or deletions to

this documentation, to the extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked

websites referenced within this site or Documentation provided by

Avaya. Avaya is not responsible for the accuracy of any information,

statement or content provided on these sites and does not

necessarily endorse the products, services, or information described

or offered within them. Avaya does not guarantee that these links will

work all the time and has no control over the availability of the linked

pages.

Warranty

Avaya provides a limited warranty on Avaya hardware and software.

Refer to your sales agreement to establish the terms of the limited

warranty. In addition, Avaya’s standard warranty language, as well as

information regarding support for this product while under warranty is

available to Avaya customers and other parties through the Avaya

Support website:

https://support.avaya.com/helpcenter/

getGenericDetails?detailId=C20091120112456651010

under the link

“Warranty & Product Lifecycle” or such successor site as designated

by Avaya. Please note that if You acquired the product(s) from an

authorized Avaya Channel Partner outside of the United States and

Canada, the warranty is provided to You by said Avaya Channel

Partner and not by Avaya.

“Hosted Service” means an Avaya hosted service subscription that

You acquire from either Avaya or an authorized Avaya Channel

Partner (as applicable) and which is described further in Hosted SAS

or other service description documentation regarding the applicable

hosted service. If You purchase a Hosted Service subscription, the

foregoing limited warranty may not apply but You may be entitled to

support services in connection with the Hosted Service as described

further in your service description documents for the applicable

Hosted Service. Contact Avaya or Avaya Channel Partner (as

applicable) for more information.

Hosted Service

THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA

HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA

CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE

FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA

WEBSITE,

HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER

THE LINK “A

vaya Terms of Use for Hosted Services” OR SUCH

SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE

APPLICABLE TO ANYONE WHO ACCESSES OR USES THE

HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED

SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON

BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE

DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY

AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF

YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A

COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT

YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE

YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU

MUST NOT ACCESS OR USE THE HOSTED SER

VICE OR

AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED

SERVICE.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA

WEBSITE,

HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,

UNDER THE LINK “A

VAYA SOFTWARE LICENSE TERMS (Avaya

Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY

AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,

USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED

FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA

CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL

AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.

UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,

AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE

WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA

AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA

RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU

AND ANYONE ELSE USING OR SELLING THE SOFTWARE

WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR

USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,

YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM

YOU ARE INSTALLING, DOWNLOADING OR USING THE

SOFTWARE (HEREINAFTER REFERRED TO

INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO

THESE TERMS AND CONDITIONS AND CREATE A BINDING

CONTRACT BETWEEN YOU AND AVAYA INC. OR THE

APPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants You a license within the scope of the license types

described below, with the exception of Heritage Nortel Software, for

which the scope of the license is detailed below. Where the order

documentation does not expressly identify a license type, the

applicable license will be a Designated System License. The

applicable number of licenses and units of capacity for which the

license is granted will be one (1), unless a different number of

licenses or units of capacity is specified in the documentation or other

materials available to You. “Software” means computer programs in

object code, provided by Avaya or an Avaya Channel Partner,

whether as stand-alone products, pre-installed on hardware products,

and any upgrades, updates, patches, bug fixes, or modified versions

thereto. “Designated Processor” means a single stand-alone

computing device. “Server” means a Designated Processor that

hosts a software application to be accessed by multiple users.

“Instance” means a single copy of the Software executing at a

particular time: (i) on one physical machine; or (ii) on one deployed

software virtual machine (“VM”) or similar deployment.

Licence types

Designated System(s) License (DS). End User may install and use

each copy or an Instance of the Software only on a number of

Designated Processors up to the number indicated in the order.

Avaya may require the Designated Processor(s) to be identified in

the order by type, serial number, feature key, Instance, location or

other specific designation, or to be provided by End User to Avaya

through electronic means established by Avaya specifically for this

purpose.

Concurrent User License (CU). End User may install and use the

Software on multiple Designated Processors or one or more Servers,

so long as only the licensed number of Units are accessing and using

the Software at any given time. A “Unit” means the unit on which

Avaya, at its sole discretion, bases the pricing of its licenses and can

be, without limitation, an agent, port or user, an e-mail or voice mail

account in the name of a person or corporate function (e.g.,

webmaster or helpdesk), or a directory entry in the administrative

database utilized by the Software that permits one user to interface

with the Software. Units may be linked to a specific, identified Server

or an Instance of the Software.

Database License (DL). End User may install and use each copy or

an Instance of the Software on one Server or on multiple Servers

provided that each of the Servers on which the Software is installed

communicates with no more than one Instance of the same

database.

CPU License (CP). End User may install and use each copy or

Instance of the Software on a number of Servers up to the number

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 A

vaya’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

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.

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 A

vaya. 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 T

erms, 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 T

O 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 (A

VC) 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

ou 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 A

vaya.

Security Vulnerabilities

Information about A

vaya’s security support policies can be found in

the Security Policies and Support section of

https://

support.avaya.com/security.

Suspected A

vaya product security vulnerabilities are handled per the

Avaya Product Security Support Flow (

https://

support.avaya.com/css/P8/documents/100161515).

Downloading Documentation

For the most current versions of Documentation, see the A

vaya

Support website:

https://support.avaya.com, or such successor site

as designated by A

vaya.

Contact Avaya Support

See the Avaya Support website:

https://support.avaya.com for

product or Hosted Service notices and articles, or to report a problem

with your A

vaya product or Hosted Service. For a list of support

telephone numbers and contact addresses, go to the Avaya Support

website:

https://support.avaya.com (or such successor site as

designated by A

vaya), 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 service marks (“Marks”) displayed in this

site, the Documentation, Hosted Service(s), and product(s) provided

by Avaya are the registered or unregistered Marks of Avaya, its

affiliates, its licensors, its suppliers, or other third parties. Users are

not permitted to use such Marks without prior written consent from

Avaya or such third party which may own the Mark. Nothing

contained in this site, the Documentation, Hosted Service(s) and

product(s) should be construed as granting, by implication, estoppel,

or otherwise, any license or right in and to the Marks without the

express written permission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners.

Linux

is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Contents

Chapter 1: Introduction............................................................................................................

Purpose.................................................................................................................................. 7

Product registration................................................................................................................. 7

Warranty................................................................................................................................. 7

Chapter 2: New in this document............................................................................................ 9

VMware vSphere 6.0 Update 3B............................................................................................... 9

Avaya Pod Orchestration Suite Release 3.1.............................................................................. 9

Avaya Pod Fx upgrades to Release 3.1................................................................................... 10

HPE Nimble CS1000 Array..................................................................................................... 11

Chapter 3: Configuring monitoring and alerts..................................................................... 12

Configuring Nimble CS1000 monitoring................................................................................... 12

Nimble CS1000 and VPFM alarms.......................................................................................... 13

Configuring EMC VNXe3200 monitoring and EMC Secure Remote Support............................... 14

Configuring EMC VNX5300 monitoring and EMC Secure Remote Support................................ 15

Configuring alarm notifications................................................................................................ 17

Configuring VPFM to monitor Avaya Pod Fx elements........................................................ 17

Creating an email action.................................................................................................. 18

Creating a response configuration.................................................................................... 19

Configuring SNMP traps for the SAL Gateway................................................................... 21

Chapter 4: Troubleshooting general issues......................................................................... 24

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

Environment......................................................................................................................... 34

ESXi host alarm after VMware 6.0 Update 3A upgrade............................................................. 36

vCenter Server inaccessible after server failure or unexpected server reboot............................. 37

Reconfiguring a cluster.......................................................................................................... 37

Timeout error configuring High Availability in vCenter .............................................................. 39

Backing up and restoring vCenter configuration....................................................................... 41

Recovering from a failed VCSA 5.5 upgrade............................................................................ 42

Avaya Aura

VMs do not recover............................................................................................ 43

Chapter 6: Troubleshooting hardware issues...................................................................... 45

Lenovo compute server power supply alarm troubleshooting.................................................... 45

Upgrading HP ProLiant Gen8 server BIOS for POST errors...................................................... 50

Upgrading Lenovo server BIOS for fan alarm........................................................................... 52

Checklist for replacing a Power Distribution Unit...................................................................... 53

Configuring switched PDUs over Ethernet......................................................................... 55

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

Configuring switched PDUs over a Console connection...................................................... 58

Chapter 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 the Avaya Pod Fx

™

Comments on this document? [email protected]

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

• Avaya Sales Engineer (SE)

• Avaya System Integrator (SI)

Product registration

To prevent service interruption, you must register your Avaya Pod Fx products.

Following are the available methods for product registration:

• Implementation as a service. If Avaya Professional Services provided implementation services

on site, Avaya Professional 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 Registration Process Help Document on the

Avaya Product Support Registration page. The document ID is 100162279.

Product registration is a required element for effective Avaya customer support. You must follow the

Partner and Customer Guidance in the Avaya Global Registration Process to help ensure the

seamless support you have come to expect from Avaya.

Warranty

Avaya provides a limited warranty on its Hardware and Software (“Product(s)”).

Refer to your sales agreement to establish the terms of the limited warranty

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

The standard warranty language for Avaya, as well as information regarding support for this Product

while under warranty, is available to Avaya customers and other parties through the Avaya Support

website: http://support.avaya.com.

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

Go to the Avaya Support website at

http://support.avaya.com.

2. In the Global search field, type warranty, to search the Avaya Knowledge Base for

warranty topics.

The system displays a list of all warranty topics.

3. Click the relevant warranty topic.

Introduction

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

Chapter 2: New in this document

The following sections outline what is new in T

roubleshooting 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.

VMware vCenter Server Appliance (VCSA) provides management for the HA clusters, vMotion, and

Dynamic Resource Schedule (DRS) rules for the ESXi hosts in the Avaya Pod Fx.

Avaya Pod Orchestration Suite Release 3.1

Avaya Pod Orchestration 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 enhancements:

• Support for Avaya Aura

7.1 applications.

• Updates to overall platform security.

New Avaya Pod Fx Release 3.1 system builds provide the following POS application versions pre-

deployed. Existing systems require an upgrade to Avaya Pod Fx Release 3.1, and the following

POS versions:

• Pod Visualization Manager (PVM) Release 3.1.

• Visualization Performance and Fault Monitoring (VPFM) Release 3.1.

• Management Server Console (MSC) Release 3.1

Important:

The following applications have been removed from the POS software starting in Release 3.1:

•

Configuration and Orchestration Manager (COM)

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

• Virtual Provisioning System (VPS)

•

IP Flow Manager (IPFM)

• Pod Utility Manager (PUM)

These applications are end of sale and end of support in Release 3.1.

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.

Important:

The Avaya Pod Utility Module has been removed from the Management Server Console

software in Release 3.1. All upgrades are now conducted using the procedures documented in

Using the Management Server Console for Avaya Pod Fx (NN47204–303).

Avaya Pod Fx upgrades must be performed by Avaya Professional Services, or an Avaya Pod Fx

Select certified Business Partner. They must plan and prepare to perform the upgrades, such as

downloading and transferring all the upgrade files required 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 Suite (POS) software

• VMware vCenter and ESXi software

• Avaya network switches software and firmware

• EMC storage array software and firmware

• HPE Nimble storage array software and firmware

• HPE or Lenovo compute servers BIOS and firmware

• ServerTech Power Distribution Unit (PDU) firmware

• Remove Unisphere Remote and deploy Unisphere Central if applicable

Warning:

vaya Pod Fx Release 3.1 requires an Avaya Aura 7.1 System Manager. Before performing any

upgrades, verify if your existing solution applications are supported on Avaya Aura 7.1 using the

product compatibility matrix available at

https://secureservices.avaya.com/compatibility-matrix/

menus/product.xhtml.

ou can upgrade ACM, and ANAV to the xCaaS 2.0 supported versions before performing an

upgrade of the Avaya Pod Fx infrastructure to Release 3.1.

New in this document

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

For more information about performing Avaya Pod Fx infrastructure upgrades, see Using the

Management Server Console for

Avaya Pod Fx (NN47204–303) (Available for Avaya authorized

professionals and 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. To schedule a design review, email

[email protected].

HPE Nimble CS1000 Array

Release 3.1 introduces the HPE Nimble CS1000 hybrid storage array as the storage solution for all

new Avaya Pod Fx platforms.

The HPE Nimble CS1000 storage array contains redundant disk controllers, redundant power,

networking ports, and expansion shelves for the storage system. The CS1000 Array can

accommodate up to 2 ES2–H expansion shelves in Release 3.1.

HPE Nimble CS1000 Array

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

Chapter 3: Configuring monitoring and

alerts

This section contains information about the configuration of monitoring and alerts for the elements of

the A

vaya Pod Fx.

Related links

Configuring Nimble CS1000 monitoring on page 12

Nimble CS1000 and VPFM alarms on page 13

Configuring EMC VNXe3200 monitoring and EMC Secure Remote Support on page 14

Configuring EMC VNX5300 monitoring and EMC Secure Remote Support on page 15

Configuring alarm notifications on page 17

Configuring Nimble CS1000 monitoring

About this task

Use the following procedure to configure diagnostic monitoring on the Nimble CS1000.

Procedure

Open a new browser window or 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 menu.

5. Select Allow Nimble Storage Support to collect analytics data automatically from the

array.

6. Select Enable Secure Tunnel.

7. Click Test Diagnostics for Nimble Analytics Settings.

A test is performed on the diagnostic settings. A checkmark should appear beside every item

in the test window. If the test fails, ensure that your firewall is allowing traffic from the

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? [email protected]

A test email will be sent to the address configured for the array. Confirm the email

configuration settings if an email is not received at the anticipated address.

9. Click Save.

Related links

Configuring monitoring and alerts on page 12

Nimble CS1000 and VPFM alarms

About this task

The Nimble CS1000 does not currently send alarms or notifications to VPFM. Configure email alerts

to receive alarms and notifications from the device.

Use the following procedure to configure email alerts.

Procedure

Open a new browser window or 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 > Email from the menu.

5. Enter a reporting email address in the Send From Address section.

Note:

This address is displayed in the From field of an email when an alarm or notification 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 has 2 Pods named ExampleCorpCallCenter and

ExampleCorpSAN each with one storage array. The administrator could enter

[email protected] and [email protected] when configuring each device to

identify where an alarm or notification originates.

6. Click Add in the Send To Addresses section.

7. Enter an email address to send alarms and notifications.

8. Repeat the previous two steps for each address to receive alarms and notifications.

9. Select Send event data to Nimble Storage Support if you wish to also send this

information directly to Nimble Support.

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.

Nimble CS1000 and VPFM alarms

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

13. Click Save.

Related links

Configuring monitoring and alerts on page 12

Configuring EMC VNXe3200 monitoring and EMC Secure

Remote Support

About this task

Use the following procedure to configure EMC monitoring and EMC Secure Remote Support

(ESRS) on the EMC VNXe3200.

Before you begin

• Work closely with the customer and local EMC support team to implement ConnectEMC and

ESRS and to discuss the implementation and Internet security issues. The customer system

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_SERVICES_RELEASE_3.08_PORT_REQUIREMEN

TS.PDF?LANGUAGE=EN_US&LANGUAGE=EN_US.

•

Valid EMC support credentials.

• Customer’s SMTP IP address (alias).

Important:

ou must schedule EMC support to complete these tasks.

Procedure

Access EMC Unisphere by opening the IP address of the device in a browser tab or from the

PVM storage component view.

2. Enter the username and password in the provided fields.

3. Click Login.

4. On the dashboard, navigate to Settings > Alert Settings.

5. Select the checkboxes entitled Enable ConnectEMC and Include Customer Contact

Information.

6. In the ConnectEMC SMTP Server field, enter the customer’s SMTP IP address.

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.

Configuring monitoring and alerts

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

9. Click Apply.

10. (Optional) On the dashboard, navigate to Settings > EMC Secure Remote Support.

11. (Optional) Click Add Credentials.

12. (Optional) Enter the EMC support credentials.

13. (Optional) Click Apply.

14. (Optional) Select the Enable ESRS check box.

15. (Optional) Configure a proxy server or policy manager, as required.

Related links

Configuring monitoring and alerts on page 12

Configuring EMC VNX5300 monitoring and EMC Secure

Remote Support

About this task

Use the following procedure to configure EMC monitoring and EMC Secure Remote Support

(ESRS) on the EMC VNX5300.

Before you begin

•

Work closely with the customer and local EMC support team to implement ConnectEMC and

ESRS and to discuss the implementation and Internet security issues. The customer system

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_SERVICES_RELEASE_3.08_PORT_REQUIREMEN

TS.PDF?LANGUAGE=EN_US&LANGUAGE=EN_US.

•

Valid EMC support credentials.

• Customer’s SMTP IP address (alias).

• Work with EMC and the customer to decide which version of ESRS should be used:

- ESRS in Unisphere for a single system.

- ESRS VE for multiple EMC VNX systems. An HA option for ESRS VE is also available.

Important:

ou must schedule EMC support to complete these tasks.

Procedure

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.

Configuring EMC VNX5300 monitoring and EMC Secure Remote Support

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

3. Click Login.

4. Select the system serial number to open the dashboard.

5. On the dashboard, navigate to System > Service Tasks.

6. Click Manage Customer Contact to set the customer contact information.

7. Update the contact information as required. Mandatory fields are noted with an asterisk.

8. Click Update.

9. Click Manage ConnectEMC.

10. In the Email section, complete the fields as follows:

a. Set the Email Priority field to Primary.

b. Set the Email Server (SMTP) field to the customer SMTP server IP address.

c. Set the Subject field to ConnectEMC.

d. Set the Recipient Address(es) field to [email protected].

e. Set the Send Email Address field to

<System_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 Online Support.

15. Click OK.

16. Click Yes when prompted to continue with the operation.

17. On the dashboard, navigate to System > Notifications.

18. Click the Notification Templates tab.

19. Press CTRL+SHIFT+F12 on the keyboard.

20. Enter the password messner when prompted.

21. Click OK.

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.

Configuring monitoring and alerts

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

28. Select a device from the list.

29. Click Use Template.

30. Select the template you previously edited.

31. Click Send Test Event.

32. Verify with EMC support personnel the test event was received successfully.

Related links

Configuring monitoring and alerts on page 12

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.

Related links

Configuring monitoring and alerts on page 12

Configuring VPFM to monitor Avaya Pod Fx elements on page 17

Creating an email action on page

Configuring SNMP traps for the SAL Gateway on page 21

Configuring VPFM to monitor Avaya Pod Fx elements

About this task

Use this procedure to configure VPFM to monitor network elements on the domain.

Before you begin

Ensure that A

vaya Pod Fx elements have been discovered by VPFM and that the VPFM Domain

holding those elements is enabled for Monitoring. If new elements are being added to the Avaya

Pod Fx solution, you must rediscover your network so they will be monitored.

Procedure

1. Click Configurations > Monitoring.

Click Add a new monitoring configuration

Enter the name Avaya CPod Managed Devices and click OK.

4. In These elements click Everything.

Configuring alarm notifications

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

The Choose a Scope screen appears.

Click Show Private Scopes .

6. Type Avaya Pod Managed Devices in the search box, select the scope then click OK.

7. In Monitor for these information types select Monitored Information.

All boxes should now display a green arrow.

Note:

By default the monitoring data will be retained for 30 days, and the polling interval will be

once every ten minutes. Y

ou can adjust this as needed and the smallest polling interval

is 1 minute. However, Avaya recommends leaving the polling interval at the default

value.

Click Apply your changes

Related links

Configuring alarm notifications on page 17

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.

Procedure

1. Navigate to Configurations > Actions.. Highlight Sample Email Action and click Clone

selected action. Enter the name Pod Fx IP Availability Email Action then click

OK.

2. Enter an email alias address in the To: field. You can customize the alias in the From: field

or leave it as default.

You can enter multiple email addresses, each separated by a semi-colon.

3. Click the Primary SMTP tab, enter the SMTP hostname or IP address for your environment.

If necessary for your environment, enter the optional information for SMTP username, SMTP

password, and SMTP Port, if not default port 25.

4. Select Use SSL if SSL is used in your environment.

Configuring monitoring and alerts

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

5. If you have a backup SMTP server, complete the configuration for that tab. Click Apply your

changes when finished.

Next steps

To test the email action, click Test action (green right-facing arrow). If the connection to your SMTP

server is successful, the system displays a pop-up window stating Action executed

successfully. The alias email account(s) will also receive a generic email message from the test.

Related links

Configuring alarm notifications on page

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. Click OK.

2. In These Elements click Everything.

The system displays the Choose a Scope screen.

3. Click Show Private Scopes

4. Enter Avaya Pod Managed Devices in the search box, select the scope then click OK.

5. On the Domain Elements & Event Types tab, select Response applies to Event Types.

6. Expand Availability Event. Expand Availability Problem. Expand Availability Failure.

Expand IP Availability Failure. Select IP Availability Failure. Clear Phone IP Disconnect.

The tree should look like the following diagram:

Configuring alarm notifications

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

7. Click the Actions to Execute tab and then click Response is triggered when. Select An

event is posted.

In Execute the following actions, select Pod Fx IP Availability Email Action.

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: [email protected] [mailto:[email protected]]

Sent: Thursday, April 21, 2016 2:16 PM

To: Pod Fx Operators

Subject: IPAvailabilityFailure on vnx-avstor-1

Domain: tpod_4200

Network Element: vnx-avstor-1

Address: 10.10.8.8

Event Type: IPAvailabilityFailure

Time: Thu Apr 21 14:09:00 PDT 2016

Configuring monitoring and alerts

October 2017 Troubleshooting the Avaya Pod Fx

™

Comments on this document? [email protected]

Page is loading ...

Avaya Pod Fx Troubleshooting Manual

Related papers

Other documents