[j-nsp] tag-protocol-id matching in vlan-tags

[Derick Winkworth]

I wonder if you had the frame egress a trunk if you would see it dual tagged with 100/100, the expected outer-tag TPID, and the 0x8100 on the inner tag...

Derick Winkworth

CCIE #15672 (RS, SP), JNCIE-M #721

http://blinking-network.blogspot.com

--- On Thu, 7/28/11, David Ball <davidtball at gmail.com> wrote:

From: David Ball <davidtball at gmail.com>
Subject: Re: [j-nsp] tag-protocol-id matching in vlan-tags
To: "Addy Mathur" <addy.mathur at gmail.com>
Cc: "Juniper-Nsp" <juniper-nsp at puck.nether.net>
Date: Thursday, July 28, 2011, 10:27 AM

  Ah, so I'm potentially not crazy (at least not for this reason).
See below, and thanks...

David

--- JUNOS 10.0R3.10 built 2010-04-16 07:14:00 UTC

{master}
me at router> show interfaces ge-1/1/0
Physical interface: ge-1/1/0, Enabled, Physical link is Up
  Interface index: 173, SNMP ifIndex: 250
  Link-level type: 52, MTU: 9192, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE
Error: None,
  Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled,
Auto-negotiation: Disabled,
  Remote fault: Online, Speed-negotiation: Disabled, Auto-MDIX: Enabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  CoS queues     : 8 supported, 8 maximum usable queues
  Current address: 00:22:83:75:69:9c, Hardware address: 00:22:83:75:69:9c
  Last flapped   : 2011-07-26 15:43:39 MDT (1d 17:08 ago)
  Input rate     : 978417760 bps (96149 pps)
  Output rate    : 988075168 bps (96491 pps)
  Active alarms  : None
  Active defects : None

  Logical interface ge-1/1/0.100 (Index 113) (SNMP ifIndex 170)
    Description: 0x88A8 TPID test
    Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x88a8.100 ] In(pop) Out(push
0x88a8.100)
    Encapsulation: VLAN-CCC
    Input packets : 14161344641
    Output packets: 14161304171
    Protocol ccc, MTU: 9192

  Logical interface ge-1/1/0.32767 (Index 114) (SNMP ifIndex 171)
    Flags: SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ]  Encapsulation: ENET2
    Input packets : 0
    Output packets: 0
    Protocol multiservice, MTU: Unlimited
      Flags: None

{master}
me at router>


On 28 July 2011 04:54, Addy Mathur <addy.mathur at gmail.com> wrote:
> On Wednesday, July 27, 2011, David Ball <davidtball at gmail.com> wrote:
>> MX running 10.0 (DPCE-R-20GE-2XGE for int in question)
>>
>> Should I expect that a logical unit configured with 'vlan-tags outer
>> 0x88A8.100' would also permit frames using TPID 8100 and VLAN ID 100 ?
>>  I kinda expected not (since it doesn't 'match'), yet if I change my
>> test set to send normal 0x8100.100 frames, they're still accepted by
>> the interface (config below) and stuffed into the associated VPN.
>>
>> [edit interfaces ge-1/1/0]
>> flexible-vlan-tagging;
>> encapsulation flexible-ethernet-services;
>> gig-ether-options {
>>  no-auto-negotiation;
>>  ethernet-switch-profile {
>>    tag-protocol-id 0x88A8;
>>  }
>> }
>> unit 100 {
>>  encapsulation vlan-ccc;
>>  vlan-tags outer 0x88A8.100;
>>  input-vlan-map pop;
>>  output-vlan-map push;
>> }
>>
>>  Are my expectations that "specifying the TPID in the vlan-tags
>> statement would ONLY match frames with that TPID" wrong?  Practice
>> would indicate that I'm wrong, but I guess I'm wondering if this is
>> expected behaviour.
>
> David:  I don't believe your expectation is incorrect. Could you please post
> the exact JUNOS release (including minor version) and the output of "show
> interface ge-1/1/0"?
>
>>
>> TIA,
>>
>> David
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp