How does bgp-vpls save the need for xstp when dual-homing a customer to multiple pe's ? ( I assume you mean vpls w/bgp ad w/bgp sig) How does ldp-vpls *not* save the need for xstp when dual-homing a customer to multiple pe's ? (based on previous assumption, this means vpls w/bgp ad w/ldp sig)
Aaron -----Original Message----- From: Caillin Bathern [mailto:[email protected]] Sent: Monday, April 22, 2013 7:57 PM To: Adam Vitkovsky; Nick Ryce; Aaron; Waris Sagheer (waris); [email protected] Subject: RE: [c-nsp] BGP Signalled VPLS VPLS multihoming is the major up-shot of BGP-VPLS in my opinion. Saves the need for xSTP within your network when dual-homing a customer to multiple PEs which makes everybody happy. Caillin -----Original Message----- From: cisco-nsp [mailto:[email protected]] On Behalf Of Adam Vitkovsky Sent: Tuesday, 23 April 2013 12:36 AM To: 'Nick Ryce'; 'Aaron'; 'Waris Sagheer (waris)'; [email protected] Subject: Re: [c-nsp] BGP Signalled VPLS While we are on the topic what do you folks think about BGP signaled VPLS please? While I would prefer BGP in favor of LDP signaling as I believe it saves control plane overhead (1 BGP session VS n-1 LDP sessions), I have heard a valid objection as to why to run yet another functionality/feature (not tested by majority of operators) when the reliable and stable LDP functionality is enabled already anyways (for p2p PWs and base MPLS). adam -----Original Message----- From: cisco-nsp [mailto:[email protected]] On Behalf Of Nick Ryce Sent: Monday, April 22, 2013 3:48 PM To: Aaron; 'Waris Sagheer (waris)'; [email protected] Subject: Re: [c-nsp] BGP Signalled VPLS Hi Aaron, The VE ID etc is for BGP signalling. Nick -- Nick Ryce Fluency Communications Ltd. e. [email protected] w. http://fluency.net.uk/ t. 0845 874 7000 From: Aaron <[email protected]<mailto:[email protected]>> Date: Monday, 22 April 2013 14:28 To: "'Waris Sagheer (waris)'" <[email protected]<mailto:[email protected]>>, Nick Ryce <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [c-nsp] BGP Signalled VPLS I ran vpls w/bgp ad w/ldg sig between (2) asr9k's and (4) me3600's and I didn't have to use ve id nor ve range.. Is there something I would miss out on without using ve id or ve range? Also, is there a default value associated with ve id or ve range that was enacted in the absence of my not explicitly configuring it ? Waris, if the VE ID is for unique PE VPLS Edge ID assignment, would that mean that my configuration without the ve id configured would have duplicate VE ID's per PE? Or maybe there is a autoassignment thing that occurs. Perhaps I'll set it up again and see what happens, as I mentioned previously I had removed my vpls architecture for l3vpn preference. Aaron From: Waris Sagheer (waris) [mailto:[email protected]] Sent: Sunday, April 21, 2013 10:10 PM To: Nick Ryce; Aaron; [email protected]<mailto:[email protected]> Subject: Re: [c-nsp] BGP Signalled VPLS All PEs within a given VPLS are assigned a unique VPLS Edge device ID (VE ID). Nick is right about BGP NLRI, VPLS BGP NLRI (RFC 4761) AFI = 25 (L2VPN) SAFI = 65 (VPLS) VE ID VE Block Offset (VBO) VE Block Size (VBS) Label Base (LB) Best Regards, [http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg ] Waris Sagheer Technical Marketing Manager Service Provider Access Group [email protected]<mailto:[email protected]> Phone: +1 408 853 6682 Mobile: +1 408 835 1389 CCIE - 19901 [Think before you print.] 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 . From: Nick Ryce <[email protected]<mailto:[email protected]>> Date: Tuesday, April 16, 2013 7:52 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [c-nsp] BGP Signalled VPLS Its part for the BGP L2VPN NLRI as far as I'm aware. -- Nick Ryce Fluency Communications Ltd. e. [email protected]<mailto:[email protected]> w. http://fluency.net.uk/ t. 0845 874 7000 On 16/04/2013 15:50, "Aaron" <[email protected]<mailto:[email protected]>> wrote: Anyone know what and why to use this "ve" stuff? I didn't use it during my vpls (ios-ioxr) trial run in my network and never understood what it was for... ve id 1 ve range 11 Aaron -----Original Message----- From: cisco-nsp [mailto:[email protected]] On Behalf Of Nick Ryce Sent: Tuesday, April 16, 2013 7:41 AM To: Nick Ryce; [email protected]<mailto:[email protected]> Subject: Re: [c-nsp] BGP Signalled VPLS Apologies the attachment has went through. ASCII art as below PE1-------PE2--------PE3 PE1 and PE3 are ME3600's and PE2 is a Juniper SRX. >From PE2 labels are being pushed/popped correctly. Nick On 16/04/2013 13:37, "Nick Ryce" <[email protected]<mailto:[email protected]>> 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. [email protected]<mailto:[email protected]><mailto:[email protected]. uk> w. http://fluency.net.uk/ t. 0845 874 7000 _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.http://www.mailguard.com.au/mg _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
