Messaging between remote controller and forwarding element

Abstract

Some embodiments of the invention provide a forwarding element that can be configured through in-band data-plane messages from a remote controller that is a physically separate machine from the forwarding element. The forwarding element of some embodiments has data plane circuits that include several configurable message-processing stages, several storage queues, and a data-plane configurator. A set of one or more message-processing stages of the data plane are configured (1) to process configuration messages received by the data plane from the remote controller and (2) to store the configuration messages in a set of one or more storage queues. The data-plane configurator receives the configuration messages stored in the set of storage queues and configures one or more of the configurable message-processing stages based on configuration data in the configuration messages.

Description

BACKGROUND

Today, forwarding elements commonly have control and data plane components. A forwarding element's control plane component often provides the interface for configuring the components of the data plane, while the data plane handles the forwarding of the data messages that the forwarding element receives. The data plane is often referred to as the forwarding plane. The data plane often is a custom-made application specific integrated circuit (ASIC) that includes multiple ingress pipelines, multiple egress pipelines, and a switching fabric between the ingress and egress pipelines. The control plane, on the other hand, is typically managed by one or more off-the-shelf processors, which supports the interface for locally or remotely receiving parameters for configuring the forwarding element.

Control plane processors can fail, and such failures can cause the forwarding elements to fail. Also, these processors add to the expense of the forwarding element. High-end processors not only cost more, but often require additional expensive components, such as high-end cooling systems, etc.

SUMMARY

Some embodiments of the invention provide a forwarding element that can be configured through in-band data-plane messages from a remote controller that is a physically separate machine from the forwarding element. The forwarding element of some embodiments has data plane circuits that include several configurable message-processing stages, several storage queues, and a data-plane configurator. A set of one or more message-processing stages of the data plane is configured (1) to process configuration messages received by the data plane from the remote controller and (2) to store the configuration messages in a set of one or more storage queues. The data-plane configurator receives the configuration messages stored in the set of storage queues and configures one or more of the configurable message-processing stages based on configuration data in the configuration messages.

In some embodiments, the configurable message-processing stages of the data plane include several ingress processing pipelines, several egress processing pipelines, and a traffic management stage between the ingress and egress processing pipelines. The traffic management stage in some embodiments includes the set of storage queues that store the configuration messages that the data-plane configurator receives. Also, in some embodiments, at least one ingress pipeline comprises a set of match-action units (MAUs) that processes configuration messages from the remote controller to convert the configuration messages from a packet-in first format to a second format for processing by the data-plane configurator. This set of MAUs in some embodiments also process other data messages as part of the data plane's forwarding operations that are needed for the forwarding element to forward data messages to their destinations or their next hop (e.g., the next forwarding element).

The data-plane configurator in some embodiments examines a configuration message to determine whether it has been corrupted, and if so, it drops the message. The configurator determines whether a data message is corrupted differently in different embodiments. For instance, in some embodiments, the data-plane configurator computes a checksum for the received message, and drops the message when the checksum indicates that the message has been corrupted. In other embodiments, the data-plane configurator performs a cyclic redundancy check (CRC) operation on the received message, and drops the message when the CRC operation indicates that the message has been corrupted. In still other embodiments, the configurator performs both checksum and CRC operations to determine whether the received message has been corrupted.

To perform a checksum operation, the data-plane configurator verifies a checksum value computed by a message-processing stage for a configuration message that the configurator receives. For instance, in some embodiments, an ingress pipeline includes a parser that extracts data from headers of the configuration messages and inserts the extracted data into message header vectors for processing by the set of MAUs. In some of these embodiments, at least one MAU in the set of MAUs computes an expected checksum value for a payload of a received message by computing a checksum of the message header and differentiating (e.g., differencing or subtracting) this computed checksum from a message checksum that was stored by the remote controller in the message header. This MAU then stores this expected checksum in the message's header vector. The data configurator then computes actual checksum value for the payload of the message and discards the message when its computed actual checksum value does not match the expected checksum value computed by the MAU.

The data-plane configurator checks the messages from the remote controller for data corruption in order to ensure reliable data plane communication between the remote controller and the configurator. To ensure reliable communication, the configurator also drops messages that do not include the appropriate transaction identifiers. Specifically, in some embodiments, the remote controller and the forwarding element insert session and transaction identifiers in the inner headers of the messages that they exchange, in order to ensure reliable data plane communication. In some embodiments, each session corresponds to a task that the forwarding element or the remote controller has to perform, and each session includes one or more transactions. A session identifier identifies each session, while a transaction identifier identifies each transaction. In some embodiments, the configurator drops any message when the message contains a transaction identifier that does not follow the transaction identifier of the previous message in the same session.

After processing a configuration message, the data-plane configurator in some embodiments generates a response message to the remote controller and supplies the response message to the message-processing stages to process and forward to the remote controller through intervening network fabric. In some embodiments, the data-plane circuit generates a first replicated message by replicating the response message for recirculating through the message-processing stages until the remote controller acknowledges receiving the response message, at which time the first replicated response message is discarded.

For instance, in the embodiments where the configurable message-processing stages includes the ingress and egress pipelines and the traffic management stage, the first replicated message is periodically stored in a rate-limited storage queue in the traffic management stage as the first replicated message recirculates through the ingress pipeline stage, the traffic management stage and the egress pipeline stage. In some of these embodiments, one of the message-processing stages (e.g., one of the MAUs) in the ingress pipeline designates a header vector associated with the data-plane configurator's response message (e.g., stores a particular value in this header vector) to direct the traffic management stage to replicate this message for recirculation.

When no acknowledgement is received from the remote controller within a duration of time, a message processing stage of the data-plane circuit modifies the first replicated message to generate a second replicated message addressed to the remote controller for retransmission of the configurator's response message to the remote controller. In some embodiments, the data-plane circuit first sends a notification to the data-plane configurator regarding the lack of response, and the data-plane configurator then directs the data-plane circuit to generate the second replicated message to send to the remote controller.

When the data-plane configurator has to provide a transport-layer acknowledgment message to the remote controller to acknowledge receiving a configuration message from the remote controller, the data-plane configurator in some embodiments provides the transport-layer acknowledgement by piggybacking this acknowledgement message in the response message that the data-plane configurator generates and provides to the message-processing stages for forwarding to the remote controller. In some of these embodiments, the response message has the same transaction and session identifiers as the remote-controller message to which it responds. In other embodiments, the configurator only embeds the session identifier in the response message, and not the transaction identifier.

The preceding Summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this document. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description and the Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description and the Drawings, but rather are to be defined by the appended claims, because the claimed subject matters can be embodied in other specific forms without departing from the spirit of the subject matters.

BRIEF DESCRIPTION OF FIGURES

The novel features of the invention are set forth in the appended claims. However, for purposes of explanation, several embodiments of the invention are set forth in the following figures.

