mkassawara at gmail
Mar 6, 2012, 5:14 AM
Post #8 of 8
Yes, because Cisco (and Juniper) use raw-mode (type 5) VLLs.
On Tue, Mar 6, 2012 at 3:08 AM, Matthew Walster <matthew [at] walster> wrote:
> Setting "tag-type tag2 ethe x/y" will allow tagged traffic to pass
> through a "regular" VLL (not raw-mode, IIRC) but from what I hear, it
> has interop issues with Cisco still.
> On 15 February 2012 00:44, Matt Kassawara <mkassawara [at] gmail> wrote:
>> Last I checked, setting tag1 to 9100 will pass tagged traffic through
>> a type 5 VLL. However, it also causes the ethertype to change on
>> ports not associated with the VLL.
>> On Tue, Feb 14, 2012 at 3:12 AM, <sam-ml [at] arahant> wrote:
>>> We had a similar problem, tried running VLL between a CER-RT (5.2) and a
>>> 7600 running SRE and later 15.x. As long as we put untagged traffic on the
>>> VLL everything worked fine, but 802.1q tagged traffic didn't pass even if
>>> we could see ARP. Brocade suggested to add the following lines to the
>>> tag-value tag2 9100
>>> tag-type cvlan tag2 svlan tag1 bvlan tag1
>>> however this didn’t work for us. We also asked if this will be fixed in
>>> the upcoming code, but apparently this is not going to happen due to an
>>> architectural limitation of the CER platform.
>>> foundry-nsp mailing list
>>> foundry-nsp [at] puck
>> foundry-nsp mailing list
>> foundry-nsp [at] puck
foundry-nsp mailing list
foundry-nsp [at] puck