[c-nsp] BGP Signalled VPLS

Fri Apr 25 13:25:23 EDT 2014

Hi all, what am I missing to get RFC4761 to work between these (2) me3600's
?  (vpls w/bgp ad and w/bgp sig).  15.3(2)S2 on both me's.

in short, i have the following on them...

*** 3600-1 ***

eng-lab-3600-1#sh run | sec l2vpn vfi context v45

l2vpn vfi context v45

vpn id 45

autodiscovery bgp signaling bgp

  ve id 1

  ve range 11

  rd 64512:451

  route-target export 64512:45

  route-target import 64512:45

*** 3600-2 ***

eng-lab-3600-2#sh run | sec l2vpn vfi context v45

l2vpn vfi context v45

vpn id 45

autodiscovery bgp signaling bgp

  ve id 2

  ve range 11

  rd 64512:452

  route-target export 64512:45

  route-target import 64512:45

----------------------------------------------------------------------------
--

Details.

eng-lab-3600-1#sh xcon all | in 45

UP pri   ac Vl45:45(Eth VLAN)            UP  vfi v45
UP

-- pri  vfi v45                          UP unkn Invalid Segment
--

UP pri   bd 45                           UP  vfi v45
UP

eng-lab-3600-1#sh bgp l2vpn vpls al su | be Neigh

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
State/PfxRcd

10.101.0.1      4        64512     933      60       38    0    0 00:43:46
0

10.101.0.2      4        64512     933      61       38    0    0 00:44:02
0

eng-lab-3600-1#sh l2vpn vfi name v45

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: v45, state: up, type: multipoint, signaling: BGP

  VPN ID: 45, VE-ID: 1, VE-SIZE: 11

  RD: 64512:451, RT: 64512:45, 64512:45

  Bridge-Domain 45 attachment circuits:

    Vlan45

  Pseudo-port interface: pseudowire100020

  Interface          Peer Address    VE-ID  Local Label  Remote Label    S

---------------------------------------------------------------------------

eng-lab-3600-2#sh xcon all | in 45

UP pri   ac Vl45:45(Eth VLAN)            UP  vfi v45
UP

-- pri  vfi v45                          UP unkn Invalid Segment
--

UP pri   bd 45                           UP  vfi v45
UP

eng-lab-3600-2#sh bgp l2vpn vpls al su | be Neigh

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
State/PfxRcd

10.101.0.1      4        64512     726      92       17    0    0 01:12:51
0

10.101.0.2      4        64512     726      91       17    0    0 01:13:00
0

eng-lab-3600-2#sh l2vpn vfi name v45

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: v45, state: up, type: multipoint, signaling: BGP

  VPN ID: 45, VE-ID: 2, VE-SIZE: 11

  RD: 64512:452, RT: 64512:45, 64512:45

  Bridge-Domain 45 attachment circuits:

    Vlan45

  Pseudo-port interface: pseudowire100015

  Interface          Peer Address    VE-ID  Local Label  Remote Label    S

From: Waris Sagheer (waris) [mailto:waris at cisco.com] 
Sent: Friday, April 26, 2013 1:57 PM
To: Aaron; 'Nick Ryce'; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] BGP Signalled VPLS

Aaron,

L2VPN context is the new L2VPN protocol based CLI.

http://www.cisco.com/en/US/partner/docs/switches/metro/me3600x_3800x/softwar
e/release/15.3_2_S/configuration/guide/swl2vpn_prot_based.html

L2VPN VFI is the legacy CLI.

Best Regards,

  <http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg> 

Waris Sagheer
Technical Marketing Manager
Service Provider Access Group
 <mailto:waris at cisco.com> waris at cisco.com
Phone: +1 408 853 6682
Mobile: +1 408 835 1389

CCIE - 19901

 Think before you print.
<http://www.cisco.com/global/EMEA/brand/signature/capital/green.gif>  Think
before you print.

This email may contain confidential and privileged material for the sole use
of the intended recipient. Any review, use, distribution or disclosure by
others is strictly prohibited. If you are not the intended recipient (or
authorized to receive for the recipient), please contact the sender by reply
email and delete all copies of this message.