FIG. 1 illustrates an example of a forwarding element with a data plane that is programmable through in-band data messages from a remote controller.

FIG. 2 illustrates an example of a network that contains the forwarding elements of some embodiments at different locations and for performing different forwarding operations.

FIG. 3 illustrates a message-processing stage within a data plane of some embodiments.

FIG. 4 illustrates a traffic manager of a data plane of some embodiments.

FIG. 5 presents a process that illustrates the operations that an ingress pipeline in the data plane performs in some embodiments to forward a data message from the remote controller to a data-plane configurator.

FIG. 6 illustrates the message format of a data message that the remote controller sends in-band to the data-plane configurator.

FIG. 7 illustrates the message format of a data message to or from the data-plane configurator.

FIG. 8 presents a process that illustrates the operations that the data-plane configurator performs in some embodiments to process a data message from the remote controller.

FIG. 9 presents a process that illustrates the operations that an ingress pipeline performs in some embodiments to forward a data message from the data-plane configurator to the remote controller.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerous details, examples, and embodiments of the invention are set forth and described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention may be practiced without some of the specific details and examples discussed.

Some embodiments of the invention provide a forwarding element that can be configured through in-band data-plane messages from a remote controller that is a physically separate machine (e.g., a virtual machine or a standalone machine) from the forwarding element. The forwarding element of some embodiments has data plane circuits that include several configurable message-processing stages, several storage queues, and a data-plane configurator. A set of one or more message-processing stages of the data plane is configured (1) to process configuration messages received by the data plane from the remote controller and (2) to store the configuration messages in a set of one or more storage queues. The data-plane configurator receives the configuration messages stored in the set of storage queues and configures one or more of the configurable message-processing stages based on configuration data in the configuration messages.

As used in this document, data messages refer to a collection of bits in a particular format sent across a network. One of ordinary skill in the art will recognize that the term data message may be used herein to refer to various formatted collections of bits that may be sent across a network, such as Ethernet frames, IP packets, TCP segments, UDP datagrams, etc. Also, as used in this document, references to L2, L3, L4, and L7 layers (or layer 2, layer 3, layer 4, layer 7) are references respectively to the second data link layer, the third network layer, the fourth transport layer, and the seventh application layer of the OSI (Open System Interconnection) layer model.

FIG. 1 illustrates an example of one such forwarding element 100 that can be configured through in-band data plane data messages from a remote controller 105, which communicates with the forwarding element through intervening network fabric 110. The forwarding element 100 can be any type of forwarding element in a network, such as a switch, a router, a bridge, etc., or any type of middlebox appliance in the network. The remote controller 105 is a separate device, or executes on a separate device than, the forwarding element 100. The intervening network fabric 110 includes one or more forwarding devices (such as switches, routers, other network devices, etc.).

The forwarding element 100 forwards data messages within a network. The forwarding element 100 can be deployed as non-edge forwarding element in the interior of a network, or can be deployed as an edge forwarding element at the edge of the network to connect to compute devices (e.g., standalone or host computers) that serve as sources and destinations of the data messages. As a non-edge forwarding element, the forwarding element 100 forwards data messages between forwarding elements in the network, while as an edge forwarding element, the forwarding element 100 forwards data messages to and from edge compute device to each other, to other edge forwarding elements and to non-edge forwarding elements.

FIG. 2 illustrates an example of a network 200 that includes several forwarding elements 100 at the edge and non-edge locations of the network to perform different operations. This network has multiple racks 205 of host computers 210, with each rack having a top-of-rack (TOR) switch 215 that is an edge switch. The TOR switches are connected by several spine switches 220, which are non-edge forwarding elements. The TOR and spine switches also connect to several routers 225, which are also non-edge forwarding elements. Each TOR switch 215, spine switch 220 and router 225 can be implemented by an in-band, programmable forwarding element 100. As such a forwarding element, each of these switches 215 or 220 and/or routers 225 can be programmed remotely by one or more remote controllers 230 through in-band data messages from these controllers that are processed by the data plane circuits of these forwarding elements 215, 220, and 225 without resorting to the control plane circuits of these forwarding elements.

As shown in FIG. 1, the forwarding element 100 includes (1) physical ports 115 that receive data messages from, and transmit data messages to, devices outside of the forwarding element, (2) a data-plane forwarding circuit (“data plane”) 120 that perform the forwarding operations of the forwarding element 100 (e.g., that receive data messages and forward the data messages to other devices), and (3) a control-plane circuit (“control plane”) 125 that provides a configuration interface for configuring the forwarding behavior of the data plane forwarding circuit.

As further shown, the data plane 120 includes ports 112, configurable message processing circuits 130 and a data-plane configurator 135. In some embodiments, several ports 112 receive data messages from and forward data messages to ports 115 of the forwarding element 100. For instance, in some embodiments, N data-plane ports 112 (e.g., 4 ports 112) are associated with each port 115 of the forwarding element. The N-ports 112 for each port 115 are viewed as N-channels of the port 115. In some embodiments, several data-plane ports 112 are associated with other modules (e.g., data plane configurator) of the data plane 120.

The configurable message-processing circuits 130 perform the configurable data-plane forwarding operations of the forwarding element to process and forward data messages to their destinations. The data-plane configurator 135 can configure the configurable message-processing circuits 130 based on configuration data supplied by the control-plane circuit 125. The data-plane configurator 135 can also configure these circuits 130 based on configuration data messages that the data plane 120 receives in-band from the remote controller 105. As further described below, one or more messages-processing circuits of the data plane are configured (1) to process configuration messages received by the data plane from the remote controller and (2) to store the configuration messages in a set of one or more storage queues. The data-plane configurator receives the configuration messages stored in the set of storage queues and configures one or more of the configurable message-processing circuits based on configuration data in the configuration messages.

In some embodiments, the configurable message-forwarding circuits 130 of the data plane include several ingress processing pipelines 140, several egress processing pipelines 142, and a traffic management stage 144 between the ingress and egress processing pipelines 140 and 142. In some embodiments, each ingress or egress pipeline is associated with one or more physical ports 115 of the forwarding element 100. Also, in some embodiments, each ingress or egress pipeline is associated with several data-plane ports 112.

Also, in some embodiments, each ingress or egress pipeline includes a parser 150, several message-processing stages 152, and a deparser 154. A pipeline's parser 150 extracts a message header from a data message that the pipeline receives for processing. In some embodiments, the extracted header is in a format of a header vector (HV), which can be modified by successive message processing stages as part of their message processing operations. The parser of a pipeline passes the payload of the message to the deparser 154 as the pipeline's message-processing stages 152 operate on the header vectors. When a pipeline finishes processing a data message and the message has to be provided to the traffic management stage 144 (in case of an ingress pipeline) or to a port 112 to forward to a port 115 (in case of an egress pipeline) to be forwarded to the message's next hop (e.g., to its destination compute node or next forwarding element), a deparser of the pipeline in some embodiments produces the data message header from the message's header vector that was processed by the last message processing stage, and combines this header with the data message's payload.

