[TOC]

The foreword 0.

We first review the knowledge point of the last article “SD-WAN Controller installation and initialization (I)”, let’s summarize as follows:

  • Controller components: vManage, vBond, vSmart, and vEdge.
  • Initial configuration of controller components;
  • Each component must pass vBond authentication and apply for a unique organization-name from Cisco.
  • VManage Manages and schedules routing policies using the vSmart interface.

After device initialization and basic configuration, the connection status of each component is normal, do you think it is time to start automatic policy delivery?

The answer is: just one step… Haha…

What’s weird here is that you have to configure it in vManage, and the parameters are basically the same as before.

Read on…

1. Configure the template

1.1 Creating various ‘Feature’ templates:

Templates -> Feature -> Add Template

1.1.1 Adding a Baud Rate Template

In “Select Devices”, Select “vEdge Cloud”, then in “Select Template”, click “System” and fill in as follows:

Note: The baud rate is required.

1.1.2 Adding template ‘VPN0’

Add a ‘default’ route

In ‘Select Devices’, Select’ vEdge Cloud ‘, then in ‘Select Template’, click ‘VPN0’ and fill in as follows:

Note: This is an Internet egress.

The ‘MPLS’ route was added

Refer to the above configuration, the overall configuration result is as follows, and finally ‘save’ template:

Note: This field indicates the MPLS VPN egress.

1.1.3 Adding the VPN10 Template

Note: If the VPN10 tenant needs to access the Internet, enable this function.

1.1.4 Adding the ‘VPN512’ template

Note: This is an out-of-band NETWORK management port (not involved in this experiment).

1.1.5 Adding the ‘VPN Interface ‘template

Example Add template interface ‘GE0/0/0’

Note: Enabling THE NAT function prevents SSH access to the device when the NAT function is unavailable.

Example Add template interface ‘GE0/1’

Adding the ‘Eth0’ template interface (out-of-band)

Example Add template interface ‘GE0/2’

Note: GE0/2 is a vstore interface.

Adding an ‘OSPF’ route Template (Optional)

In ‘Select Devices’, Select’ vEdge Cloud ‘, go to ‘Select Template’ -> OTHER TEMPLATES, click ‘OSPF’, fill in as shown below, and SAVE’ SAVE’ :

Note: If OSPF is configured, two-way injection with OMP is required. However, the operation here is simple.

1.1.6 Viewing a Created Template

1.1.7 Creating a Device Template

2. Application template

2.1 Creating a Device Template

Note: The device template needs to be associated with nine Feature templates.

2.2 Pushing a Template

  1. Attach Devies by clicking on the right ‘three dots’ :

  1. Popup window, select the corresponding device ‘vedge’, ‘vedge2’ on the left, move to the right, and click ‘Attach’
  2. Enter the parameters manually, as shown in the following figure: VeDGE1 configuration:

Vedge2 configuration:

After filling in, the effect is as follows:

Note: You can also export, fill in and import a CSV file.

When you are done, click ‘Next’ to go to the Next step.

  1. Last Push Configuration

Note: In this step, you can also adjust “Set device Rollback Time” and compare the configurations before and after to ensure that the command is delivered correctly.

  1. Push success

Note: here I am the effect of the updated configuration, is the update.

  1. Verify the associated template



    Note: Device templates have been associated with the two devices, and the status is normal.
  2. The vedge command cannot be configured

Note: The configuration can take effect only when the vedge is in communication with the Controller or is not included.

If you like my article, welcome to follow my public number: drip technology, scan code attention, irregularly share