*
> dewdrop: ok=1changed=0unreachable=0failed=0
> skipped=0rescued=0ignored=0
>
> As you can see, it produced the output you expected in the right order.
>
> I can only conclude that the version of the cisco.io
you can see, it produced the output you expected in the right order.
>
> I can only conclude that the version of the cisco.ios collection you are
> using is (a) different from mine and (b) somewhat broken, at least in this
> one case. My version seems to be (from
> /usr/lib/python3.12/
> > How can I fix this?
> You can start by showing us how you render them. What does your "Render
> the provided configuration" task look like?
>
> On 4/5/24 3:36 AM, L. Jankok wrote:
>
> When using the cisco.ios.ios_acls module I get the remarks at the end
When using the cisco.ios.ios_acls module I get the remarks at the end of
the standard access-list instead of between the ACL entries.
When I render the following:
acls:
- afi: ipv4
acls:
- name: ACL-EXAMPLE
acl_type: standard
aces:
- sequence: 10
PR with
> the issue <https://github.com/ansible-collections/cisco.ios/issues/512>
> tagged.
>
> Regards,
> Sagar Paul
> *E - sagp...@redhat.com <https://groups.google.com/> GH - KB-perByte*
>
> On Sun, Mar 6, 2022 at 4:04 PM L. Jankok wrote:
>
>> Hi Sagar,
&
Hi Sagar,
If I want to change to scope myself, can you tell me which file I need to
patch?
Regards,
Lucio Jankok
Op ma 7 feb. 2022 om 12:42 schreef Sagar Paul :
> Hey Lucio,
>
> The scope of the l2_interfaces module depends on the command `show
> running-config | section ^interface` the facts
Thank you Sagar!
Much appreciated.
Op ma 7 feb. 2022 om 12:42 schreef Sagar Paul :
> Hey Lucio,
>
> The scope of the l2_interfaces module depends on the command `show
> running-config | section ^interface` the facts are generated with the
> config op from the specific command. You may want to
Hi Thom,
Thank you for your time and your interest, truly appreciated.
With interface templates you will not see the vlans or other port
configurations on the interface when running show run int interface-name.
To see the applied configuration on the interface the command "show
derived-config" is
Hi Saga,
Actually there is.
The configuration is being applied using source templates.
Regards,
Lucio Jankok
Op vr 4 feb. 2022 om 11:01 schreef Sagar Paul :
>
> Hey Lucio,
> as I see in the config that you have shared, there is no switchport or
> vlan data to parse as per the current scope
Hi Sagar,
The following is the case:
*With the following platform I have no issues*
platform: cisco WS-3850-24S
net_iostype: IOS-XE
net_version: 16.06.05
output:
net_interfaces - show me interface configuration per interface
net_neighbors - shows me Mac address etc for all connected devices
Hi,
When I use the gather fact module and choose to get the l2_interfaces, it
doesn't return the l2_interfaces properties.
When I use the same playbook on catalyst 3650 (also ios-xe) I get the
l2_interfaces properties.
Is this a known issue?
Regards,
Lucio Jankok
--
You received this message
Hi,
In the past when I have used ansible_network_resources.l2_interfaces it
provided me with a dictionary. But now I am getting a class type list
variable instead of a dictionary (which is odd). Therefore I am missing all
those values like item.access, item.trunk etc.
I know I am missing
Hi there,
I am using the following tasks to iterate over all policy-maps (outer loop)
and I would also like to iterate over all class-maps into each policy-map
(inner-loop)
- name: Gather all policy-maps
ansible.utils.cli_parse:
command: show policy-map
parser:
13 matches
Mail list logo
