ipnetworking.net

linux and networking articles

Tag: CCNP-SP (page 1 of 5)

CCNP Service Provider completed

Today I passed the SP-Edge exam! With this I completed the CCIP to CCNP-SP conversion.

I started studying this track in August so it took me 2-2.5 months to do the 3 exams. The exams are definatly “doable” if you lab the different topics that are there. Also the topology created in this post worked out very nicely for just the CCNP-SP track. You can basicly build any scenario using just VMware and IOS-XRv + CSR1000v.

One book that I recommend to buy when learning CCNP-SP is MPLS enabled applications.

Carrier Ethernet in Service Provider IP NGN Environments

This post will cover CCNP-SP topics listed under section 4.0 of the CCNP SPEDGE blueprint. I used several resources online and my own lab to create the information and config snippets listed here. The code snippets only contain relevant information to configure the particular feature. Most examples are only worked out for use with IOS-XR or parts where i am not familiar with on IOS-XE.

4.1 Describe Carrier Ethernet forums and standards (MEF, IEEE, IETF)

Metro Ethernet Forum (MEF):

The Metro Ethernet Forum (MEF) is a nonprofit international industry consortium, dedicated to worldwide adoption of Carrier Ethernet networks and services. The forum is composed of leading service providers, major incumbent local exchange carriers, network equipment vendors, and other networking companies that share an interest in Metro Ethernet.

The MEF is a combination of a technical and a marketing forum to promote the adoption of Metro Ethernet. This is a key differentiator from other standard bodies such as the Internet Engineering Task Force and the Institute of Electrical and Electronics Engineers (IEEE). The forum makes recommendations to existing standards bodies and creates specifications that are not being developed by (or fall within the scope of) other standards bodies.

Institute of Electrical and Electronics Engineers (IEEE):

IEEE stands for the “Institute of Electrical and Electronics Engineers” and is an association. IEEE’s membership has long been composed of engineers and scientists. Allied professionals who are members include computer scientists, software developers, information technology professionals, physicists, and medical doctors, in addition to IEEE’s electrical and electronics engineering core. For this reason the organization no longer goes by the full name, except on legal business documents, and is referred to simply as IEEE.

Internet Engineering Task Force (IETF):

The Internet Engineering Task Force (IETF) develops and promotes voluntary Internet standards, in particular the standards that comprise the Internet protocol suite (TCP/IP). It is an open standards organization, with no formal membership or membership requirements. All participants and managers are volunteers, though their work is usually funded by their employers or sponsors.

Continue reading

Passed the CCNP SP-CORE exam

Today i passed the CCNP SP-CORE exam, the exam was a fair one. Some things were not listed on the blueprint and deserved a good gamble. I noticed it’s good to practice a lot with IOS-XR as most questions are related to -XR. Still happy with the VMware setup i made as it is a good fit for the CCNP-SP track.

Anyway I am happy with the result, only one more exam (SP-EDGE) to go before CCIP is converted to the CCNP-SP. Some posts are already done regarding the SP-EDGE track, the ones that are still missing will soon be here. I am planning to take the SP-EDGE exam within 4 weeks.

Layer 2 VPNs in Service Provider IP NGN Environments

This post will cover CCNP-SP topics listed under section 3.0 of the CCNP SPEDGE blueprint. I used several resources online and my own lab to create the information and config snippets listed here. The code snippets only contain relevant information to configure the particular feature. Most examples are only worked out for use with IOS-XR or area’s where i am not familiar with on IOS-XE.

3.1 Describe L2TPv3 VPNs over an IP Core network

L2TPv3 offers a point-to-point VPN tunnel where layer 2 is transported over a layer 3 IP infrastructure. It is sometimes called a pseudowire and can be considered as a L2-bridge. L2TPv3 does not require MPLS, only IP connectivity between the two sites. The encapsulation on the pseudowire is configured with ‘encapsulation l2tpv3’.

3.2 Describe L2VPN (AToM and VPLS) over an IP/MPLS core network

L2VPN allows the Service Provider to use a single infrastructure for both IP and legacy services. L2 VPN can be used in the form of AToM and VPLS.

AToM

Any Transport over MPLS (AToM), is pretty equivalent to L2TPv3, with the exception that an MPLS network is required. When configuring a pseudowire LDP sets up a targeted LDP session to the PE in question to exchange a VPN label. The encapsulation on the pseudowire is configured as ‘encapsulation mpls’. The transport label follows the normal LSP build with either LDP/MPLS TE/BGP+label path. AToM is a point-to-point solution.

The attachment circuit (AC) is the interface on the PE that is facing the customers CE. The configuration on this interface at the PE side needs to be as default as possible. (Only speed/duplex settings)

Protocols that can be tunneled by using AToM are:

  • Ethernet
  • Frame-Relay
  • ATM
  • HDLC
  • PPP
  • Anything :) (platform dependent)

VPLS

Virtual Private Lan Service (VPLS) offers multipoint-to-multipoint networks. It requires an MPLS enabled network. A PE router enabled for VPLS is routing based on the ethernet MAC address.

Continue reading

Older posts

© 2017 ipnetworking.net

Theme by Anders NorenUp ↑