From the blueprint, navigate to Staged > Virtual > Routing Zones and click Create Routing Zone.

Name the VRF Finance and leave the remaining fields empty, which allows the values to be assigned from a resource pool. Select the Default_immutable routing policy, which affects the route-maps that Apstra applies to the RZ. Leave all other fields in their default settings.

Now, we need to assign the resources to the RZ where the red tabs are indicating. Edit the fields as you have done in earlier exercises. Use the pools listed in the table below for these assignments.

Your screen should now appear as the image below.

Click the Finance RZ name in the table to reveal the details of this instance. You can see the resources that have now been allocated to this RZ.

In the routing zone details view, click the Assign DHCP Servers button.

In the dialog that appears, enter the DHCP server IP address 9.0.0.1, then click Update.

Click the yellow Uncommitted tab to view our staged changes. After viewing the details, we will click Commit. In the dialog that appears, enter the revision description "Added Finance routing zone", then click Commit. Your blueprint will now be updated with the changes.

Navigate to Staged > Connectivity Templates and click the edit button to the right of the external_router_peering that we created earlier.

Select the Primitives tab then click IP LInk and the BGP Peering (Generic System) to add these primitives to the existing CT. You should now see two groups of parameters each representing VRF peering with the external router.

Now, select the Parameters tab and add the following configuration to the newly added primitives.

Click Update.

A new resource tab is now present for Finance: To Generic Link IPs because of our CT additions. Navigate to Staged > Virtual > Routing Zones and you will see the red tab for this resource. Edit this tab and assign the external-router pool, like you have done previously.

From the blueprint, navigate to Staged > Virtual > Virtual Networks and click Create Virtual Network.

Enter/select values as shown in the table below.

Scroll down to the Assigned To section and select all racks. Leave the VLAN ID fields blank to allow Apstra to automatically assign the VLAN number.

Click Create to create the virtual network and return to the list view. The new finance-www virtual network appears in the list. We’ll need to assign resources for it. We’ll do that after creating a couple more virtual networks, then we will assign resources to all three VNs with one transaction.

Click Create Virtual Network.

Enter/select values as shown in the table below.

Scroll down to the Assigned To section and select all racks. Leave the VLAN ID fields blank to allow Apstra to automatically assign the VLAN number.

Click Create to create the virtual network and return to the list view. The new finance-app virtual network appears in the list view.

Click Create Virtual Networks.

Enter/select values as shown in the table below.

Scroll down to the Assigned To section and select all switches. Leave the VLAN ID fields blank to allow Apstra to automatically assign the VLAN number.

Click Create to create the virtual network and return to the list view. The new finance-db virtual network appears in the list view.

Click the red status indicator next to one of the required resources, then click the Update assignments button to see available resource pools.

Select the pools as specified in the table below for the required resource that you are assigning.

Click the Save button. When the resource has been successfully assigned, the red status indicator turns green.

Navigate to Staged > Connectivity Templates and you will see the three new CTs in the VN creation process.

Select the Assign icon for the Tagged VxLAN 'finance-app' connectivity template. Check the select box to the right of all interfaces not greyed out. Since this is for server assignment leave the interfaces tagged with "Router" unchecked.

Click the Assign button and repeat these steps for the two remaining CTs.

Click Uncommitted to see the new virtual networks listed in the Logical Diff tab. If you are feeling particularly adventurous, click the Full Nodes Diff tab and explore the extensive details of everything that will be added to the design.

Click Commit, and enter the description "Added virtual networks", then click Commit to commit changes to the Active blueprint and deploy the new networks.

Recall that we had Cloudlabs perform an update to update the external router. This action applies the settings to enable peering with the leaf pair, within each virtual network.

Click Add Configuration, enter apstra-pod1 or yourname-pod1, if it is not pre-populated. Click Submit. The new peerings will automatically be configured.

Return to the Apstra CloudLabs portal where we started the topology at the beginning of this lab.

Scroll down to the VMs section, click Connect and open a terminal. Use the credentials for aztp-vm1 found in the table.

Enter 3 to connect to leaf1_server1. If you are asked if you want to continue connecting, enter yes.

Enter the password for leaf1_server1 (admin).

run sudo dhclient -r && sudo dhclient. This process takes a moment for interfaces to obtain an IP address.

Make sure eth1.3 received an address via DHCP after rebooting with the command: ip -4 -o addr show eth1.3.

Repeat the dhclient reboot process for the remaining servers if they have not obtained an IP address already on interface eth1.3.

Ping the other servers to confirm that you receive responses. For example: To connect to leaf2_server1, ping 172.20.yoursubnet#.8. (To stop pinging press ctl-c.)