From Sebastien.Roy@Sun.COM Fri Feb 6 14:32:34 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n16MWY09004145 for ; Fri, 6 Feb 2009 14:32:34 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n16MWXQF021340 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 6 Feb 2009 14:32:34 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEO00K011A9KS00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 14:32:33 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEO00AII1A9EQB0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 14:32:33 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n16MWWGb009135 for ; Fri, 06 Feb 2009 22:32:32 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEN00200ZW0LW00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:32:32 -0700 (MST) Received: from [192.168.1.5] ([unknown] [173.76.18.185]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEO004Z919OS210@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:32:13 -0700 (MST) Date: Fri, 06 Feb 2009 17:32:11 -0500 From: Sebastien Roy Subject: PSARC 2009/069 802.1Q tag mode link property Sender: Sebastien.Roy@Sun.COM To: PSARC-ext Message-id: <1233959531.19176.243.camel@seb> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Evolution 2.24.2 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 5027 802.1Q tag mode link property Release binding: Patch Interface Stability: Committed Related Case: PSARC 2006/358 VLAN Observability Enhancement Summary ------- This case introduces a GLDv3 link property named "tagmode" to control the conditions in which the kernel inserts VLAN tags in outgoing packets. Background ---------- The comprehensive VLAN tagging changes made by PSARC 2006/358 also fixed a bug that prevented Solaris from inserting a user priority tag (VLAN tag with NULL VLAN ID bug non-zero priority) when the sender specifies a priority for an outgoing packet over a physical Ethernet link. This bug was: 6434130 i_dls_ether_header() doesn't generate VLAN header when priority is non-zero As a result of this bug fix, when an application requests a user priority (either by using the DL_UDQOS_REQ DLPI primitive, by setting the dl_priority field of a DL_UNITDATA_REQ message, or by setting b_band on an M_DATA message) when sending a packet on a physical Ethernet link, the kernel will insert a VLAN header with a NULL VLAN ID and a priority as specified by the user. This new behavior is in-line with the 802.1Q IEEE specification. Bridges receiving such packets should recognize these as user-priority tagged packets and process the priority setting accordingly. Unfortunately, experience with this fix has uncovered that a number of widely used bridges (switches) don't handle these special user-priority tagged packets and simply drop them. This problem is documented in detail in the following CR: 6797256 GLD interfaces unexpectedly send VLAN tagged packets This issue, in combination with the fact that some widely deployed applications unconditionally request priority processing on all of their outgoing packets, means that these applications no longer work at all over physical Ethernet links connected to these problematic switches. Solution -------- This case introduces a link property (see dladm(1M)) named "tagmode" that controls the conditions in which the kernel will insert VLAN tags on packets being transmitted on the link. Two mode values can be assigned to this property: normal Insert a VLAN tag to outgoing packets as needed whenever requested. This includes two cases: 1. The packet belongs to a VLAN. 2. The user requested priority tagging. vlanonly Only insert a VLAN tag when the outgoing packet belongs to a VLAN. If a tag is being inserted in this mode and the user has also requested a non-zero priority, the priority is honored and included in the VLAN tag. Only DL_ETHER links will support this property, and its default value will be "vlanonly". Setting the property to "normal" demonstrates deliberate understanding that the feature is functional on the associated datalink. Impact On IFF_COS_ENABLED Flag ------------------------------ The IFF_COS_ENABLED flag documented as "Cos" in ifconfig(1M) reflects whether or not an interface supports a class of service marking (with 802.1D user priority marking being one example). This flag is currently set on all GLDv3 datalinks regardless of their ability to honor user priorities. One consumer of this flag is the IPQos functionality, which can be configured to request per-packet user priorities over CoS-capable interfaces (see ipqos(7ipp) and ipqosconf(1M)). It does this on IP interfaces that have the IFF_COS_ENABLED flag set. In order to accurately reflect the link's abilities to use priorities, this case changes the system such that the IFF_COS_ENABLED flag will only be set on VLAN links and on physical links that have their "tagmode" properties set to "normal". This will ensure that IPQos and other consumers of the IFF_COS_ENABLED flag do not erroneously request priorities over links that don't support them or have been explicitly configured to not use them. Change of System Default Behavior --------------------------------- The choice of "vlanonly" as the default value for the "tagmode" link property constitutes a change in behavior from how the system behaved after the fix to 6434130 was integrated. As previously mentioned, the fix to 6434130 caused the system to always insert a user-priority tag when requested. It will now only do so if the administrator explicitly changes the "tagmode" property to have the value "normal". The fix to 6434130 was included with s10u7, and prior to that, most drivers (including all GLDv2 and GLDv3 drivers) failed to insert user-priority tags. Since 6434130 has no external customer records, one can thus assume that no-one noticed that this was broken, and so reverting the system default behavior back to its prior state will not be disruptive. The dladm(1M) man page will be updated to document the "tagmode" link property, and the "CoS" section of the ifconfig(1M) man page will be modified to describe how to enable "CoS" using the "tagmode" property. From Sebastien.Roy@sun.com Fri Feb 6 14:35:53 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n16MZrm4004357 for ; Fri, 6 Feb 2009 14:35:53 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n16MZlie003394 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 6 Feb 2009 14:35:53 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEO004071FRJ800@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:35:51 -0700 (MST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEO001RS1FRKE20@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:35:51 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n16MZp4g024903 for ; Fri, 06 Feb 2009 22:35:51 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEO00B001A34Y00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:35:51 -0700 (MST) Received: from [192.168.1.5] ([unknown] [173.76.18.185]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEO004N51FQS230@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:35:51 -0700 (MST) Date: Fri, 06 Feb 2009 17:35:49 -0500 From: Sebastien Roy Subject: Re: PSARC 2009/069 802.1Q tag mode link property In-reply-to: <1233959531.19176.243.camel@seb> Sender: Sebastien.Roy@sun.com To: PSARC-ext Message-id: <1233959749.19176.244.camel@seb> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Evolution 2.24.2 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1233959531.19176.243.camel@seb> Status: RO Content-Length: 197 On Fri, 2009-02-06 at 17:32 -0500, Sebastien Roy wrote: > 802.1Q tag mode link property > I forgot to mention that I'm sponsoring this case for myself, and it times out on February 13th. -Seb From carlsonj@phorcys.east.sun.com Fri Feb 6 14:41:36 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n16Mfado004562 for ; Fri, 6 Feb 2009 14:41:36 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n16MfZd1025523; Fri, 6 Feb 2009 14:41:35 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEO005011PB5M00@brm-avmta-1.central.sun.com>; Fri, 06 Feb 2009 15:41:35 -0700 (MST) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEO0019F1PAKE30@brm-avmta-1.central.sun.com>; Fri, 06 Feb 2009 15:41:34 -0700 (MST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n16MfUug026629; Fri, 06 Feb 2009 17:41:30 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n16MfU4Q026626; Fri, 06 Feb 2009 17:41:30 -0500 (EST) Date: Fri, 06 Feb 2009 17:41:30 -0500 From: James Carlson Subject: Re: PSARC 2009/069 802.1Q tag mode link property In-reply-to: <1233959749.19176.244.camel@seb> To: Sebastien Roy Cc: PSARC-ext Message-id: <18828.48282.25907.648565@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1233959531.19176.243.camel@seb> <1233959749.19176.244.camel@seb> Status: RO Content-Length: 451 Sebastien Roy writes: > On Fri, 2009-02-06 at 17:32 -0500, Sebastien Roy wrote: > > 802.1Q tag mode link property > > > > I forgot to mention that I'm sponsoring this case for myself, and it > times out on February 13th. +1 -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From gdamore@sun.com Fri Feb 6 14:47:55 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n16MltHO005882 for ; Fri, 6 Feb 2009 14:47:55 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n16Mlq2k009825 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 6 Feb 2009 14:47:55 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEO0050P1ZURY00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:47:54 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEO001D61ZSK730@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 15:47:53 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n16MlqxY011107 for ; Fri, 06 Feb 2009 14:47:52 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEO00D001VCVJ00@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 14:47:52 -0800 (PST) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEO007QS1ZLHS20@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 06 Feb 2009 14:47:46 -0800 (PST) Date: Fri, 06 Feb 2009 14:47:45 -0800 From: "Garrett D'Amore" Subject: Re: PSARC 2009/069 802.1Q tag mode link property In-reply-to: <1233959531.19176.243.camel@seb> Sender: Garrett.Damore@sun.com To: Sebastien Roy Cc: PSARC-ext Message-id: <498CBE11.8020900@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1233959531.19176.243.camel@seb> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 5499 +1. Thanks for the detailed write up. (And, btw, -1 to the applications that assume QoS is always present, and -1 to the switch vendors that still haven't got tagged packet processing in their products. :-) -- Garrett Sebastien Roy wrote: > 802.1Q tag mode link property > > Release binding: Patch > Interface Stability: Committed > Related Case: PSARC 2006/358 VLAN Observability Enhancement > > Summary > ------- > > This case introduces a GLDv3 link property named "tagmode" to > control the conditions in which the kernel inserts VLAN tags in > outgoing packets. > > Background > ---------- > > The comprehensive VLAN tagging changes made by PSARC 2006/358 also > fixed a bug that prevented Solaris from inserting a user priority > tag (VLAN tag with NULL VLAN ID bug non-zero priority) when the > sender specifies a priority for an outgoing packet over a physical > Ethernet link. This bug was: > > 6434130 i_dls_ether_header() doesn't generate VLAN header when > priority is non-zero > > As a result of this bug fix, when an application requests a user > priority (either by using the DL_UDQOS_REQ DLPI primitive, by > setting the dl_priority field of a DL_UNITDATA_REQ message, or by > setting b_band on an M_DATA message) when sending a packet on a > physical Ethernet link, the kernel will insert a VLAN header with a > NULL VLAN ID and a priority as specified by the user. > > This new behavior is in-line with the 802.1Q IEEE specification. > Bridges receiving such packets should recognize these as > user-priority tagged packets and process the priority setting > accordingly. > > Unfortunately, experience with this fix has uncovered that a number > of widely used bridges (switches) don't handle these special > user-priority tagged packets and simply drop them. This problem is > documented in detail in the following CR: > > 6797256 GLD interfaces unexpectedly send VLAN tagged packets > > This issue, in combination with the fact that some widely deployed > applications unconditionally request priority processing on all of > their outgoing packets, means that these applications no longer work > at all over physical Ethernet links connected to these problematic > switches. > > > Solution > -------- > > This case introduces a link property (see dladm(1M)) named "tagmode" > that controls the conditions in which the kernel will insert VLAN > tags on packets being transmitted on the link. Two mode values can > be assigned to this property: > > normal Insert a VLAN tag to outgoing packets as needed > whenever requested. This includes two cases: > > 1. The packet belongs to a VLAN. > 2. The user requested priority tagging. > > vlanonly Only insert a VLAN tag when the outgoing packet > belongs to a VLAN. If a tag is being inserted in this > mode and the user has also requested a non-zero > priority, the priority is honored and included in the > VLAN tag. > > Only DL_ETHER links will support this property, and its default > value will be "vlanonly". Setting the property to "normal" > demonstrates deliberate understanding that the feature is functional > on the associated datalink. > > Impact On IFF_COS_ENABLED Flag > ------------------------------ > > The IFF_COS_ENABLED flag documented as "Cos" in ifconfig(1M) > reflects whether or not an interface supports a class of service > marking (with 802.1D user priority marking being one example). This > flag is currently set on all GLDv3 datalinks regardless of their > ability to honor user priorities. > > One consumer of this flag is the IPQos functionality, which can be > configured to request per-packet user priorities over CoS-capable > interfaces (see ipqos(7ipp) and ipqosconf(1M)). It does this on IP > interfaces that have the IFF_COS_ENABLED flag set. > > In order to accurately reflect the link's abilities to use > priorities, this case changes the system such that the > IFF_COS_ENABLED flag will only be set on VLAN links and on physical > links that have their "tagmode" properties set to "normal". This > will ensure that IPQos and other consumers of the IFF_COS_ENABLED > flag do not erroneously request priorities over links that don't > support them or have been explicitly configured to not use them. > > Change of System Default Behavior > --------------------------------- > > The choice of "vlanonly" as the default value for the "tagmode" link > property constitutes a change in behavior from how the system > behaved after the fix to 6434130 was integrated. As previously > mentioned, the fix to 6434130 caused the system to always insert a > user-priority tag when requested. It will now only do so if the > administrator explicitly changes the "tagmode" property to have the > value "normal". > > The fix to 6434130 was included with s10u7, and prior to that, most > drivers (including all GLDv2 and GLDv3 drivers) failed to insert > user-priority tags. Since 6434130 has no external customer records, > one can thus assume that no-one noticed that this was broken, and so > reverting the system default behavior back to its prior state will > not be disruptive. > > The dladm(1M) man page will be updated to document the "tagmode" > link property, and the "CoS" section of the ifconfig(1M) man page > will be modified to describe how to enable "CoS" using the "tagmode" > property. > > > From Richard.Matthews@sun.com Wed Feb 11 08:19:18 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1BGJHWh009310 for ; Wed, 11 Feb 2009 08:19:17 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1BGJGq0030477 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 11 Feb 2009 09:19:17 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEW00709TC39D00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 08:19:15 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEW003YJTC3I990@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 08:19:15 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1BGJF5J027466 for ; Wed, 11 Feb 2009 16:19:15 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEW00600SITYA00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 09:19:15 -0700 (MST) Received: from [129.152.9.14] ([unknown] [129.152.9.14]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEW00D37TBVHZ40@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 09:19:08 -0700 (MST) Date: Wed, 11 Feb 2009 10:19:06 -0600 From: Rick Matthews Subject: Re: PSARC 2009/069 802.1Q tag mode link property In-reply-to: <1233959531.19176.243.camel@seb> Sender: Richard.Matthews@sun.com To: Sebastien Roy Cc: PSARC-ext Reply-to: Richard.Matthews@sun.com Message-id: <4992FA7A.10000@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1233959531.19176.243.camel@seb> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 624 A nit question: Is there the means to determine a dropped packet occurred due to the user priority tag, and automatically setting the tagmode to vlanonly? -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From Sebastien.Roy@sun.com Wed Feb 11 08:23:53 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1BGNqwN009878 for ; Wed, 11 Feb 2009 08:23:53 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1BGNpQf022120 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 11 Feb 2009 08:23:52 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEW00707TJRPB00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 09:23:51 -0700 (MST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEW004NJTJQ9O30@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 09:23:50 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1BGNoP4016238 for ; Wed, 11 Feb 2009 16:23:50 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEW00E00OC7UD00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 09:23:50 -0700 (MST) Received: from [129.148.174.103] ([unknown] [129.148.174.103]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEW00G05TJPAF40@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 09:23:50 -0700 (MST) Date: Wed, 11 Feb 2009 11:23:36 -0500 From: Sebastien Roy Subject: Re: PSARC 2009/069 802.1Q tag mode link property In-reply-to: <4992FA7A.10000@Sun.COM> Sender: Sebastien.Roy@sun.com To: Richard.Matthews@sun.com Cc: PSARC-ext Message-id: <1234369416.20937.8.camel@strat> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Evolution 2.24.2 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1233959531.19176.243.camel@seb> <4992FA7A.10000@Sun.COM> Status: RO Content-Length: 328 On Wed, 2009-02-11 at 10:19 -0600, Rick Matthews wrote: > A nit question: Is there the means to determine a dropped packet occurred > due to the user priority tag, and automatically setting the tagmode to > vlanonly? Unfortunately no. There is no way to know the reason why a down-stream bridge has dropped a packet. -Seb From Sebastien.Roy@sun.com Wed Feb 11 10:51:11 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1BIpAjW010435 for ; Wed, 11 Feb 2009 10:51:11 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n1BIp6rC029802 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 12 Feb 2009 02:51:09 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEX00H0V0CQ1700@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 10:50:50 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEX00KYU0CP1WE0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 10:50:50 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1BIonNQ028267 for ; Wed, 11 Feb 2009 18:50:49 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEX0050005LHR00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 11:50:49 -0700 (MST) Received: from [129.148.174.103] ([unknown] [129.148.174.103]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEX00L7W0CMYHB0@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 11 Feb 2009 11:50:47 -0700 (MST) Date: Wed, 11 Feb 2009 13:50:34 -0500 From: Sebastien Roy Subject: Re: PSARC 2009/069 802.1Q tag mode link property In-reply-to: <1233959531.19176.243.camel@seb> Sender: Sebastien.Roy@sun.com To: PSARC-ext Message-id: <1234378234.20937.19.camel@strat> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Evolution 2.24.2 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1233959531.19176.243.camel@seb> Status: RO Content-Length: 61 This case was approved during today's PSARC business. -Seb