AND – A technical introduction

Advanced Network Design

AND FaultLocalizerInteractive Localization of Network

Disturbances

D. Kelly, 27 February 2009

Why network monitoring?

Reduce maintenance costs

Detect Fault ASAP

Resolve network fault ASAP

Maintaining reliable multimedia networks

Comparison with incumbent telcos

Keeping customers online ...

... keeping customers

AND FaultLocalizer

AND FaultLocalizer

Interface to network monitoring systems

Visualises alarms in network documentation

Alarms generated by NMS

Alarms manually generated in AND network documentation

Table overview of current alarms (filtering possible)

Alarm hotspots - geographical overview of current alarms

Comparison of performance data with AND calculations

Combines AND network simulation with live information

AND FaultLocalizer

Introduction

Alarming & Monitoring Solutions

Manual tracing for common cause failure

Transponder monitoring

Statistical analysis monitoring

Others

AND FaultLocalizer

Common Cause Failure

Select problematic outlets

Colour coding denotes number of customers affected

Identify suspect device at common point

Change component’s operational status to disturbed

Alarm table is automatically updated

Corresponding hotspot alarm is activated

AND FaultLocalizer

Tracing in AND documentation

Monitoring Solutions

Functions

Transponders strategically placed in active network components

amplifiers, power supply units, etc.

Pre-defined tolerance values stored in transponder

Network component monitors own performance

NMS polls transponder or trap is set in transponder.

If value lies outside tolerances NMS generates warning message

Market examples

ROSA, Cisco/SA

EMS, Teleste

KOM, Kathrein

Promptlink

Proxilliant (ingress measurement)

AND FaultLocalizer

Transponder Monitoring

Monitoring Solutions

Functions

Gather and analyse network traffic & performance data

Typically via cable modems and CMTS

Detects network issues based on analysis results

Market examples

ServAssure from Arris (previously Stargus, C-Cor CableEdge)

Auspice (recently acquired by Arris)

Visum from Teledesign, Brazil

AND interfaces

Provision of network structure data

Collected or exported?

Reception of alarm data

AND FaultLocalizer

Statistical Analysis Monitoring

Monitoring Solutions

PathTrak, JDSU

Enables operator to identify ingress issues in upstream

Alarm information limited to fibre node

Handled similarly to transponder monitoring solutions

Hunter, Arcom Digital

Uses radar technology to identify location of network issues

Marker known as common path distortion (CPD)

Handled similarly to statistical analysis monitoring

CPD alarm with affected node and zone information

Ingress alarm with affected narrow zone information

Outage alarm based on node return signal processing

AND FaultLocalizer

Other Solutions

AND FaultLocalizer

AND FaultLocalizer

IT Overview

AND Data-base

LegendDaCo = Data CollectorNIS = Network Infrastructure

= data flow between AND and NMS

AND SmartServer

DaCo

NMS Transponder Monitoring

Alarms

HFC Network

NMSStatistical Analysis

Monitoring

Alarms

NISInterface

NIS

CRMSOAP I/F

CRM Database

AND FaultLocalizer

Alarm ID (from NMS)

System ID (from NMS)

Component ID (from NMS)

Alarm message (from NMS)

Severity level status

Low (default), Medium, High

Alarm hierarchy status

Primary (default)

Secondary (i.e. follow-on alarm)

Alarm counter

Alarm acknowledge

AND Localizer

Alarm Data

AND FaultLocalizer

Filter alarms to show specific region

e.g. Munich South

Edit alarm states

Delete alarms

Search alarms

Acknowledge alarms

Hide/unhide

Secondary alarms

According to severity levels

According to NMS

Sort alarms

AND FaultLocalizer

Alarm Table Functions

AND FaultLocalizer

AND FaultLocalizer

Alarm Table

AND FaultLocalizer

AND FaultLocalizer

Alarm Hotspot Overview

Alarm Filtering

Area filter for monitoring stations

Zip code

Determine monitoring source

Colour coded (user definable)

Hide/unhide alarms according to NMS

Determine severity level

Low (default), Medium, High

Hide/unhide alarms according to severity level

Distinguish between primary and secondary alarms

Evaluation by AND

Hide/unhide secondary alarms

AND FaultLocalizer

Alarm Management

Provisioning monitored components in AND

Monitored Component ID

System ID of NMS

Uniqueness of Component ID verified

Informing service staff

E.g. E-mail to service staff on priority issues

Informing call desk

Determine affected subscribers

Address forward to CRM

Keeping customers updated

AND FaultLocalizer

Future Developments

Populating transponder with threshold values

Network documentation updates taken into consideration

Real time level queries

Real-time values comparison with AND calculations.

Calling up NMS from AND

Accessing further information

AND FaultLocalizer

AND FaultLocalizer - Roadmap

Stage 1 – ca. 06/2009

Interface to network monitoring systems

Geographical & table overview of current alarms

Visualisation of alarms in network documentation

Stage 2 – ca.10/2009

Alarm Management Enhancements

Stage 3 – ca. 02/2010

Population of transponders with AND data

Comparison of performance data with AND calculations

AND FaultLocalizer

AND – A technical introduction

Thank you

for your attentionDiarmuid KellyANDsolution

www.and-solution.com