Troubleshooting and Support

Getting Support

This section of the documentation aims to help with with your interaction with Oracle Communications Technical Support. The role of the support team is to provide you with the information and tools you require to quickly resolve an incident. Oracle Communications works with you to ensure you get the support required to efficiently work with your implementation of Unified Assurance.

Contacting Support

Customers with valid support contracts may contact support via the following methods from 8 AM to 5 PM Central U.S., Monday through Friday.

Level Description

Oracle Communications prioritizes incidents as follows:

  1. Application Outage: system completely non-functional.

  2. Application Error without total loss of functionality; business impacting.

  3. Application Error without total loss of functionality; not business impacting.

  4. Application Inaccuracy.

Important Steps To Take Before You Contact Support

To get the most out of support, we recommend that you adhere to the following steps:

  1. Review on-line product material.

  2. Review Product Release Notes.

  3. Check the support site for updates and upgrades.

  4. Validate that the most recent versions are installed.

  5. Review the training material.

  6. Perform troubleshooting:

    • Isolate the problem.

    • Establish possible causes.

    • Test possible causes.

    • Document all troubleshooting activity with DEBUG logs, highlighting errors, and provide a screenshot.

Important Information To Gather Before Contacting Oracle Communications Support

  1. Verify your Support Contract. Is your Maintenance directly with Oracle Communications or one of our Partners? Customers with Partner provided Maintenance will have tickets reassigned to the appropriate Partner.

  2. List Product Versions and Platforms:

    • Product Versions

    • Hardware Platforms

    • Operating Systems and Versions

  3. List Changes. Provide a list of any recent changes (patches, upgrades, hardware changes, hostname or DNS changes, network configuration changes, etc.) that have been made affecting the systems themselves, or the devices/systems being monitored.

  4. What is the Ticket Type:

    • Question

    • Issue

    • Support Account Request

    • Feature Request

    • Documentation Request

  5. Categorize The Issue:

    • Application Outage: system completely non-functional.

    • Application Error without total loss of functionality; business impacting.

    • Application Error without total loss of functionality; not business impacting.

    • Application Inaccuracy.

  6. Describe the Issue:

    • Logs. Collect all relevant log files or excerpts. Whenever possible, set the application log level to DEBUG and capture the behavior at this level before collecting the logs. Provide screen shots of the behavior and/or error messages. Screen shots are often helpful because they show the complete error message as well as the context around which the error occurred.

    • Occurrence. Explain when the behavior first occurred.

    • Frequency. Where appropriate, the frequency of the behavior should be provided.

    • Reproducibility. If the problem is reproducible, please list the steps required to cause it. Also, if not set already, set the log level of the application to DEBUG and perform the steps necessary to reproduce the problem.

FAQs

This section provides you with the answers to frequently asked questions.

How Do I fix the Text File Busy Errors During Update?

While updating a package, you might get an error saying there is an problem with a post-commit file, and a text file is busy. Use the following steps to resolve the issue:

  1. Manually delete the file that is referenced in the error (or move it out of the way if the file can not be deleted). For this example, the correct file to delete/move is $A1BASEDIR/var/repos/dashboards/hooks/post-commit file.

  2. Copy the $A1BASEDIR/distrib/hooks/post-commit file to $A1BASEDIR/var/repos/dashboards/hooks/post-commit.

  3. Finally, re-installing the package.

How Do I Represent Time Values as Metric Data?

The recommended way to store time values is to set the Unit Division to Time and store everything relative to 1 second. This allows our internal Unit Division calculations to appropriately scale different values of time. A value stored as .001 would display as 1ms. A value stored as 300 would display as 5min.

What Are the Limitations of the Out-of-the-box Ping Device Tool?

While viewing the event list, a Ping Device tool has been included a that can ping a device and show the results. However, the ping is being sent from the Presentation server. While this works very well in many environments, some environments have configured network segregation and the presentation server is not capable of reaching the devices, so the Ping Device tool will not show a valid result.

How Do I Safely Override Default Vendor Configurations?

The following link provides you with the guide to override default vendor configurations: Override Default Vendor Configuration

How Do I Change Default User Session Timeout?

The default user session will timeout 8 hours after the last API call is made by the user. This includes refresh calls made by interfaces that auto-refresh like Dashboards or the EventList. This can be extended for all users by updating the PHP variable in a custom Apache include file.

  1. Add the file base-phptimeout.conf under $A1BASEDIR/etc/apache.

  2. Add the following in the conf file to set a session time out of 86400 seconds or one day. php_value session.gc_maxlifetime 86400.

  3. Restart the web Application systemctl restart assure1-web.

How Do I Configure DNS Caching for Optimal Performance

DNS caching on Linux is disabled by default, which can cause performance issues (increased load on DNS servers, increased response latency, etc) in large scale implementations. For optimal performance, it is recommended that a DNS caching agent be configured on all Unified Assurance servers.

Recommended DNS Caching agents:

What is $A1BASEDIR?

This is the variable name of your Unified Assurance installation. Each deployment could have a different base directory.

Glossary

The following list defines the words and abbreviations that are used in this documentation: