Layer 3 VPNs can be implemented in conjunction with L2TPv3 tunnels. The solution lends itself to implementation where the SP does not implement MPLS transport mechanism in the core to forward packets. Implementation of L2TPv3 tunnels creates a tunnel network as an overlay to the IP backbone, which interconnects the PE routers to transport VPN traffic. The multipoint tunnel uses BGP to distribute VPNv4 information between PE routers. The advertised next hop in BGP VPNv4 triggers tunnel endpoint discovery. Dynamic L3 VPN implementation over multipoint L2TPv3 tunnels provides the ability for multiple service providers to cooperate and offer a joint VPN service with traffic tunneled directly from the ingress PE router at one service provider directly to the egress PE router at a different service provider site.

source is cisco press, MPLS Configuration on Cisco IOS Software, 2005

rate if useful,,,

Hi Guru Prasad,

Thanks for you response but I could do some test in my lab and found that MP-BGP can come up even without enabling MPLS on interface.

In live network, I am trying to integrate one of non-MPLS enable in to MPLS and before I enabled interface with MPLS, I want to have MP-BGP with VPNv4 RR but some how it is not comming up. Howerver after doing my test in lab it is clear that MPLS not required to enable to get MP-BGP up.

Regards,

Chintan

Hi,

I am getting below error message. Can any one let me know what it indicates ?

BGP Notification sent, finite state machine error

Message received that caused BGP to send a Notification:

FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

002B0104 201C005A D44A4575 0E020C02

00800042 00010400 010001

Regards,

Chintan

Chintan,

This message tells you that the notification message has been sent in response to an invalid BGP open message. Here's a decoded version of the dumped message:

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

00 2B 01 04 20 1C 00 5A D4 4A 45 75 0E 02 0C 02

00 80 00 42 00 01 04 00 01 00 01

BGP Marker: 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

BGP Length: 0x002B - 43 bytes

BGP Type: 0x01 - OPEN message

Parsing OPEN Message

==========================================

VERSION: 0x04 - 4

AS: 0x201C - 8220

HOLD TIME: 0x005A - 90

ROUTER ID: 0xD44A4575 - 212.74.69.117

OPTIONAL PARAMETERS LENGTH: 0x0E - 14 bytes

Param Type: 2 - Optional Parameter

Param Length: 12

Cap Type: 0x02 - 2

Route Refresh Capability (new)

Cap Length: 0x00 - 0 bytes

Cap Type: 0x80 - 128

Route Refresh Capability (old)

Cap Length: 0x00 - 0 bytes

Cap Type: 0x42 - 66

Unknown Capability

Cap Length: 0x00 - 0 bytes

Cap Value: 0x - 0

Cap Type: 0x01 - 1

Multi Protocol Capability

Cap Length: 0x04 - 4 bytes

AFI: 0x0001 - 1

Reserved Bits: 0x00 - 0

SAFI: 0x01 - 1

Are the two peers Cisco devices?

Regards,

Hi,

No.These two peers are not cisco devices.

One is Juniper and other is Cisco.

Could you let me know where could be issue ?

Regards,

Chintan

Chintan,

According to the error message, the BGP open message sent by the Juniper peer is corrupted.

Regards,

so that agree with what i have said earlier mate

it dose not need mpls

mpls for faster forwarding and to decrease the cpu load on the P routers

rate if useful

and about the error sorry i ahve no idea

good luck

Hi,

i would like to share here that my issue is resolved.Unfortuanly, Juniper doesn't work like cisco and we need to enable MPLS globally to negotiate VPNV4 capability with MP BGP peer. It means MPLS is required in Juniper but not in Cisco.

Thanks everyone.

Regards,

Chintan.