I believe what everybody is trying to reference is actually the subspec contained in 802.3x, which is generally dealing with Full Duplex transmission. An optional subcomponent deals with flow control using "pause" frames. This appears in these links (watch wrap): http://www.ieng.com/univercd/cc/td/doc/cisintwk/ito_doc/ethernet .htm Search on "flow control" and here: http://www.cisco.com/warp/public/cc/so/neso/lnso/lnmnso/fesol_wp .htm The actual configuration steps can be found here for a CAT 1900: http://www.cisco.com/univercd/cc/td/doc/product/lan/28201900/192 8v9x/cli/part1.htm#xtocid1592737 a 2900/3500XL: http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/29_3 5xp/cmdref/macrcli.htm#xtocid397620 a 6500/XDI interface: http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sft_ 6_1/cmd_ref/set_po_r.htm#30647 HTH, Paul Werner > Guys, this "pause" frame does not appear to have anything whatsoever to > do > with flow control of data transmission. Unless I am blind as a bat I am > reading the link below to be referencing auto negotiation of links > between > NIC and switch or any device on a port and switch.. > > Look, if a switch cannot output data as fast as it comes in, and the > buffers > fill, then packets get dropped. Same as with a router. or a PC. ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
