Re: Pseudowire Headend (PWHE) - Configuration

tckoon · ‎11-01-2013

refer to following url for the configuration sample.

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.3/lxvpn/configuration/guide/vc43vpls.html#wp1323265

I would like to understand what is the purpose or explanation of the use of the generic-interface-list

It is a must to define generic-interface-list on interface pw-ether ?

generic-interface-list il1

interface gig0/1/0/0

interface gig0/2/0/0

generic-interface-list il2

interface gig0/1/0/1

interface gig0/2/0/1

interface pw-ether1

ipv4 address 10.1.1.2/24

attach generic-interface-list il1

interface pw-ether2

ipv4 address 10.1.2.2/24

attach generic-interface-list il2

l2vpn

xconnect group pwhe

p2p pwhe1

interface pw-ether1

neighbor 100.100.100.100 pw-id 1

p2p pwhe2

interface pw-ether2

neighbor 100.100.100.100 pw-id 2

mrboogieman · ‎11-28-2013

Hello, How you doing

As far as i know thegeneric-interface-list are used by the router as a reference when it needs to use some resources like for example queues (remember taht pw-ether interfaces support QoS ). And yes if you want to enable a xconnect you need this generic-interface-list attached to the pw-ether

For example if you have a generic-interface-list that doesn´t have any interface defined

RP/0/RSP0/CPU0:PE5-BNG-ASR9K#show run generic-interface-list

Thu Nov 28 16:26:41.372 UTC

generic-interface-list il1

!

then you attach it to the pw-ether

RP/0/RSP0/CPU0:PE5-BNG-ASR9K#show run interface pw-eth66

Thu Nov 28 16:26:50.108 UTC

interface PW-Ether66

mtu 1574

vrf PRIV5

ipv4 address 66.0.0.1 255.255.255.252

attach generic-interface-list il1

!

then configure a xconnect

!

xconnect group group3

p2p P2P3

interface PW-Ether66

neighbor ipv4 3.3.3.30 pw-id 321

pw-class pwclass1

!

RP/0/RSP0/CPU0:PE5-BNG-ASR9K#show l2vpn xconnect

Thu Nov 28 16:28:05.765 UTC

Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,

SB = Standby, SR = Standby Ready, (PP) = Partially Programmed

XConnect Segment 1 Segment 2

Group Name ST Description ST Description ST

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

group1 P2P1 UP BE1.200 UP 1.1.1.1 3210 UP

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

group3 P2P3 UR PE66 DN 3.3.3.30 321 UR // this neighbor doesn´t come up because the generic-interface-list doesn´t have any interface

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

but if you add any new interface to the generic-interface

RP/0/RSP0/CPU0:PE5-BNG-ASR9K(config)#generic-interface-list il1

RP/0/RSP0/CPU0:PE5-BNG-ASR9K(config-gen-if-list)#interface bundle-eth1

RP/0/RSP0/CPU0:PE5-BNG-ASR9K(config-gen-if-list)#

RP/0/RSP0/CPU0:PE5-BNG-ASR9K(config-gen-if-list)#commit

you can see this

RP/0/RSP0/CPU0:PE5-BNG-ASR9K#show l2vpn xconnect

Thu Nov 28 16:28:29.922 UTC

Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,

SB = Standby, SR = Standby Ready, (PP) = Partially Programmed

XConnect Segment 1 Segment 2

Group Name ST Description ST Description ST

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

group1 P2P1 UP BE1.200 UP 1.1.1.1 3210 UP

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

group3 P2P3 UP PE66 UP 3.3.3.30 321 UP // voila, now is up

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

Good luck

Sanjeewa Dharmasiri · ‎10-24-2017

Hi,

I have two queries.

1. Can we match tagged frames on PW-Ether interface like we do in regular L3 interface.

2. Can we attach multiple PW-Ether interfaces to the same xconnect group.

Thanks

Sanjeewa D.