InlineIpfixDfwConfig1

JSON Example

{
    "active_flow_export_timeout": 0,
    "collector": "string",
    "observation_domain_id": 0,
    "priority": 0,
    "template_parameters": {
        "destination_address": false,
        "destination_transport_port": false,
        "firewall_event": false,
        "flow_direction": false,
        "flow_end": false,
        "flow_start": false,
        "icmp_code": false,
        "octet_delta_count": false,
        "packet_delta_count": false,
        "protocol_identifier": false,
        "rule_id": false,
        "source_address": false,
        "source_icmp_type": false,
        "source_transport_port": false,
        "vif_uuid": false
    }
}

integer As int64 As int64

active_flow_export_timeout

Optional

Constraints: minimum: 1 maximum: 60 default: 1

For long standing active flows, IPFIX records will be sent per timeout period

string

collector

Required

Each IPFIX DFW config can have its own collector config.

integer As int64 As int64

observation_domain_id

Required

Constraints: minimum: 0 maximum: 4294967295

An identifier that is unique to the exporting process and used to meter the Flows.

integer As int64 As int64

priority

Required

Constraints: minimum: 0 maximum: 65536 default: 0

This priority field is used to resolve conflicts in Logical Ports which are covered by more than one IPFIX profiles. The IPFIX exporter will send records to Collectors in highest priority profile (lowest number) only.

IpfixDfwTemplateParameters

template_parameters

Optional

This entity represents the flow parameters which are exported.

Used By

IpfixDfwConfig