In an ingress or egress pipeline, each message-processing stage includes message-processing circuitry for processing received data messages by performing one or more operations based on header vectors associated with the data messages. FIG. 3 illustrates an example of a match-action unit (MAU) 152 of some embodiments. As mentioned above, an ingress pipeline 140 or egress pipeline 142 in some embodiments has several MAU stages 152, each of which includes message-processing circuitry for forwarding received data messages and/or performing stateful operations based on these data messages. An MAU performs these operations by processing values stored in the header vectors of the data messages, as received from the message parser 150 or from a previous MAU 152 in its message processing pipeline.

As shown in FIG. 3, the MAU 152 in some embodiments has a set of one or more match tables 305, a data plane stateful processing unit 310 (DSPU), a set of one or more stateful tables 315, an action crossbar 330, an action parameter memory 320, an action instruction memory 325, and an action engine 335. The match table set 305 can compare one or more fields in a received message's header vector (HV) to identify one or more matching flow entries (i.e., entries that match the message's HV). The match table set can be TCAM tables or exact match tables in some embodiments. In some embodiments, the match table set can be accessed at an address that is a value extracted from one or more fields of the message's header vector, or it can be a hash of this extracted value.

In some embodiments, the value stored in a match table record that matches a message's flow identifier, or that is accessed at a hash-generated address, provides addresses for the action parameter memory 320 and action instruction memory 325. Also, such a value from the match table can provide an address and/or parameter for one or more records in the stateful table set 315, and can provide an instruction and/or parameter for the DSPU 310. As shown, the DSPU 310 and the stateful table set 315 also receive a processed message's header vector. The header vectors can include instructions and/or parameters for the DSPU, while containing addresses and/or parameters for the stateful table set 315.

The DSPU 310 and the stateful table set 315 form the MAU's stateful sub-unit 312, which performs stateful operations, such as maintaining data regarding acknowledgments and calculating statistics regarding how often data messages are re-circulated. The DSPU 310 in some embodiments performs one or more stateful operations, while a stateful table 315 stores state data used and generated by the DSPU 310. In some embodiments, the DSPU includes one or more programmable arithmetic logic units (ALUs) that perform operations synchronously with the dataflow of the message-processing pipeline (i.e., synchronously at the line rate). As such, the DSPU can process a different header vector on every clock cycle, thus ensuring that the DSPU would be able to operate synchronously with the dataflow of the message-processing pipeline. In some embodiments, a DSPU performs every computation with fixed latency (e.g., fixed number of clock cycles). Examples of such operations in some embodiments include maintaining statistics (e.g., counts) about how often packets are re-circulated, as further described below.

The DSPU 310 output a set of action parameters to the action crossbar 330. The action parameter memory 320 also outputs a set of action parameters to this crossbar 330. The action parameter memory 320 retrieves the action parameter that it outputs from its record that is identified by the address provided by the match table set 305. The action crossbar 330 in some embodiments maps the action parameters received from the DSPU 310 and action parameter memory 320 to an action parameter bus 340 of the action engine 335. This bus provides the set of action parameters to the action engine 335. For different data messages, the action crossbar 330 can map the action parameters from DSPU 310 and memory 320 differently to this bus 340. The crossbar can supply the action parameters from either of these sources in their entirety to this bus 340, or it can concurrently select different portions of these parameters for this bus in some embodiments.

The action engine 335 also receives a set of instructions to execute from the action instruction memory 325. This memory 325 retrieves the instruction set from its record that is identified by the address provided by the match table set 305. The action engine 335 also receives the header vector for each message that the MAU processes. Such a header vector can also contain a portion or the entirety of an instruction set to process and/or a parameter set for processing the instruction set. In some embodiments, the data-plane configurator supplies flow entries (e.g., the ACL flow-match identifiers and/or action identifiers) in one or more MAU tables (e.g., at the direction of the local control plane 125 and/or the remote controller 105).

The action engine 335 in some embodiments includes a parameter multiplexer and a very large instruction word (VLIW) processor. In some embodiments, the VLIW processor is a set of one or more ALUs. In some embodiments, the parameter multiplexer receives the parameter sets from the action crossbar 330 and input header vector and outputs the parameters as operands to the VLIW processor according to the instruction set (from the instruction memory 335 or the header vector). The VLIW processor executes instructions (from the instruction memory 335 or the header vector) applied to operands received from the parameter multiplexer. The action engine 335 stores the output of its operation in the header vector in order to effectuate a message forwarding operation and/or stateful operation of its MAU stage 152. The output of the action engine 335 forms a modified header vector (HV′) for the next MAU stage.

In other embodiments, the match tables 305 and the action tables 315, 320 and 325 of the MAU stage 152 can be accessed through other methods as well. For instance, in some embodiments, each action table 315, 320 or 325 can be addressed through a direct addressing scheme, an indirect addressing scheme, and an independent addressing scheme. The addressing scheme that is used depends on the configuration of the MAU stage, which in some embodiments, is fixed for all data messages being processed, while in other embodiments can be different for different data messages being processed.

In the direct addressing scheme, the action table uses the same address that is used to address the matching flow entry in the match table set 305. As in the case of a match table 305, this address can be a hash generated address value or a value from the header vector. Specifically, the direct address for an action table can be a hash address that a hash generator (not shown) of the MAU generates by hashing a value from one or more fields of the message's header vector. Alternatively, this direct address can be a value extracted from one or more fields of the header vector.

On the other hand, the indirect addressing scheme accesses an action table by using an address value that is extracted from one or more records that are identified in the match table set 305 for a message's header vector. As mentioned above, the match table records are identified through direct addressing or record matching operations in some embodiments.

The independent address scheme is similar to the direct addressing scheme except that it does not use the same address that is used to access the match table set 305. Like the direct addressing scheme, the table address in the independent addressing scheme can either be the value extracted from one or more fields of the message's header vector, or it can be a hash of this extracted value. In some embodiments, not all the action tables 315, 320 and 325 can be accessed through these three addressing schemes, e.g., the action instruction memory 325 in some embodiments is accessed through only the direct and indirect addressing schemes.

The traffic management stage 144 provides the hardware switching fabric that directs a data message from one ingress pipeline 140 to an egress pipeline 142 (e.g., an egress pipeline associated with the forwarding-element port 115 from which the data message has to exit the data plane). This stage also has numerous queues for storing the data messages, and through these queues and their associated scheduling, this stage can perform quality of service (QoS) operations in order to ensure the desired throughput and service through the forwarding element.

FIG. 4 illustrates an example of the traffic management stage 144 of some embodiments. As shown, the traffic manager 400 includes ingress queues 405, egress queues 410 and hardware switching fabric 415 between the ingress and egress queues. In some embodiments, each ingress queue is associated with an ingress pipeline 140, while each egress queue is associated with an egress pipeline 142.

