PW to EVPN-VPWS Seamless Migration

[Dhikra Marghli]

Hello

I have router NCS540 cisco as a  A-PE 

p2p EVPN

   interface <type_number>.<vlan_id>

   neighbor evpn evi <evi_id > service <service_id======>  what is the method can  allocate <evi_id > service <service_id>  for each service  ?? 

Please I  wait expert Service provider help me 

Thanks ina advance .

[Dhikra Marghli]

Hello 

I wait some one help me or can give me answer for this problem 

Thanks

[decode.chr13 · Accepted solution]

Hello 

EVI = EVPN instance. An EVI represents a VPN on a PE router. It serves the same role of an IP VPN Routing and Forwarding (VRF). Is a number between 1-65534 so you can choose it as customer AS Number or you can use an internal numbering system if you have/build one.

Service = Service ID. It's a number between 1-4294967294 and represents your pseudowire id (pw-id) for that attachment circuit id (ac-id). It's not compulsory, but it's better to have an internal numbering system considering that you have 10 digits there. For example: digit 1 = country, 2-3 = city, etc...

Hope it helps you

[Dhikra Marghli]

Hi

i wait your reply

thanks

[Dhikra Marghli]

Hello Decode ,

Thanks to reply me and also  for your answer .

example

we have service Internet in Access-PE1( NCS 540 cisco )and also in Access-PE2 ( NCS540 -Cisco ) so we want enable EVPN-VPWS  in both A-PE .

so  :

p2p EVPN

   interface <type_number>.<vlan_id>

   neighbor evpn evi <evi_id > service <service_id>======> First Question : according to your answer , evi-id for neigbor A-PE2 will be customer AS Number or between  64.512 – 65.534 – private AS numbers. ??? 

!===>  second question :==>Service ID !!! you say :  it's better to have an internal numbering system considering that you have 10 digits ?? i don't unterstand : we take service Internet !! 

please can you give me an an example !

Thanks i wait your reply and your answer from you 

!

evpn

 evi <evi-id>

  bgp

!

[decode.chr13 · Accepted solution]

Regarding EVI what I said is it can be ASN, not compulsory. You can invent internal numbering like customer1 = evi 101, customer 2 = evi 102 or whatever floats your boat.

Example:

A-PE1

p2p EVPN

   interface Te0/0/0/11.153

   neighbor evpn evi 65100 service 10111153 ! -> where (10111153 => 1 = location / 01 = a-pe1 / 11 = port 11 / 153 = vlan)

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

A-PE2

p2p EVPN

   interface Te0/0/0/7.209

   neighbor evpn evi 1855 service 10207209 ! -> where (10207209 => 1 = location / 02 = a-pe2 / 07 = port 7 / 209 = vlan)