Date: Tue, 19 Mar 2024 12:22:22 +0000 (UTC) Message-ID: <1687157049.3768.1710850942144@fra-prod-wiki02.geant.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3767_343317304.1710850942138" ------=_Part_3767_343317304.1710850942138 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Operations, Administration & Maintenance (OAM) refers to protocols a= nd mechanisms that help operator to achieve the so-called FCAPS functionali= ties.
FCAPS is the key concept used to define the overall functionality of an = enterprise management system and the acronym stands for Fault, Configur= ation, Accounting, Performance, and Security.
In particular Ethernet operations, administration and maintenanc= e (EOAM) refers to protocols on Ethernet networks that provide fea= tures like fault indication, performance monitoring, security management, d= iagnostic functions, configuration and service provisioning.
Different standards have been developed based on the concept of EOAM, su= ch as:
For sake of clarity it is important to say that the IEEE 802.1ag and the ITU-T Y.1731 are identical = in the connectivity management part.
What ITU provides in addition to that is performance management through = the mean of performance messages.
In one of the activities carried on in GEANT3, Ethernet OAM functions we= re tested over a dedicated testbed established by five NRENs (JANET, NORDUn= et, PSNC, SURFnet and CESNET) and one University (Essex Univerity).
The main idea behind it was gaining some initial experience in monitorin= g and troubleshooting wide-area point-to-point Ethernet connections using t= he Ethernet OAM functions.
The equipment used in the testbed was from different vendors, including = Ciena, Extreme Networks, Cisco, and Brocade. Where the equipment didn't sup= ported the required set of Ethernet OAM functions, small OAM agents on loan= from vendors
(Overture and Accedian Networks) were installed in the trial sites. The = links between sites were of different types: all of them had an Ethernet Us= er Network Interface (UNI) at both ends, but in between different combinati= ons of Multi-Protocol Label
Switching (MPLS), OTN, and tunnelling through IP were used.
The trial objectives were:
command lines to invoke state and performance data periodically, which i=
s not ideal.
The main finding from the trial is that the Ethernet OAM functions embedde=
d in the carrier-grade Ethernet equipment can be used for effective monitor=
ing and visualizing of the health and performance of wide-area Ethernet ser=
vices.
Some problems were experienced when measuring the One-way delay and the =
Jitter.
The document with all results and details can be found here.
Many vendors have implemented EOAM features in their devices in order to= provide powerful troubleshooting tools like layer 2 traceroute.
--AlessandraScicchitano - last ch= ange 07 Jun 2012