Chapters and transcript times will be ready shortly. You can use the video’s Play control or open the MP4 below.
Chapters
Narration transcript
The English narration in this video. Select a time to watch that moment.
Run Ansible playbooks from a simulated Linux or Windows PC inside your nuLAB lab.
In My Labs, open Marketplace, choose Labs and find the free Ansible Starter Lab.
Install your own copy; the starter contains one IOS XE router and three ready-to-use controller PCs.
Open the Linux PC desktop and launch Ansible Manager.
The starter includes a YAML playbook and an INI inventory in the controller’s Ansible workspace.
The inventory names the target, its address and the connection settings for this disposable lab.
This playbook uses RESTCONF to change the IOS XE router’s hostname.
Select the playbook and inventory, then limit this run to the router alias.
Validate and preview hosts to confirm the selected target before running tasks.
The preview validates the files and lists hosts without changing the router.
Turn on Check mode to predict the supported configuration change.
The recap predicts one change; the router still has its original hostname.
Turn off Check mode and run the playbook to apply the change.
Read the task output, exit status and per-host recap.
Open the router terminal and verify the new hostname in its running configuration.
Run the same playbook again; an already correct configuration reports zero changes.
The Windows PC also has Ansible Manager and its own copies of the starter files.
Preview the target from Windows, then check the already configured router.
You can use the terminal too; this PowerShell command lists the selected hosts.
To bring your own playbook, open File Manager on the controller where you will run it.
Import the YAML file into the controller’s Ansible workspace.
Files are local to that simulated PC; importing here does not add files to the other controllers.
Refresh Ansible Manager and select the newly imported playbook.
Preview the host selection and use Check mode before applying your new task.
Apply the playbook, then verify the second hostname change in the router terminal.
The Linux terminal can run the same imported playbook with its inventory and host limit.
A repeat reports zero changes because the requested hostname already matches.
An incorrect host limit fails clearly and leaves the router unchanged.
Restore the valid limit and run again to confirm recovery.
Save the lab and router configuration, then reopen your lab to check the saved workspace.
Use the supported playbook subset shown in Manager; roles, loops, templates and arbitrary plugins are outside it.
The companion Help article covers inventory syntax, supported modules, connection setup and troubleshooting.