hi benedikt,
I did some extra checking. since we can only do type5 PW for PWHE and BNG, it means that it expects a C-tag.
the main interface, untagged, can't therefore accept a control policy (blocked in cli), an l2transport untagged efp will not appreciate a control policy because it is l3 config (that is not allowed on EFP's).
I am trying to find out if there is another work around than this:
make an untagged EFP on the PWHE:
interface PW-Ether60.1 l2transport
encapsulation untagged
put that EFP in an xconnect with a local interface:
l2vpn
xconnect group hey
p2p there
interface PW-Ether60.1
interface TenGigE0/2/0/22.1 << also an untagged EFP
!
define the EFP for the local interface. either we add a vlan and pop the tag or we can use untagged here for the efp also.
int te 0/2/0/22.1 l2trans
encap dot1q 10
rewrite ingress tag pop 1 sym
connect the port 22 in this example to another interface on the same linecard or somewhere on the card, say port 23.
then on port 23's subinterface (if using vlan imposition) or the main interface (if remain untagged) we'll apply the subscriber config:
int te 0/2/0/23.1
encap dot1q 10
ipv4 point
ipv4 unn loop <>
service-policy type control subscriber BLABLA
bba-group etc.
Can you let us know what linecards on the 7600 you have to see if we can do tag imposition there via a direct imposition or a tag dot1q native (so untagged packet are getting the native vlan tag).
Separately I will see if we can open up the untagged pw-ether interface for bng.
cheers!
xander