The switching fabric 415 directs a data message from an ingress queue 405 of an ingress pipeline 140 to an egress queue 410 of an egress pipeline 142. In some embodiments, the switching fabric is a crossbar switching fabric that forwards messages from ingress pipelines to egress pipelines based on header vector parameters that the ingress processing pipelines can modify while processing the messages. As further described below, some embodiments use two or more queues (e.g., egress queues 410) of the traffic manager to store data plane data messages (that contain control-plane instruction and data) exchanged between the remote controller 105 and the data-plane configurator 135. In some embodiments, the data-plane configurator can specify the rates for data message inflow and/or outflow from the one or more queues in the traffic manager (e.g., at the direction of the local control plane 125 and/or the remote controller 105).

As mentioned above, the data plane 120 not only processes data messages received by the forwarding element to forward the messages to their next hops, but also processes and passes data messages (that contain control-plane instructions and/or data) between the remote controller 105 and the data-plane configurator 135. Through the data messages exchanged with the data-plane configurator 135, the remote controller 105 can direct the data-plane configurator 135 to configure the data plane 120 (e.g., to write ACL flow entries in the MAU tables, to configure queues in the TM, to provide instructions to the DSPUs, etc.).

To forward a data message from the remote controller 105 to the data-plane configurator 135, the ingress pipelines 140 perform several operations that are illustrated in FIG. 5. As shown, a parser 150 of an ingress pipeline 140 initially extracts (at 505) the received message's header and creates a header vector for processing by message processing stages 152.

FIG. 6 illustrates the message format of a data message 600 that the remote controller 105 sends in-band to the data-plane configurator 135. The forwarding element 100 uses the same message format when forwarding a message from the configurator 135 to the remote controller 105. As shown, the message has an outer header 605 and a payload 610. The outer header 605 includes layer 2 to layer 4 (L2-L4) address values that are needed for directing the data message from the remote controller 105 to the forwarding element 100 through any intervening network fabric 110. The message-processing stages 152 and the data-plane configurator 135 in some embodiments are agnostic to outer header formats. Different outer headers (e.g., TCP or UDP with SEQ/ACK, L2/L3 or source routing, etc.) are used in different deployments. In some embodiments, the outer headers contain transport layer sequence and acknowledgement numbers.

When the data message is from the controller 105 to the configurator 135, the payload 610 of the outer header 605 is provided to the L4 application process (e.g., the TCP process) of the configurator. As shown in FIG. 6, the payload 610 includes an inner header 615, an inner payload 620, and a payload CRC value 625. The inner header 615 includes control application parameters that the remote controller 105 and data-plane configurator 135 need to identify the session and the transaction within the session. In some embodiments, each task that the configurator 135 or controller 105 has to perform is associated with a session, and each sub-task that needs to be performed for each task is associated with a transaction. Also, in some of these embodiments, each session has an associated session identifier and each transaction has an associated transaction identifier. As shown in FIG. 6, the control application parameters in the inner header 615 in some embodiments are the session identifier 630 and the transaction identifier 635 associated with the data message.

The inner payload 620 contains the instruction and/or data that the controller 105 sends to the configurator 135 (or the configurator sends to the controller when the message is from the configurator to the controller). The payload CRC value 625 is a value that the message recipient (i.e., the configurator 135 or the controller 105) uses for a CRC check that it performs to ensure that the payload was not corrupted, as further described below.

After the ingress pipeline's parser 150 extracts (at 505) the received message's outer header 605 and creates a header vector for the received message, one of the message-processing stages 152 of the ingress pipeline identifies (at 510) the data message as being from remote controller 105, and hence as containing control application instructions/data in its payload for the data-plane configurator 135. In some embodiments, the message-processing stage 152 identifies (at 510) the message as being from the remote controller 105 by matching one or more source address fields of the message (which were embedded in the header vector by the parser) to a flow entry in an MAU match table of that stage. This flow entry specifies an action that directs the MAU to modify the header vector to direct the received data message to a controller-message queue 180 of the traffic manager 144. By so modifying the header vector, the message-processing unit designates (at 515) the header vector as being associated with a message for the data configurator 135.

Next, at 520, another message-processing stage 152 of the ingress pipeline 140 computes an expected payload checksum. As further described below, the data-plane configurator in some embodiments examines a received message to determine whether it has been corrupted, and if so, it drops the message. The data-plane configurator 135 performs this operation to ensure reliable control application messaging in the data plane, which is susceptible to data-message transmission errors. To assist in the data-plane configurator's checksum verification operation, one MAU in the ingress pipeline computes an expected checksum value for a payload of a received message by computing a checksum of the message header and differentiating (e.g., differencing) this computed checksum from a message checksum that was stored by the remote controller in the message header. This MAU then stores this expected checksum in the message's header vector. The data configurator then computes an actual checksum value for the payload of the message and discards the message when its computed actual checksum value does not match the expected checksum value computed by the MAU, as further described below.

At 525, the deparser of the ingress pipeline 140 reconstitutes the received data message by combining its payload with the metadata that is stored in this message's header vector, which was processed by the message-processing stages 152 of the ingress pipeline. This reconstituted message has a field that directs the traffic manager to forward this message to the controller-message queue 180. In some embodiments, the reconstituted message is no longer in the message format 600 in which it was received. Rather now, the message is in a message format used by the data-plane configurator 135. FIG. 7 illustrates an example of the format of the data message as it is provided to the data-plane configurator 135. The data message has a set of metadata fields 705. It also has an expected payload checksum 710 that was computed by the ingress pipeline 140. Lastly, it has payload 715 that is similar to the payload 610 of the received message. After 525, the process 500 ends.

The controller-message queue 180 has a finite size. When this queue is full, the traffic manager 144 drop any new data message that has to be placed in this queue. This ensures that the remote controller or another device pretending to be the remote controller cannot overwhelm the data configurator or the data plane circuit with too many configuration data messages.

From the controller-message queue 180, the TM forwards the reconstituted message to an egress pipeline associated with an egress data-plane port 112 that forwards messages to the data-plane configurator 135. As mentioned above, different data-plane ports 112 are associated with different functionalities of the forwarding element. For example, in some embodiments, one data-plane port directs messages to the configurator 135, while another data-plane port 112 recirculates the messages by directing them to one or more ingress pipelines.

To ensure reliable data plane communication between the remote controller 105 and the configurator 135, the data-plane configurator 135 in some embodiments drops remote-controller data messages that have been corrupted and/or that do not include the proper transaction identifier (e.g., the next transaction identifier in a sequence of transaction identifiers for a session identifier). In some embodiments, the data-plane configurator 135 detects whether the message has been corrupted by validating the expected payload checksum that the ingress pipeline computes, and by performing a CRC verification on the payload.

