Using Configuration Templates for Aruba CX 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 CX 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.
|
|
Aruba CX switches can only be configured using configuration templates. You cannot move a Aruba CX switch from a template group to a UI group in Aruba Central. If attempted, a warning is displayed that the Aruba CX switch cannot be moved to a UI group, because UI group is not supported on Aruba CX switches. When you onboard a factory default Aruba CX switch, the switch is listed under in the > page, because UI group is not supported on Aruba CX switches. When you pre-provision a Aruba CX switch, the switch is listed under in the > page, because UI group is not available for Aruba CX switches. For Aruba CX switches, the feature is not supported. |
Creating a Configuration Template
To create a configuration template for switches:
1. In the app, set the filter to a template group.
The dashboard context for the group is displayed.
2. Under , click > .
3. Click the Config icon.
The tabs to configure switches using templates is displayed.
4. Click the tab. The Templates page is displayed.
5. Click to add a new template. The window is displayed.
6. In the tab, enter a name for the template in the field.
7. In the drop-down, select .
8. 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 software version for —To apply the template to all switch models running the selected software version.
for and a switch model for —To apply the template to a switch model and all software versions supported by the selected switch model.
A switch model and a software version—To apply the template to a specific switch model and the software version. The template created for a switch model and a software version takes precedence over the template that is created for all platforms and versions.
9. Select the manufacturing part number of the switch in the drop-down.
|
|
The drop-down is displayed only if you select a switch model in the 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. |
10. Click . The Template tab is displayed.
11. Build a new template by adding the output of the show running-config from the switch CLI in the text box. Ensure that the template text adheres to the guidelines listed in the Important Points to Note.
|
|
You must manually create the template for the Aruba CX switch in a group, along with the password in plaintext format. You can use the output of the show running-config command to create the template. You can also add variables to use the same template for onboarding multiple Aruba CX switches. For more information on variables, see Downloading Sample Variables File. 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 Aruba CX switches, you must configure the password only in plaintext. Also, the format of password must be user admin group administrators password plaintext <string>. |
12. Click . 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
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
