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

Hierarchical Navigation

Partner Central

Multi Protocol Label Switching VPN

Cisco Powered Managed Services

A Cisco Powered managed MPLS VPN service provides private IP networks with high quality, secure, any-to-any connectivity.

The service is based on the Cisco IP NGN Architecture, Multi Protocol Label Switching (MPLS) and Cisco Design and Implementation Guides.

The service delivers appropriate levels of latency, jitter, and packet loss to ensure the successful, concurrent handling of multiple types of traffic, especially voice and video, from customer site to customer site.

The network classifies and prioritizes traffic flows from end to end, enabling SLAs for multiple classes 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)
Network foundation for VPN service must be based on IP/MPLS Network design diagram or Technical Service Description (TSD) demonstrating the deployment of MPLS over a Cisco IP network. Refer to RFC 2547—BGP/MPLS VPN
Connectivity provided to the Internet from the VPN Partner must demonstrate that the service offers Internet connectivity across the MPLS backbone to eliminate the need to carry Internet bound traffic back to a customer’s regional HQ site and then on to the external Internet connection. A default route to the Internet can be injected in to the VPN, drawing traffic that does not go to a specific location on the customer network. A managed firewall then screens traffic
Customer ability to select a full mesh VPN option where all sites can pass traffic directly to each other Generally part of the Marketing Service Description (MSD); other service description may also be acceptable
Customer ability to select a design configuration option that will emulate a hub and spoke environment Part of the MSD, or Partner must be able to demonstrate network design option available to customer
Extranet access to VPN The service offering needs to include the ability to connect to a Community of interest network. This extranet allows interested companies to connect together to share information. Partner must demonstrate how this service is secured to ensure that each customer’s VPN is protected from access by another company
Layer 3 network reach The network needs to support IP routing capability, as opposed to Layer 1 or Layer 2 backhaul services, to provide the full benefits of Layer 3 connectivity in each country or region the service is offered in. Partner must be able to demonstrate the existence of a network design process to ensure this. This must include the decision criteria of what the routing node distribution needs to be to adequately cover population densities in each country served
Customer Edge—Provider Edge routing protocol support Partner must support BGP, OSPF, EIGRP and static routing protocols between the CPE and the Provider Edge Router
Remote access via Internet Service must support the ability to gain access to VPN resources via the Internet. Partner must demonstrate how this is achieved. May require client software on remote User access devices

Architecture and Technical Attributes


Requirement Auditor Instructions (What to Look for)
Network foundation for VPN service must be based on IP/MPLS Network design diagram or technical service description demonstrating the deployment of MPLS over a Cisco IP network. Refer to RFC 2547—BGP/MPLS VPN
Connectivity to the Internet must be available as an option for the service Partner must demonstrate that the service offers Internet connectivity across the MPLS backbone to eliminate the need to carry Internet bound traffic back to a customers regional HQ site and then on to the external Internet connection. A default route to the Internet can be injected in to the VPN, drawing traffic that does not go to a specific location on the customer network. A managed firewall then screens traffic
Customer ability to select a full mesh VPN option where all sites can pass traffic directly to each other Generally part of the Marketing Service Description (MSD); other service description may also be acceptable
Remote access via Internet Service must support the ability to gain access to VPN resources via the Internet. Partner must demonstrate how this is achieved. May require client software on remote User access devices

There are no services being offered at the Legacy level.

Related Tools