X hits on this document





5 / 22

Activity/Service Name xiii

Activities/Services Provided xiv

Resource dimensioning and allocation

Engineering the network elements for more efficient utilization and assurance to meet QoS. For example, sizing buffers.

Configuring for redundancies to assure reliability requirements

This is to design the network/systems to provide some tolerance to faults. For example, providing alternative routing, redundant computing, etc.

Initializing and terminating network operations, device reset.

This task is to initialize or shutdown the network and systems.

Setting values for fault threshold, health check intervals, performance thresholds

This task requires an enterprise manager to set and configure threshold values for the purpose of alarm monitoring and performance monitoring.

Polling for faults, health check, running watch-dog timers, processing traps

This task defines the function of either receiving or polling for alarms.

Log control

Diagnostic testing, testing capacity and special conditions

Testing to either proactively detect a failure of some device/application/element or trying to locate faults.

fault location

Determination of fault location through testing, alarm correlation, analysis, etc.

Fault data summarization

Reconfigure, reroute, remove Reroute

Activities to recover from fault conditions

Issue trouble ticket

Activity to document fault

Dispatch technician

Determining  the set of key performance indicators

The task of determining what performance metrics to measure. Examples are delay, response time, packet loss,  buffer overlflow, etc.

Mapping SLA/user perf. objectives into network/system performance  objectives

Mapping higher level service agreements such as response time, to network and system performance objectives such as processing times on each CPU, transport time, priority setting, etc.

Continuous real-time performance monitoring, performance alarm generation

Alarms, statistics, history, and host/conversation groups are  used to monitor and maintain network/system availability based on application-layer traffic. Performance metrics at the interface, device, and protocol levels are collected regularly to facilitate enterprise management, capacity planning, rerouting functions The EMSs typically collect, store, and present performance data from network devices and servers.

Examples of  performance metrics colleted are: response time,  jitter (delay variance),  packet loss, input/output queuing time, input/output buffer overflow,  transaction time,  occupancy (utilization) of resources.

Performance and statistical analysis of measured values,  Performance data summarization

Post analysis of measured performance indicators for capacity planning, traffic engineering, reconfigurations, etc.


Printed 6/18/2004

Document info
Document views31
Page views31
Page last viewedSat Oct 22 01:53:00 UTC 2016