Flylib.com

Books Software

 
 
 

Coverage and Topology


Coverage and Topology

Preference should be given to providers that can offer provider edge (PE) devices in the majority of the vicinities where you have site locations. The reason for this is that latency over the high-speed networks that connect PE devices is much lower than the latency of lower-speed links connecting enterprise edge routers to the PE. The more PEs in the vicinity of your site locations, the less backhaul over low-speed networks that is required.

When considering extranet capability, it is likely that the sites on your network that you want to be visible to a partner remain limited in scope, meaning that the partner is not simply made part of the any-to-any VPN. Therefore, you should determine if the provider can support one of these scenarios for extranet connectivity:

  • A Layer 2 VPN service between your enterprise and an extranet partner site, terminating in a separate data-link connection identifier (DLCI), virtual circuit (VC), or VLAN for each partner site.

  • A separate virtual routing/forwarding instance (VRF) per extranet partner site, delivered via a separate DLCI, VC, or VLAN to the CE router.

These issues could be addressed by questions such as the following:

  • PE coverage Please provide the global locations (cities) where you locate your PE routers, owned and operated by you, for customer connections.

  • Partners ' PE coverage and interconnects If you leverage partners to provide local access, please give the global locations (cities) where your partners provide PE routers. Please provide the global locations (cities) where you interconnect with the partners' networks. Please also provide details on the Cisco Powered Network (CPN) designations and use of Cisco equipment in each partner's network.

  • Extranet connectivity Can you offer an Layer 2 VPN service between a Cisco extranet partner site and Cisco, terminating in a separate DLCI, VC, or VLAN for each partner site at a Cisco location? Can you offer a separate Layer 3 VRF for each extranet partner site, terminating on the Cisco customer edge (CE) router in a separate DLCI, VC, or VLAN?



Customer Edge Router Management

Enterprises have to choose whether they want the CE managed by themselves or the provider. If managed by the enterprise, this is called an unmanaged service, and it has the following benefits.

It allows the enterprise to manage other information technology (IT) infrastructure services on the CEs, such as public switched telephone network (PSTN) gateway functionality or content distribution functionality.

Many new features are applicable primarily at the WAN/VPN edge, where more advanced functionality is needed to offer the level of service for enterprise applications. Such an example is advanced QoS functionality.

When the CEs are accessible from the enterprise network, the enterprise can observe and communicate the state of the WAN interfaces upon circuit or equipment failure to assist in troubleshooting, rather than first forcing a service provider's dispatch to look at the equipment.

This permits the enterprise to deploy enterprise security capabilities, such as encryption, directly on the CE instead of having to provide a second router to interface with a service provider's managed router.

The following may be considered suitable questions to cover these issues:

  • Unmanaged/managed CE service Do you offer an unmanaged CE service where the enterprise maintains ownership of the router's configurations?

  • Intelligent intermediary devices Do you use intelligent intermediary devices to monitor link status and performance?