Rt updating bgp 0 0 0 00
Each PE device is responsible for allocating customer Layer 2 frames to the appropriate VPWS and for proper forwarding to the intended destinations.
In essence, L2VPNs are virtual point-to-point circuit that use the underlying Transport Labels (LDP/RSVP) or a statically defined MPLS path to go between two PE’s, that allows the extension of a layer 2 broadcast domain.
The received LSP will be configured on the remote PE, so under set protocols connections remote-interface-switch site A interface xe-0/1/0.0 set protocols connections remote-interface-switch site A transmit-lsp to-site A set protocols connections remote-interface-switch site A receive-lsp to-Master show connections CCC and TCC connections [Link Monitoring On] Legend for status (St): Legend for connection types: UN -- uninitialized if-sw: interface switching NP -- not present rmt-if: remote interface switching WE -- wrong encapsulation lsp-sw: LSP switching DS -- disabled tx-p2mp-sw: transmit P2MP switching Dn -- down rx-p2mp-sw: receive P2MP switching - show mpls lsp Ingress LSP: 1 sessions To From State Rt P Active Path LSPname 192.168.2.2 192.168.2.1 Up 0 * to-site A to-site A Total 1 displayed, Up 1, Down 0 Egress LSP: 1 sessions To From State Rt Style Labelin Labelout LSPname 192.168.2.1 192.168.2.2 Up 0 1 FF 300080 - to-Master Total 1 displayed, Up 1, Down 0 Transit LSP: 0 sessions Total 0 displayed, Up 0, Down 0[email protected]:~$ ping -c 2 -q 192.168.137.3 PING 192.168.137.3 (192.168.137.3) 56(84) bytes of data.
--- 192.168.137.3 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.358/0.532/0.707/0.176 ms I had planned to have a wee bit more to this post, with what I was actually testing ,however, this is getting a bit longer than I expected, so I'll make this into a two-part 😉 My next post will detail, how you can use traffic engineering to manipulate a L2VPN path between 2 PE routers!
CCC needs to have a LSP for to transmit and another to receive traffic.
So firstly, we will need to get the LSPs configured.
The bulk and most depth of my testing was with that method…
I used set protocols bgp group Master type internal set protocols bgp group Master local-address 192.168.2.1 set protocols bgp group Master family inet unicast set protocols bgp group Master family inet6 unicast set protocols bgp group Master local-as 100 set protocols bgp group Master neighbor 192.168.2.2 set protocols bgp group Master neighbor 192.168.2.3set protocols isis reference-bandwidth 1000g set protocols isis level 1 disable set protocols isis level 2 wide-metrics-only set protocols isis interface xe-1/0/0.0 ldp-synchronization set protocols isis interface xe-1/0/0.0 point-to-point set protocols isis interface xe-1/0/0.0 link-protection set protocols isis interface xe-1/0/2.0 ldp-synchronization set protocols isis interface xe-1/0/2.0 point-to-point set protocols isis interface xe-1/0/2.0 link-protection set protocols isis interface xe-1/0/3.0 ldp-synchronization set protocols isis interface xe-1/0/3.0 point-to-point set protocols isis interface xe-1/0/3.0 link-protection set protocols isis interface lo0.0sset protocols ldp track-igp-metric set protocols ldp explicit-null set protocols ldp transport-address router-id set protocols ldp interface xe-1/0/0.0 set protocols ldp interface xe-1/0/2.0 set protocols ldp interface lo0.0 All configurations will be done on the Master and Site A, and for my examples I will show work done on the Master Instance. Let’s get cracking 😀 As stated before, BGP is used as the VPN signalling method, with that in mind, we will need to enable layer-2 signalling within MP-BGP. The RD has to be unique per device with RT matching on all devices within the L2VPN, this is important, so that traffic can be routed accordingly per site.
If you need multiple sites on the same layer 2 broadcast you will need to consider Virtual Private Lan Service (VPLS) or Ethernet VPN (EVPN).
Within Junos there are 3 ways of configuring L2VPNs, two are regarded as In our network, we use the Kompella style of L2VPNs.
In addition, routing-instance has to be set to set routing-instances Master instance-type l2vpn set routing-instances Master interface xe-0/1/0.0 set routing-instances Master route-distinguisher 101 set routing-instances Master vrf-target target:100 identifier must be unique to the entire site within the L2VPN as the site ID is used to compute label values for site-to-site communications.
The interface(s) have to be defined within l2vpn and l2vpn site stanzas.