Geekly Articles each Day
📜 ⬆️ ⬇️

Monitoring Avaya Aura distributed stations using Zabbix

Introductory


It took me to monitor the Avaya station. There were no problems with the version of Communication Manager above R16.0.141 - everything is very well and transparently visible in SNMP, including the status of trunks and internal numbers. But with earlier versions - an ambush. And if we consider that there were more than 30 such stations, and there were at least 10–20 trunks on each (and on some hundreds) - the task turned out to be a little non-trivial. But since you still have to do it, you had to decide). So…

Formulation of the problem


What we need:

  1. Catch a trunk failure within 1-2 hours after a fall
  2. To catch the massive failure of internal numbers (disconnecting 10-20% of internal numbers within 10-20 minutes)
  3. The refusal of any of the offices or the appearance of errors on them
  4. Catch the failure of key internal numbers (incoming groups, VIPs, etc.)
  5. Monitor the status of DECT-bases connected to stations
  6. Well, it would be good to get up-to-date information about the software version at the stations, serial numbers and other.

What we have of equipment



Preparatory work


Configure zabbix server


  1. We agree that the server is already configured to work with SNMP and SNMPtrap;
  2. Set up a breakdown of rsyslog by different files and allow it to receive messages from other hosts. To do this, edit the rsyslog.conf config

    $UDPServerRun 514 $InputTCPServerRun 514 $template FROMHOSTIP,"%fromhost-ip%" $template FILENAME,"/var/log/rsyslog/%fromhost-ip%/syslog.log"

    and then restart rsyslog;
    ')
  3. We put the files trunk2type.sh , trunk2ip.sh , and trunk2alive.sh from the archive into the externalscripts directory;

  4. Put the file convert_trunks.sh in any place and configure its execution via cron every 10 minutes.

Do not forget to change these scripts variable PATH_TXT to the current.

Configure Avaya Aura Communication Manager


Enable SNMP


  1. Go to the browser on the Communication Manager web interface.
  2. In the menu Administration → Server Maintenance → Alarms → SNMP Agent we set the following parameters:

    1. Access from IP-addressess: Any or specify the IP address of the Zabbix server
    2. Enable SNMP Community v2 and set the name of the read-only community to public
    3. Save the settings.

  3. Apply the settings by restarting the agent (Alarms → Agent Status)
  4. In the Security → Firewall menu, we enable snmp and snmptrap (you must put both checkboxes in front of the corresponding services)

Let's enable the collection of trunk statistics


  1. Launch Avaya Site Administration, connect to the station and execute the command:

     ch mea tru

    And then we will indicate all the numbers of trunks for which we need to collect statistics. On versions R13 and earlier quantities of observed trunks is limited to 20 trunks.

Set up DECT stations


Avaya DECT R3


Settings should be made only on the main base. The remaining bases will pick up these parameters automatically.

  1. When you enable SNMP, specify the IP address of the Zabbix server and the community public.
  2. We will specify it Syslog-server. Port 514.

Avaya DECT R4


Settings should be made only on the main and backup bases. The remaining bases will pick up these parameters automatically.

  1. When you enable SNMP, specify the IP address of the Zabbix server and the community public.
  2. We will specify it Syslog-server. Port 514. Logging level 4 (Warnings) or 3 (Errors).

Spectralink IP-DECT Server 400/6500


Settings should be made only on the main base. The remaining bases will pick up these parameters automatically. When applying the SNMP settings, the database will require a reboot !!!

  1. When you enable SNMP, specify the IP address of the Zabbix server, and the community public
  2. We will specify it Syslog-server. Port 514. logging level 4 (Warnings) or 3 (Errors)

Set up Media Gateways


After logging in via telnet or ssh to the media gateway, we will enter the following commands:

 snmp-server community read-only public read-write <rw community> set snmp trap <IP-> set snmp community trap public

We form the list of trunks


To monitor the trunk, we need the following information for each of the trunks:

  1. Trunk number
  2. Trunk name
  3. Trunk type
  4. Number of lines in trunk
  5. Number of out-of-service lines
  6. IP address of the far end of the trunk

All this data can be obtained via SNMP, but in this case it will not be possible to associate the trunk number with the address of its far node. So you have to do it manually. To facilitate this task, I created in Excel an file that forms the list we need based on the results of those commands from Avaya Site Administration. The procedure is as follows:

  1. In Avaya Site Administration, press Ctrl + R and make reports to the csv files for each of the three commands:

    • li tru
    • li sign
    • li node-n a (at stations previously R15, this command looks like li node-n)

  2. The results of each of the three teams are imported into the appropriate sheets of the Excel file.
  3. On the sheet Zabbix as a result we will get the table we need. We export it to a text file with the name avaya_node-names_ <IP-address of the station> .txt

Establishment of nodes in Zabbix


In Zabbix we start hosts of stations, gateways and main DETC-bases, attaching the following templates to them:


Since some of the parameters are collected once a day and the templates use auto-detection of the vast majority of parameters, note that we will receive actual data only in a day and a half.

Conclusion


There are several points that I want to draw attention to:


Links


Source: https://habr.com/ru/post/356348/

More articles:


All Articles