Avaya Diagnostics: Config Validate Tool R2 Trial Discussion

[roberto]

All,

This thread is being created to facilitate discussions around the Avaya Diagnostic Portal's Config Validate Tool R2 trial currently underway.

Please feel free to post topics related to the trial. What worked, what didn't, and anything else that comes to mind.

The purpose of this discussion thread is to share experiences and help each other out in making the most effective use of these diagnostic capabilities.

Thanks,

Roberto Faria
Avaya Diagnostics

[roberto]

Config Validate Tool R2 utilizes Siebel data to determine if assets are remotely connectable. It leverages the uniquely assigned asset's SEID to reach the particular device over modem or SAL.

If you are not seeing a particular asset after launching CVT and entering the SoldTo/FL, it may point to a problem with the asset registration for remote connectivity. This is typically completed during the technical onboarding phase of asset registration.

With the launch of the Global Registration Tool R3.0, SEIDs can be allocated in a matter of minutes using the Technical On-boarding wizard therein.

An overview of the new GRT system can be found here:
http://support.avaya.com/registration

The GRT tool itself can be found here:
http://support.avaya.com/grt

If anyone has any questions around this, just let me know.

Thanks,

Roberto

[roberto]

Hello everyone,

The CVT R2 User Guide is now available as a draft. I will send all trial participants a copy of the user guide via e-mail, but I have also attached it to this post for easy access.

If anyone has any questions on the user guide please let me know.

Thanks,

Roberto

[roberto]

Trial Participants,

If you encounter any connectivity related issues which prevents you from using the Config Validate Tool, the first step would be to open an ITSS ticket to alert the Avaya Connectivity support team of potential remote access problems.

I have attached to this post a short guide on how to open a Partner ITSS ticket.

Thanks,

Roberto

[rdrago]

I tried to get the report for 0005131212 and received this on the GUI:
Avaya Diagnostic Portal

Avaya Config Validation Tool: Request SUCCESSFUL!

The request has been made and you should receive an e-mail notification of its completion after which you may view the generated report.

However, I received this email in response:

Your request for Configuration Validation Tool report(s) have failed because of a Configuration Validation Tool system error.

Report ID - c0c3410d-aa78-41a7-93e3-a42c1dea1fbc

• Product: S88IPA
• Report Title: ADP 120213

Please follow the steps below:

1. Create an ITSS ticket in the partner-ITSS under corporate applications and choose the Configuration Validation Tool.
2. Provide the FL and product.

Thank you for choosing Avaya.

Please visit support.avaya.com for product documentation, downloads, service request management, tutorials and more online technical support services.

[roberto]

We have received reports of a system error with the following exception highlighted in the PDF report's Session Details section:

11/26/2013 18:16:19 GMT] (+459.2s) The product connection has failed. The tool is unable to run validate script.
Internal Error Occurred. com.avaya.a2r.services.connection.exceptions.Promp tNotMatchedException:
java.io.IOException: Time expired, no match found

You may obtain further information about what failed by looking at the PDF report on the Support Site.

If this is the same error you are receiving, there is a fix being rolled into the production systems this week. I will post an update as soon as I've confirmed its release.

If it is something else, please post the error message from the Session Details section of the PDF report, and I'll research the problem further.

Thanks,

Roberto

[roberto]

Another issue that has been seen over the past week is failures with the following information in the PDF report Session Details section:

Connection attempt 1 failed for: <SEID> 0 -- com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Connection attempt 2 failed for: <SEID> 0 -- com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Connection attempt 3 failed for: <SEID> 0 -- com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Failed all connections attempts for <SEID>

Where SEID = (xxx)xxx-xxxx - your device's solution element identifier.

In reviewing the PIE/SAL polling data for the SEID's Asset, one of the causes of this is that the Avaya Product Connect system cannot reach the device through the SAL gateway (or modem bank). For SAL, it is worthwhile checking your Managed Elements list in your SAL Gateway and ensure it has all the information that was used to provision the products via the GRT tool.

For information on how to provision the products in the Managed Elements list in SAL, see the SAL Gateway Implementation Guide (Pages 69-75 - Managed Element Configuration)

Thanks,

Roberto

[roberto]

It was raised over the past few weeks that the assets displayed by the CVT tool are not user-friendly. The good news is that you are able to give the asset a nickname that you can relate to and therefore easily identify the device you want to work on.

To set up asset nicknames, you can use this Web Tip Article: Managing Assets and Serial Numbers

If you have any issues, just let me know.

Roberto

[roberto]

Hello everyone,

We've had a new production system update pushed out over the weekend. The new update includes validation assessment changes.

Please try out the latest version of the tool, and let me know if you run into any issues.

Thanks,

Roberto

[roberto]

We have some good enhancements on their way.

The Avaya Diagnostic Portal is being redesigned to be a landing page where all new Diagnostic tools can be found.

This new ADP Landing page will be launched in conjunction with Config Validate Tool R2, and those that are part of the CVT R2 trial will be the first to see it.

I will send all trial participants an e-mail with a sneak-peek at what the new ADP Landing page will look like.

The new ADP Landing page will become active on December 19th. More details to follow.

Roberto