mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-22 18:07:40 +00:00
Code Issues Releases Wiki Activity
ovs/lib/ofp-errors.h

529 lines
16 KiB
C
Raw Normal View History

Automatically extract error types and codes for formatting.
2011-01-12 13:42:50 -08:00
/*
Global replace of Nicira Networks. Replaced all instances of Nicira Networks(, Inc) to Nicira, Inc. Feature #10593 Signed-off-by: Raju Subramanian <rsubramanian@nicira.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-05-02 15:21:36 -07:00
* Copyright (c) 2008, 2009, 2010, 2011, 2012 Nicira, Inc.
Automatically extract error types and codes for formatting.
2011-01-12 13:42:50 -08:00
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at:
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#ifndef OFP_ERRORS_H
#define OFP_ERRORS_H 1
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
#include <stdbool.h>
#include <stddef.h>
Automatically extract error types and codes for formatting.
2011-01-12 13:42:50 -08:00
#include <stdint.h>
ofp-util: Make ofperr_encode_msg__() use correct Open Flow version Make ofperr_encode_msg__() use correct Open Flow version in the header of messages. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-08-01 16:01:48 +09:00
#include "openflow/openflow.h"
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
struct ds;
ofp-msgs: New approach to encoding and decoding OpenFlow headers. OpenFlow headers are not as uniform as they could be, with size, alignment, and numbering changes from one version to another and across varieties (e.g. ordinary messages vs. "stats" messages). Until now the Open vSwitch internal APIs haven't done a good job of abstracting those differences in header formats. This commit changes that; from this commit forward very little code actually needs to understand the header format or numbering. Instead, it can just encode or decode, or pull or put, the header using a more abstract API using the ofpraw_, ofptype_, and other APIs in the new ofp-msgs module. Signed-off-by: Ben Pfaff <blp@nicira.com> Tested-by: Simon Horman <horms@verge.net.au> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-07-19 23:23:17 -07:00
struct ofpbuf;
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* Error codes.
*
* We embed system errno values and OpenFlow standard and vendor extension
* error codes into the positive range of "int":
*
* - Errno values are assumed to use the range 1 through 2**30 - 1.
*
* (C and POSIX say that errno values are positive. We assume that they
* are less than 2**29. They are actually less than 65536 on at least
* Linux, FreeBSD, OpenBSD, and Windows.)
*
* - OpenFlow standard and vendor extension error codes use the range
* starting at 2**30 (OFPERR_OFS).
*
* Zero and negative values are not used.
*/
#define OFPERR_OFS (1 << 30)
ofp-errors: Ignore text enclosed in square brackets Enhance to extract-ofp-errors to omit text enclosed in square brackets from error description. This allows some commentary other than the error description to be supplied in ofp-errors.h As suggested by Ben Pfaff <blp@nicira.com> Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added the large comment on enum ofperr.] Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-09-05 11:50:36 +09:00
/* OpenFlow error codes.
*
* The comments below are parsed by the extract-ofp-errors program at build
* time and used to determine the mapping between "enum ofperr" constants and
* error type/code values used in the OpenFlow protocol:
*
* - The first part of each comment specifies OpenFlow type/code for each
* protocol that supports the error.
*
* - Additional text is a human-readable description of the meaning of each
* error, used to explain the error to the user. Any text enclosed in
* square brackets is omitted; this can be used to explain rationale for
* choice of error codes in the case where this is desirable. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
enum ofperr {
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* Expected duplications. */
/* Expected: 3,5 in OF1.1 means both OFPBIC_BAD_EXPERIMENTER and
* OFPBIC_BAD_EXP_TYPE. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## ------------------ ## */
/* ## OFPET_HELLO_FAILED ## */
/* ## ------------------ ## */
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(0). Hello protocol failed. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_HELLO_FAILED = OFPERR_OFS,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(0,0). No compatible version. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPHFC_INCOMPATIBLE,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(0,1). Permissions error. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPHFC_EPERM,
/* ## ----------------- ## */
/* ## OFPET_BAD_REQUEST ## */
/* ## ----------------- ## */
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1). Request was not understood. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_BAD_REQUEST,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,0). ofp_header.version not supported. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BAD_VERSION,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,1). ofp_header.type not supported. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BAD_TYPE,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,2). ofp_stats_msg.type not supported. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BAD_STAT,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,3). Vendor not supported (in ofp_vendor_header or
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* ofp_stats_msg). */
OFPERR_OFPBRC_BAD_VENDOR,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,4). Vendor subtype not supported. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BAD_SUBTYPE,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,5). Permissions error. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_EPERM,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,6). Wrong request length for type. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BAD_LEN,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,7). Specified buffer has already been used. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BUFFER_EMPTY,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(1,8). Specified buffer does not exist. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BUFFER_UNKNOWN,
ofp-errors: Use OFPERR_OFPBRC_BAD_TABLE_ID * In the case of OpenFlow 1.1+ OFPERR_OFPBRC_BAD_TABLE_ID is defined in the specification and seems to be the most appropriate error to use when an unknown table id is encountered. * In the case of OpenFlow 1.0 no appropriate error message seems to exist. Perhaps because an invalid port is not possible? I'm unsure. In any case, make use of a non-standard error code (1,512). This was formerly known as OFPERR_NXBRC_BAD_TABLE_ID but has been rolled into OFPERR_OFPBRC_BAD_TABLE_ID to allow the latter to be used without concern for the prevailing Open Flow version. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-09-05 11:50:38 +09:00
/* NX1.0(1,512), OF1.1+(1,9). Specified table-id invalid or does not exist.
* [ A non-standard error (1,512), formerly OFPERR_NXBRC_BAD_TABLE_ID,
* is used for OpenFlow 1.0 as there seems to be no appropriste error
* code defined the specification. ] */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBRC_BAD_TABLE_ID,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(1,10). Denied because controller is slave. */
OFPERR_OFPBRC_IS_SLAVE,
ofp-errors: Use OFPERR_OFPBRC_BAD_PORT * In the case of OpenFlow 1.2+ OFPERR_OFPBRC_BAD_PORT is defined in the specification and seems to be the most appropriate error to use when an invalid port is encountered in a Packet Out request. * In the case of OpenFlow 1.0 and 1.1 no appropriate error message seems to exist. Perhaps because an invalid port is not possible? I'm unsure. In any case, make use of a non-standard error code (1,514). This was formerly known as OFPERR_NXBRC_BAD_IN_PORT but has been rolled into OFPERR_NXBRC_BAD_IN_PORT to allow the latter to be used without concern for the prevailing Open Flow version. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-09-05 11:50:37 +09:00
/* NX1.0(1,514), NX1.1(1,514), OF1.2+(1,11). Invalid port.
* [ A non-standard error (1,514), formerly
* OFPERR_NXBRC_BAD_IN_PORT is used for OpenFlow 1.0 and 1.1 as there
* seems to be no appropriste error code defined the specifications. ] */
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
OFPERR_OFPBRC_BAD_PORT,
/* OF1.2+(1,12). Invalid packet in packet-out. */
OFPERR_OFPBRC_BAD_PACKET,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* NX1.0+(1,256). Invalid NXM flow match. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_NXBRC_NXM_INVALID,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* NX1.0+(1,257). The nxm_type, or nxm_type taken in combination with
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* nxm_hasmask or nxm_length or both, is invalid or not implemented. */
OFPERR_NXBRC_NXM_BAD_TYPE,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* NX1.0+(1,515). Must-be-zero field had nonzero value. */
Add ability to direct "packet-in"s to particular controllers. Nicira's controllers are somewhat heterogeneous, so that particular "packet-in" messages should be directed to particular controllers. This new Nicira extension action allows designating a controller or controllers to receive the "packet-in" using a 16-bit integer ID. The new NXAST_CONTROLLER action also specifies the "reason" code to include in the "packet-in" message. This is particularly useful for simulating a "no-match" "packet-in" using a rule. Feature #8946. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-02-09 14:17:33 -08:00
OFPERR_NXBRC_MUST_BE_ZERO,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* NX1.0+(1,516). The reason in an ofp_port_status message is not
* valid. */
Abstract everything that uses ofp_phy_port, add OF1.1 support. Reviewed-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-02-15 16:33:04 -08:00
OFPERR_NXBRC_BAD_REASON,
ofproto: New feature to notify controllers of flow table changes. OpenFlow switching monitoring and controller coordination can be made more efficient if the switch can notify a controller of flow table changes as they occur, rather than periodically polling for changes. This commit implements such a feature. Feature #6633. CC: Natasha Gude <natasha@nicira.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-07-12 14:18:05 -07:00
/* NX1.0+(1,517). The 'id' in an NXST_FLOW_MONITOR request is the same as
* an existing monitor id (or two monitors in the same NXST_FLOW_MONITOR
* request have the same 'id'). */
OFPERR_NXBRC_FM_DUPLICATE_ID,
/* NX1.0+(1,518). The 'flags' in an NXST_FLOW_MONITOR request either does
* not specify at least one of the NXFMF_ADD, NXFMF_DELETE, or NXFMF_MODIFY
* flags, or specifies a flag bit that is not defined. */
OFPERR_NXBRC_FM_BAD_FLAGS,
/* NX1.0+(1,519). The 'id' in an NXT_FLOW_MONITOR_CANCEL request is not
* the id of any existing monitor. */
OFPERR_NXBRC_FM_BAD_ID,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## ---------------- ## */
/* ## OFPET_BAD_ACTION ## */
/* ## ---------------- ## */
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2). Error in action description. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_BAD_ACTION,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,0). Unknown action type. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_TYPE,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,1). Length problem in actions. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_LEN,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,2). Unknown experimenter id specified. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_VENDOR,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,3). Unknown action type for experimenter id. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_VENDOR_TYPE,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,4). Problem validating output port. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_OUT_PORT,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,5). Bad action argument. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_ARGUMENT,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,6). Permissions error. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_EPERM,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,7). Can't handle this many actions. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_TOO_MANY,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* OF1.0+(2,8). Problem validating output queue. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_QUEUE,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(2,9). Invalid group id in forward action. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_OUT_GROUP,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(2,10). Action can't apply for this match. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_MATCH_INCONSISTENT,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(2,11). Action order is unsupported for the action list in an
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* Apply-Actions instruction */
OFPERR_OFPBAC_UNSUPPORTED_ORDER,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(2,12). Actions uses an unsupported tag/encap. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBAC_BAD_TAG,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(2,13). Unsupported type in SET_FIELD action. */
OFPERR_OFPBAC_SET_TYPE,
/* OF1.2+(2,14). Length problem in SET_FIELD action. */
OFPERR_OFPBAC_SET_LEN,
/* OF1.2+(2,15). Bad argument in SET_FIELD action. */
OFPERR_OFPBAC_ARGUMENT,
ofp-errors: Rename "OF" to "OF1.0+", "NX" to "NX1.0+". This seems like a more reasonable way to do things given that we will soon need "OpenFlow 1.1 and later" and "OpenFlow 1.1 only" keywords. Signed-off-by: Ben Pfaff <blp@nicira.com> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:22:42 -07:00
/* NX1.0+(2,256). Must-be-zero action argument had nonzero value. */
Add ability to direct "packet-in"s to particular controllers. Nicira's controllers are somewhat heterogeneous, so that particular "packet-in" messages should be directed to particular controllers. This new Nicira extension action allows designating a controller or controllers to receive the "packet-in" using a 16-bit integer ID. The new NXAST_CONTROLLER action also specifies the "reason" code to include in the "packet-in" message. This is particularly useful for simulating a "no-match" "packet-in" using a rule. Feature #8946. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-02-09 14:17:33 -08:00
OFPERR_NXBAC_MUST_BE_ZERO,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## --------------------- ## */
/* ## OFPET_BAD_INSTRUCTION ## */
/* ## --------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(3). Error in instruction list. */
ofp-actions: Add decoding and encoding OF1.1 instructions and actions. So far, only the Apply-Actions instruction is supported, and only actions that have identical semantics to OpenFlow 1.0 actions. Co-authored-by: Simon Horman <horms@verge.net.au> Co-authored-by: Isaku Yamahata <yamahata@valinux.co.jp> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-07-03 22:14:29 -07:00
OFPERR_OFPIT_BAD_INSTRUCTION,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(3,0). Unknown instruction. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBIC_UNKNOWN_INST,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(3,1). Switch or table does not support the instruction. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBIC_UNSUP_INST,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(3,2). Invalid Table-ID specified. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBIC_BAD_TABLE_ID,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(3,3). Metadata value unsupported by datapath. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBIC_UNSUP_METADATA,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(3,4). Metadata mask value unsupported by datapath. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBIC_UNSUP_METADATA_MASK,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.1+(3,5). Unknown experimenter id specified. */
OFPERR_OFPBIC_BAD_EXPERIMENTER,
/* OF1.1(3,5), OF1.2+(3,6). Unknown instruction for experimenter id. */
OFPERR_OFPBIC_BAD_EXP_TYPE,
/* OF1.2+(3,7). Length problem in instructions. */
OFPERR_OFPBIC_BAD_LEN,
/* OF1.2+(3,8). Permissions error. */
OFPERR_OFPBIC_EPERM,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## --------------- ## */
/* ## OFPET_BAD_MATCH ## */
/* ## --------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4). Error in match. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_BAD_MATCH,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,0). Unsupported match type specified by the match */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBMC_BAD_TYPE,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,1). Length problem in match. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBMC_BAD_LEN,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,2). Match uses an unsupported tag/encap. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBMC_BAD_TAG,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,3). Unsupported datalink addr mask - switch does not support
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* arbitrary datalink address mask. */
OFPERR_OFPBMC_BAD_DL_ADDR_MASK,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,4). Unsupported network addr mask - switch does not support
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* arbitrary network address mask. */
OFPERR_OFPBMC_BAD_NW_ADDR_MASK,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,5). Unsupported wildcard specified in the match. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBMC_BAD_WILDCARDS,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(4,6). Unsupported field in the match. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBMC_BAD_FIELD,
ofp-errors: Use standardised code for OFPERR_OFPBMC_BAD_VALUE Use standardised code for Open Flow 1.1 OFPERR_OFPBMC_BAD_VALUE OFPERR_OFPBMC_BAD_VALUE is defined in Open Flow 1.1 as (4,7), so use that code instead of a non-standard one. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-09-04 15:52:03 +09:00
/* NX1.0(1,258), OF1.1+(4,7). Unsupported value in a match
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
* field. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPBMC_BAD_VALUE,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* NX1.0(1,259), NX1.1(1,259), OF1.2+(4,8). Unsupported mask specified in
* the match, field is not dl-address or nw-address. */
OFPERR_OFPBMC_BAD_MASK,
/* NX1.0(1,260), NX1.1(1,260), OF1.2+(4,9). A prerequisite was not met. */
OFPERR_OFPBMC_BAD_PREREQ,
/* NX1.0(1,261), NX1.1(1,261), OF1.2+(4,10). A field type was
* duplicated. */
OFPERR_OFPBMC_DUP_FIELD,
/* OF1.2+(4,11). Permissions error. */
OFPERR_OFPBMC_EPERM,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## --------------------- ## */
/* ## OFPET_FLOW_MOD_FAILED ## */
/* ## --------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(3), OF1.1+(5). Problem modifying flow entry. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_FLOW_MOD_FAILED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(5,0). Unspecified error. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPFMFC_UNKNOWN,
ofp-errors: Merge OF1.0 "all tables full" with OF1.1+ "table full". These codes represent essentially the same condition and only one of them exists in any given version of OpenFlow, so merge them together into a single OFPERR_* code. Reported-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-10-12 10:15:11 -07:00
/* OF1.0(3,0), OF1.1+(5,1). Flow not added because of full table(s). */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPFMFC_TABLE_FULL,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(5,2). Table does not exist */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPFMFC_BAD_TABLE_ID,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(3,1), OF1.1+(5,3). Attempted to add overlapping flow with
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* CHECK_OVERLAP flag set. */
OFPERR_OFPFMFC_OVERLAP,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(3,2), OF1.1+(5,4). Permissions error. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPFMFC_EPERM,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(5,5). Flow not added because of unsupported idle/hard
* timeout. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPFMFC_BAD_TIMEOUT,
/* OF1.0(3,3). Flow not added because of non-zero idle/hard timeout. */
OFPERR_OFPFMFC_BAD_EMERG_TIMEOUT,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(3,4), OF1.1+(5,6). Unsupported or unknown command. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPFMFC_BAD_COMMAND,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(5,7). Unsupported or unknown flags. */
OFPERR_OFPFMFC_BAD_FLAGS,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* OF1.0(3,5). Unsupported action list - cannot process in the order
* specified. */
OFPERR_OFPFMFC_UNSUPPORTED,
/* NX1.0(3,256), NX1.1(5,256). Generic hardware error. */
OFPERR_NXFMFC_HARDWARE,
/* NX1.0(3,257), NX1.1(5,257). A nonexistent table ID was specified in the
* "command" field of struct ofp_flow_mod, when the nxt_flow_mod_table_id
* extension is enabled. */
OFPERR_NXFMFC_BAD_TABLE_ID,
/* ## ---------------------- ## */
/* ## OFPET_GROUP_MOD_FAILED ## */
/* ## ---------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6). Problem modifying group entry. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_GROUP_MOD_FAILED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,0). Group not added because a group ADD attempted to replace
* an already-present group. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPGMFC_GROUP_EXISTS,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,1). Group not added because Group specified is invalid. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPGMFC_INVALID_GROUP,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,2). Switch does not support unequal load sharing with select
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* groups. */
OFPERR_OFPGMFC_WEIGHT_UNSUPPORTED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,3). The group table is full. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPGMFC_OUT_OF_GROUPS,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,4). The maximum number of action buckets for a group has been
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* exceeded. */
OFPERR_OFPGMFC_OUT_OF_BUCKETS,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,5). Switch does not support groups that forward to groups. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPGMFC_CHAINING_UNSUPPORTED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,6). This group cannot watch the watch_port or watch_group
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* specified. */
OFPERR_OFPGMFC_WATCH_UNSUPPORTED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,7). Group entry would cause a loop. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPGMFC_LOOP,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(6,8). Group not modified because a group MODIFY attempted to
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* modify a non-existent group. */
OFPERR_OFPGMFC_UNKNOWN_GROUP,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(6,9). Group not deleted because another
group is forwarding to it. */
OFPERR_OFPGMFC_CHAINED_GROUP,
/* OF1.2+(6,10). Unsupported or unknown group type. */
OFPERR_OFPGMFC_BAD_TYPE,
/* OF1.2+(6,11). Unsupported or unknown command. */
OFPERR_OFPGMFC_BAD_COMMAND,
/* OF1.2+(6,12). Error in bucket. */
OFPERR_OFPGMFC_OFPGMFC_BAD_BUCKET,
/* OF1.2+(6,13). Error in watch port/group. */
OFPERR_OFPGMFC_OFPGMFC_BAD_WATCH,
/* OF1.2+(6,14). Permissions error. */
OFPERR_OFPGMFC_OFPGMFC_EPERM,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## --------------------- ## */
/* ## OFPET_PORT_MOD_FAILED ## */
/* ## --------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(4), OF1.1+(7). OFPT_PORT_MOD failed. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_PORT_MOD_FAILED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(4,0), OF1.1+(7,0). Specified port does not exist. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPPMFC_BAD_PORT,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(4,1), OF1.1+(7,1). Specified hardware address does not match the
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
* port number. */
OFPERR_OFPPMFC_BAD_HW_ADDR,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(7,2). Specified config is invalid. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPPMFC_BAD_CONFIG,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(7,3). Specified advertise is invalid. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPPMFC_BAD_ADVERTISE,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(7,4). Permissions error. */
OFPERR_OFPPMFC_EPERM,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## ---------------------- ## */
/* ## OFPET_TABLE_MOD_FAILED ## */
/* ## ---------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(8). Table mod request failed. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_TABLE_MOD_FAILED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(8,0). Specified table does not exist. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPTMFC_BAD_TABLE,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(8,1). Specified config is invalid. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPTMFC_BAD_CONFIG,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(8,2). Permissions error. */
OFPERR_OFPTMFC_EPERM,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
/* ## --------------------- ## */
/* ## OFPET_QUEUE_OP_FAILED ## */
/* ## --------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(5), OF1.1+(9). Queue operation failed. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_QUEUE_OP_FAILED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(5,0), OF1.1+(9,0). Invalid port (or port does not exist). */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPQOFC_BAD_PORT,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(5,1), OF1.1+(9,1). Queue does not exist. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPQOFC_BAD_QUEUE,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.0(5,2), OF1.1+(9,2). Permissions error. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPQOFC_EPERM,
/* ## -------------------------- ## */
/* ## OFPET_SWITCH_CONFIG_FAILED ## */
/* ## -------------------------- ## */
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(10). Switch config request failed. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPET_SWITCH_CONFIG_FAILED,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(10,0). Specified flags is invalid. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPSCFC_BAD_FLAGS,
ofp-errors: Use OF1.1+ in place of OF1.1 throughout. In general, I guess that the common case is for most error codes to be retained without change in future versions of OpenFlow, so to me it seems best to use the "+" version "by default". Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 11:25:52 -07:00
/* OF1.1+(10,1). Specified len is invalid. */
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
OFPERR_OFPSCFC_BAD_LEN,
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
/* OF1.2+(10,2). Permissions error. */
OFPERR_OFPSCFC_EPERM,
/* ## ------------------------- ## */
/* ## OFPET_ROLE_REQUEST_FAILED ## */
/* ## ------------------------- ## */
/* OF1.2+(11). Controller Role request failed. */
OFPERR_OFPET_ROLE_REQUEST_FAILED,
/* OF1.2+(11,0). Stale Message: old generation_id. */
OFPERR_OFPRRFC_STALE,
/* OF1.2+(11,1). Controller role change unsupported. */
OFPERR_OFPRRFC_UNSUP,
/* NX1.0(1,513), NX1.1(1,513), OF1.2+(11,2). Invalid role. */
OFPERR_OFPRRFC_BAD_ROLE,
/* ## ------------------ ## */
/* ## OFPET_EXPERIMENTER ## */
/* ## ------------------ ## */
/* OF1.2+(0xffff). Experimenter error messages. */
OFPERR_OFPET_EXPERIMENTER,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
};
ofp-error: Remove ofperr_domain from external API It seems that ofp_version suffices in all cases. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-08-01 16:01:49 +09:00
const char *ofperr_domain_get_name(enum ofp_version);
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
bool ofperr_is_valid(enum ofperr);
bool ofperr_is_category(enum ofperr);
bool ofperr_is_nx_extension(enum ofperr);
ofp-error: Remove ofperr_domain from external API It seems that ofp_version suffices in all cases. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-08-01 16:01:49 +09:00
bool ofperr_is_encodable(enum ofperr, enum ofp_version);
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
ofp-error: Remove ofperr_domain from external API It seems that ofp_version suffices in all cases. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-08-01 16:01:49 +09:00
enum ofperr ofperr_decode(enum ofp_version, uint16_t type, uint16_t code);
enum ofperr ofperr_decode_type(enum ofp_version, uint16_t type);
Add error codes for Open Flow v1.2 * Where Open Flow 1.2 breaks apart error codes defined in previous versions, provide all new definitions to previous versions and map the numeric error code to the first first definition supplied in ofp-errors.h. The case handled so far is: OFPERR_OFPBIC_BAD_EXP_TYPE -> { OFPERR_OFPBIC_BAD_EXPERIMENTER, OFPERR_OFPBIC_BAD_EXP_TYPE } * Where Open Flow 1.2 adds error codes that were previously defined as Nicira extension errors define the later in terms of the new codes. Signed-off-by: Simon Horman <horms@verge.net.au> [blp@nicira.com added better error checking in extract-ofp-errors, added unit tests, miscellaneous cleanup] Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Simon Horman <horms@verge.net.au>
2012-03-26 13:46:35 -07:00
enum ofperr ofperr_from_name(const char *);
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
ofp-msgs: New approach to encoding and decoding OpenFlow headers. OpenFlow headers are not as uniform as they could be, with size, alignment, and numbering changes from one version to another and across varieties (e.g. ordinary messages vs. "stats" messages). Until now the Open vSwitch internal APIs haven't done a good job of abstracting those differences in header formats. This commit changes that; from this commit forward very little code actually needs to understand the header format or numbering. Instead, it can just encode or decode, or pull or put, the header using a more abstract API using the ofpraw_, ofptype_, and other APIs in the new ofp-msgs module. Signed-off-by: Ben Pfaff <blp@nicira.com> Tested-by: Simon Horman <horms@verge.net.au> Reviewed-by: Simon Horman <horms@verge.net.au>
2012-07-19 23:23:17 -07:00
enum ofperr ofperr_decode_msg(const struct ofp_header *,
struct ofpbuf *payload);
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
struct ofpbuf *ofperr_encode_reply(enum ofperr, const struct ofp_header *);
ofp-util: Make ofperr_encode_msg__() use correct Open Flow version Make ofperr_encode_msg__() use correct Open Flow version in the header of messages. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-08-01 16:01:48 +09:00
struct ofpbuf *ofperr_encode_hello(enum ofperr, enum ofp_version ofp_version,
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
const char *);
ofp-error: Remove ofperr_domain from external API It seems that ofp_version suffices in all cases. Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-08-01 16:01:49 +09:00
int ofperr_get_type(enum ofperr, enum ofp_version);
int ofperr_get_code(enum ofperr, enum ofp_version);
Better abstract OpenFlow error codes. This commit switches from using the actual protocol values of error codes internally in Open vSwitch, to using abstract values that are translated to and from protocol values at message parsing and serialization time. I believe that this makes the code easier to read and to write. This is also one step along the way toward OpenFlow 1.1 support because OpenFlow 1.1 renumbered a bunch of error codes. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-01-12 15:48:19 -08:00
const char *ofperr_get_name(enum ofperr);
const char *ofperr_get_description(enum ofperr);
void ofperr_format(struct ds *, enum ofperr);
const char *ofperr_to_string(enum ofperr);
Automatically extract error types and codes for formatting.
2011-01-12 13:42:50 -08:00
#endif /* ofp-errors.h */
Reference in New Issue Copy Permalink