Parameter |
Choices/Defaults |
Comments |
address
string
|
|
Specifies the IP address that will receive messages from the specified local Log Destination.
This parameter is only available when type is management-port .
When creating a new log destination and type is management-port , this parameter is required.
|
description
string
|
|
The description of the log destination.
|
distribution
string
|
Choices:
- adaptive
- balanced
- replicated
|
Specifies the distribution method used by the Remote High Speed Log destination to send messages to pool members.
When adaptive , connections to pool members will be added as required to provide enough logging bandwidth. This can have the undesirable effect of logs accumulating on only one pool member when it provides sufficient logging bandwidth on its own.
When balanced , sends each successive log to a new pool member, balancing the logs among them according to the pool's load balancing method.
When replicated , replicates each log to all pool members, for redundancy.
When creating a new log destination and type is remote-high-speed-log , if this parameter is not specified, the default is adaptive .
|
forward_to
string
|
|
When type is remote-syslog , specifies the management port log destination, which will be used to forward the logs to a single log server, or a remote high-speed log destination, which will be used to forward the logs to a pool of remote log servers.
When type is splunk or arcsight , specifies the log destination to which logs are forwarded. This log destination may be a management port destination, a remote high-speed log destination, or a remote Syslog destination which is configured to send logs to an ArcSight or Splunk server.
When creating a new log destination and type is remote-syslog , splunk , or arcsight , this parameter is required.
|
name
string
/ required
|
|
Specifies the name of the log destination.
|
partition
string
|
Default:
"Common"
|
Device partition to manage resources on.
|
pool
string
|
|
When type is remote-high-speed-log , specifies the existing pool of remote high-speed log servers where logs will be sent.
When type is ipfix , specifies the existing LTM pool of remote IPFIX collectors. Any BIG-IP application that uses this log destination sends its IP-traffic logs to this pool of collectors.
When creating a new destination and type is remote-high-speed-log or ipfix , this parameter is required.
|
port
integer
|
|
Specifies the port of the IP address that will receive messages from the specified local Log Destination.
This parameter is only available when type is management-port .
When creating a new log destination and type is management-port , this parameter is required.
|
protocol
string
|
Choices:
- tcp
- udp
- ipfix
- netflow-9
|
When type is remote-high-speed-log , specifies the protocol for the system to use to send logs to the pool of remote high-speed log servers, where the logs are stored.
When type is ipfix , can be IPFIX or Netflow v9, depending on the type of collectors you have in the pool that you specify.
When type is management-port , specifies the protocol used to send messages to the specified location.
When type is management-port , only tcp and udp are valid values.
|
provider
dictionary
added in 1.0.0 of f5networks.f5_modules
|
|
A dict object containing connection details.
|
|
auth_provider
string
|
|
Configures the auth provider for to obtain authentication tokens from the remote device.
This option is really used when working with BIG-IQ devices.
|
|
no_f5_teem
boolean
|
|
If yes , TEEM telemetry data is not sent to F5.
You may omit this option by setting the environment variable F5_TEEM .
|
|
password
string
/ required
|
|
The password for the user account used to connect to the BIG-IP.
You may omit this option by setting the environment variable F5_PASSWORD .
aliases: pass, pwd
|
|
server
string
/ required
|
|
The BIG-IP host.
You may omit this option by setting the environment variable F5_SERVER .
|
|
server_port
integer
|
Default:
443
|
The BIG-IP server port.
You may omit this option by setting the environment variable F5_SERVER_PORT .
|
|
timeout
integer
|
|
Specifies the timeout in seconds for communicating with the network device for either connecting or sending commands. If the timeout is exceeded before the operation is completed, the module will error.
|
|
transport
string
|
|
Configures the transport connection to use when connecting to the remote device.
|
|
user
string
/ required
|
|
The username to connect to the BIG-IP with. This user must have administrative privileges on the device.
You may omit this option by setting the environment variable F5_USER .
|
|
validate_certs
boolean
|
|
If no , SSL certificates are not validated. Use this only on personally controlled sites using self-signed certificates.
You may omit this option by setting the environment variable F5_VALIDATE_CERTS .
|
server_ssl_profile
string
|
|
If the transport_profile is a TCP profile, you can use this field to choose a Secure Socket Layer (SSL) profile for sending logs to the IPFIX collectors.
An SSL server profile defines how to communicate securely over SSL or Transport Layer Security (TLS).
This parameter is only available when type is ipfix .
|
state
string
|
Choices:
present ←
- absent
|
When present , ensures the resource exists.
When absent , ensures the resource is removed.
|
syslog_format
string
|
Choices:
- bsd-syslog
- syslog
- legacy-bigip
- rfc5424
- rfc3164
|
Specifies the method to use to format the logs associated with the remote Syslog log destination.
When creating a new log destination (and type is remote-syslog ), if this parameter is not specified, the default is bsd-syslog .
The syslog and rfc5424 choices are the same.
The bsd-syslog and rfc3164 choices are the same.
|
template_delete_delay
integer
|
|
Enter the time (in seconds) that the BIG-IP device should pause between deleting an obsolete IPFIX template and reusing its template ID.
This feature is useful for systems where you use iRules to create customized IPFIX templates.
|
template_retransmit_interval
integer
|
|
Enter the time (in seconds) between each transmission of IPFIX templates to the pool of IPFIX collectors.
The logging destination periodically retransmits all of its IPFIX templates at the interval you set in this field. These retransmissions are helpful for UDP, a lossy transport mechanism.
This parameter is only available when type is ipfix .
|
transport_profile
string
|
|
Is a transport profile based on either TCP or UDP.
This profile defines the TCP or UDP options used to send IP-traffic logs to the pool of collectors.
This parameter is only available when type is ipfix .
|
type
string
/ required
|
Choices:
- remote-high-speed-log
- remote-syslog
- arcsight
- splunk
- management-port
- ipfix
|
Specifies the type of log destination.
Once created, this parameter cannot be changed.
|