This topic is to discuss the following lesson:
Hi, I see some field is “Device Specific” but I don’t see any picture we need input value into this field
Hello Gioi
For each item in the Basic Configuration section, there is a mini dropdown menu from which you can choose one of three options. These options are depicted using icons, which I have listed below:
- Global
- Device specific
- Default
Not all options have all three available. For example, the Site ID doesn’t have a Default available because it is unique to each individual device. When you choose Device Specific, it allows you to manually input values, such as that shown for the system site ID.
When you choose Global or Default, you don’t have to input any values as those are automatically populated.
I hope this has been helpful!
Laz
Hi Rene,
Could you please explain about GPS and Tracker in template config.
Hello Kanu
These are additional parameters that you can set for Viptela devices. The details of each tab are further described in the following Cisco Viptela documentation:
If you have any further questions, please let us know!
I hope this has been helpful!
Laz
Hi Rene and Laz,
What is the point of the template if we still have to add the device to vmanage.
In your notes you mentioned that the we attach the device, but the device needs to be added first to vmanage?
Shouldn’t the template automatically discover and add the vmanage?
Hello Champion
A prerequisite of using templates is having the device added to the vManage controller. It is actually via the vManage interface that you can configure the devices that use templates. So templates don’t solve the problem of automatic discovery and addition to the vManage controller, but they deliver a more scalable way of configuring large numbers of devices.
I hope this has been helpful!
Laz
This is in reference to the SDWAN training class for “Device and Feature Templates”.
I believe that we have to configure some basic settings on vedge and make it available in the vmanage. Only thereafter, we should be able to configure these devices using the templates. You have direclty shown that devices are already available in vManage and apply the templates to it.
Kindly clarify the minimun settings required to add the vEdge to vManage first.
Hello Saifuddin
Yes, you are correct! Actually, this lesson is part of a larger course on SD-WAN, and many of the tasks needed to bring the setup to the point it is in at the beginning of the lesson take place in previous lessons. The whole course with the lessons in order can be found here:
The process of applying the basic settings needed on the vEdge to make it available in the vManage is called vEdge onboarding. Information about vEdge onboarding can be found at the following lesson:
I hope this has been helpful!
Laz
How to use the CLI - addon template in the feature templates? Are there any relevant tutorials? When I created one by myself, I only entered “system” and successfully created a CLI - addon template. Will this cause any problems?
Hello Tong
That’s an excellent question! We don’t have a lesson that specifically deals with CLI add-on templates, but I can give you a brief overview in this post, as well as some links to Cisco resouces.
First, let me clarify that the CLI add-on templates are different from the feature templates. CLI add-on templates are special templates where you paste CLI snippets to augment or override what the standard feature templates generate. This is useful for applying commands and settings for which the vManage GUI templates don’t have a field/checkbox/input. When a device template includes both a feature template and a CLI add-on template, vManage merges configs, and the CLI Add-On always wins on conflicts. So it’s meant to complement, not replace, feature templates.
Note that within the text of the CLI add-on template, only qualified CLIs are allowed. However, the text box you are given is not interactive, so if you put in CLI commands with incorrect syntax, it won’t check them for you. It will run with an error when it is actually used. So you can create a CLI Add-on template using the text “system” as you did, and it will successfully create it. However, when the time comes to use it, it will produce an error, because that is not a proper CLI command.
Take a look at the following link that further describes the feature in detail:
I hope this has been helpful!
Laz
Hi, I was trying to create a Cli Add-On template for a device type where I can add description for different interfaces on switch ports. For example, I have 8 switchports of a device type and different interface will have different descriptions.
Now, I was trying to create a CLI Add-on template but when I tried to apply with 1 interface description it was not accepting and showing all interface descriptions are mandatory. How can I make them optional? I want to update 1 interface description for now leaving others empty. Any help would be appreciated.
Hello Pijush
In a CLI Add-On template, any variables that you define are normally treated as required when the template is attached to a device. So if you create variables for all eight interface descriptions, vManage will expect you to provide values for all of them.
One way to handle this is to avoid defining variables for interfaces you do not want to configure yet. For example, you can create the CLI Add-On template only for the specific interface you want to update:
interface GigabitEthernet0/0/1
description {{description}}
Then you only need to provide the description for that one interface.
If you want to use a single template for multiple interfaces, you may need to use optional/conditional logic if your vManage version supports it, or create separate CLI Add-On templates for each interface or group of interfaces. This gives you more flexibility and avoids being forced to populate descriptions for interfaces you do not want to modify yet.
So in your case, the simplest approach would be to create the CLI Add-On only for the interface you want to update now, and add more interfaces later when needed.
Note that the behavior may vary slightly depending on the vManage version and template type you are using. In general, it’s a good idea to keep the CLI add-on small and only include the commands you actually want pushed. Let us know how you get along!!
I hope this has been helpful!
Laz