Transmit and Receive buffers are memory spaces allocated by a router or a switch to handle traffic bursts.
For example, traffic burst could be: all ports trying to send data to a single uplink port on a router/switch. When incoming/outgoing traffic exceeds physical capacity of a switch/router, buffering comes into action. Otherwise data would be dropped. Usually Tx/Rx buffers are implemented using a pool of [shared] memory.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Generally they are "special" queues to deal with packets/frames arriving on an interface or waiting to be transmitted on an interface. What's "special" about them is they often have special hardware support to insure a packet/frame is processed within the real-time requirements of the interface. Even something as "simple" as the console's serial port generally has special receive/transmit buffers, although for single characters.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...