For corporate legal information go to:
 <http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
http://www.cisco.com/web/about/doing_business/legal/cri/index.html

From: "aaron1 at gvtc.com" <aaron1 at gvtc.com>
Date: Thursday, April 25, 2013 2:26 PM
To: 'Nick Ryce' <nick at fluency.net.uk>, "cisco-nsp at puck.nether.net"
<cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] BGP Signalled VPLS

Thanks Nick,

Yeah I recall using no rd and no route targets with a vpls w/bd ad and ldp

sig.... must have all worked with some automagic rd and rt thingy's

Also my version of me3600 ios doesn't have bgp signaling possible, only ldp.

I think a previous poster (waris maybe) mentioned that 15.3(2)S or something

like that was required for bgp sig and that cisco is making a move towards

more support for bgp sig.

I was just exploring some of this in my me3600 with 15.2(4)S1.... 

What is the difference in the 2 following things... ?  l2 vfi and l2vpn

context vfi ?

Switch(config)#l2 vfi ?

  WORD  VFI name

Switch(config)#l2vpn vfi context vfi ?

  <cr>

Why would I use one over the other?

Aaron

-----Original Message-----

From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Nick

Ryce

Sent: Thursday, April 25, 2013 3:15 PM

To: cisco-nsp at puck.nether.net

Subject: Re: [c-nsp] BGP Signalled VPLS

Had a call with cisco tac and they managed to get it working by removing the

RD.

No idea why this resolved it.  Now to try and get it to working with a

juniper PE.

Nick

--

Nick Ryce

Fluency Communications Ltd.

e. nick at fluency.net.uk

w. http://fluency.net.uk/

t. 0845 874 7000

On 16/04/2013 13:37, "Nick Ryce" <nick at fluency.net.uk> wrote:

Hi,

I have 2 x ME3600x running me360x-universalk9-mz.153-2.S and am looking 

to use the new VPLS BGP signalling functionality.

I am using RSVP with the topology attached but I cannot get traffic to 

pass.  Any ideas?

Configs as below.

Any help with debug commands would also be greatly appreciated.

hostname PE1

!

!

!

no aaa new-model

ip routing

!

!

!

!

ip name-server 8.8.8.8

!

!

mpls traffic-eng tunnels

l2vpn vfi context lab

vpn id 512

autodiscovery bgp signaling bgp

  ve id 1

  ve range 11

  rd 172.16.1.1:512

  route-target export 56595:512

  route-target import 56595:512

!

vlan 512

name lab

!

l2 router-id 172.16.1.1

!

!

!

interface Loopback0

ip address 172.16.1.1 255.255.255.255

ip ospf 1 area 0.0.0.0

!

interface Tunnel0

description PE1-to-PE2

ip unnumbered Loopback0

tunnel mode mpls traffic-eng

tunnel destination 172.16.2.2

tunnel mpls traffic-eng priority 1 1

tunnel mpls traffic-eng path-option 1 dynamic !

interface Tunnel1

description PE1-toPE3

ip unnumbered Loopback0

tunnel mode mpls traffic-eng

tunnel destination 172.16.3.3

tunnel mpls traffic-eng priority 1 1

tunnel mpls traffic-eng path-option 1 dynamic !

interface GigabitEthernet0/1

no switchport

ip address 10.0.0.1 255.255.255.252

mpls traffic-eng tunnels

ip rsvp bandwidth percent 100

!

interface GigabitEthernet0/2

switchport access vlan 512

!

router ospf 1

router-id 172.16.1.1

network 10.0.0.0 0.0.0.3 area 0.0.0.0

mpls traffic-eng router-id Loopback0

mpls traffic-eng area 0.0.0.0

!

router bgp 56595

bgp log-neighbor-changes

bgp graceful-restart restart-time 120

bgp graceful-restart stalepath-time 360  bgp graceful-restart  no bgp 

