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
When a new port-channel is configured within vlans, and first vlan where it's configured is as tagged, and then a second vlan is configured as untagged vlan, the switch comes up with an error.
Once first entry commented out, it passes fine.
Then, when entry added again, it passes fine and required configuration is achieved.
ALLOW_WORLD_READABLE_TMPFILES(/home/wojciechk/git/auto/ansible.cfg) = True
ANSIBLE_COW_SELECTION(/home/wojciechk/git/auto/ansible.cfg) = stegosaurus
ANSIBLE_FORCE_COLOR(/home/wojciechk/git/auto/ansible.cfg) = True
ANSIBLE_NOCOWS(/home/wojciechk/git/auto/ansible.cfg) = True
COLLECTIONS_PATHS(/home/wojciechk/git/auto/ansible.cfg) = [u'/home/wojciechk/git/auto/galaxy-roles']
DEFAULT_FORKS(/home/wojciechk/git/auto/ansible.cfg) = 20
DEFAULT_LOG_PATH(/home/wojciechk/git/auto/ansible.cfg) = /home/wojciechk/git/auto/log_ansible.txt
DEFAULT_MANAGED_STR(/home/wojciechk/git/auto/ansible.cfg) = This file is being managed with Ansible. Do NOT update it manually.
DEFAULT_ROLES_PATH(/home/wojciechk/git/auto/ansible.cfg) = [u'/home/wojciechk/git/auto/galaxy-roles', u'/home/wojciechk/git/auto/roles']
DEFAULT_TRANSPORT(/home/wojciechk/git/auto/ansible.cfg) = ssh
DISPLAY_SKIPPED_HOSTS(env: ANSIBLE_DISPLAY_SKIPPED_HOSTS) = True
HOST_KEY_CHECKING(/home/wojciechk/git/auto/ansible.cfg) = False
INTERPRETER_PYTHON(/home/wojciechk/git/auto/ansible.cfg) = /usr/bin/python3
INVENTORY_ENABLED(/home/wojciechk/git/auto/ansible.cfg) = [u'auto', u'vmware_vm_inventory', u'yaml', u'host_list']
OS / ENVIRONMENT
Current Type : S5148F
Hardware Revision : A00
Software Version : 10.4.3.6
STEPS TO REPRODUCE
I have multiple vlans configured.
I have added port-channel 3 to the configuration, and added it to relevant vlans.
Once first entry (for vlan12) was commented out, it passes fine.
Then, when entry added again, it passes fine and required configuration is achieved.
(IPs changed for privacy).
To add to this one, once a port has been disabled and had
switchport: false
The the VLAN role is helpless witch turning it back on. Regardless whether I want switchport mode access or mode trunk, the role is unable to turn it on.
fatal: [lon1sw1]: FAILED! => changed=false
command: switchport access vlan 2001
msg: |-
switchport access vlan 2001
% Error: vlan2001, Interface being added (to VLAN) is not in switchport mode access or trunk!.
lon1sw1(conf-if-eth1/1/5)#
rc: -32603
Please fix it, as I need to apply fixes manually everytime this shows up...
SUMMARY
When a new port-channel is configured within vlans, and first vlan where it's configured is as tagged, and then a second vlan is configured as untagged vlan, the switch comes up with an error.
Once first entry commented out, it passes fine.
Then, when entry added again, it passes fine and required configuration is achieved.
ISSUE TYPE
COMPONENT NAME
os10_vlan
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Current Type : S5148F
Hardware Revision : A00
Software Version : 10.4.3.6
STEPS TO REPRODUCE
I have multiple vlans configured.
I have added port-channel 3 to the configuration, and added it to relevant vlans.
Once first entry (for vlan12) was commented out, it passes fine.
Then, when entry added again, it passes fine and required configuration is achieved.
(IPs changed for privacy).
EXPECTED RESULTS
Port-channel 3 added will have trunk mode enabled, with access mode for vlan 2255 and trunk mode for vlan 12.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: