tcsillag at interware
May 3, 2012, 7:18 AM
Post #6 of 6
It looks like it won't accept interfaces:
telnet [at] FastIro(config)#tag-type
telnet [at] FastIro(config)#tag-type 9100
telnet [at] FastIro(config)#tag-type 9100 eth 1 to 2
Invalid input -> eth 1 to 2 ?
I'll try the following setup:
- connect 2 cat2950 boxes to the FWS, and config 9100 as tag-type.
- config the uplink as trunk on the catalysts, but untagged on the FWS
- configure vlans on the catalysts and the FWS
If the catalysts see each other through the FWS, but don't see the FWS
itself, then it should be kinda QinQ, right?
On 05/03/2012 03:29 PM, Clayton Zekelman wrote:
> On a FESX424, the command would be:
> tag-type 9100 ethe 13 to 24
> Did you try that on the FWS?
> At 08:41 AM 03/05/2012, Tamas Csillag wrote:
>> On 05/03/2012 02:34 PM, Eric Helm wrote:
>>> On 5/2/2012 4:16 PM, Tamas Csillag wrote:
>>>> Dear All,
>>>> After exploring the possibilities of my FWS24 (kinda old, I know), I
>>>> found these options:
>>>> aggregated-vlan support for larger Ethernet frame up to 1530 bytes
>>>> tag-type Customize value used to indicate tagged VLAN port
>>>> Does this mean that this baby supports Q-in-Q?
>>>> Also, does anybody have an older FastIron config guide? Most stuff I
>>>> dig up is for the FWS624 and other newer switches.
>>> You can do it with the tag-type command. A caveat on the FastIron
>>> platform is that command applies to a port region, not just a single
>>> port. Port regions on those are 1-12 and 13-24 I believe.
>> That's what I gathered from the Fastiron config guides too, but the
>> command does not take an interface as an argument, just the integer,
>> tag-type <number> <cr>
>> So I assume it's for the whole system, then?
>> foundry-nsp mailing list
>> foundry-nsp [at] puck
> Clayton Zekelman
> Managed Network Systems Inc. (MNSi)
> 3363 Tecumseh Rd. E
> Windsor, Ontario
> N8W 1H4
> tel. 519-985-8410
> fax. 519-985-8409
foundry-nsp mailing list
foundry-nsp [at] puck