Download RAD Data comm T1 Specifications

Installation and Operation Manual
Appendix C Operation, Administration, and Maintenance (OAM)
Figure C-1. OAM Architecture
Handling of OAM Levels
UNI_C to UNI_N Direction
In the UNI_C to UNI_N direction RICi-4E1/T1, RICi-8E1/T1 block 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 flows 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.
Note
A flow can belong only to one UNI in the same RICi-4E1/T1, RICi-8E1/T1.
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 contains
at least one service instance.
RICi-4E1/T1, RICi-8E1/T1 Ver. 2.0
OAM Entities
C-3