Implementing Cisco Service Provider Next-Generation Edge Network Services (SPEDGE) 642-889 Interactive Bootcamp

http://www.cisco.com/en/US/docs/wireless/asr_901/Configuration/Guide/eompls.html

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6553/prod_presentation0900aecd80311df4.pdf

None

None

None

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtl2tpv3.html#wp1040784
The Layer 2 Tunnel Protocol Version 3 feature expands on Cisco support of the Layer 2 Tunnel Protocol Version 3 {L2TPv3}. L2TPv3 is an Internet Engineering Task Force {IETF} l2tpext working group draft that provides several enhancements to L2TP for the capability to tunnel any Layer 2 payload over L2TP.
Specifically, L2TPv3 defines the L2TP protocol for tunneling Layer 2 payloads over an IP core network using Layer 2 virtual private networks {VPNs}. Benefits of this feature include the following:
•L2TPv3 simplifies deployment of VPNs
•L2TPv3 does not require Multiprotocol Label Switching
•L2TPv3 supports Layer 2 tunneling over IP for any payload http://www.cisco.com/en/US/products/ps6646/products_ios_protocol_option_home.html
Cisco Any Transport over MPLS {AToM} is a solution for transporting Layer 2 packets over an MPLS backbone. It enables Service Providers to supply connectivity between customer sites with existing data link layer {Layer 2} networks via a single, integrated, packet-based network infrastructure: a Cisco MPLS network. Without separate networks that each have network management environments, Service Providers can deliver Layer 2 connections over an MPLS backbone.
Cisco AToM provides a common framework to encapsulate and transport supported Layer 2 traffic types over an MPLS network core. Service Providers can use a single MPLS network infrastructure to offer connectivity for supported Layer 2 traffic and for IP traffic in Layer 3 VPNs.

None

None

None

# show vfi

http://www.cisco.com/en/US/docs/routers/asr9000/software/routing/configuration/guide/rcasr9kstat.html#wp1041 359

Provisioning an AToM Static Pseudowire
In this configuration task, you use options in the xconnect Ethernet interface configuration command to specify a static connection, and mpls commands in xconnect mode to statically set the following pseudowire parameters:
•Set the local and remote pseudowire labels
•Enable or disable sending the MPLS control word


Haven\'t been able to find where MTU Must match

https://supportforums.cisco.com/thread/191993
Use the red bgp <asn> metric transparent command to preserve the RIP metrics.
When RIP routes are redistributed into BGP, the route metric is stored in the BGP MED value. When BGP routes are redistributed into RIP, and the transparent keyword used, the MED value is copied back as the RIP metric. Without the transparent keyword, the metric value specified is applied to all the routes.

None

6PE is for transporting ipv6 natively and 6VPE is for ipv6 mpls vpns

• E-Line is based on a point-to-point Ethernet Virtual Connection. Two E-Line services are defined:
- Ethernet Private Line {EPL}: A very simple and basic point-to-point service characterized by low frame delay, frame delay variation, and frame loss ratio. No service multiplexing is allowed, and other than a committed information rate {CIR} no class of service {CoS} {Bandwidth Profiling} is allowed.
- Ethernet Virtual Private Line {EVPL}: A point-to-point service wherein service multiplexing {more than one Ethernet Virtual Connection} is allowed. The individual Ethernet Virtual Circuits can be defined with a rich set of Bandwidth Profiles and Layer 2 Control Protocol Processing methods as defined by the Metro Ethernet Forum.

show xconnect all
check value is mpls or l2tp or Ethernet etc in segment field

http://blog.initialdraft.com/archives/1537/

http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.6/routing/configuration/guide/rc36book.pdf

None