LAB GUIDE
NetEdit 2.1 - Part 3 – Overlays
and Solution Deployment
IMPORTANT! THIS GUIDE ASSUMES THAT THE AOS-CX OVA HAS BEEN INSTALLED AND WORKS IN GNS3
OR EVE-NG. PLEASE REFER TO GNS3/EVE-NG INITIAL SETUP LABS IF REQUIRED.
[Link]
TABLE OF CONTENTS
Lab Objective ................................................................................................................................................. 2
Lab Overview ................................................................................................................................................. 2
Lab Network Layout ....................................................................................................................................... 2
Lab Task 1. Creating and Visualizing an Overlay .......................................................................................... 2
Lab Task 2. Changing Configurations using Deploy Solutions ...................................................................... 5
1
Lab Objective
This is the first of a NetEdit lab series. At the end of the lab series, you will be able to operate an Aruba AOS-CX Network using
Aruba NetEdit 2.1.
Lab Overview
In this third lab of the NetEdit Series, you will configure a Static VXLAN Tunnel using the Multi-Editor Tool and use the Deploy
Solution tool as an alternative way of managing configurations.
This lab requires is the continuation of Lab 1 and assumes that:
• you have completed Lab 1 and Lab 2
• the configuration of the switches is still active
• NetEdit is in the same state as it was at the end of Lab 2
Lab Network Layout
Figure 1. Lab topology and addresses
Lab Task 1. Creating and Visualizing an Overlay
Repeat the steps of Part 2 – Lab Task 2 to create the Change Validation test and
• Create the change validation Command Script
Commands
show interface vxlan
show interface vxlan vni
show interface vxlan vteps
• Create the corresponding Command Mapping
Note: The VXLAN change validation will only be applied to the access switches. In the sceen capture below, notice the right
panel where the Access query has been applied. This is one of the most important use cases of the query feature.
2
Configure Static VXLAN
In the Device page, select both access switches, and select the Edit Config (ACTION).
• Configure the static VXLAN interface
Source IP – Loopback 0
• ACC1A: [Link]
• ACC1B: [Link]
VTEP-peer – Peer Loopback 0
• ACC1A: [Link]
• ACC1B: [Link]
Validate the configuration, and deploy.
• At the top of the editor panel find these 3 options and click on VALIDATE
• If the validation is successful, RETURN TO PLAN and DEPLOY
• Open Change Validation
• Analyze the outputs of the commands included in the Static VXLAN script
show interface vxlan
show interface vxlan vni
show interface vxlan vteps
3
• A successful deployment is reflected by:
Command: show interface vxlan
Interface vxlan1 is up
Admin state is up
Command: show interface vxlan vni
VNI-status : operational
Command: show interface vteps
Source Destination Origin Status VNI . . .
---------------- ---------------- ------------ --------------------- --------- . . .
[Link] [Link] static operational 1010 . . .
If the state is different from operation, ensure that the command “no shutdown” was included in the interface vxlan 1
configuration. By default, the interface is down.
• If the configuration change was successful, COMMIT the changes.
• Return to the Network page .
• On the left panel, locate the Segmentation and enable the display for VNI 1010
Segmentation: enabled
Switch to Switch: Selected
VNI: 1010
The network graph should have changed:
• Click on the yellow link (VXLAN Tunnel)
• On the right panel, locate the Properties: Link box
• Verify the information provided
4
Lab Task 2. Changing Configurations using Deploy Solutions
In this activity, you will use “Deploy Solution” to configure the DNS Server on all switches at once.
As you go through the lab activity, compare the steps with the multi-editor process.
Create the Change Validation test.
• Create the change validation Command Script
Commands
show ip dns
ping [Link] vrf mgmt
• Create the corresponding Command Mapping
• Return to the Network page .
• Select all 3 switches and in the ACTION menu, open Deploy Solutions and select DNS management
5
• In the Deploy Solution form enter
DNS Server IPs: [Link]
VRF: mgmt
Leave all other parameters in default state.
• PREVIEW
Scroll down to verifiy that the right command is ready for deployment. Click OK.
• CREATE
• If all the validation is successful, DEPLOY
• Open Change Validation and look for the result of the ping command
6
• COMMIT
Important: Keep the lab as it is at this point for the NetEdit 2.1 Part 4
7
Document type
Headline text
[Link]
3333 Scott Blvd. Santa Clara, CA 95054
1.844.472.2782 | T: 1.408.227.4500 | FAX: 1.408.227.4550 | info@[Link]
8
