The End-to-End Ethernet (Cont'd)

A significant challenge posed by such a configuration is that the combination of CSs that make up the end service can span technologies and domains, and are often managed by disparate element managers. From a customer perspective, the collection of CSs is a single entity, and service providers would benefit greatly from being able to manage it as such, regardless of the technology nuances.

Service providers can overcome the challenges created by disparate element managers by using multi-dimensional service aware management to provide end-to-end fault management for “always on” services. Multi-dimensional service aware management enables the carrier to provide network and service management from a single entity as opposed to many one-dimensional element managers.

The service aware manager understands the hierarchy and relationships among the collection of CSs with which an end service is constructed, which enables the management system to react to individual nodal and CS events. Information can be correlated and presented to the operator relationally, allowing rapid recognition of and reaction to problems. Consider a carrier Ethernet VPN for an enterprise that is carrying VoIP, video, and data traffic with the appropriate service levels. The Ethernet VPN uses a VLAN in the access network and converges into a VPLS VPN at the provider edge (PE). Service aware management binds these two technology CSs (VLAN and VPLS) together to form an end-to-end picture of the service. By doing this, when problems occur on the CS, the carrier knows where the problem is and, more importantly, to what degree the end user’s experience is compromised.

Operational Simplicity with Ethernet OAM
Ethernet OAM is seen as a prerequisite for efficient rollout of carrier Ethernet services. End-to-end network management for Ethernet virtual circuits (EVCs) is dependant on OAM tools in the data plane and control plane to verify continuity, connectivity and performance of the EVC. For in-band testing, the OAM packets closely resemble customer packets to effectively test the customer’s forwarding path, but they are distinguishable from customer packets so they are kept within the service provider’s network and not forwarded to the customer.

« Previous   |   1   |   2   |   3   |   4   |   Subscribe

Send Comment

© 2005, All information contained herein is the sole property of Pipeline Publishing, LLC. Pipeline Publishing LLC reserves all rights and privileges regarding the use of this information. Any unauthorized use, such as copying, modifying, or reprinting, will be prosecuted under the fullest extent under the governing law.