Log::IPFIXInformationElement::DataType¶
Members¶
Member
Value
Description
IPFIX_DATA_TYPE_UNKNOWN
0
The data type is unknown (or unsupported by iControl).
IPFIX_DATA_TYPE_OCTETARRAY
1
Represents a finite-length string of octets.
IPFIX_DATA_TYPE_UNSIGNED8
2
A non-negative integer value in the range of 0 to 255.
IPFIX_DATA_TYPE_UNSIGNED16
3
A non-negative integer value in the range of 0 to 65535.
IPFIX_DATA_TYPE_UNSIGNED32
4
A non-negative integer value in the range of 0 to 4294967295.
IPFIX_DATA_TYPE_UNSIGNED64
5
A non-negative integer value in the range of 0 to 18446744073709551615.
IPFIX_DATA_TYPE_SIGNED8
6
An integer value in the range of -127 to 128.
IPFIX_DATA_TYPE_SIGNED16
7
An integer value in the range of -32768 to 32767.
IPFIX_DATA_TYPE_SIGNED32
8
An integer value in the range of -2147483648 to 2147483647.
IPFIX_DATA_TYPE_SIGNED64
9
An integer value in the range of -9223372036854775808 to 9223372036854775807.
IPFIX_DATA_TYPE_FLOAT32
10
Corresponds to an IEEE single-precision 32-bit floating point type as defined in IEEE.754.1985.
IPFIX_DATA_TYPE_FLOAT64
11
Corresponds to an IEEE double-precision 64-bit floating point type as defined in IEEE.754.1985.
IPFIX_DATA_TYPE_BOOLEAN
12
Represents a binary value. The only allowed values are “true” and “false”.
IPFIX_DATA_TYPE_MACADDRESS
13
Represents a string of 6 octets.
IPFIX_DATA_TYPE_STRING
14
The type “string” represents a finite-length string of valid characters from the Unicode character encoding set ISO.10646-1.1993. Unicode allows for ASCII ISO.646.1991 and many other international character sets to be used.
IPFIX_DATA_TYPE_DATETIMESECONDS
15
The type “dateTimeSeconds” represents a time value in units of seconds based on coordinated universal time (UTC). The choice of an epoch, for example, 00:00 UTC, January 1, 1970, is left to corresponding encoding specifications for this type, for example, the IPFIX protocol specification. Leap seconds are excluded. Note that transformation of values might be required between different encodings if different epoch values are used.
IPFIX_DATA_TYPE_DATETIMEMILLISECONDS
16
The type “dateTimeMilliseconds” represents a time value in units of seconds based on coordinated universal time (UTC). The choice of an epoch, for example, 00:00 UTC, January 1,1970, is left to corresponding encoding specifications for this type, for example, the IPFIX protocol specification. Leap seconds are excluded. Note that transformation of values might be required between different encodings if different epoch values are used.
IPFIX_DATA_TYPE_DATETIMEMICROSECONDS
17
The type “dateTimeMicroseconds” represents a time value in units of seconds based on coordinated universal time (UTC). The choice of an epoch, for example, 00:00 UTC, January 1,1970, is left to corresponding encoding specifications for this type, for example, the IPFIX protocol specification. Leap seconds are excluded. Note that transformation of values might be required between different encodings if different epoch values are used.
IPFIX_DATA_TYPE_DATETIMENANOSECONDS
18
The type “dateTimeNanoseconds” represents a time value in units of seconds based on coordinated universal time (UTC). The choice of an epoch, for example, 00:00 UTC, January 1,1970, is left to corresponding encoding specifications for this type, for example, the IPFIX protocol specification. Leap seconds are excluded. Note that transformation of values might be required between different encodings if different epoch values are used.
IPFIX_DATA_TYPE_IPV4ADDRESS
19
Represents a value of an IPv4 address.
IPFIX_DATA_TYPE_IPV6ADDRESS
20
Represents a value of an IPv6 address. @Introduced BIG-IP_v11.6.0
See Also¶
Warning
The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.
Sample Code¶
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.