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.
Creating a Configuration Template
To create a configuration template for switches:
- In the app, use the filter to select a template group.
- Under , click > .
- Click the
configuration icon to display the switch configuration dashboard.
- Click . The Templates page is displayed.
- Click to add a new template. The window is displayed.
- Enter a name for the template in the field.
- Ensure that is selected in the drop-down.
- Select the switch model and software version. You can specify any of the following combinations:
- for both and —To apply the template to all switch models and all supported switch software versions.
- for and a specific software version for —To apply the template to all switch models running the specified software version.
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.
for and a specific switch model for —To apply the template to a specific switch model and all software versions supported by the selected switch model.
-
Select the manufacturing part number of the switch in the
drop-down.The Part Number drop-down is displayed only if you select a switch model in the Model drop-down.
If you select a specific switch model and part number, you can apply the template to a standalone switch and not to a stack.
If you select
in the drop-down, or if you select a switch model and in the drop-down, you can apply a template to both a standalone switch and stack. - 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 Important Points to Note.
text box. Ensure that the template text adheres to the guidelines listed in theTo import configuration text from a switch that is already provisioned in the template group:
- Select the switch from which you want to import the configuration.
- Click . The imported configuration is displayed in the text box.
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 as per your deployment requirements.
All switch templates must include a password command to set a password for the device. The template cannot be saved without adding a password command. If the configuration that is pushed from Aruba Central to the device does not contain a password command, the configuration push is aborted for the device and a log is added to the audit trail. For example, if you add the password command in a condition block and the condition evaluates to false, the configuration that is pushed will not contain the password command. For more information, see Managing Password in Configuration Templates .
For more information about using password commands, see the Configuring Username and Password Security chapter in the HPE ArubaOS-Switch Access Security Guide.
- Click Aruba Central with the new configuration. . After you apply the configuration template, switches reboot and reconnect to
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 exit 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 4.5.6.7 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
Best Practices
Aruba recommends you to follow the below steps to use configuration templates in managing switches:
- Configure the switch.
- Add the switch to Aruba Central.
- Create the template, You can use option to import an existing template created for switches.
- Modify the template based on the user requirement. For example, addition or removal of variables.
- Save the edited template.