default ipv4-unicast  neighbor 172.16.2.2 remote-as 56595  neighbor 

172.16.2.2 update-source Loopback0  neighbor 172.16.3.3 remote-as 56595  

neighbor 172.16.3.3 update-source Loopback0  !

address-family ipv4

  neighbor 172.16.2.2 activate

  neighbor 172.16.2.2 send-community extended

  neighbor 172.16.3.3 activate

  neighbor 172.16.3.3 send-community extended  exit-address-family  !

address-family vpnv4

  neighbor 172.16.2.2 activate

  neighbor 172.16.2.2 send-community extended

  neighbor 172.16.3.3 activate

  neighbor 172.16.3.3 send-community extended  exit-address-family  !

address-family l2vpn vpls

  neighbor 172.16.2.2 activate

  neighbor 172.16.2.2 send-community extended

  neighbor 172.16.2.2 prefix-length-size 2

  neighbor 172.16.2.2 suppress-signaling-protocol ldp

  neighbor 172.16.3.3 activate

  neighbor 172.16.3.3 send-community extended

  neighbor 172.16.3.3 suppress-signaling-protocol ldp  

exit-address-family

hostname PE3

!

!

!

no aaa new-model

ip routing

!

!

!

!

ip name-server 8.8.8.8

ipv6 multicast rpf use-bgp

!

!

mpls traffic-eng tunnels

l2vpn vfi context lab

vpn id 512

autodiscovery bgp signaling bgp

  ve id 3

  ve range 11

  rd 172.16.3.3:512

  route-target export 56595:512

  route-target import 56595:512

vlan 512

name test

!

!

!

!

interface Loopback0

ip address 172.16.3.3 255.255.255.255

ip ospf 1 area 0.0.0.0

!

interface Tunnel0

description PE3-to-PE2

ip unnumbered Loopback0

tunnel mode mpls traffic-eng

tunnel destination 172.16.2.2

tunnel mpls traffic-eng priority 1 1

tunnel mpls traffic-eng path-option 1 dynamic !

interface Tunnel1

description PE3-to-PE1

ip unnumbered Loopback0

tunnel mode mpls traffic-eng

tunnel destination 172.16.1.1

tunnel mpls traffic-eng priority 1 1

tunnel mpls traffic-eng path-option 1 dynamic !

interface GigabitEthernet0

ip address 46.226.1.178 255.255.255.248  speed auto  duplex auto  

negotiation auto !

interface GigabitEthernet0/1

no switchport

ip address 10.0.0.6 255.255.255.252

mpls traffic-eng tunnels

ip rsvp bandwidth percent 100

!

interface GigabitEthernet0/2

switchport access vlan 512

!

interface Vlan512

no ip address

member vfi lab

!

router ospf 1

router-id 172.16.3.3

network 10.0.0.4 0.0.0.3 area 0.0.0.0

mpls traffic-eng router-id Loopback0

mpls traffic-eng area 0.0.0.0

!

router bgp 56595

bgp log-neighbor-changes

bgp graceful-restart restart-time 120

bgp graceful-restart stalepath-time 360  bgp graceful-restart  no bgp 

default ipv4-unicast  neighbor 172.16.1.1 remote-as 56595  neighbor 

172.16.1.1 update-source Loopback0  neighbor 172.16.2.2 remote-as 56595  

neighbor 172.16.2.2 update-source Loopback0  !

address-family ipv4

  neighbor 172.16.1.1 activate

  neighbor 172.16.1.1 send-community extended

  neighbor 172.16.2.2 activate

  neighbor 172.16.2.2 send-community extended  exit-address-family  !

address-family vpnv4

  neighbor 172.16.1.1 activate

  neighbor 172.16.1.1 send-community extended

  neighbor 172.16.2.2 activate

  neighbor 172.16.2.2 send-community extended  exit-address-family  !

