Contents

SIGTRAN interconnects and other custom linksets can be monitored with YateMMI and Zabbix.

YateMMI will only show status of the linksets and the count of messages exchanged through each linkset.
Zabbix allows to create Items, Triggers and Maps

Items are variables where gathered data from a host are stored.

Triggers are logical expressions that “evaluate” data gathered by Items and also represent the current system state.

Maps can be created with various elements in order to have an overview of your infrastructure.

API settings for STP equipment

For monitoring with YateMMI and/or Zabbix, we need to instruct the API to know/respond on requests regarding interconnect linksets and/or custom SIGTRAN links added to YateSTP equipment.

We need to edit /etc/yate/stp/yatestp.conf file and include in [api] section the names of the linksets we need API to be aware of.

This will also allow YateMMI to show Status information for equipment type YateSTP, if Additional details checkbox is checked.
Status information for ayn equipment can be seen from: YateMMI → Equipment → YateSTP (or any other equipment) → Status

[api]
extra_stats=sig ls_NewYorkSTP1_SparkleSTP1, sig
ls_NewYorkSTP2_SparkleSTP2, sig ls_NewYorkSTP1_ValenciaSTP1_cross_internal,
sig ls_NewYorkSTP1_ValenciaSTP1_cross_external, sig NewYorkSTP1_FrankfurtSCF1

Used variables, taken from /etc/yate/stp/ysig-custom.conf (file created by the sysadmin) or /etc/yate/stp/ysig-config.conf (file created by the YateMMI).

Values after ‘sig ‘ are the names of sections of type: ss7-mtp3 / ss7-m3ua

To verify possible values connect to telnet on product and type ‘status sig ‘ (and press TAB). Recommended values can be set.

ls_NewYorkSTP1_SparkleSTP1

MTP3 linkset for interconnect with Telecom Italia Sparkle (STP1)
ls_NewYorkSTP1_SparkleSTP2

MTP3 linkset for interconnect with Telecom Italia Sparkle (STP2)
ls_NewYorkSTP1_ValenciaSTP2_cross_internal

MTP3 Cross linkset between your STPs located in NewYork and your STPs located in Valencia, that routes internal PCs (Point Codes)

To allow NewYork STP1 to reach equipment behind Valencia STP

ls_NewYorkSTP1_ValenciaSTP2_cross_external

MTP3 Cross linkset between your STPs located in NewYork and your STPs located in Valencia, that routes external PCs (Point Codes)

To allow NewYork STP1 to reach Telecom Italia Sparkle interconnect equipment trough Valencia STP

NewYorkSTP1_FrankfurtSCF1

M3UA ASP link to a SCF equipment [Service Control Function (SCF) or Service Control Point (SCP)]

This is how they are seen in YateMMI:

Zabbix settings

Create Items:

Zabbix web interface → Configuration → Hosts → NewYorkSTP1 → Items → Create Item

Please take a look at Key variable as it is the most important, but it is good to check also the -Host interface- value.
- Key variable example for MTP3 linkset:
  yate.sig_ls_NewYorkSTP1_SparkleSTP1.status
  - taken from the name of the linkset used in ysig-custom.conf/ysig-config.conf file or yatestp.conf [api] section, with yate.sig added as prefix
  - it can be also seen in the YateMMI picture above of YateSTP status
- Key variable example for M3UA link:
  yate.sig_my_FrankfurtSCF1[M3UA_ASP/my_FrankfurtSCF1|3]
Select the suitable Data type for your Key
Add this Item in a new group of Items (as Application) (Ex: SIGTRAN interconnect)

Create Triggers for newly created Items:

Zabbix web interface → Configuration → Hosts → NewYorkSTP1 → Triggers → Create Trigger

Name: NewYorkSTP1 to SparkleSTP1 linkset
Please take a look at Expression, Recovery expression and fields.
- Value and examples of the Expression and the Recovery expression for MTP3 linkset trigger:
  - Problem: {yate-stp – core.yatebts.com:yate.sig_ls_NewYorkSTP1_SparkleSTP1.status.str(“non-operational”)}=1
  - Recovery: {yate-stp – core.yatebts.com:yate.sig_ls_ls_NewYorkSTP1_SparkleSTP1.status.str(“operational”)}=1
- Value and example of the Expression and the Recovery expression for M3UA link trigger
  - Name: NewYorkSTP1 to FrankfurtSCF1 M3UA link
  - Problem: {yate-stp – core.yatebts.com:yate.sig_my_FrankfurtSCF1[M3UA_ASP/my_FrankfurtSCF1|3].str(“Active”)}=0
  - Recovery: {yate-stp – core.yatebts.com:yate.sig_my_FrankfurtSCF1[M3UA_ASP/my_FrankfurtSCF1|3].str(“Active”)}=1

Create Maps:

Zabbix web interface → Monitoring → Maps → Edit map

In order to create the map, we need to know the nodes of the map, so:

We have 3 STPs in the network (2 in NY: NewYorkSTP1, NewYorkSTP2 and 1 in VLC: ValenciaSTP1)
We connect 2 STPs of Sparkle (SparkleSTP1 and SparkleSTP2)
And one SCF located in Frankfurt, FrankfurtSCF1

So, our nodes (are already added as Hosts, from Zabbix web interface → Configuration → Hosts → “Add host”) will be added in the map Hosts. Then we add interconnect nodes (SparkleSTP1 and SparkleSTP2) as Triggers. Then we create the links (linksets) from interconnecting nodes (SparkleSTP1 and SparkleSTP2) to NewYorkSTP1.

This is how they are seen in Zabbix.

Monitoring SIGTRAN interconnect and Zabbix

API settings for STP equipment

Zabbix settings

Our solutions