Installing the SolutionPack

Using the console, install the .
Make sure you review requirements and complete relevant procedures described in Overview, and have your credentials for Avaya Aura Communication Manager and M&R on hand.
  1. Log in to M&R with root privileges.
    For example,
    http://
    Frontend-hostname
    :58080/APG
  2. Select
    Administration
    .
  3. Select
    Centralized Management
    in the
    Administration
    tree.
  4. Select
    SolutionPack Center
    .
  5. Select
    Avaya Aura Communication Manager
    in the
    Browse and Install SolutionPacks
    screen.
  6. Read the summary information and click
    Install
    .
  7. Select the components to install.
    1. Accept the default name,
      avaya-voip-acm
      , in the
      Instance name
      field.
    2. Select the M&R server that will host the data collector in the
      Data collection
      list box.
    3. Select the M&R server to host the reports in the
      Reports
      list box.
    4. Click
      Next
      .
  8. Accept the default values for the
    Data Collection
    and
    Alerting on Data Collection
    panes.
  9. Enter the server addresses, root credentials, and path to the Perl executable directory for the Avaya VoIP-specific configuration.
    After installing the SolutionPack, you can click the Device Discovery link in the post install message window, and follow this link to configure SNMP monitoring for the Avaya Call Managers you provided during SolutionPack installation. Alternatively you can add the devices later by accessing the Device Discovery module from Administration window. Follow these steps:
    1. Create a collector (if you have not already created one). Navigate to
      Device Discovery
      Collectors
      Add New Collector
      .
    2. Add a device to Watch4net: Navigate to
      Administration
      Modules
      Device Discovery
      Devices
      Add New Device
      , and then configure the name of the device and IP address as part of Main parameters.
      Make the
      Device Type
      CallManager
      , otherwise data for Avaya Health reports will not be displayed in the console.
    3. Configure SNMP Credentials.
    4. Add the previously created collector.
    5. Select appropriate Avaya capabilities for
      AVAYA-SERVER, GENERIC-INTERFACES, GENERIC-SYSUPTIME
      .
    6. Distribute: navigate to
      Device Discovery
      Dashboard
      and then click
      distribute all approved devices with Capabilities on all enabled collectors
      .
Allow four to five polling cycles to pass before viewing reports.
If data for CDR reports does not appear, verify whether the CDR Link established successfully by executing the
status cdr-link
command from SAT terminal. Link state should be up.
sample output : CDR LINK STATUS Primary Secondary Link State: up down Number of Retries: ÿÿÿÿ Date & Time: 2014/02/06 03:46:08 2014/01/16 10:08:20 Forward Seq. No: 0 0 Backward Seq. No: 0 0 CDR Buffer % Full: 0.00 0.00 Reason Code: OK Maintenance busy 2. If Link state is down, then execute "test cdr-link primary long" command from SAT terminal to test primary cdr link. Test 215 should PASS. Sample Output : TEST RESULTS Port Mtce Name Alt. Name Test No. Result Error Code PRI-CDR 213 PASS PRI-CDR 215 PASS
If the Test 215 = fail, verify:
  • Watch4Net server is reachable from ACM
  • CDR Listener is running on Watch4Net Server on port 5001(default)