Network Service Monitoring

AggreGate Network Manager keeps valuable information about IP network services, such as Internet connectibity, VoIP or IPTV. Services may be defined by their termination points (Customer Edge device and port) or full paths up to MPLS cloud or neghbouring networks. Each service is associated with a particular user (customer of a telecom operator or internal business unit of a corporation), so information about this user's SLAs is always by hand.

Once a network incident occurs, the system starts a multi-stage network incident impact evaluation sequence:

• First, it uses intelligent event correlation and root cause analysis algorithms to indicate a single point of failure.
• Next, the system masks and suppresses all non-root failure events, effectively decreasing number of operator-level alarms to one primary alert.
• Then the system finds all affected services, i.e. services those path goes through the root failure point. If service paths are dynamic, the system applies network topology knowledge to figure out how they are switched/routed at the moment.
• At the next step, every affected service is analyzed in order to figure out whether any alternative routes are available. That's necessary to distinguish between complete services failures and partial degradations caused by switching to failover routes.
• The overall incident impact is now evaluated based on number of services affected, their importance, and degradation ratio.
• Finally, initial alert's severity is updated according to its service impact. This happens right before the alert is routed to ITSM/Service Desk for further processing.

IT service registry is normally maintained in a third-party OSS/BSS system that includes billing, CRM and other modules. AggreGate Platform is flexible enough to retrieve structured service data from the inventory system using SOAP, CORBA, HTTP/REST, SQL or any custom API. However, it's possible to set up and keep IT service registry within AggreGate Network Manager. In this case service descriptors will be stored in server database.

Monitoring Access-level and Aggregation-level Telecom Networks

This video illustrates the concepts of IP network service monitoring that relies on topology-based event correlation. The video was made quite short due to split-second SNMP polling performed by AggreGate Network Manager.

In this demo, IP services are imported from a third-party Inventory system. The custom UI for the demo, including the customized fault/degradation alert list and IP video window, was built in AggreGate’s integrated UI editor.

Download

Feature Comparison

Purchase