5 typical service oam deployment and applications, Typical service oam deployment and applications – CANOGA PERKINS 9145E NID Software Version 3.1 User Manual

Page 141

Advertising
background image

9145E NID Software User’s Manual

Service OAM

Service OAM

126

Table 11-1. SOAM protocol support for 802.1ag and Y.1731

11.1.5 Typical Service OAM Deployment and Applications

The application shown in Figure 11-3 is an example of a service provider network consisting of
two Metro Ethernet Networks (MEN), MEN-A and MEN-B, interconnected at an NNI interface.
The 9145E, 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
portioned 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-3 contains four hierarchical domains. At the
lowest 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
monitoring.

The SOAM levels used by different organizations are decided based on administrative
recommendations.

Feature

802.1ag

Y.1731

Continuity check

Yes

Yes

Connectivity Fault Management

Loopback
Unicast
Multicast
Sweep

Yes
N/A
Yes

Yes
Yes
Yes

Linktrace

Yes

Yes

AIS

N/A

Yes

RDI

Yes

Yes

Advertising