Abstract: A method and a network device for sharing bandwidth among a group of classes of traffic for an interface are provided. Bandwidth may be allocated to at least one traffic class of a first priority for the interface. At least some unused bandwidth of the at least one traffic class may be allocated to at least one other traffic class of a second priority for the interface. In some implementations, weighted constituents may be allocated unused interface bandwidth based on an assigned weight of each of the weighted constituents of the interface.

Abstract: A method and a network device for sharing bandwidth among a group of classes of traffic for an interface are provided. Bandwidth may be allocated to at least one traffic class of a first priority for the interface. At least some unused bandwidth of the at least one traffic class may be allocated to at least one other traffic class of a second priority for the interface. In some implementations, weighted constituents may be allocated unused interface bandwidth based on an assigned weight of each of the weighted constituents of the interface.

Abstract: A method and a network device for sharing bandwidth among a group of classes of traffic for an interface are provided. Bandwidth may be allocated to at least one traffic class of a first priority for the interface. At least some unused bandwidth of the at least one traffic class may be allocated to at least one other traffic class of a second priority for the interface. In some implementations, weighted constituents may be allocated unused interface bandwidth based on an assigned weight of each of the weighted constituents of the interface.

Abstract: A network bridge/router for identifying a data unit to be routed by a network bridge/router, for identifying a protocol associated with the received data unit to be routed, and for carrying out appropriate data unit transfer operations, all in hardware. A Receive Header Processor (RHP) analyzes the destination address of the received data unit, in hardware, for determining if routing or bridging is required. If routing is required, the RHP uses portions of the received data unit header as a compare value against predefined values stored in data structures which provide a protocol ID identifying the protocol of the received data unit and serving as an index to the appropriate microcode handling routine, executed by the RHP, for the data unit. The handling routine causes the RHP to forward data unit identifying information appropriate to the identified protocol and obtained from the received data unit to further hardware-based data unit processing elements.

Abstract: At least a portion of the data units in a bridge/router are processed by logic circuits according to cast type. The cast type, source address and destination address of an incoming data unit are determined by examining the header. For a unicast data unit, the source address and destination address are employed to obtain a transmit port indicator from memory, and the unicast data unit is directed to the port indicated by the transmit port indicator. For a non-unicast data unit, the source address and destination address are employed to obtain a first port mask that indicates valid ports for receipt of the data unit and a second port mask that indicates valid ports for transmission of the data unit from memory. The first and second port masks are combined to generate a third port mask, and the non-unicast data unit is directed to the ports indicated by the third port mask.

Abstract: Logic circuits are employed in a telecommunications bridge/router device to examine a received frame to determine which VLAN, if any, the frame is associated with. The protocol type, receive port identification, and receive VLAN tag are employed to determine the transmit port identification and transmit VLAN tag. A predefined table indicates which ports within the bridge/router are associated with the VLAN. The frame is excluded from transmission through the ports that are not associated with members of the respective the VLAN.