address-family l2vpn vpls

  neighbor 172.16.1.1 activate

  neighbor 172.16.1.1 send-community extended

  neighbor 172.16.1.1 suppress-signaling-protocol ldp

  neighbor 172.16.2.2 activate

  neighbor 172.16.2.2 send-community extended

  neighbor 172.16.2.2 prefix-length-size 2

  neighbor 172.16.2.2 suppress-signaling-protocol ldp  

exit-address-family

Tunnels are up in both directions.

Output of some commands as below

PE3#show l2vpn vfi name lab

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: lab, state: up, type: multipoint, signaling: BGP

  VPN ID: 512, VE-ID: 3, VE-SIZE: 11

  RD: 172.16.3.3:512, RT: 56595:512, 56595:512

  Bridge-Domain 512 attachment circuits:

    Vlan512

  Pseudo-port interface: pseudowire100001

  Interface          Peer Address    VE-ID  Local Label  Remote Label    S

PE1#show l2vpn vfi name lab

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: lab, state: down, type: multipoint, signaling: BGP

  VPN ID: 512, VE-ID: 1, VE-SIZE: 11

  RD: 172.16.1.1:512, RT: 56595:512, 56595:512

  Bridge-Domain 512 attachment circuits:

    Vlan512

  Pseudo-port interface: pseudowire100003

  Interface          Peer Address    VE-ID  Local Label  Remote Label    S

PE3#show bgp l2vpn vpls all

BGP table version is 28, local router ID is 172.16.3.3 Status codes: s 

suppressed, d damped, h history, * valid, > best, i - internal,

              r RIB-failure, S Stale, m multipath, b backup-path, f 

RT-Filter,

              x best-external, a additional-path, c RIB-compressed, 

Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V 

valid, I invalid, N Not found

     Network          Next Hop            Metric LocPrf Weight Path

Route Distinguisher: 172.16.1.1:512

*>i 172.16.1.1:512:VEID-1:Blk-1/136

                       172.16.1.1               0    100      0 ?

Route Distinguisher: 172.16.2.2:512

*>i 172.16.2.2:512:VEID-2:Blk-1/136

                       172.16.2.2                    100      0 i

*>i 172.16.2.2:512:VEID-2:Blk-1/136

                       172.16.2.2                    100      0 i

Route Distinguisher: 172.16.3.3:512

*>  172.16.3.3:512:VEID-3:Blk-1/136

                       0.0.0.0                            32768 ?

PE1# show bgp l2vpn vpls all

BGP table version is 39, local router ID is 172.16.1.1 Status codes: s 

suppressed, d damped, h history, * valid, > best, i - internal,

              r RIB-failure, S Stale, m multipath, b backup-path, f 

RT-Filter,

              x best-external, a additional-path, c RIB-compressed, 

Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V 

valid, I invalid, N Not found

     Network          Next Hop            Metric LocPrf Weight Path

Route Distinguisher: 172.16.1.1:512

*>  172.16.1.1:512:VEID-1:Blk-1/136

                       0.0.0.0                            32768 ?

Route Distinguisher: 172.16.2.2:512

*>i 172.16.2.2:512:VEID-2:Blk-1/136

                       172.16.2.2                    100      0 i

*>i 172.16.2.2:512:VEID-2:Blk-1/136

                       172.16.2.2                    100      0 i

Route Distinguisher: 172.16.3.3:512

*>i 172.16.3.3:512:VEID-3:Blk-1/136

                       172.16.3.3               0    100      0 ?

Nick

--

Nick Ryce

Fluency Communications Ltd.

e. nick at fluency.net.uk<mailto:nick at fluency.net.uk>

w. http://fluency.net.uk/

t. 0845 874 7000

_______________________________________________

cisco-nsp mailing list  cisco-nsp at puck.nether.net 

https://puck.nether.net/mailman/listinfo/cisco-nsp

archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________

cisco-nsp mailing list  cisco-nsp at puck.nether.net

https://puck.nether.net/mailman/listinfo/cisco-nsp

archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________

cisco-nsp mailing list  cisco-nsp at puck.nether.net

https://puck.nether.net/mailman/listinfo/cisco-nsp

archive at http://puck.nether.net/pipermail/cisco-nsp/