Marvell Israel (misl) Ltd.

Marvell International Limited

Marvellworld Trade Ltd.

Marvell Asia Pte., Ltd.

Marvell Semiconductor, Inc.

David Melman

Tal Mizrahi

Carmi Arad

Rami Zemach

Nafea Bishara

Tsahi Daniel

Nir Haim Arad

Ilan Yerushalmi

Ilan Mayer-Wolf

Martin Leslie White

Adar Peery

Nafea Bshara

Donald Robert Pannell

Uri Safrai

Lior Valency

Ronen Tausi

Dor Joseph Kampeas

Michael Orr

Zvi Shmilovici Leib

Yoram Revah

Ehud Sivan

Itay Peled

Gad Hutt

Ilan Mayer-wolf

Yosef Katan

Shmuel Melman

Eran Regev

Alex Kogan

Ilya Kharamatsky

Avin Faldu

In a network switching system that comprises a plurality of interconnected network devices, a first network device transmits one or more first packets via a first network interface of the first network device, the one or more first packets belonging to a packet flow. The first network device receives a message that indicates congestion corresponding to the packet flow within the network switching system. In response to the message, the first network device selects a second network interface of the first network device for transmitting one or more second packets that belong to the packet flow. After receiving the message, the first network device transmits the one or more second packets via the second network interface of the first network device.

Notification-based load balancing in a network

A network device includes a receive processor configured to store, in a packet memory, a payload of a packet received from a communication network. The network device also includes a packet processor configured to modify one or more fields of a header of the packet to generate a modified header, perform egress classification of the packet based on the modified header, and store the modified header in the packet memory. The network device further includes a transmit processor configured to transmit the packet in accordance with the egress classification. The transmit processor is configured to, in response to a decision that the packet is to be transmitted from the network device, generate a transmit packet from the payload retrieved from the packet memory and the modified header retrieved from the packet memory and cause the transmit packet to be transmitted to a destination in the communication network.

Egress packet processing using a modified packet header separate from a stored payload

A source switching device in a switching system receives information measured by a target switching device in the switching system. The information is indicative of an amount of data received in a given amount of time by the target switching device via each of two or more first links coupled to the target switching device. The source switching device determines, based at least in part on the information received from the target device, a path, from among multiple paths from the source switching device to the target switching device, for transmission of a packet flow directed to the target switching device. The source switching device transmits, via the determined path for transmission of the packet flow to the target device, one or more packets belonging to the packet flow.

Distributed dynamic load balancing in network systems

A network device includes a plurality of network interfaces configured to couple with a plurality of physical network links. A packet processor is configured to process packets received via the plurality of network interfaces. The packet processor includes a path selection engine that is configured to: for each of at least some packets processed by the packet processor, successively make path selection decisions that correspond to respective routing domains within a hierarchical communication network, the path selection decisions for forwarding the packet through the hierarchical communication network.

Hierarchical path selection in a communication network

Methods and systems are provided for processing a received packet based on associated state information. A packet processor of a network device receives a packet from a network. The received packet is classified as belonging to at least one respective identified flow from among a plurality of identified flows. For a respective received packet that belongs to an identified flow a current state value for the identified flow is ascertained based on a state table. The current state value is assigned to the respective received packet based on the current state value using the state table for the identified flow. A packet processing operation is subsequently performed on the respective received packet based in part on the state value of the identified flow to which the respective packet belongs.

Systems and methods for stateful packet processing

A method for managing an alert generated by a sensor of a security system that is associated with a property, the method comprises: receiving, by a server, a first indication about the alert; searching, by the server and in one or more data structures, for a validator that is associated with a validator address that is within a first predefined area that comprises a location of the property; sending, by the server, to a device of the validator, a validation request for validating the alert; and informing at least one entity out of a police and a central monitoring station about the alert after the validator validated the alert.

System and method for distributed security

A network device includes a packet processor that: determines at least one egress port via which a received packet is to be transmitted by the network device; modifies one or more fields in a header of the packet to generate a modified header; determines, based at least in part on the modified header, whether the packet a) is to be transmitted or b) is to be discarded; and stores the modified header in a packet memory. In response to the determination that the packet is to be transmitted, a transmit processor of the network device: retrieves a payload of the packet from the packet memory; retrieves the modified header from the packet memory; generates a transmit packet at least by combining the payload of the packet with the modified header; and transmits the transmit packet via the determined at least one egress port of the network device.

A switching system comprises a controlling switch and a plurality of port extenders. One of the port extenders includes: at least one upstream port; multiple downstream ports; and a forwarding engine. A forwarding database is populated with entries indicating associations between i) respective network addresses corresponding to devices coupled to downstream ports, and ii) respective local downstream ports. The forwarding database excludes entries corresponding to network addresses corresponding to devices coupled to the at least one upstream port. The forwarding engine is configured to: for a first packet received via one of the local downstream ports, and having a destination network address in the forwarding database, forward the first packet to a different local downstream port indicated by the forwarding database. For a second packet received via one of the local downstream ports, and having a destination network address not in the forwarding database, forward the second packet to the at least one upstream port.

Port extender with local switching

An apparatus for forwarding packets includes a packet processing pipeline having a processing unit that processes packets compliant with a recognized communication protocol. A first port coupled to the packet processing pipeline is configured to receive a packet that does not comply with the recognized communication protocol and has a header that conforms to a second communication protocol. A data extraction unit extracts first destination information from the header of the packet and, based on the first destination information, generates second destination information that conforms to the recognized communication protocol. The processing unit determines, based on the second destination information, an egress interface to which the packet is to be forwarded.

System and method for adapting a packet processing pipeline

A general load balancing value for a packet received by a network device is generated based at least in part on information in a header of the packet. The packet is directed to a network interface group comprising a set of network interfaces via which the packet can be transmitted towards a destination of the packet. A group-specific load balancing value for the packet is then determined based on group-specific load balancing configuration corresponding to the network interface group and is used to select a network interface, from among the set of network interfaces, and the packet is transmitted towards the destination of the packet via the selected network interface. The group-specific load balancing configuration corresponding to the network interface group is subsequently reconfigured to redistribute selection of network interfaces, among the set of network interfaces, for transmission of packets subsequently directed to the network interface group.

Group specific load balancing in network devices

A network device comprises time measurement units configured to measure receipt times and transmit times of packets received/transmitted via network interfaces. One or more memories store configuration information that indicates certain network interface pairs and/or certain packet flows that are enabled for latency measurement. A packet processor includes a latency monitoring trigger unit configured to select, using the configuration information, packets that are forwarded between the certain network interface pairs and/or that belong to the certain packet flows for latency monitoring. One or more latency measurement units determine respective latencies for packets selected by the latency monitoring trigger unit using respective receipt times and respective transmit times for the packets selected by the latency monitoring trigger unit, calculates latency statistics for the certain network interface pairs and/or the certain packet flows using the respective latencies, and stores the latency statistics in the one or more memories.

Latency monitoring for network devices

At least a payload of a packet that is received by a network device is stored in a packet memory. The packet is processed at least to determine at least one egress port via which the packet is to be transmitted, modify a header of the packet to generate a modified header, and determine, based at least in part on the modified header, whether the packet is to be transmitted or to be discarded by the network device. In response to determining that the packet is to be transmitted, the at least the payload of the packet is retrieved from the packet memory, a transmit packet is generated at least by combining the at least the payload of the packet with the modified header, and the transmit packet is transmitted via the determined at least one egress port of the network device.

Growing community of inventors

D.N. Bikat Beit Hakerem, Israel

David Melman