Specifications

Installation and Operation Manual Appendix C Operation, Administration and Maintenance (OAM)
LA-210 Ver. 1.5 OAM Entities C-3
Figure C-1. OAM Architecture
Handling of OAM Levels
UNI_C to UNI_N Direction
In the UNI_C to UNI_N direction LA-210 blocks all OAM messages with OAM level
greater than 2. Messages with other OAM levels are passed transparently.
Network Ingress to UNI_N Direction
All OAM messages coming from the network ingress with the ETX MAC address or
with the special OAM multicast address are sent to the CPU. All other OAM
messages are passed transparently to the user ports as per the respective flow
definition.
C.3 OAM Entities
This section describes the OAM entities hierarchy. Figure C-2 illustrates the
relationship between UNI, flow and Service Instance (COS ID), when one or more
service instances belong to one flow and one or more flow belong to a UNI. From
the OAM perspective, the continuity messages and defects are activated per flow,
and the PM is activated per service instance.
A flow can belong only to one UNI in the same LA-210.
Figure C-2. UNI, Flow and Service Instance (COS ID)
Figure
C-3 , Figure C-4 and Figure C-5 illustrate different combinations of UNIs,
flows and service instances. Each UNI contains at least one flow, which contain at
least one service instance.
• In the one flow per UNI case (
Figure C-3 ), the PM and CC are transmitted
once.
Note