You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're experiencing an issue with the cisco.ios.ios_config module. It appears that it corrects/removes duplicate lines before pushing config to the switch. Our task configures these duplicate lines underneath different subcategories however, so they're actually valid code instead of real duplicates. We tried several module options (lines, block, etc.) to see if that would solve our issue, but unfortunately it didn't.
Simple example
Class-map A
Line A
Class-map B
Line A
Class-map C
Line A
turns into
Class-map A
Line A
Class-map B
Class-map C
Could you please assist with this issue? Is is a functionality that can be disabled? Is it an issue that requires a fix? Can we code an easy work-around?
!
policy-map PM_E_1gb
description policy map that processes all outgoing traffic for 1Gb interfaces
class CM_Q1
bandwidth remaining ratio 3
class CM_Q2
bandwidth remaining ratio 3
class CM_Q3
bandwidth remaining ratio 3
class CM_Q4
bandwidth remaining ratio 3
class CM_Q5
bandwidth remaining ratio 3
class CM_Q6
priority level 2
class CM_Q7
priority level 1
class class-default
bandwidth remaining ratio 3
police rate percent 10
conform-action transmit
exceed-action drop
ACTUAL RESULTS
After running the task the switch config shows that 'bandwidth remaining ratio 3' has only been applied to class-default.
We ran some tests, and its always the first 'bandwidth remaining ratio 3' command to the switch that gets applied. In this case class-default.
!
policy-map PM_E_1gb
description policy map that processes all outgoing traffic for 1Gb interfaces
class CM_Q1
class CM_Q2
class CM_Q3
class CM_Q4
class CM_Q5
class CM_Q6
priority level 2
class CM_Q7
priority level 1
class class-default
bandwidth remaining ratio 3
police rate percent 10
conform-action transmit
exceed-action drop
. Task output
This contains the debug and -vvv task output:
The text was updated successfully, but these errors were encountered:
RobKoerts
changed the title
The cisco.ios.ios_config module doesn't push valid duplicate lines (same config lines in subcatecories) to the switch
The cisco.ios.ios_config module doesn't push valid duplicate lines (identical config lines in subcatecories) to the switch
Feb 3, 2023
RobKoerts
changed the title
The cisco.ios.ios_config module doesn't push valid duplicate lines (identical config lines in subcatecories) to the switch
The cisco.ios.ios_config module doesn't push valid duplicate lines (identical config lines in different subcatecories) to the switch
Feb 3, 2023
SUMMARY
We're experiencing an issue with the cisco.ios.ios_config module. It appears that it corrects/removes duplicate lines before pushing config to the switch. Our task configures these duplicate lines underneath different subcategories however, so they're actually valid code instead of real duplicates. We tried several module options (lines, block, etc.) to see if that would solve our issue, but unfortunately it didn't.
Simple example
Class-map A
Line A
Class-map B
Line A
Class-map C
Line A
turns into
Class-map A
Line A
Class-map B
Class-map C
Could you please assist with this issue? Is is a functionality that can be disabled? Is it an issue that requires a fix? Can we code an easy work-around?
ISSUE TYPE
COMPONENT NAME
cisco.ios.ios_config
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Server that runs Ansible
.
Target switch
STEPS TO REPRODUCE
Here's an example regarding QoS policy-maps from A to Z, including a debug and the configured and expected switch config:
Policy-map task
.
Policy-map JINJA2 template
.
Variables
EXPECTED RESULTS
This is the switch config we expected:
ACTUAL RESULTS
After running the task the switch config shows that 'bandwidth remaining ratio 3' has only been applied to class-default.
We ran some tests, and its always the first 'bandwidth remaining ratio 3' command to the switch that gets applied. In this case class-default.
.
Task output
This contains the debug and -vvv task output:
The text was updated successfully, but these errors were encountered: