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]

Hello everyone!

Our CVT trial continues. We are investigating connectivity improvements based on the tool's usage so far. Thank you for your help in testing our diagnostic tools. It provides us with valuable information to continue enhancing the tools that you use.

Additionally, I was informed this morning that the Avaya Diagnostic Portal and many of the Avaya web tools are down this morning. The IT team is working on restoring service, and I will send out an update once things are back to normal.

As always, please continue to send me feedback on what you require and what we can do to make supporting Avaya products easier for you.

Thanks!

Roberto

[roberto]

Originally Posted by roberto

Hello everyone!

Additionally, I was informed this morning that the Avaya Diagnostic Portal and many of the Avaya web tools are down this morning. The IT team is working on restoring service, and I will send out an update once things are back to normal.

The Avaya Diagnostic Portal along with Config Validate Tool are all back up and running. Thank you to all for your patience while service was being restored.

As an FYI, the other web applications that were also affected were:

1.ASCA
2.Avaya Networking Health Check
3.Configuration Validation
4.CS1000 Advanced Diagnostic Tool
5.Password Reset
6.Security Screener

These are all back to normal now as well. Root cause and prevention analysis is underway internally.

[roberto]

We have a new version of the Global Registration Tool 3.0 Technical Onboarding Document. This will help with resolving remote connectivity problems to devices and allow CVT to be used with it.

Based on feedback from customers and partners, SAL Gateway provisioning was not clear as a manual step in the semi-automated GRT technical on-boarding process.

Through our CVT R2 Trial we have identified the areas needed for GRT improvement, and a new GRT 3.0 document has been published.

You can find the new updated GRT 3.0 document here:

https://support.avaya.com/css/P8/documents/100175932

The types of errors with CVT that this will resolve are the ones that produce the following error:

[01/31/2014 22:59:25 GMT] (+5.1s) Attempting connection...
Start connection by using login id: inads
Connection attempt 1 failed for: <SEID> Error code: 0 --
com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Connection attempt 2 failed for: <SEID> Error code: 0 --
com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Connection attempt 3 failed for: <SEID> Error code: 0 --
com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Failed all connections attempts for <SEID>
Internal Error Occurred. com.avaya.a2r.services.connection.exceptions.Produ ctConnectionException: Unable to

connect to product: <SEID>.

Please take a look at the new GRT guide. If anyone needs any assistance with it, please let me know, and I would be glad to set up some time for us to walk through it together.

Cheers,

Roberto

[roberto]

For those that have yet to see the new Avaya Diagnostic Portal, it has now replaced the old single-tool version in the All Tools section of the Support site.

The ADP can be viewed by Tools or by applicable Products from the following links:

Tool View: https://secureservices.avaya.com/adp...toolView.xhtml
Product View: https://secureservices.avaya.com/adp...ductView.xhtml

Please give it a try and let me know if you have any questions or comments.

Thanks!