wti.remote.cpm_syslog_client_info lookup – Get network SYSLOG Client parameters from WTI OOB and PDU devices
Note
This lookup plugin is part of the wti.remote collection (version 1.0.4).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install wti.remote
.
To use it in a playbook, specify: wti.remote.cpm_syslog_client_info
.
New in version 2.11.0: of wti.remote
Parameters
Parameter |
Comments |
---|---|
This is the Password of the WTI device to send the module. |
|
This is the URL of the WTI device to send the module. |
|
This is the Username of the WTI device to send the module. |
|
This is the ethernet port name that is getting retrieved. It can include a single ethernet port name, multiple ethernet port names separated by commas or not defined for all ports. Choices:
|
|
Designates to use an https connection or http connection. Choices:
|
|
Flag to control if the lookup will observe HTTP proxy environment variables when present. Choices:
|
|
If false, SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. Choices:
|
Examples
- name: Get the network SYSLOG Client Parameters for all interfaces of a WTI device.
cpm_interface_info:
cpm_url: "nonexist.wti.com"
cpm_username: "super"
cpm_password: "super"
use_https: true
validate_certs: false
- name: Get the network SYSLOG Client Parameters for eth0 of a WTI device.
cpm_interface_info:
cpm_url: "nonexist.wti.com"
cpm_username: "super"
cpm_password: "super"
use_https: false
validate_certs: false
interface: "eth0"
Return Values
Common return values are documented here, the following are the fields unique to this lookup:
Key |
Description |
---|---|
The output JSON returned from the commands sent Returned: always |
|
Current k/v pairs of SYSLOG Client info for the WTI device after module execution. Returned: always Sample: {“syslogclient”: {“ietf-ipv4”: {“clients”: [{“address”: “”, “index”: “1”, “port”: “514”, “secure”: “0”, “transport”: “0”}, {“address”: “”, “index”: “2”, “port”: “514”, “secure”: “0”, “transport”: “0”}, {“address”: “”, “index”: “3”, “port”: “514”, “secure”: “0”, “transport”: “0”}, {“address”: “”, “index”: “4”, “port”: “514”, “secure”: “0”, “transport”: “0”}]}, “ietf-ipv6”: {“clients”: [{“address”: “”, “index”: “1”, “port”: “514”, “secure”: “0”, “transport”: “0”}, {“address”: “”, “index”: “2”, “port”: “514”, “secure”: “0”, “transport”: “0”}, {“address”: “”, “index”: “3”, “port”: “514”, “secure”: “0”, “transport”: “0”}, {“address”: “”, “index”: “4”, “port”: “514”, “secure”: “0”, “transport”: “0”}]}}} |
Authors
Western Telematic Inc. (@wtinetworkgear)
Hint
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.