Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Partner Central

Managed Metro Ethernet

Cisco Powered Managed Services

A Cisco Powered managed Metro Ethernet service provides high-speed, site-to-site connectivity. It supports the delivery of voice, video, and other mission-critical applications.

This service is based on the Cisco IP NGN Architecture, Cisco Design and Implementation Guide, and Metro Ethernet Forum standards and specifications.

The service delivers a variety of point-to-point and multipoint Ethernet services over Layer 1, Layer 2, and Layer 3 topologies with seamless integration. It allows for QoS functionality, including classification and prioritization techniques to enable multiple levels of service.

The service also provides comprehensive SLAs covering the overall performance of the service, and online access to real-time and historical service-performance reports.

To view a complete list of requirements for this service, please visit the Managed Services: Portfolio Requirements

To view the full Bills of Material for this service, please visit the MSCP Portfolio: Bills of Material



Architecture and Technical Attributes


Requirement Auditor Instructions (What to Look for)
Support for at least two of the three service types defined in the Metro Ethernet Forum (MEF) guidelines sections 6 and 10.1 Partner must demonstrate support for at least two of the three following service types: point-to-point EVC (E-Line), root-to-leaf EVC and multipoint to multipoint EVC (E-LAN), as described in section 6.1
Ability to connect multiple CPE devices from the same site Documented evidence in the Marketing Service Description (MSD) or equivalent documentation outlining customer design options
Service frame transparency—deliver frames across the service without adversely affecting the format See MEF 10.1 sec 6.5.3
Layer 2 control processing requirements Conformance to the mandatory requirements in MEF 6 section 7 table 9
E-LMI support Service must support the E-LMI functionality mandated in MEF 16, specifically the ability to auto-configure the CE and to provide EVC status information
Provision of a service that allows the customer to specify which VLAN ID they use See MEF 10.1 sec 7. The service must allow the preservation of the CE-VLAN ID, or for this to be different at the ingress and egress UNI

Architecture and Technical Attributes


Requirement Auditor Instructions (What to Look for)
Support for at least one service as defined in the Metro Ethernet Forum (MEF) guidelines sections 6 and 10.1—Ethernet Virtual Leased Lines or Virtual Private LAN Service Partner must demonstrate support for at least two of the three following service types: point to point EVC, multipoint EVC E-Line) and multipoint to multipoint EVC—(E-LAN), described in section 6.1. UNI 1.1 or UNI 1.2 as specified in MEF 13
Service frame transparency—deliver frames across the service without adversely affecting the format See MEF 10.1 sec 6.5.3
Layer 2 control processing requirements Conformance to the mandatory requirements in MEF 6 section 7 table 9

There are no services being offered at the Legacy level.

Related Tools