Solved: Re: new MPLS | need help

musthafa786 · ‎02-17-2013

Hi,

My company is going to install new MPLS link from ISP to connecting remote site, what are the main things need to consider ( or prepare) from our perspective (both hardware and configuration) ?

Regards,

Musthafa

Giuseppe Larosa · ‎02-18-2013

Hello Musthafa,

MPLS services are provided in such a way that nothing special is required to the customer.

If the MPLS service is a L3 VPN you will need to configure two point to point links one in HQ one in remote site.

Each router will peer with the SP PE node locally connected and it will be SP duty to make possible communication between local site and remote site.

The MPLS service may be a L2 VPN instead. In this case your two routers will peer at IP level (OSI layer3) and will share a common IP subnet like they were directly connected to each other.

So a short list of items are :

MPLS type of service ( L3 VPN or L2 VPN)

type of interface to be used including Vlan encapsulation for example FE interface with tagged frames and vlan-id 530.

The IP addressing to be used.

For L3 VPN: the PE-CE protocol static routes or eBGP ( other options are possible like OSPF or EIGRP but less likely).

The MTU (for L3 VPN is generally 1500 bytes)

All this info is provided by the SP

For L2 VPN the most important aspects are:

the MTU, the L2 encapsulation to be used like tagged with vlan-id 530 or frame-relay with DLCI 120.

This info is provided by SP.

The IP subnet to be used on the pseudowire is left to your choice in this case

Hope to help

Giuseppe

View solution in original post

Alessio Andreoli · ‎02-20-2013

Hi Musthafa,
L2VPN is too generic. Is it going to be a p2p or a p2mp? In case of a point to multipoint a few more considerations have to be done. Again, as Giuseppe said, the customer will not even notice an MPLS cloud in between their CE.

Alessio

Sent from Cisco Technical Support iPad App

View solution in original post

Giuseppe Larosa · ‎02-18-2013

Hello Musthafa,

MPLS services are provided in such a way that nothing special is required to the customer.

If the MPLS service is a L3 VPN you will need to configure two point to point links one in HQ one in remote site.

Each router will peer with the SP PE node locally connected and it will be SP duty to make possible communication between local site and remote site.

The MPLS service may be a L2 VPN instead. In this case your two routers will peer at IP level (OSI layer3) and will share a common IP subnet like they were directly connected to each other.

So a short list of items are :

MPLS type of service ( L3 VPN or L2 VPN)

type of interface to be used including Vlan encapsulation for example FE interface with tagged frames and vlan-id 530.

The IP addressing to be used.

For L3 VPN: the PE-CE protocol static routes or eBGP ( other options are possible like OSPF or EIGRP but less likely).

The MTU (for L3 VPN is generally 1500 bytes)

All this info is provided by the SP

For L2 VPN the most important aspects are:

the MTU, the L2 encapsulation to be used like tagged with vlan-id 530 or frame-relay with DLCI 120.

This info is provided by SP.

The IP subnet to be used on the pseudowire is left to your choice in this case

Hope to help

Giuseppe

musthafa786 · ‎02-20-2013

Thanks Giuseppe , Sorry for delay in reply.

Yes I have confirmed that ISP is going to provide L2 VPN,

Do you have any good document which can give more detials on L2 VPN, Thanks.

Regards,

Musthafa

Alessio Andreoli · ‎02-20-2013

Hi Musthafa,
L2VPN is too generic. Is it going to be a p2p or a p2mp? In case of a point to multipoint a few more considerations have to be done. Again, as Giuseppe said, the customer will not even notice an MPLS cloud in between their CE.

Alessio

Sent from Cisco Technical Support iPad App

musthafa786 · ‎02-24-2013

Thanks Guiseppe and Alessio for your information..

Regards,

Musthafa