This configuration ensures availability and stability of the VoIP service, especially during peak traffic hours in your network. Because VoIP implementations require you to separate the data and voice network in order to route packets between them, you need either a layer 3 switch or a router. Our example is based on a scenario you are most likely to come across when dealing with VoIP networks. A good example of a router-on-a-stick configuration (which also happens to be the one we are going to cover) would be a Call Manager Express installation where there is the need to split the VoIP network, consisting of your Cisco IP Phone devices, from your data network where all workstations and servers are located. While some believe the term 'router-on-a-stick' sounds a bit silly, it's a very popular term and commonly used in networks where no layer-3 switch exists. In this setup, the switch is configured with multiple VLANs and the router performs all routing between the different networks/VLANs.
+ Variables: Using YAML, a file can list variables that Ansible will substitute into templates.Router-on-a-stick is a term frequently used to describe a setup up that consists of a router and switch connected using one Ethernet link configured as an 802.1q trunk link. + Templates: Using Jinja2 language, the templates represent a device’s configuration but with variables. An example of a task is to ping all hosts in group. Hosts in an inventory can be divided into smaller groups for easier management and configuration.
+ Inventory: a file contains a list of the hosts (usually their IP addresses, ports) which you want to configure or manage.
Ansible playbooks are written in YAML format. Ansible playbooks are files that contain tasks to configure hosts. + Playbooks: These files provide actions and logic about what Ansible should do. Once Ansible is installed, it creates several text files: Therefore Ansible uses SSH (NETCONF over SSH in particular) to “push” changes and extract information to managed devices. Agentless means that the managed device does not need any code (agent) to be installed on it. In this tutorial we will learn some basic knowledge of Ansible in the scope of CCNA level.Īnsible uses an agentless architecture to manage network devices. There are several automation tools available to make configuration management easier: Ansible, Chef, Puppet… The goal of these tools is to reduce the complexity and time to configure and maintain networks (especially big ones with hundreds of devices).
0 kommentar(er)
