![]() In this case anything coming in with a dot1q tag of 100 will be placed into vpn-id 1. This is then mapped to the vpn-id for the VPLS service. interface xe46.100 switchportĪgain, a switchport defined as an access-if-evpn is necessary. All that is necessary is to bind the mac vrf to the evpn vpn id. There is no end point defined as a xconnect. Host-reachability-protocol evpn-bgp ORANGE The BGP setup is the same so we’ll focus solely on the differences. Success! The CEs can reach each other over the EVPN-VPWS circuit. Since this is VPWS there are no macs learned on the device. VNID Interface VlanId In-VlanId Mac-Addr VTEP-Ip/ESI Type Status MAC mo The mac addresses are sent via an EVPN type-2 route between PEs. Network Next Hop Metric LocPrf Weight Path Peer Encap Origin codes: i - IGP, e - EGP, ? - incomplete Status codes: s suppressed, d damped, h history, a add-path, * valid, > best, i - internal, ipa.net#show bgp l2vpn evpn vrf BLUEīGP table version is 1, local router ID is 100.127.0.1 We can see the CE macs as mac-ip routes in evpn. The tunnels are up, installed, and ready for forwarding. Total number of entries are 1 .ipa.net#show evpn mpls xconnect tunnel VPN-ID EVI-Name MTU VPN-ID Source Destination PE-IP MTU Type NWġ00 - 1500 2 xe46.10 - Single Homed Port - 100.127.0.2 1500 AC-NW NW Anything arriving on xe46.10 with a dot1q tag of 10 is placed into this tunnel. This maps back to the EVPN mac-vrf via the xconnect. It has to be a switchport with a type of access-if-evpn. This is the remote PE vpn-id, in this case 2.įinally it is assigned to a switchport. Since this is VPWS it is considered a cross connect xconnect and a target is defined. These are global settings for the environment.įor the creation of the service we’ll start by making a mac vrf to generate the information needed to create a EVPN type 2 route (mac-ip). ipa.net:Įvpn mpls id 100 xconnect target-mpls-id 2ĮVPN MPLS has to be enabled. ! .ipa.net#show bgp l2vpn evpn summaryīGP router identifier 100.127.0.1, local AS number 65000 First we have to build an EVPN BGP session between the two routers. Next we can build EVPN on top of the underlay to begin delivering services. We can see both device’s node-sids in the label table on ipi-1. ![]() Now we can see that we have a clns/isis neighbor with ipi-2 as well as learned labels. O - OSPF/OSPF6 SR, i - ISIS SR, k - SR CLIĬode FEC/VRF/L2CKT ILM-ID In-Label Out-Label In-Intf Out-Intf/VRF Nexthop K - CLI ILM, T - MPLS-TP, s - Stitched ILMī - BGP, K - CLI, V - LDP_VC, I - IGP_SHORTCUT ipa.net xe48 3c2c.99c0.00aa Up 26 L1L2 IS-IS .ipa.net#show mpls ilm-tableĬodes: > - installed ILM, * - selected ILM, p - stale ILM System Id Interface SNPA State Holdtime Type Protocol ipa.net#show run isisįinally, we have to enable ISIS for segment routing. Additionally, we run mpls sr-prefer as this will prefer SR labels over LDP or RSVP-TE labels. Since our segment routing global block starts at 16000 the node-sid becomes 16101 as the index + the start of the SRGB defines the sid. We have to set an index to create the node-sid for this device. IGP and Label Distributionįirst let’s look at the IGP setup and label distribution as everything else will be built on top of this. We’re utilizing ISIS-SR as it is increasingly replacing LDP and RSVP-TE for label distribution. Since we’re looking at an MPLS data plane we will utilize ISIS-SR for MPLS. Lets take a look at basic EVPN-VPWS and EVPN-VPLS deployment. I recently discussed this on a podcast EVPN doesn’t need VxLAN if you want to know more on that topic. Don’t forget EVPN and VxLAN aren’t mutually exclusive, EVPN runs on and was originally designed for a MPLS data plane. IP Infusion just released OcNOS version 6.0 and the release notes, as well as press release, show a focus on EVPN with an MPLS data plane.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |