SevOne

SevOne

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

How SevOne monitors Telco Domains and integrate the metrics and topology with Cloud Pak for AIOps

By Basak Vogt posted Wed February 28, 2024 08:05 AM

  

As a proactive capability of SevOne, we can send all the events as well as topology to Cloud Pak for AIOps (CP4AIOps) whenever we detect an anomaly. AIOps can analyze these events and find the probable cause. And then allow you to execute the associated runbook to fix the issue.

Here I would like to highlight the value of the SevOne and CP4AIOps integration. I will demonstrate one of the scenarios of a Telco Network where an issue has developed.

We can monitor different domains in SevOne as well as different network components such as RAN, Transport and Core Network. In this scenario there is an issue that’s impacting all the domains. We can show several alerts and anomalies generated by SevOne with the value of Anomaly Detection and we are going to demonstrate these issues.

In this scenario we demonstrate different domains, and we focus on different entities such as vRAN or on a specific CSR Router or in a specific Network Function.

Here SevOne can detect anomalies with ML perspective as well as highlights all the issues in the complete Network Domains. There are issues on AMF Network Functions, Transmission on vRAN, there are Voltage issues on CSR Router.

 

Are there any correlations? Are they related with each other? Are there any correlation between the Voltage and the accessibility, transmission and network functions and the traffic and why? 

 

All these events’ probable cause can be Voltage, either with the optical interface that is generating the packet errors, is reducing the traffic or that is restricting the number of people connecting?

We can detect all these issues and severities in SevOne and visualize them.  When all these issues come together for instance in real production environment, we can visually correlate them automatically. Here we would demonstrate manually.

 

Once we have these events as well as topologies, we can send them to CP4AIOps. Now it’s time CP4AIOps to correlate those events and understand the root cause automatically based on different functionalities and algorithms as well as grouping them together.

Here we can demonstrate SevOne sends the topology information as well as events to CP4AIOps.

Not only grouping, correlating and topology management but also CP4AIOps can execute Runbooks to fix the issues.

 

Voltage of an optical interface may impact many other domains and can take weeks or longer to fix the issues. Probably we need to think first what the problem is; RAN or Core or Transport. The value of the integration between SevOne and CP4AIOps is to reduce the time it takes to resolve the issues by allowing us to see the “Big Picture” and identify the underlying cause.

0 comments
45 views

Permalink