This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About plonergan
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- LIVEcommunity
- About plonergan
02-22-2022
7Posts
0Likes
0Solutions
Feb 22, 2022Last Visited
User
Activity
User
Profile
Latest posts by plonergan
| Subject | Views | Posted |
|---|---|---|
| 1311 | 02-11-2022 08:02 AM | |
| 1339 | 02-11-2022 07:00 AM | |
| 1439 | 02-09-2022 01:35 PM | |
| 1000 | 02-03-2022 12:26 PM | |
| 1046 | 02-03-2022 11:05 AM |
User Badges
Community Statistics
| Member Since | 01-27-2022 06:11 AM |
| Date Last Visited | 02-22-2022 08:17 AM |
| Posts | 7 |
02-11-2022
08:02 AM
Jimmy, The documentation update addresses my follow-up question #1. What about #2, the atomicity of the task? It seems you wouldn't want to leave the interface partially configured if the task fails. At least, I wouldn't want to. Peter
... View more
02-11-2022
07:00 AM
Jimmy, That fixed the problem - thanks, I've been banging my head against the wall for two weeks on that one. However, I'm still left with two questions: 1) Why is the vsys required to set the zone, but not to create the interface, add a comment, vrouter, IP address, etc.? All those worked fine without the vsys parameter. 2) If I try to assign a zone without the vsys parameter, and trigger the error as above, all the other task parameters (comment, vrouter, IP address, etc.) are effective, even though the task fails. Doesn't that violate the Ansible philosophy that tasks should be atomic, and either succeed or be completely backed out?
... View more
02-09-2022
01:35 PM
Hello, I'm trying to update or create an aggregate interface or subinterface with a zone_name parameter. Something like: --- - hosts: all name: CONFIGURE NEW AGGREGATE AND SUBINTERFACE IN EXISTING ZONE connection: local gather_facts: False collections: - paloaltonetworks.panos vars: ansible_python_interpreter: /var/lib/awx/venv/ansible/bin/python3 tasks: - name: Configure aggregate interface panos_aggregate_interface: provider: '{{ provider }}' template: "test" if_name: ae2 zone_name: Access Whether the interface exists or not, whether the zone already exists or not, whether the interface is already in the target zone or not, I get the following: The full traceback is: File "/tmp/ansible_panos_aggregate_interface_payload_m7t77c6e/ansible_panos_aggregate_interface_payload.zip/ansible_collections/paloaltonetworks/panos/plugins/modules/panos_aggregate_interface.py", line 296, in main File "/var/lib/awx/venv/ansible/lib/python3.6/site-packages/panos/network.py", line 1063, in set_zone zone_name, mode, refresh, update, running_config, return_type File "/var/lib/awx/venv/ansible/lib/python3.6/site-packages/panos/network.py", line 393, in set_zone mode=mode, File "/var/lib/awx/venv/ansible/lib/python3.6/site-packages/panos/base.py", line 1639, in _set_reference obj.update(reference_var) File "/var/lib/awx/venv/ansible/lib/python3.6/site-packages/panos/base.py", line 702, in update retry_on_peer=self.HA_SYNC, File "/var/lib/awx/venv/ansible/lib/python3.6/site-packages/panos/base.py", line 3682, in method raise the_exception and "msg": "Failed setref: layer3 'ae2' is not a valid reference" If I try something similar with panos_l3_subinterface, I get the same error (slightly different line number references in the calling code). Environment is paloaltonetworks.panos collection 2.9.0 pan-os-python 1.6.0 pandevice 0.14.0 ansible 2.9.11 Python 3.6.8
... View more
02-03-2022
12:26 PM
Yes, but the results aren't much more informative. { "msg": "Subset must be one of [ha, system, config], got vr", "invocation": { "module_args": { "provider": { "api_key": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "ip_address": "lab-pan.net.umd.edu", "username": "admin", "port": 443, "password": null, "serial_number": null }, "gather_subset": [ "vr" ], "username": "admin", "port": 443, "ip_address": null, "password": null, "api_key": null } }, "_ansible_no_log": false, "changed": false }
... View more
02-03-2022
11:05 AM
Looks OK too. pip list | grep pan pan-os-python 1.6.0 pan-python 0.16.0 pandevice 0.14.0
... View more
02-03-2022
10:13 AM
gather_subset : [ ' system' ] works fine. My environment is pretty back-level compared to yours but the panos collection is up to date. ansible --version ansible 2.9.11 config file = /etc/ansible/ansible.cfg configured module search path = ['/usr/local/lib/python3.6/site-packages/git_acp/modules'] ansible python module location = /usr/lib/python3.6/site-packages/ansible executable location = /usr/bin/ansible python version = 3.6.8 (default, Apr 16 2020, 01:36:27) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]
... View more
01-27-2022
06:23 AM
Hello, The module documentation for panos_facts says the gather_subset parameter should be a list with values from all, system, session, interfaces, ha, routing, vr, vsys and config, But when I run a playbook with gather_subset : [ ' vr' ] I get "msg": "Subset must be one of [config, system, ha], got vr". I'm running the panos colletion 2.9.0. Where should I start troubleshooting? Peter
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
02-22-2022
08:17 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2022 - Palo Alto Networks