|
Posted by Sailing on August 7, 2006, 8:39 pm
If you were Registered and logged in, you could reply and use other advanced thread options
as we all know, the function of flow control can be set on a single
port.
but i'm wondering can it be applied to a trunk?
i feel the answer should be no, however, if we regard a trunk is a
logic link, confused...
|
 
| |
Posted by Rich Seifert on August 8, 2006, 11:31 am
If you were Registered and logged in, you could reply and use other advanced thread options
> as we all know, the function of flow control can be set on a single
> port.
> but i'm wondering can it be applied to a trunk?
> i feel the answer should be no, however, if we regard a trunk is a
> logic link, confused...
IEEE 802.3x (full-duplex flow control) resides (architecturally) below
the link aggregation sublayer. Thus, it applies only to an individual
port, and not to an aggregation (so-called "trunk group").
--
Rich Seifert Networks and Communications Consulting
21885 Bear Creek Way
(408) 395-5700 Los Gatos, CA 95033
(408) 228-0803 FAX
Send replies to: usenet at richseifert dot com
----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
|
|
Posted by Albert Manfredi on August 8, 2006, 12:19 pm
If you were Registered and logged in, you could reply and use other advanced thread options
>
>> as we all know, the function of flow control can be set on a single
>> port.
>> but i'm wondering can it be applied to a trunk?
>> i feel the answer should be no, however, if we regard a trunk is a
>> logic link, confused...
>
>
> IEEE 802.3x (full-duplex flow control) resides (architecturally) below
> the link aggregation sublayer. Thus, it applies only to an individual
> port, and not to an aggregation (so-called "trunk group").
You're probably right that the original post was referring to link
aggregation, but possibly he was referring to a trunk segment of a VLAN
setup?
I was thinking about VLANs when I first read the post. In which case,
flow control would work on trunk segments.
Bert
|
|
Posted by Sailing on August 9, 2006, 4:57 am
If you were Registered and logged in, you could reply and use other advanced thread options
Albert Manfredi wrote:
>
> >
> >> as we all know, the function of flow control can be set on a single
> >> port.
> >> but i'm wondering can it be applied to a trunk?
> >> i feel the answer should be no, however, if we regard a trunk is a
> >> logic link, confused...
> >
> >
> > IEEE 802.3x (full-duplex flow control) resides (architecturally) below
> > the link aggregation sublayer. Thus, it applies only to an individual
> > port, and not to an aggregation (so-called "trunk group").
>
> You're probably right that the original post was referring to link
> aggregation, but possibly he was referring to a trunk segment of a VLAN
> setup?
>
> I was thinking about VLANs when I first read the post. In which case,
> flow control would work on trunk segments.
>
> Bert
Thank you for your help...
well, what's the difference between "a trunk segment of a VLAN" and
link aggregation?
i don't think i have a clear idea referring to VLAN segment.
i looked up some documents and found the following definition:
a trunk link is a lan segment containing vlan-aware bridges and
vlan-aware end stations.
but can you explain it more explicately?
|
|
Posted by Albert Manfredi on August 9, 2006, 3:57 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> well, what's the difference between "a trunk segment of a VLAN" and
> link aggregation?
> i don't think i have a clear idea referring to VLAN segment.
> i looked up some documents and found the following definition:
> a trunk link is a lan segment containing vlan-aware bridges and
> vlan-aware end stations.
> but can you explain it more explicately?
Link aggegation is a scheme whereby you tie together multiple Ethernet
segments to behave as if it were only one, faster link. Typically,
between two switches. This technique is sometimes referred to as
"inverse multiplexing." This is described in 802.3-2005 Clause 43.
VLANs are described in 802.1Q. The idea is to have one physical Ethernet
(or other link layer) behave as if you had multiple Ethernets. By adding
overhead fields to the Ethernet frame, a VLAN trunk segment can carry
frames which are meant to belong to different LANs. Typically, these
trunk segments are only used between switches or routers, although in
principle they could also be used between two hosts, between hosts and
routers, between hosts and switches.
You're really doing two opposite things here. Either bundling multiple
physical Ethernet segments to behave as if they were one, or adding
overhead to Ethernet frames to allow a single segment to behave as if it
were multiple physcal Ethernet segments.
So how does this relate to flow cntrol. Flow control operates on
individual physical Ethernet segments, between switches, or between
switches and hosts. So flow control would not work if you have multiple
physical segments aggregated into a single trunk. There's no scheme (as
of now) to guarantee that the flow control operation can be synchronized
precisely among multiple Ethernet segments, which choreography would be
needed if you expect to be able to aggregate multiple segments. But
since flow control operates independently of the Ethernet data frames,
it should work just fine in a VLAN trunk example. Flow control doesn't
know or care whether that segment is pretending to be many different
segments. It just applies backpressure as buffers reach a certain level.
Bert
|
| Similar Threads | Posted | | Ethernet and Flow Control | June 30, 2006, 4:34 pm |
| Flow control frames: will I see them with tcpdump? | January 30, 2006, 10:05 am |
| Problem with PAUSE frames ethernet flow control | September 25, 2008, 7:09 am |
| are flow control and half-duplex support mandatory for gigabit Ethernet? | December 8, 2006, 10:29 am |
| some question about Trunk | May 15, 2006, 8:57 pm |
| redundant ports in trunk | January 10, 2006, 10:25 pm |
| Netgear and Cisco Trunk | May 3, 2007, 4:04 am |
| Help with VRRP and Vlan trunk | January 4, 2008, 9:50 am |
| configring trunk ports on Dell 6224 | March 8, 2007, 8:45 pm |
| To flow or not to flow | November 12, 2007, 8:48 am |
|
|
NewsGroups 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map