WEBVTT

1
00:00:00.050 --> 00:00:08.050
Run Ansible playbooks from a simulated Linux or Windows PC inside your nuLAB lab.

2
00:00:15.300 --> 00:00:23.300
In My Labs, open Marketplace, choose Labs and find the free Ansible Starter Lab.

3
00:00:27.050 --> 00:00:36.050
Install your own copy; the starter contains one IOS XE router and three ready-to-use controller PCs.

4
00:00:45.000 --> 00:00:50.500
Open the Linux PC desktop and launch Ansible Manager.

5
00:00:50.700 --> 00:00:59.200
The starter includes a YAML playbook and an INI inventory in the controller’s Ansible workspace.

6
00:01:06.250 --> 00:01:14.750
The inventory names the target, its address and the connection settings for this disposable lab.

7
00:01:16.150 --> 00:01:23.250
This playbook uses RESTCONF to change the IOS XE router’s hostname.

8
00:01:34.000 --> 00:01:41.500
Select the playbook and inventory, then limit this run to the router alias.

9
00:01:45.150 --> 00:01:52.150
Validate and preview hosts to confirm the selected target before running tasks.

10
00:01:52.500 --> 00:01:59.500
The preview validates the files and lists hosts without changing the router.

11
00:02:14.100 --> 00:02:20.100
Turn on Check mode to predict the supported configuration change.

12
00:02:27.350 --> 00:02:34.450
The recap predicts one change; the router still has its original hostname.

13
00:02:45.200 --> 00:02:52.200
Turn off Check mode and run the playbook to apply the change.

14
00:02:52.700 --> 00:02:58.450
Read the task output, exit status and per-host recap.

15
00:03:03.500 --> 00:03:11.000
Open the router terminal and verify the new hostname in its running configuration.

16
00:03:21.900 --> 00:03:29.450
Run the same playbook again; an already correct configuration reports zero changes.

17
00:03:39.250 --> 00:03:47.750
The Windows PC also has Ansible Manager and its own copies of the starter files.

18
00:03:52.000 --> 00:03:58.500
Preview the target from Windows, then check the already configured router.

19
00:04:06.450 --> 00:04:13.950
You can use the terminal too; this PowerShell command lists the selected hosts.

20
00:04:21.550 --> 00:04:30.550
To bring your own playbook, open File Manager on the controller where you will run it.

21
00:04:33.650 --> 00:04:39.150
Import the YAML file into the controller’s Ansible workspace.

22
00:04:39.550 --> 00:04:49.050
Files are local to that simulated PC; importing here does not add files to the other controllers.

23
00:04:57.250 --> 00:05:02.750
Refresh Ansible Manager and select the newly imported playbook.

24
00:05:05.650 --> 00:05:13.150
Preview the host selection and use Check mode before applying your new task.

25
00:05:18.250 --> 00:05:25.750
Apply the playbook, then verify the second hostname change in the router terminal.

26
00:05:31.300 --> 00:05:39.800
The Linux terminal can run the same imported playbook with its inventory and host limit.

27
00:05:40.050 --> 00:05:47.150
A repeat reports zero changes because the requested hostname already matches.

28
00:05:59.200 --> 00:06:05.700
An incorrect host limit fails clearly and leaves the router unchanged.

29
00:06:09.000 --> 00:06:15.000
Restore the valid limit and run again to confirm recovery.

30
00:06:36.600 --> 00:06:45.100
Save the lab and router configuration, then reopen your lab to check the saved workspace.

31
00:06:54.550 --> 00:07:04.200
Use the supported playbook subset shown in Manager; roles, loops, templates and arbitrary plugins are outside it.

32
00:07:04.350 --> 00:07:12.400
The companion Help article covers inventory syntax, supported modules, connection setup and troubleshooting.