SICOS: Monitoring of communications of companies in ONO

After finalizing the tests of concept of a selection process initiated in 2012, ONO chose us at the end of July 2013, for the implementation of the new manager based in Open Source communications CPEs equipment software enterprise customers (Customer-Premises Equipment).


sicos-ono-esquema


The solution is based on components of the t-QoSMoS portfolio in which there are collected Open Source components such as Zabbix, Rancid, Talend Open Studio, Pentaho, TacPlus, and includes adaptations made to achieve optimal integration, both among them and with the customer’s systems, developed on the basis of the programming (API) interfaces and data structures well documented that such components are presented, meeting the requirements established by ONO.


 


{slider-main Functionalities:|closed}


{slider Network|closed}



  • Fault and performance monitoring, based on Zabbix.

  • Inventory, information on teams and customers, implemented into Zabbix MySQL database using additional tables.

  • Configuration and access to CPEs, Rancid and TAC_PLUS.

  • User portal based on TomCat Apache, accessible by registered users in corporate LDAP, and integrating the GUI of other components.

  • Integration CPEs and other NMS via SNMP, including consultancy in ICMP.

  • Reporting, with Pentaho, running on Tomcat server.


{slider Data integration}


The different types of integration of data included in this solution are resolved using the Talend Open Studio component for Data Integration, composed of an element of Edition, which allows you to define and describe the workflow to implement, and other runtime, these flows in the operating environment. Three types of data streams are contemplated:



  • Supply: implemented through a battery of scripts that include performances on the components of the solution, previously parameterized via the web.

  • Diagnosis: for the implementation of various actions of test and validation equipment CPEs, which invoke different commands set in advance.

  • ETL: for historical to a second database data export, preferably Colonnade, for the purpose of carrying out the exploitation oriented Business Analytics of information, in the event that the data volume is high and/or required reduced access times.


{/sliders}


{/sliders-main}

Publicado en Old

Share

Contact

Access