Limitations
The following are the current limitations while configuring OcNOS through Ansible.
1. The following commands in OcNOS require the device to be rebooted to be effective.
• hardware-profile
• forwarding profile
• maximum-paths
• copy empty-config startup-config
Ansible returns success while configuring these commands. However, the device needs to be rebooted to make these effective.
2. By default, ANSIBLE_PERSISTENT_COMMAND_TIMEOUT is set to 30 (seconds). While pushing large configs through Ansible which might be taking more time than this default timeout, it is suggested that to increase the ansible_command_timeout to appropriate value. In group_vars/ocnos.yml, it is suggested to add the below line with appropriate timeout value:
ansible_command_timeout: 1800
3. While configuring the below commands, there are certain warning messages shown to the customer. Currently Ansible treats them as failure and returns failure even though it is successful. It is suggested that the user takes appropriate action while configuring these commands.
• no ip vrf <vrf-id>
• While re-configuring shaping as part of QoS:
policy-map type queuing shaper
class type queuing defaultq
shape 10 gbps
exit
Last modified date: 06/08/2023