After processing a configuration message from the remote controller, the data-plane configurator in some embodiments sends an acknowledgment message to the remote controller to indicate the processing of the configuration message. In some embodiments, the remote controller executes a standard layer 4 protocol (e.g., TCP) that requires its message destinations to acknowledge receiving its data messages. Also, in some embodiments, the remote controller only accepts data messages with expected transport sequence numbers, and drops data messages from the remote controller that it receives with unexpected transport sequence numbers. Thus, in these embodiments, the data-plane configurator acknowledges receiving each data message from the remote controller by sending an acknowledgment message with the correct sequence number to the remote controller. When the data-plane configurator processes a first data message from the remote controller and has to send to the remote controller a reply second data message with payload data in response to the first data message, the data-plane configurator includes (i.e., piggybacks) its acknowledgment to the first data message in the second message.

When the data-plane configurator generates a response message to the remote controller, it supplies the response message to the message-processing stages to process and forward to the remote controller through intervening network fabric. In some embodiments, the data-plane circuit generates a first replicated message by replicating the response message for recirculating through the message-processing stages until the remote controller acknowledges receiving the response message, at which time the first replicated response message is discarded. For instance, in some embodiments, the first replicated message is stored in a rate-limited storage queue 182 in the traffic management stage and is periodically re-circulated through the data plane circuit until an MAU stage of the ingress pipeline detects an acknowledgment from the remote controller that it has received the data message from the data-plane configurator.

FIG. 8 presents an exemplary process 800 that conceptually illustrates a sense of operations that the data-plane configurator 135 performs in some embodiments when it receives a data message from the remote-controller queue 180 and its associated egress pipeline 142. In this example, the data-plane configurator 135 processes this data message and generates a reply message that contains data that the configurator collects in response to the received data message. However, as further described below, the configurator in some cases can process a data message from the remote controller and just provide an acknowledgment to this message.

As shown, the configurator 135 determines (at 805) whether the message has been corrupted. The configurator determines whether a data message is corrupted differently in different embodiments. For instance, in some embodiments, the data-plane configurator performs a cyclic redundancy check (CRC) operation on the received message, and drops the message when the CRC operation indicates that the message has been corrupted. As mentioned above, a data message from the remote controller 105 in some embodiments includes a payload CRC value 625 that the data configurator 135 compares with a CRC value that the configurator generates in order to determine whether the payload has been corrupted. When the computed and received CRC values match, the data configurator determines that the payload has not been corrupted. Otherwise, when these two values do not match during the CRC check, the configurator determines that the payload has been corrupted.

Also, in some embodiments, the data-plane configurator computes a checksum for the payload 620 of the received message, and then determines whether the computed checksum matches the expected payload checksum computed by the ingress pipeline. In still other embodiments, the configurator performs both checksum and CRC operations to determine whether the received message has been corrupted. When the data-plane configurator 135 determines that the received message has been corrupted (e.g., when the computed actual checksum does not match the ingress-pipeline computed expected checksum, or when the CRC verification fails), the configurator drops (at 810) the message and the process 800 ends for the received message.

When the data-plane configurator 135 determines (at 805) that the received message has not been corrupted, the configurator 135 determines (at 815) whether for the session identified by the session identifier in the received message, the transaction identifier follows the transaction identifier of the previous message from the remote controller in this session. If not, the data-plane configurator 135 drops (at 810) the message and the process 800 ends for the received message.

When the configurator 135 determines (at 815) that the transaction identifier follows the transaction identifier of the previous controller message in this session, the configurator processes (at 820) the remote-controller instruction and/or data contained in the payload of the received message. This process can include configuring one or more configurable elements in the ingress pipeline 140, egress pipeline 142 and/or TM 144. Examples of this configuration include storing ACLs in the MAUs 152 of the ingress or egress pipelines, setting scheduling parameters (e.g., output rates) for the queues in the TMs, etc. At 820, the processing of the remote-controller instruction might also involve performing other operations, such as collecting statistics stored in the data plane (e.g., counter values maintained in the data plane) and forwarding these collected statistics to the remote controller.

In some embodiments, the data-plane configurator 135 performs these configuration operations analogously to when it receives instructions from the local control plane 125 to configure the data plane, except that the registers that it now reads have been populated by a parser (not shown) of the configurator 135 that extracts data from the message that an egress port 112 directs to the configurator 135. These configuration operations in some embodiments are standard operations that data-plane configurators use to configure the data plane circuits at the direction of the local control plane. In some embodiments, the data-plane configurator 135 is a PCIe interface with the standard PCIe interface components, such as microcontroller, memory, etc.

At 820, the configurator 135 collects data in response to its processing of the received data message. Examples of such data include statistics maintained in the data plane (e.g., counter values associated with flow records in the match-action tables of the MAUs). Next, at 825, the configurator generates a response message to the remote controller. In this response, the configurator in some embodiments embeds the session identifier and the transaction identifier. In some embodiments, this transaction identifier is the transaction identifier of the message received from the remote controller. In other embodiments, the configurator only embeds the session identifier in the response message, and not the transaction identifier.

After processing a message from the remote controller, the data-plane configurator in some embodiments has to send an acknowledgment message to the remote controller to indicate the processing of the message, as the remote controller executes a standard layer 4 protocol (e.g., TCP) that requires its message destinations to acknowledge receiving its data messages. Accordingly, in the response message that it generates at 825, the configurator also embeds the transport-layer acknowledgement to the received message (i.e., the message that caused the configurator 135 to perform the process 800).

In other words, the configurator piggybacks the transport layer acknowledgement message in the control-application response message that the configurator generates in response to the message received from the remote controller. In some embodiments, the configurator also increments the layer 4 parameters (e.g., the layer 4 sequence number) in the outer header, as the remote controller uses these incremented values to verify that it has received the data messages from the forwarding element 100 in the proper sequence. The configurator 135 next supplies (at 830) the generated response message to an ingress pipeline 140 to process and forward to the remote controller through intervening network fabric. After 835, the process 800 ends.

In the example illustrated in FIG. 8, the data plane configurator 135 piggybacks its acknowledgment to the remote-controller message in its response message to the remote controller. However, in some embodiments, each time the configurator 135 processes a remote-controller message, it does not have to generate a response message with a payload for the remote controller. In such cases, the configurator 135 simply generates and sends an acknowledgment message with the correct sequence number to the remote controller. Also, in the above-described embodiments, the configurator does not increment the transaction identifier. In other embodiments, however, the configurator increments the transaction identifier, each time that it sends a response message with a payload or with an instruction to the remote controller.

To ensure reliable control-application messaging in the data plane, the data plane circuits replicate the response message, send the response message to the remote controller, and recirculate the replicated message until the remote controller acknowledges receiving the response message. To accomplish this, the ingress pipeline 140 (e.g., an MAU 152 in the ingress pipeline) that receives the response message from the configurator 135 marks the message's header vector to indicate that it has to be multi-casted by the TM 144 to both the recirculation queue 182 and the data-plane port 112 (that is associated with port 115) associated with the remote controller 105.

