CANOGA PERKINS 9145E NID Software Version 4.10 - Manual (Page 215)

Service OAM 9145E NID Software User’s Manual
Service OAM
203
Figure 11-3 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
system 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,
consistency 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, a MEP is attached to an MA or a
MEG, and so on. When you configure SOAM entities, you must therefore follow a certain
sequence:
1. Configure the MD entities first. Up to eight MDs can be configured in a 9145E NID, using
the procedures described in section 11.3.
2. Configure the MA and MEG entities. Choose the VLAN type for the MA (C-Tagged, S-
Tagged, or none) when you create the MAs and MEGs. The actual VLANs associated
with an MA or MEG can be configured at that time, or they can be added or removed later
during runtime operations. An MA must be associated with an MD created in step 1.