[c-nsp] 7600 layer 2 local switching: EVC to SVI

[Arie Vayner (avayner)]

Tassos,

I do not think so, as the SVI would be the local switching/mac learning
resource in this case...
On 7600 any service which requires L2 switching (and/or L3 routing)
requires an SVI. Even if you configure a layer 3 sub-interface, an
internal SVI is allocated...

Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tassos
Chatzithomaoglou
Sent: Saturday, February 04, 2012 10:36
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 7600 layer 2 local switching: EVC to SVI

Similar to this case, is there a way (or any future plans) to connect an
EVC directly to a VFI?
Currently i'm using EVC => SVI => VFI, but i would like to avoid the
intermediate step, something that ASR9k can already do.

--
Tassos


Jason Lixfeld wrote on 3/2/2012 23:24:
> Ah-so.  This worked like a charm.  Thanks Arie (and other off-list
replies that eluded to the same thing).
>
> On 2012-02-03, at 2:45 PM, Arie Vayner (avayner) wrote:
>
>> Jason,
>>
>> The local connect option ("connect ..." CLI) is used to connect 2 
>> EVCs together, without a shared SVI between them.
>> This is basically the local alternative of a p2p xconnect.
>>
>> If you want to use local switching, through an SVI (mac learning etc,

>> but allows also using non-EVC access ports), you just use the 
>> "bridge-domain VLAN-ID" command inside both EVCs.
>>
>> Arie
>>
>> -----Original Message-----
>> From: cisco-nsp-bounces at puck.nether.net 
>> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jason Lixfeld
>> Sent: Friday, February 03, 2012 20:37
>> To: cisco-nsp at puck.nether.net
>> Subject: [c-nsp] 7600 layer 2 local switching: EVC to SVI
>>
>> I'm planning to upgrade a 7600/Sup720 from 12.2(33)SRC4 to 
>> 12.2(33)SRE5 and in the process migrate some carrier connections to 
>> EVCs which will require layer 2 local switching to connect the 
>> locally significant VLAN ID of the EFP to the global VLAN.
>>
>> The command set between SRC and SRE seems to differ somewhat and I'm 
>> having a hard time getting EVC to SVI based local switching working.

>> On another 7600, I'm running an engineering build of SRE that was 
>> provided to me by my SE to test a commit for an outstanding bug.  I 
>> was hoping this other device and engineering build would be adequate 
>> to use as an SRE test bed.  The engineering build seems to be based 
>> on the Advanced Enterprise Services feature set, not the Advanced IP 
>> Services feature set that we will actually be using.
>>
>> I'm trying to lab up the EVC to SVI local switching config, but it's 
>> giving me problems and I'm not sure if it's the engineering build 
>> that is causing me grief or if what I want to do just won't work.  As

>> you can imagine, I'd like to try and get this all proved out ahead of

>> time so there are no gotchas during the upgrade.
>>
>> The issue I'm running into in the engineering build is that the 
>> parser is expecting a service instance identifier after the VLAN 
>> identifier, which doesn't jive; can't make an EFP on an SVI:
>>
>> 7600#sh run int g7/0/0
>> Building configuration...
>>
>> Current configuration : 238 bytes
>> !
>> interface GigabitEthernet7/0/0
>> description NNI Testing Port
>> mtu 9216
>> no ip address
>> speed 1000
>> mls qos trust dscp
>> no cdp enable
>> service instance 100 ethernet
>>   encapsulation dot1q 100
>>   rewrite ingress tag pop 1 symmetric !
>> end
>>
>> 7600#sh run int vlan 100
>> Building configuration...
>>
>> Current configuration : 40 bytes
>> !
>> interface Vlan100
>> no ip address
>> end
>>
>> 7600#conf t
>> Enter configuration commands, one per line.  End with CNTL/Z.
>> 7600(config)#connect test gi7/0/0 100 vlan 100 ?
>>   <1-4294967295>   Service Instance Identifier
>>
>> 7600(config)#
>>
>> The SRC parser seems to think different:
>>
>> 7600#sh run int g7/0/17
>> Building configuration...
>>
>> Current configuration : 227 bytes
>> !
>> interface GigabitEthernet7/0/17
>> description NNI Testing Port
>> mtu 9216
>> no ip address
>> mls qos trust dscp
>> no cdp enable
>> service instance 100 ethernet
>>   encapsulation dot1q 100
>>   rewrite ingress tag pop 1 symmetric !
>> end
>>
>> 7600#sh run int vlan 100
>> Building configuration...
>>
>> Current configuration : 40 bytes
>> !
>> interface Vlan100
>> no ip address
>> end
>>
>> 7600#conf t
>> Enter configuration commands, one per line.  End with CNTL/Z.
>> 7600(config)#connect test gi7/0/17 100 vlan 100 ?
>>   <1-4294967295>   Service Instance Identifier
>>   interworking    Configure Interworking Type for this connection
>>
>> 7600(config)#connect test gi7/0/17 100 vlan 100 interworking ethernet

>> 7600(config-connection)#
>>
>> Anyone know if production SRE5 Advanced IP Services is similar to 
>> what works in SRC?
>>
>> Thanks in advance.
>> _______________________________________________
>> 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/
>
> _______________________________________________
> 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/
>
_______________________________________________
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/