FIG. 9 illustrates a process 900 that the data plane circuits perform in some embodiments to process response messages from the data-plane configurator 135. As shown, the parser 150 of the ingress pipeline 140 that receives the data message from the configurator, generates (at 905) the header vector for this message, while directing this message's payload to the deparser of the ingress pipeline. In doing this, the parser transforms the data message from a configurator format to a message-out format.

Next, at 910, one of the message-processing stages 152 creates in a stateful table 315 an Ack_Received Boolean variable for the data message, and sets the value of this variable to False. At 915, the same or different message-processing stage creates in the same or different stateful table 315 a Seq_Num_Sent variable, which corresponds to the sequence number assigned to the response message from the data-plane configurator 135. This stored sequence number is used in some embodiments to determine whether the data plane 120 subsequently receives a layer-4 acknowledgment reply to its response message.

At 920, a message-processing stage 152 marks the header vector to indicate that the received configurator message should be replicated and re-circulated by the TM. Once the deparser of the ingress pipeline (that processes the response message from the configurator) combines the header vector and the payload of this message, the TM gets the message, and from the marked multi-cast fields in this message, determines that it has to multi-cast this message to both the recirculation queue 182 and the data-plane port 112 associated with the remote controller 105. The TM then directs the received message to the egress queue 410 that is associated with the data-plane port 112 that is associated with (e.g., that is directly or indirectly communicatively connected) with the remote controller 105. In some embodiments, the data message format 600 of FIG. 6 is the format of the message that is sent to the remote controller 105 with the session ID, transaction ID, checksum value and CRC values provided by the data-plane configurator 135.

The TM also replicates the received message and directs this replicated message to the TM's recirculation queue 182 (which in some embodiments is another egress queue 410 of the TM). The recirculation queue in some embodiments is a rate-limited queue that stores the messages that it receives for a time period that can be configured by the configurator 135. Storing the replicated message in the rate-limited queue allows the data plane to reduce the rate at which the replicated message recirculates through the data plane 120 while waiting for the remote controller 105 to acknowledge receiving the message from the configurator 135. The TM retrieves the re-circulated message from the recirculation queue 182 periodically based on the configured output rate of this queue, and directs this message to egress queue 410 that is associated with the data-plane port 112 that recirculates its output back to an ingress pipeline 140.

The data plane process 900 transitions from 920 to 925, where it remains until it receives an acknowledgment from the remote controller that it has received the configurator's message, it determines that it has to retransmit the configurator's message, or it determines that it has to stop the recirculation and retransmission as the remote controller has failed to a particular number of retransmitted messages. When it receives an acknowledgement message, the process 900 uses the stored sequence number (that it previously stored at 915) to determine that the acknowledgement message was for the response message forwarded at 920.

In some embodiments, the data plane does not determine whether it has to retransmit the configurator's message to the remote controller, but rather informs the configurator 135 that the remote controller has not acknowledged a previously transmitted message, and the configurator has to regenerate the data message for retransmission. The data plane 120 in some embodiments so informs the configurator by having the MAU stage that maintains the recirculation count for the replicated message, mark the header vector for the replicated message to direct the traffic manager to direct the replicated message to the data plane configurator, or to drop the replicated message and direct another message to the data plane configurator. In notifying the data plane configurator 135, the traffic manager in some embodiments stops recirculating the replicated packet through the data plane, as the data plane configurator has to regenerate the message to the remote controller.

When the remote controller sends a valid acknowledgement to the configurator's message, a message-processing stage 152 of the ingress pipeline that processes the message from the controller, detects this acknowledgement and changes the Ack_Received field in the stateful memory 315 to True for the configurator message associated with the received acknowledgement. In some embodiments, the same ingress pipeline 140 processes all the data messages from the remote controller and the original and re-circulated messages from the data configurator 135, as only the remote controller is implemented by one server that connects to the forwarding element 100 through one ingress port 115 that is associated with one ingress data-plane port 112 for message from the remote controller. However, even in embodiments in which the remote controller is implemented by a cluster of servers, one ingress pipeline 140 processes all the data messages from and to a remote controller during one session (as identified by one session identifier) because one session is only managed by one server in the remote controller cluster. As such, these embodiments do not have to address receiving message acknowledgments from a remote controller in a different ingress pipeline than the ingress pipeline through which the re-circulated messages pass through.

In some embodiments, the message-processing stage 152 disregards an acknowledgement message when sequence number in this message is smaller than the Seq_Num_Sent that the data plane circuits stored for the configurator's data message to the remote controller 105. This is because the lower sequence number indicates that the acknowledgement message is a prior message that acknowledges a prior message from the configurator. When the message-processing stage 152 disregards an acknowledgement message, it marks the header vector for this message for dropping.

The next time that the re-circulated, replicated message passes through a message-processing stage that checks the stateful memory 315, the message-processing stage checks the Ack_Received field, determines that the acknowledgment has been sent, and then marks the header vector for this re-circulated, replicated message for dropping. When processing the reconstituted message with this header vector, the TM then analyzes the field marked up to indicate that the replicated message should be dropped and then drops this message instead of storing it in the recirculation queue 182. In other embodiments, a message-processing stage that processes the re-circulated message drops this message when it detects that the stateful table stores an Ack_Received value that is True. After 925, the process ends.

By allowing the data plane circuits of a forwarding element to be programmed by a remote-controller through in-band data messages, some embodiments of the invention improve the fault-tolerance of the forwarding element because the forwarding element no longer has to be taken offline the moment that its control plane processor fails. Also, this remote data-plane programmability of the forwarding element allows the forwarding element to use no control-plane processor or to use simpler control-plane processor(s). This, in turn, reduces the cost and complexity of the forwarding element.

While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. Accordingly, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.

Claims

1. Network switch circuitry for use in association with a remote controller, the network switch circuitry also being for use in forwarding frame data received by the network switch circuitry to at least one next hop destination via at least one network, the network switch circuitry comprising: frame data processing circuitry to process the received frame data in association with the forwarding of the received frame data, the received frame data comprising header data, the frame data processing circuitry being configurable to comprise: a plurality of packet processing pipelines, the plurality of packet processing pipelines being programmable, at least in part, based upon instructions to be received by the network switch circuitry, the plurality of packet processing pipelines comprising: at least one ingress pipeline comprising a set of pipeline stages, the set of pipeline stages comprising parser circuitry to obtain the header data; andat least one egress pipeline comprising at least one stage to generate, at least in part, at least one output frame that is to be forwarded to the at least one network hop destination from the network switch circuitry via the at least one network; andtraffic management circuitry for use in queuing-related, scheduling-related, quality of service-related, and replication-related operations associated with processing of the frame data;wherein: the at least one ingress pipeline and the at least one egress pipeline also comprise match-action units to modify, based upon comparison of at least certain portions of the header data with table data of the network switch circuitry, the header data for use in generating the at least one output frame;the network switch circuitry is also programmable based upon other frame data received by the network switch circuitry from the remote controller via the at least one network;the other frame data is comprised in at least one Ethernet frame from the remote controller;the at least one Ethernet frame comprises header field information to be used to associate the at least one Ethernet frame with the remote controller, at least in part;the network switch circuitry is to generate, in reply to the at least one Ethernet frame, at least one other Ethernet frame;the network switch circuitry is to send the at least one other Ethernet frame to the remote controller via the at least one ingress pipeline;the network switch circuitry is programmable to generate statistical data related to the network switch circuitry for transmission via the at least one network; andthe instructions are to be generated local to the network switch circuitry and are to be provided to the network switch circuitry via an interface of the network switch circuitry.

