ansible_network_os informs Ansible which Network platform the hosts corresponds to. This is required when using ansible_connection=network_cli.
For network_cli connection methods the ansible_network_os variable must be set. This variable informs Ansible which network platform each host corresponds to. For example, if the device is a Juniper router, ansible_network_os must be set to junos. This can be set as a variable or even within the inventory itself. Refer to the following table for the networking platforms corresponding ansible_network_os parameter:
you can use ansible_network_os in an inventory. for example:
[ios] ios01.example.net
[ios:vars] ansible_connection=network_cli ansible_user=username ansible_become=yes ansible_become_method=enable ansible_network_os=ios or directly in playbook
Or you can use ansible_network_os in playbooks. For example:
Thank you for the reply and all the information but here i am looking specifically for the checkpoint firewall os name which i should mention.
ansible_network _os: ? (for checkpoint firewall)
TASK [trib_role : SHOW CONFIG] **************************************************************************************************************************************************************************************************************
fatal: [firewall]: FAILED! => {“msg”: “unable to load API plugin for network_os checkpoint”}
to retry, use: --limit @/etc/ansible/cp1.retry
When i am using network_cli then below error is coming:
-bash-4.2$ ansible-playbook cp2.yml
PLAY [CheckPoint health Status] *************************************************************************************************************************************************************************************************************
TASK [checkpoint healthcheck commands] ******************************************************************************************************************************************************************************************************
fatal: [firewall]: FAILED! => {“msg”: “unable to set terminal parameters”}
It does support these modules. I have already tested in my test lab environment.
It’s just the production where i am getting these error messages and need help.