[c-nsp] config example xconnent between ASR9K and 6500

[Alejandro Aristizabal]

Hi !!!


My topology is in the attached file, please see attached file.


Description:

-I need to configure a service between SWL2 A and SWL2 B, as you can see 
in the figure SWL2 A is connected to a 6500, and SWL2 B
is in a L2 Ring (with MSTP protocol) where ASR9K is also part of it and 
the reason why ASR subinterface MUST be part of a bridge domain.



configuration is like this:

IOS:
interface GigabitEthernet4/24.70
  encapsulation dot1Q 70
  xconnect 10.248.10.7 70 encapsulation mpls
end


l2vpn
  xconnect group PRUEBA
   p2p ENSAYO
    interface GigabitEthernet0/0/0/2.70
    neighbor 172.31.171.254 pw-id 70




until here works, So the configuration you send me works, but then when 
ASR subtinterface cant be part of the bridge domian, when a try to 
configurate it doesnt let me do it.


RP/0/RSP0/CPU0:ASR9K_CALI(config)#l2vpn
RP/0/RSP0/CPU0:ASR9K_CALI(config-l2vpn)#bridge group BG_MST_VALLE
RP/0/RSP0/CPU0:ASR9K_CALI(config-l2vpn-bg)#  bridge-domain 
BD_MST-VALLE-VLAN-70
RP/0/RSP0/CPU0:ASR9K_CALI(config-l2vpn-bg-bd)#interface 
GigabitEthernet0/0/0/2.70
RP/0/RSP0/CPU0:ASR9K_CALI(config-l2vpn-bg-bd-ac)#commit
Wed Sep 20 16:42:10.751 gmt

% Failed to commit one or more configuration items during a 
pseudo-atomic operation. All changes made have been reverted. Please 
issue 'show configuration failed' from this session to view the errors

RP/0/RSP0/CPU0:ASR9K_CALI(config-l2vpn-bg-bd-ac)#show configuration failed
Wed Sep 20 16:42:21.645 gmt
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.


l2vpn
  bridge group BG_MST_VALLE
   bridge-domain BD_MST-VALLE-VLAN-70
    interface GigabitEthernet0/0/0/2.70
!!% Invalid argument: Interface already used for L2VPN



6500 has an  WS-SUP720-3B


how can I fix this issue ???

thanks every one !!!



El 20/09/17 11:05, David Wilkinson escribió:
> On 20/09/17 11:19, James Bensley wrote:
>> To make a point to point pseudowire from an ASR9K to a 6500 using
>> sub-interface you need config as follows;
>>
>> IOS-XR:
>> l2vpn
>>   xconnect group test-VC117
>>    p2p XR-to-IOS-vc117
>>     interface TenGigE0/0/0/3.3406
>>     neighbor ipv4 10.0.0.10 pw-id 117
>>
>>
>> interface TenGigE0/0/0/3.3406 l2transport
>>   description PERF-Link-Test:VC117
>>   encapsulation dot1q 3406
>>   rewrite ingress tag pop 1 symmetric
>>   mtu 1518
>>
>>
>> IOS:
>> interface GigabitEthernet2/8/30.3406
>>   description PERF-Link-Test:VC117
>>   encapsulation dot1Q 3406
>>   xconnect 10.0.0.11 117 encapsulation mpls
>>
>> This should work on a 6509-E type chasses with DFC4s et al. (SUP2T
>> etc). On older SUP720 I'm not sure. For some older Cisco devices like
>> 7200s they would negotiate to VC Type 4 by default and ASR9Ks use VC
>> type 5 by default. So in this case of a tagged sub-interfface you can
>> force either device to use VC-Type 4 or 5 to match the other using a
>> pseudowire-class and munge the MTU manually on the interfaces to match
>> within LDP.
>>
>> If you have this working on a 6500 with SUP720, what is the config you
>> have used please?
>>
>> Also what is the output from the following commands when you set up a
>> p2p pseudowire, not using a bridge domain:
>>
>> 6500: show mpls l2transport binding xxx
>> 6500: show mpls l2transport vc xxx detail
>> 9K: show l2vpn xconnect pw-id xxx detail
>>
> That should work on a SUP720, although I have only done a SUP720 
> subinterface in to a bridge domain on the ASR end.
> The ones which I have to an xconnect on the ASR end are to the whole 
> interface on the 6500 end.
>
> IOS-XR:
> l2vpn
>  bridge group test-VC117
>   bridge-domain XR-to-IOS-vc117
>    interface BVI3406
>    neighbor 10.0.0.10 pw-id 117
>
>
>
> IOS:
> interface GigabitEthernet2/8/30.3406
>  description PERF-Link-Test:VC117
>  encapsulation dot1Q 3406
>  xconnect 10.0.0.11 117 encapsulation mpls
>
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>


--