CANOGA PERKINS 9145EMP NID Software Version 4.0 - Manual (Page 148)

Service OAM 9145EMP NID Software User’s Manual
Service OAM
133
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, and may be attached to a
particular VLAN multiplexing record; 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 proper EVC records, as shown in Chapter 12 of this manual. An EVC
record cannot be deleted or modified if SOAM entities are connected on it.
2. Configure the MD entities first. Up to eight MDs can be configured in a 9145EMP NID,
using the procedures described in section 11.3.
3. Configure the MA and MEG entities. A MA/MEG must be associated with an underlaying
VLAN Multiplexing record, with the exception of untagged MEGs/MAs. Choose the proper
VLAN type (C-Tag or S-Tag) when you create the MAs and MEGs.
If the VLAN type is S, then the VLAN list must contain only one element, which is the S-
Tag value of the corresponding VLAN Multiplexing record.
If the VLAN type is C, the VLAN list must contain only VLAN IDs that are included in C-
VLAN list of the corresponding VLAN Multiplexing record. The list of VLANs associated
with an CType MA or MEG can be changed runtime; however all VLANs must be included
in the C-VLAN list of the VLAN multiplexing record
4. Configure the MEPs. Each MEP is associated with an existing MA or MEG, created in
step 2.
5. Create the MIP entities. A MIP is associated with an MD (for 802.1ag MIPs) or with a
MEG (for Y.1731 MIPs).
6. If required, configure the AIS client server relationships, as described in section 11.9. The
AIS client server relationships are established between the MEPs and MIPs configured in
the previous steps.
At runtime, deleting a lower level entity (such as a MA or a MEG) will automatically delete all
higher level entities and relationships that are attached to the deleted object. For example,
deleting an MD will automatically delete the MAs attached to the MD, as well as all MEPs, MIPs,
and AIS associations related to the deleted MD
. VLAN Multiplexing records associated with MAs
or MEGs cannot be deleted while the MA is still configured.
11.1.7 Screen Navigation
SOAM parameters and procedures are configured using the menus described in this chapter.
The menu hierarchy for SOAM is illustrated in Figure 11-3.