World Wide Packets 

OAM: Operations, Administration and Maintenance

Introduction

The scope of this paper is to describe the Ethernet and MPLS tools and procedures to accomplish Operations, Administration and Maintenance (OAM). This functionality addresses the fault management aspects of the Fault, Configuration, Accounting, Performance, Security (FCAPS) model as defined by the ITU-T Telecommunication Management Network (TMN). This paper provides an overview of the shaded portion of the figure below.

FCAPS ArchitectureLegend:

  • NEL, Network Element Layer, e.g. devices
  • EML, Element Management Layer, e.g. device level functions
  • NML, Network Management Layer, e.g. topology management
  • SML, Service Management Layer, e.g. service level agreements
  • BML, Business Management Layer, e.g. budgeting and billing.

Recent enhancements to Ethernet and MPLS have added Carrier Class OAM features for monitoring, detecting, verifying, isolating and repairing faults with appropriate notifi cations to network administrators. These enhancements enable network operators to deploy time-saving automated self-healing practices, as well as on-demand diagnostics and troubleshooting techniques.

The purpose of OAM is to improve revenue growth and profi tability for the service providers, as outlined in the following table.

Objectives
Protecting Revenue
By preventing service outages
By offering faster service restoration
Maximizing Revenue Growth
By enabling richer service offering
Reducing operational costs
By reducing repair costs
By reducing operational overhead

This white paper describes the OAM features in the context of the objectives above and the unique benefi ts of the World Wide Packets’ solution.

Continue