CANOGA PERKINS 9145EMP NID Software Version 3.1 - Manual (Page 141)

Service OAM 9145EMP NID Software User’s Manual
Service OAM
129
Figure 11-2 Typical Service OAM deployment and applications
11.1.6 Typical Configuration Sequence
The SOAM entities described in section 11.1.1 are creatable entities; they do not exist in the sys-
tem when the system starts with the factory defaults. You must explicitly create those entities in
the system using the screens and procedures described in this chapter.
The process of creating a new entity in the system includes a validation phase. The validation
phase starts when the (A)dd command is issued. For each newly created entity, all attributes
specified by the user are validated for value (the expected ranges) and consistency (that is, con-
sistency among the parameters of the same entity and with the existing system configuration). If
the validation fails, the entity is not created until the user corrects the validation error and a new
(A)dd command is issued.
The SOAM configuration model defines the hierarchical relationship between MDs, MAs, MEPs,
and MIPs. An MA is always attached to a particular existing MD, and may be attached to a partic-
ular VLAN multiplexing record; a MEP is attached to an MA or a MEG, and so on. When you con-
figure SOAM entities, you must therefore follow a certain sequence:
1. Configure the proper VLAN Multiplexing records, as shown in Chapter 12 of this manual.
A VLAN multiplexing record cannot be deleted or modified if SOAM entities are con-
nected on it.