Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Anders Löwinger]

On 2016-09-19 22:48, Peter Rathlev wrote:

Just to be crystal clear: Sup2T hardware and software fully supports
using same VLAN ID on different interfaces, and you can mix it with a
SVI for good measure. Nick Cutting posted a configuration snippet that
shows what can be done.


Ok missed that, and its great news!


The Sup2T certainly has shortcomings but this is not one of them.


Agree.

Anyone tried the sup6t? Any feedback?

/Anders

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Peter Rathlev]

On Mon, 2016-09-19 at 11:39 +0200, Anders Löwinger wrote:
> Sup2t has support in HW for using same VLAN-id on different L3 
> interfaces. Cisco has no SW to support it :(

Just to be crystal clear: Sup2T hardware and software fully supports
using same VLAN ID on different interfaces, and you can mix it with a
SVI for good measure. Nick Cutting posted a configuration snippet that
shows what can be done.

The Sup2T certainly has shortcomings but this is not one of them.

-- 
Peter

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Pavel Skovajsa]

It's a switch!
-pavel

On Mon, Sep 19, 2016 at 11:39 AM, Anders Löwinger  wrote:

> On 2016-09-19 10:19, Gert Doering wrote:
>
>> Things like that makes one wonder if Sup2T is intentionally trying to
>> kill the platform...  "too late, too limited, too stupid design decisions"
>> (like, the new netflow implementation "with MAC addresses").
>>
>
> Sup2t has support in HW for using same VLAN-id on different L3 interfaces.
> Cisco has no SW to support it :(
>
>
> /Anders
>
>
> ___
> cisco-nsp mailing list  cisco-nsp@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Anders Löwinger]

On 2016-09-19 10:19, Gert Doering wrote:

Things like that makes one wonder if Sup2T is intentionally trying to
kill the platform...  "too late, too limited, too stupid design decisions"
(like, the new netflow implementation "with MAC addresses").


Sup2t has support in HW for using same VLAN-id on different L3 
interfaces. Cisco has no SW to support it :(



/Anders

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Gert Doering]

Hi,

On Mon, Sep 19, 2016 at 09:52:33AM +0200, Peter Rathlev wrote:
> I haven't played with it, but the implementation on Sup2T seems quite
> limited. As a start you need to globally enable provider-bridge dot1ad
> mode, which is incompatible with using LACP.

Things like that makes one wonder if Sup2T is intentionally trying to 
kill the platform...  "too late, too limited, too stupid design decisions"
(like, the new netflow implementation "with MAC addresses").

gert
-- 
USENET is *not* the non-clickable part of WWW!
   //www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025g...@net.informatik.tu-muenchen.de


signature.asc
Description: PGP signature
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Patrick M. Hausen]

Good morning,

> Am 19.09.2016 um 09:52 schrieb Peter Rathlev :
> 
> On Sat, 2016-09-17 at 14:24 +0200, Łukasz Bromirski wrote:
>>> On 16 Sep 2016, at 17:32, Nick Cutting wrote:
>>> Depends on supervisor - With sup 2t - you could reuse vlans on
>>> subinterfaces, here is 2 subinterfaces on different ports, and an
>>> SVI all on vlan 281
>>> 
>>> !
>>> interface Vlan281
>>> no ip address
>>> shutdown
>>> end
>>> !
>>> interface TenGigabitEthernet2/5/9.281
>>> encapsulation dot1Q 281
>>> end
>>> !
>>> interface TenGigabitEthernet2/5/8.281
>>> encapsulation dot1Q 281
>>> end
>>  
>> That’s actually config that will work with all Supervisors, wrong
>> example :)
> 
> Nick is right, the config he showed would not work on Sup720 or
> earlier. And it wouldn't matter if VTP was enabled or not. If the VLAN
> exists "switched" then the first "encapsulation dot1q" command will be
> rejected with "Command rejected: VLAN  already in use by interface
> Vlan". Trying to create more than two subinterfaces using the same
> VLAN (on different interfaces of course) is rejected with "Command
> rejected: VLAN  not available".

Correct. My problem is that I have a new peering partner and his VLANs
are already in use on my side. On the "toy" platforms like 1812 or a FreeBSD
or Linux host it's straightforward to just create a subinterface with the 
appropriate
tags attached to the packets. So I thought I could do the same on my Cat6500.

I just found out about VLAN mapping:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/vlans.html#wp1044990

This *would* do the trick for me, if it wasn't for the fact that the mapping
is applied to all 12 ports in a port group. And since the VLAN is in use there
are of course ports where I don't want to map it ...

*argh* Can't they implement a single advanced feature in an unsurprising manner?

Thanks for all your help
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Cat6500 VLAN cannot be assigned to a routed port sub-if?

[Peter Rathlev]

On Sat, 2016-09-17 at 14:24 +0200, Łukasz Bromirski wrote:
> > On 16 Sep 2016, at 17:32, Nick Cutting wrote:
> > Depends on supervisor - With sup 2t - you could reuse vlans on
> > subinterfaces, here is 2 subinterfaces on different ports, and an
> > SVI all on vlan 281
> > 
> > !
> > interface Vlan281
> > no ip address
> > shutdown
> > end
> > !
> > interface TenGigabitEthernet2/5/9.281
> > encapsulation dot1Q 281
> > end
> > !
> > interface TenGigabitEthernet2/5/8.281
> > encapsulation dot1Q 281
> > end
> 
> That’s actually config that will work with all Supervisors, wrong
> example :)

Nick is right, the config he showed would not work on Sup720 or
earlier. And it wouldn't matter if VTP was enabled or not. If the VLAN
exists "switched" then the first "encapsulation dot1q" command will be
rejected with "Command rejected: VLAN  already in use by interface
Vlan". Trying to create more than two subinterfaces using the same
VLAN (on different interfaces of course) is rejected with "Command
rejected: VLAN  not available".

Sup2T doesn't have these problems.

> I understand Patrick is looking for a way to distinguish switched
> VLANs from routed VLANs, and indeed VLANs can be reused to forward
> different traffic with VLAN local significance on 6500/7600 starting
> from Sup2T.
> 
> For that (Patrick) needs bridge domains, so EVC infra - which is
> available on Sup2T with all ports, even with classical “LAN” cards -
> no SIPs needed.

I haven't played with it, but the implementation on Sup2T seems quite
limited. As a start you need to globally enable provider-bridge dot1ad
mode, which is incompatible with using LACP.

-- 
Peter

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Upgrading a C3750x-24T-S only works up to 15.2(1)E3

[Grischa Stegemann]

Hi Bjoern

Am 15.09.16 um 12:32 schrieb bjo...@verfriemelt.com:
> We have a stack of 2 C3750x-24T-S Switches and want to upgrade the IOS
> to support C3KX-NM-10G. I have successfully upgraded the member to
> 15.2(4)E2 but i have no success with the master. 

We had the very same issue with a 3750-X-stack and another 15 something
version two years ago. It's a horror scenario if you were planning a
"hitless rolling stack upgrade" and end up with a completely crashing
stack. :(


> Is there some hope?

We went through TAC and finally got the box replaced. I have no
knowledge of any other solution.

Grischa

-- 
Plus.line AG - https://www.plusline.net - Frankfurt am Main
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/