# Cisco Modules

**URL:** <https://forum.ansible.com/t/cisco-modules/20990>\
**Category:** Ansible Project\
**Created:** [March 26, 2016, 1:41am UTC](https://forum.ansible.com/t/cisco-modules/20990 "2016-03-26T01:41:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roger\_Gomez](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@Roger\_Gomez](https://forum.ansible.com/u/Roger_Gomez)\
**Post date:** [March 26, 2016, 1:41am UTC](https://forum.ansible.com/t/cisco-modules/20990/1 "2016-03-26T01:41:01Z")

</div>

Normally when we use regular plays, we define a group of hosts and all the tasks in the playbook are executed in the list of hosts defined. For the case of the Cisco modules we need an additional host inside each module declaration for the tasks:

`

---

<div class="post-metadata">

**Author:** ![Lisa\_Huang](https://avatars.discourse-cdn.com/v4/letter/l/f04885/32.png) [@Lisa\_Huang](https://forum.ansible.com/u/Lisa_Huang)\
**Post date:** [July 13, 2016, 8:29pm UTC](https://forum.ansible.com/t/cisco-modules/20990/2 "2016-07-13T20:29:35Z")

</div>

My guess it is for nxapi API.
