You are here: Home > Device Configuration and Network Management > Aruba Switches > Provisioning Switches Using Configuration Templates

Using Configuration Templates for Switch Management

Templates in Aruba Central refer to a set of configuration commands that can be used by the administrators for provisioning devices in a group. Configuration templates enable administrators to apply a set of configuration parameters simultaneously to multiple switches in a group and thus automate switch deployments.


To minimize configuration errors and troubleshoot device-specific configuration issues, Aruba recommends that the device administrators familiarize themselves with the CLI configuration commands available on Aruba switches.

Creating a Group for Template-Based Configuration

For template-based provisioning, switches must be assigned to a group with template-based configuration method enabled.

For more information, see Creating a Group and Assigning Devices to Groups.

Creating a Configuration Template

To create a configuration template for switches:

1. From the app selector, click Wired Configuration.

2. Select a template group. The Templates page opens.

3. Click + to add a new template. The Add Template pop-up window opens.

4. Enter a name for the template.

5. Ensure that Aruba Switch is selected in the Device drop-down.

6. Select the switch model and the software version. You can specify any of the following combinations:

ALL for both Model and Version—To apply the template to all switch models and all supported switch software versions.

ALL for Model and a specific software version for Version—To apply the template to all switch models running the specified software version.

ALL for Version and a specific switch model for Model—To apply the template to a specific switch model and all software versions supported by the selected switch model.

A specific switch model and a software version—To apply the template to a specific switch model and the software version. The template created for a specific switch model and a firmware version takes precedence over the template that is created for all platforms and versions.

7. Enter the manufacturing part number of the switch for Part Number. The Part Number field is not applicable for switch stacks.

8. Build a new template or import configuration information from a switch that is already provisioned in the template group.

To build a new template, add the switch command information in the Template Text field. Ensure that the template text adheres to the guidelines listed in the Important Points to Note.

To import configuration text from a switch that is already provisioned in the template group:

a. Select the switch from which you want to import the configuration.

b. Click Import Template. The imported configuration is displayed in the Template text box.

c. If required, modify the configuration parameters. Ensure that the template text adheres to the guidelines listed in the Important Points to Note.


Importing configuration from an existing device in the template group allows you to quickly create a basic template. However, before applying the template to other switches in the group, ensure that the template text is variabilized based on the deployment requirements. For more information on template variables, see Managing Variable Files.

9. Click Save. After you apply the configuration template, switches reboot and reconnect to Aruba Central with the new configuration.

Important Points to Note

Note the following points when adding configuration text to a template:

The CLI syntax in the switch template must be accurate. Aruba recommends that you validate the configuration syntax on the switch before adding it to the template text.

Ensure that the command text indentation matches the indentation in the running configuration.

The commands in the template are case-sensitive.

The following example illustrates the case discrepancies that the users must avoid in the template text:

trunk E1-E4 trk1 trunk

interface Trk1

dhcp-snooping trust



trunk E1-E4 trk1 trunk

switch-interconnect trk1


trunk E5-E6 trk2 trunk

vlan 5

name "VLAN5"

untagged Trk2

tagged Trk1

isolate-list Trk1

ip igmp forcedfastleave Trk1

ip igmp blocked Trk1

ip igmp forward Trk1

forbid Trk1


loop-protect Trk2


trunk E1-E4 trk1 trunk

trunk E4-E5 trk2 trunk

spanning-tree Trk1 priority 4

spanning-tree Trk2 admin-edge-port


trunk A2-A4 trk1 trunk

igmp fastlearn Trk1


trunk E4-E5 trk2 trunk

ip source-binding 2 b05ada-96a4a0 Trk2


[no] ip source-binding trap OutOfResources


snmp-server mib hpSwitchAuthMIB ..


snmp-server mib hpicfMACsec unsecured-access ..


[no] lldp config <P-PORT-LIST> dot1TlvEnable ..


[no] lldp config <P-PORT-LIST> medTlvEnable ..


no lldp config <P-PORT-LIST> medPortLocation..


[no] lldp config <P-PORT-LIST> dot3TlvEnable ..


[no] lldp config <P-PORT-LIST> basicTlvEnable ..


[no] lldp config <P-PORT-LIST> ipAddrEnable <lldp-ip>


trunk-load-balance L4-based

trunk-load-balance L3-based


See also: Managing Variable Files

Best Practices

Aruba recommends you to follow the below steps to use configuration templates in managing switches:

1. Configure the switch.

2. Add the switch to Aruba Central.

3. Create the template. You can use Import template option to import an existing template created for switches.

4. Modify the template based on the requirement. For example, addittion or removal of variables.

5. Save the edited template.