2. The network switch circuitry of claim 1, wherein: the at least one other Ethernet frame is to include identifying data associated with a reply to the at least one Ethernet frame from the remote controller; andthe network switch circuitry is to perform at least one action to be determined based at least in part upon at least one matching operation involving, at least in part, the other frame data.

3. The network switch circuitry of claim 2, wherein: the statistical data is associated with data-plane counter data; andthe network switch circuitry is comprised, at least in part, in an application specific integrated circuit (ASIC).

4. The network switch circuitry of claim 3, wherein: the network switch circuitry is usable to implement one or more of the following: a top-of-rack switch;a router; and/ora spine switch.

5. The network switch circuitry of claim 4, wherein: the network switch circuitry is for use in association with: at least one network fabric; and/orat least one TCAM.

6. The network switch circuitry of claim 3, wherein: the network switch circuitry is to obtain an expected checksum value from the at least one Ethernet frame;the network switch circuitry is to compute an actual checksum value based, at least in part, upon the at least one Ethernet frame; andthe network switch circuitry is to check for corruption, at least in part, of the at least one Ethernet frame by comparing the actual checksum value with the expected checksum value.

7. The network switch circuitry of claim 6, wherein: the actual checksum value and the expected checksum value comprise cyclic redundancy check (CRC) values.

8. The network switch circuitry of claim 7, wherein: the interface of the network switch circuitry comprises microcontroller and PCIe components.

9. At least one non-transitory machine-readable memory storing program instructions to be executed by network switch circuitry, the network switch circuitry being for use in association with a remote controller, the network switch circuitry also being for use in forwarding frame data received by the network switch circuitry to at least one next hop destination via at least one network, the program instructions, when executed by the network switch circuitry, resulting in the network switch circuitry being configured for performance of operations comprising: processing, by frame data processing circuitry of the network switch circuitry, the received frame data in association with the forwarding of the received frame data, the received frame data comprising header data, the frame data processing circuitry being configurable to comprise: a plurality of packet processing pipelines, the plurality of packet processing pipelines being programmable, at least in part, based upon other instructions to be received by the network switch circuitry, the plurality of packet processing pipelines comprising: at least one ingress pipeline comprising a set of pipeline stages, the set of pipeline stages comprising parser circuitry to obtain the header data; andat least one egress pipeline comprising at least one stage to generate, at least in part, at least one output frame that is to be forwarded to the at least one network hop destination from the network switch circuitry via the at least one network; andtraffic management circuitry for use in queuing-related, scheduling-related, quality of service-related, and replication-related operations associated with processing of the frame data;wherein: the at least one ingress pipeline and the at least one egress pipeline also comprise match-action units to modify, based upon comparison of at least certain portions of the header data with table data of the network switch circuitry, the header data for use in generating the at least one output frame;the network switch circuitry is also programmable based upon other frame data received by the network switch circuitry from the remote controller via the at least one network;the other frame data is comprised in at least one Ethernet frame from the remote controller;the at least one Ethernet frame comprises header field information to be used to associate the at least one Ethernet frame with the remote controller, at least in part;the network switch circuitry is to generate, in reply to the at least one Ethernet frame, at least one other Ethernet frame;the network switch circuitry is to send the at least one other Ethernet frame to the remote controller via the at least one ingress pipeline;the network switch circuitry is programmable to generate statistical data related to the network switch circuitry for transmission via the at least one network; andthe other instructions are to be generated local to the network switch circuitry and are to be provided to the network switch circuitry via an interface of the network switch circuitry.

10. The at least one non-transitory machine-readable memory of claim 9, wherein: the at least one other Ethernet frame is to include identifying data associated with a reply to the at least one Ethernet frame from the remote controller; andthe network switch circuitry is to perform at least one action to be determined based at least in part upon at least one matching operation involving, at least in part, the other frame data.

11. The at least one non-transitory machine-readable memory of claim 10, wherein: the statistical data is associated with data-plane counter data; andthe network switch circuitry is comprised, at least in part, in an application specific integrated circuit (ASIC).

12. The at least one non-transitory machine-readable memory of claim 11, wherein: the network switch circuitry is usable to implement one or more of the following: a top-of-rack switch;a router; and/ora spine switch.

13. The at least one non-transitory machine-readable memory of claim 12, wherein: the network switch circuitry is for use in association with: at least one network fabric; and/orat least one TCAM.

14. The at least one non-transitory machine-readable memory of claim 11, wherein: the network switch circuitry is to obtain an expected checksum value from the at least one Ethernet frame;the network switch circuitry is to compute an actual checksum value based, at least in part, upon the at least one Ethernet frame; andthe network switch circuitry is to check for corruption, at least in part, of the at least one Ethernet frame by comparing the actual checksum value with the expected checksum value.

15. The at least one non-transitory machine-readable memory of claim 14, wherein: the actual checksum value and the expected checksum value comprise cyclic redundancy check (CRC) values.

16. The at least one non-transitory machine-readable memory of claim 15, wherein: the interface of the network switch circuitry comprises microcontroller and PCIe components.

17. A method implemented using a network switch circuitry, the network switch circuitry being for use in association with a remote controller, the network switch circuitry also being for use in forwarding frame data received by the network switch circuitry to at least one next hop destination via at least one network, the method comprising: processing, by frame data processing circuitry of the network switch circuitry, the received frame data in association with the forwarding of the received frame data, the received frame data comprising header data, the frame data processing circuitry being configurable to comprise: a plurality of packet processing pipelines, the plurality of packet processing pipelines being programmable, at least in part, based upon other instructions to be received by the network switch circuitry, the plurality of packet processing pipelines comprising: at least one ingress pipeline comprising a set of pipeline stages, the set of pipeline stages comprising parser circuitry to obtain the header data; andat least one egress pipeline comprising at least one stage to generate, at least in part, at least one output frame that is to be forwarded to the at least one network hop destination from the network switch circuitry via the at least one network; andtraffic management circuitry for use in queuing-related, scheduling-related, quality of service-related, and replication-related operations associated with processing of the frame data;wherein: the at least one ingress pipeline and the at least one egress pipeline also comprise match-action units to modify, based upon comparison of at least certain portions of the header data with table data of the network switch circuitry, the header data for use in generating the at least one output frame;the network switch circuitry is also programmable based upon other frame data received by the network switch circuitry from the remote controller via the at least one network;the other frame data is comprised in at least one Ethernet frame from the remote controller;the at least one Ethernet frame comprises header field information to be used to associate the at least one Ethernet frame with the remote controller, at least in part;the network switch circuitry is to generate, in reply to the at least one Ethernet frame, at least one other Ethernet frame;the network switch circuitry is to send the at least one other Ethernet frame to the remote controller via the at least one ingress pipeline;the network switch circuitry is programmable to generate statistical data related to the network switch circuitry for transmission via the at least one network; andthe other instructions are to be generated local to the network switch circuitry and are to be provided to the network switch circuitry via an interface of the network switch circuitry.

