Lab Guide 1 - Multi-vendor

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

Name the new Routing Zone Finance and select the Default Immutable Routing policy.

Assign the EVPN L3 VNI pool as shown below.

Click the Save button. The red status indicator turns green when the resource has been successfully assigned.

Select the new Finance Routing Zone in the VRF Name column. On the Finance Routing Zone detail page, click the Assign DHCP Servers button.

Enter 9.0.0.1 as the DHCP server IP address, then click Update.

Click Uncommitted to see the staged changes. Take a moment to review this tab and become familiar with how your intent is represented in the staged changes.

Click Commit, enter the revision description "Added routing zone", then click Commit to commit the changes to the Active Blueprint.

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

Select the Primitives tab, then click IP Link to add a new primitive to the template. Next, click BGP Peering (Generic System) to add it to the template. You should now see two groups of parameters, each representing VRF peering with the external router.

Select the Parameters tab and add the following configuration to the newly added primitives.

Click Update.

The new IP link added to the Connectivity Template introduces additional resource requirements. Navigate to Staged > Virtual > Routing Zones > Resource Allocation and assign the resources shown in the table below.

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

Enter or select the values 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 for each switch.

Click Create to create the virtual network and return to the list view. The new finance-www virtual network appears in the list. You will see red indicators showing where resources are needed. We will wait to assign the resource pools until we create two more virtual networks.

Click Create Virtual Network.

Enter or select the values 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. Check whether any additional resources are needed.

Click Create Virtual Network.

Enter or select the values 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.

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

Select the pools specified in the table below for the required resource assignments. This will populate the values needed by all three overlays.

Click the Save button. When the resources have been successfully assigned, the red status indicators turn green.

When creating the virtual networks, we chose the option to automatically create a tagged Connectivity Template for each network. Interfaces must now be assigned to these Connectivity Templates. Navigate to Staged > Connectivity Templates. You will see three new Connectivity Templates.

Select the Assign icon for the Tagged VxLAN 'finance-app' Connectivity Template. Select the checkbox to the right of each interface that is not grayed out. Because this Connectivity Template is for server assignments, leave the interfaces tagged with Router unchecked.

Click the Assign button and repeat these steps for the other two Connectivity Templates. Your assignment table should appear as shown below.

Click Uncommitted to see the new virtual networks listed in the Logical Diff tab.

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

Recall that we previously used the CloudLabs portal to update the external router configuration. We need to perform this step again to apply the peering settings for the new virtual networks.

Click Add Configuration and enter apstra-pod1 or yourname-pod1 if the field is not already populated. Click Submit. The new peerings will be configured automatically.

Return to the Apstra CloudLabs portal where you 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 whether 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 while the interfaces obtain IP addresses.

Verify that eth1.3 received an IP address via DHCP by running ip -4 -o addr show eth1.3.

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

Ping the other servers to confirm connectivity. For example, to ping leaf2_server1, run ping 172.20.yoursubnet#.8. Press Ctrl+C to stop the ping.

ping -I eth1.3 10.30.42.1

ping -I eth1.3 10.30.43.1

ping -I eth1.3 10.30.44.1