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

9145EMP NID Software User’s Manual Service OAM
Service OAM
128
Sender ID TLVs may be included, based on configuration, in CCM, LBM, and LTM packets. The
far end system, upon receiving a packet containing a Sender ID TLV, parses and displays this
information, which better identifies a particular node. The 9145EMP NID displays the content of
the Sender ID TLVs received from far end system in the Connectivity Check Database (see sec-
tion 11.6.5).
Port ID TLVs are optionally used for Linktrace reply messages, to identify a particular port on a
given system. Port ID TLVs received from the far end are displayed in the Linktrace monitoring
screen (see section 11.6.6.2).
11.1.5 Typical Service OAM Deployment and Applications
The application shown in Figure 11-2 is an example of a service provider network consisting of
two Metro Ethernet Networks (MEN), MENA and MENB, interconnected at an NNI interface. The
9145EMP, located in the customer premises, provides the demarcation between the customer
and the service provider networks. When SOAM fault monitoring is used, the network can be por-
tioned into multiple hierarchical domains that allow better isolation of faults in the network. Every
domain has some administrative boundaries.
For example the topology described in Figure 11-2 contains four hierarchical domains. At the low-
est level (MD1) three distinct domains are monitoring point-to-point UNI and NNI links. Two Level
4 domains (MD4), MEN A and MEN B, are monitoring the end-to-end connectivity inside each
Metro Ethernet Network in the topology. The service provider monitors its end-to-end service via
a level 5 domain (MD5), while the subscriber uses a level 6 domain for customer-level monitor-
ing.
The SOAM levels used by different organizations are decided based on administrative recom-
mendations.