18. The method of claim 17, wherein: the at least one other Ethernet frame is to include identifying data associated with a reply to the at least one Ethernet frame from the remote controller; andthe network switch circuitry is to perform at least one action to be determined based at least in part upon at least one matching operation involving, at least in part, the other frame data.

19. The method of claim 18, wherein: the interface of the network switch circuitry comprises microcontroller and PCIe components;the network switch circuitry is to obtain an expected checksum value from the at least one Ethernet frame;the network switch circuitry is to compute an actual checksum value based, at least in part, upon the at least one Ethernet frame; andthe network switch circuitry is to check for corruption, at least in part, of the at least one Ethernet frame by comparing the actual checksum value with the expected checksum value.

20. A network switch system for use in association with a remote controller, the network switch system also being for use in forwarding frame data received by the network switch system to at least one next hop destination via at least one network, the network switch system comprising: physical ports to be coupled to the at least one network, the physical ports to be used in frame data reception and transmission via the at least one network; andnetwork switch circuitry, the network switch circuitry comprising: frame data processing circuitry to process the received frame data in association with the forwarding of the received frame data, the received frame data comprising header data, the frame data processing circuitry being configurable to comprise: a plurality of packet processing pipelines, the plurality of packet processing pipelines being programmable, at least in part, based upon instructions to be received by the network switch circuitry, the plurality of packet processing pipelines comprising: at least one ingress pipeline comprising a set of pipeline stages, the set of pipeline stages comprising parser circuitry to obtain the header data; andat least one egress pipeline comprising at least one stage to generate, at least in part, at least one output frame that is to be forwarded to the at least one network hop destination from the network switch circuitry via at least one of the physical ports and the at least one network; andtraffic management circuitry for use in queuing-related, scheduling-related, quality of service-related, and replication-related operations associated with processing of the frame data;wherein: the at least one ingress pipeline and the at least one egress pipeline also comprise match-action units to modify, based upon comparison of at least certain portions of the header data with table data of the network switch circuitry, the header data for use in generating the at least one output frame;the network switch circuitry is also programmable based upon other frame data received by the network switch circuitry from the remote controller via the at least one network;the other frame data is comprised in at least one Ethernet frame from the remote controller;the at least one Ethernet frame comprises header field information to be used to associate the at least one Ethernet frame with the remote controller, at least in part;the network switch circuitry is to generate, in reply to the at least one Ethernet frame, at least one other Ethernet frame;the network switch circuitry is to send the at least one other Ethernet frame to the remote controller via the at least one ingress pipeline;the network switch circuitry is programmable to generate statistical data related to the network switch circuitry for transmission via the at least one network; andthe instructions are to be generated local to the network switch circuitry and are to be provided to the network switch circuitry via an interface of the network switch circuitry.

21. The network switch system of claim 20, wherein: the interface of the network switch circuitry comprises microcontroller and PCIe components;the at least one other Ethernet frame is to include identifying data associated with a reply to the at least one Ethernet frame from the remote controller; andthe network switch circuitry is to perform at least one action to be determined based at least in part upon at least one matching operation involving, at least in part, the other frame data.

22. The network switch system of claim 21, wherein: the network switch circuitry is to obtain an expected checksum value from the at least one Ethernet frame;the network switch circuitry is to compute an actual checksum value based, at least in part, upon the at least one Ethernet frame; andthe network switch circuitry is to check for corruption, at least in part, of the at least one Ethernet frame by comparing the actual checksum value with the expected checksum value.

23. A networked computer system for use in association with a remote controller, the networked computer system also being for use in forwarding frame data received by the networked computer system to at least one next hop destination via at least one network, the networked computer system comprising: at least one rack;at least one network switch system comprised in the at least one rack, the at least one network switch system comprising: physical ports to be coupled to the at least one network, the physical ports to be used in frame data reception and transmission via the at least one network; andnetwork switch circuitry, the network switch circuitry comprising: frame data processing circuitry to process the received frame data in association with the forwarding of the received frame data, the received frame data comprising header data, the frame data processing circuitry being configurable to comprise: a plurality of packet processing pipelines, the plurality of packet processing pipelines being programmable, at least in part, based upon instructions to be received by the network switch circuitry, the plurality of packet processing pipelines comprising: at least one ingress pipeline comprising a set of pipeline stages, the set of pipeline stages comprising parser circuitry to obtain the header data; and at least one egress pipeline comprising at least one stage to generate, at least in part, at least one output frame that is to be forwarded to the at least one network hop destination from the network switch circuitry via at least one of the physical ports and the at least one network; andtraffic management circuitry for use in queuing-related, scheduling-related, quality of service-related, and replication-related operations associated with processing of the frame data;wherein: the at least one ingress pipeline and the at least one egress pipeline also comprise match-action units to modify, based upon comparison of at least certain portions of the header data with table data of the network switch circuitry, the header data for use in generating the at least one output frame;the network switch circuitry is also programmable based upon other frame data received by the network switch circuitry from the remote controller via the at least one network;the other frame data is comprised in at least one Ethernet frame from the remote controller;the at least one Ethernet frame comprises header field information to be used to associate the at least one Ethernet frame with the remote controller, at least in part;the network switch circuitry is to generate, in reply to the at least one Ethernet frame, at least one other Ethernet frame;the network switch circuitry is to send the at least one other Ethernet frame to the remote controller via the at least one ingress pipeline;the network switch circuitry is programmable to generate statistical data related to the network switch circuitry for transmission via the at least one network; andthe instructions are to be generated local to the network switch circuitry and are to be provided to the network switch circuitry via an interface of the network switch circuitry.

24. The networked computer system of claim 23, wherein: the at least one rack is associated with at least one host computer;the at least one network switch system comprises a plurality of network switch systems;the plurality of network switch systems implement one or more of the following: at least one top-of-rack switch;at least one router; and/orat least one spine switch.

25. The networked computer system of claim 24, wherein: the plurality of network switch systems also implement at least one edge switch; andthe at least one rack comprises a plurality of racks that comprise the plurality of network switch systems.