Abstract:
A method of handling packets includes inserting a stack-specific tag into a packet, then processing the packet in a stack of network switches in accordance with tag information in the stack-specific tag. The stack-specific tag is then removed from the packet.
Abstract:
A network switch for network communications includes a protocol determining means for determining whether an incoming packet is an IP packet or an IPX packet. L3 lookup tables, IP router tables, and IPX router tables are provided. A concurrent lookup is performed of the L3 lookup table, and either the IP router table or the IPX router table, depending upon the determination of the packet type. If a match is found on the L3 table, the packet is forwarded based on the L3 match. If no match is found on the L3 lookup, then a longest prefix cache lookup is performed on the appropriate IP or IPX router table, and the packet is forwarded based upon the match of the longest prefix cache lookup. If no match is provided, then the packet is forwarded to the CPU interface.
Abstract:
A switch is configured to block packets from being transmitted through designated ports. The switch has port bitmap generator configured to obtain a port bitmap and a table is configured to store a block mask indicating which port the packet should not be transmitted. A block mask lookup is configured to determine the block mask for the packet from the table, and a transmit port bitmap generator is configured to determine which ports the packet should be transmitted using the port bitmap and the block mask.
Abstract:
A method for managing congestion in a stack of network switches includes the steps of receiving an incoming packet on a first port of a network switch for transmission to a destination port and determining if the destination port of the packet is a monitored port. Thereafter, the method determines a queue status of the destination port, if the destination port is determined to be a monitored port, and preschedules transmission of the incoming packet to the destination port if the destination port is determined to be a monitored port.
Abstract:
A network switch stack configuration includes a first network switch having a plurality of data ports, a first stacking port, and a first CPU interface. A second network switch has a plurality of data ports, a second stacking port, and a second CPU interface. A common CPU is connected to the first CPU interface and the second CPU interface, such that the first stacking port and the second stacking port are communicatively connected. Therefore incoming packets on any of the plurality of data ports on the first and second switches can be effectively switched to any of the plurality of data ports on either of the first and second network switches.
Abstract:
A network switch and a method thereof for network communications include a first data port interface and a second data port interface supporting a data port transmitting and receiving data at a first data rate and a second data rate, respectively. The switch has a CPU interface to communicate with a CPU and a memory management unit to communicate data from at least one of the first and second data port interfaces and a memory. The switch includes a communication channel communicating data and messaging information between the first and second data port interfaces and the memory management unit and lookup tables, including an address resolution lookup table and a VLAN table. The first or second data port interfaces determine an egress port for an incoming data packet from a search of the address resolution lookup table and the VLAN table using a VLAN ID from the incoming data packet.
Abstract:
A network switch for switching packets from a source to a destination includes a source port for receiving an incoming packet from a source, a destination port that contains a path to a destination for the packet, and a programmable counter unit for counting a number of packets of selected packet types which are received by the switch.
Abstract:
An apparatus provides an integrated single chip solution to solve Switching/Bridging, Security, Access Control, Bandwidth Management—Quality of Service issues, Roaming—Clean Hand off, Anticipatory Load Management, Location Tracking, Support for Revenue Generating Services—Fine grain QoS, Bandwidth Control, Billing and management. The architecture is such that it not only resolves the problems pertinent to WLAN it is also scalable and useful for building a number of useful networking products that fulfill enterprise security and wired and wireless networking needs. In accordance with a further aspect of the invention, the architecture supports stacking so as to enable the combining of two or more devices to create the equivalent of a single device with a larger port count, depending on system needs and preferences, while also providing support for services such as trunking, mirroring and QoS across all the ports.
Abstract:
An apparatus provides a hardware-based solution to enable roaming with session persistence within or between subnets. In accordance with a further aspect of the invention, one approach described herein is based on NAT/NAPT, while another uses aspects of Mobile IP. The architecture involved in both hardware approaches is such that it is scalable for implementation in a variety networking products that fulfill enterprise security and all possible combinations of wired and wireless networking needs, such as access points, access point concentrators, wireless-ready wiring closet or edge switches, and wireless co-processors.
Abstract:
A network switch for switching packets from a source to a destination includes a source port for receiving an incoming packet from a source, a destination port which contains a path to a destination for the packet, and a filter unit for constructing and applying a filter to selected fields of the incoming packet. The filter unit further includes filtering logic for selecting desired fields of the incoming packet and copying selected field information therefrom. The filtering logic also constructs a field value based upon the selected fields, and applies a plurality stored field masks on the field value. The switch additionally includes a rules table which contains a plurality of rules therein. The filtering logic is configured to perform lookups of the rules table in order to determine actions which must be taken based upon the result of a comparison between the field value and the stored filter masks and the rules table lookup.