community.arubanetworks.comcommunity.arubanetworks.com/aruba/attachments/aruba/CloudMan… · TEMPLATES AND STANDA LONE ARUBAOS-SWITCHES (AOS-S) CONTENTS DOCUMENT REVISION HISTORY

ARUBA CENTRAL KICK START #1

TEMPLATES AND STANDALONE ARUBAOS-SWITCHES (AOS-S) APRIL 2018

2

TEMPLATES AND STANDALONE ARUBAOS-SWITCHES (AOS-S)

CONTENTS DOCUMENT REVISION HISTORY ....................................................................................................................................... 4 DOCUMENT SUMMARY ....................................................................................................................................................... 5 SECTION 1 - CENTRAL BASICS AND INITIAL SETUP ...................................................................................................... 6

INTRO TO TEMPLATE GROUPS (TGS) ..................................................................................................................................... 6 Creating a Template Group ............................................................................................................................................ 6

SETTING FIRMWARE COMPLIANCE ......................................................................................................................................... 8 SECTION 2 - INTRODUCTION TO TEMPLATES ............................................................................................................... 11

ADDING TEMPLATES TO THE TEMPLATE GROUP ................................................................................................................... 11 CREATING A TEMPLATE FILE................................................................................................................................................ 14

SECTION 3 - INTRODUCTION TO VARIABLE FILES ....................................................................................................... 15 UPLOADING A VARIABLES FILE ............................................................................................................................................. 15

SECTION 4 - PUTTING IT ALL TOGETHER ...................................................................................................................... 16 BRINGING UP A DEVICE ....................................................................................................................................................... 18

With Direct Console Access ......................................................................................................................................... 19 With or Without Direct Console Access........................................................................................................................ 20

SECTION 5 – ONGOING OPERATIONS ............................................................................................................................ 25 BACKUP AND RESTORE ....................................................................................................................................................... 25

Creating a Backup ........................................................................................................................................................ 25 Restoring a Backup ...................................................................................................................................................... 26

MODIFYING A TEMPLATE ..................................................................................................................................................... 26 MODIFYING VARIABLES ....................................................................................................................................................... 26 REPLACING A FAILED SWITCH .............................................................................................................................................. 27 FACTORY DEFAULTING A SWITCH ........................................................................................................................................ 27

SECTION 6 – WHEN THINGS GO WRONG ....................................................................................................................... 28 CONFIGURATION CHANGE FAILURE ...................................................................................................................................... 28 SOME THINGS YOU SHOULD KNOW ..................................................................................................................................... 29

Heartbeats and Websocket .......................................................................................................................................... 29 APPENDIX A – TEMPLATE FILES ..................................................................................................................................... 31

2920_TEMPLATE: ............................................................................................................................................................... 31 2930F_TEMPLATE: ............................................................................................................................................................. 49 2930M_TEMPLATE: ............................................................................................................................................................ 68

APPENDIX B – VARIABLES FILE ...................................................................................................................................... 85 2920 24 PORT .................................................................................................................................................................... 85 2930F-8 10 PORT............................................................................................................................................................... 88 2930M 24 PORT ................................................................................................................................................................. 89

3


Figure 1 – Create New Group Dialog ................................................................................................................ 7 Figure 2 – Group Listing ................................................................................................................................... 7 Figure 3 – Firmware Compliance Setting Dialog ............................................................................................... 8 Figure 4 – Firmware Compliance Selection ....................................................................................................... 9 Figure 5 – Firmware Upgrade Status .............................................................................................................. 10 Figure 6 – Select the Template Group to add Templates ................................................................................ 11 Figure 7 – Template Dialog ............................................................................................................................. 12 Figure 8 – Enter Template Text and Modify Template Parameters ................................................................. 13 Figure 9 – Three Templates Created and Listed ............................................................................................. 13 Figure 10 – Template Variables Box ............................................................................................................... 14 Figure 11 – Variables File Upload Successful ................................................................................................. 15 Figure 12 – Blank Variables Window – No Devices yet Assigned to the Template Group ............................... 16 Figure 13 – Group Level Device Variables Table ............................................................................................ 17 Figure 14 – Selecting an Individual Device ..................................................................................................... 17 Figure 15 – Device Level Variables Table ....................................................................................................... 18 Figure 16 – Event Listing of a Good ZTP ........................................................................................................ 19 Figure 17 – ZTP Complete .............................................................................................................................. 20 Figure 18 – Activate Pre-ZTP Device History .................................................................................................. 21 Figure 19 – Central Pre-ZTP Device Listing .................................................................................................... 22 Figure 20 – Successful Activate Redirection to Central ................................................................................... 23 Figure 21 – Central Audit Trail of a Successful ZTP ........................................................................................ 24 Figure 22 – Creating a New Template Group Backup ..................................................................................... 25 Figure 23 – Switch Log – Heartbeats of a Disconnected Switch ..................................................................... 29 Figure 24 – Switch Retrying to Establish the Websocket Connection to Central ............................................. 30

4


Document Revision History Date Modified Revised By Description 11-May-2018 Dominic Buonocore Initial Draft released for review

• Central version 2.4.2-166-P • AOS-S version 16.05.0007

12-May-2018 Dominic Buonocore Release 1.0 • Added callouts to Figures • Minor edits

5


Document Summary This document is intended to provide the reader with a good understanding of how to deploy ArubaOS-Switches (AOS-S) using Template Groups on the Aruba Central Cloud service. The focus of this Kick Start is on the ArubaOS-Switch (AOS-S) models in a NON-Stacked deployment. Stacking will be address in a separate Kick start.

Section 1 covers the basics and initial setup of the Central service for the purpose of deploying an AOS-S using templates. It is beyond the scope of this document to provide a detailed review of the Central service. Therefore it is assumed the reader is reasonably familiar with Central and already has an active Central Admin account.

One final note, while this document includes example templates and a Variable files, these are by no means the best, nor only way to accomplish a deployment with templates. They are simply a working example of how to do this. As you will see and learn from your own trails and errors, the possibilities are numerous on just how to use this powerful feature.

6


Section 1 - Central Basics and Initial Setup As stated earlier, it is assumed that the reader is already familiar with Central and the concepts of Groups and Device management etcetera.

Intro to Template Groups (TGs) Template Groups are completely based on text configuration files, not on UI based, visual, configuration selections. When a group is set as a template group, the UI configuration wizards for the devices in that group are disabled.

Within this document the author has chosen to use Template Groups based on geographical regions similar to what a global enterprise might choose to use. Further, the groups are specific to standalone switches, that is, switches that are not deployed as stacks. As you will see in the examples given there are multiple templates in the group that are specific to the different switch product families (i.e. 2920, 2930F, 2930M). And finally each of these templates have been built to handle all of the different family members.

This example approach to Template Groups, is just that, an example. The reader needs to give some thought to just how they would like to set this up. There is no right or wrong way, and it is beyond the scope of this document to provide the reader with a best practice! This is really a tradeoff between how many TGs you would have and then just how complex and or how many actual templates one would have to build and maintain. Addition things to consider are the day 2 ongoing operational aspects of how you have structured your TGs. Things to think about would be, firmware levels and upgrading procedures and the impact these activities will have on the TGs and the deployed sites they are maintaining.

Creating a Template Group To create a template group, complete the following steps:

1. From the app selector on the left pane, select the Global Settings app.

2. Click Manage Groups.

3. Click (+) to create a new group. The Create New Group pane appears.

4. To set the group as a template group, select the Use As a Template Group check box.

5. Enter a name for the TG.

6. Click Add Group.

Figure 1 below shows the TG named switch-standalone-amer used throughout this document.

7


Figure 1 – Create New Group Dialog

Once the group has been added you can hover your mouse over its name in the list and you will be presented with two option on the right (see Figure 2 below). The first option to the right is the “config” button. Clicking this is a shortcut to selecting the group as the active group to work with.

Figure 2 – Group Listing

Name the Group

Set as a Template Group

Add the Group

Click Config to jump to Wired Management (WD)

8


Setting Firmware Compliance At this point you can begin to add your templates and variable files, these will be covered in the following sections, but right now is a good time to consider what the firmware level is that you want to deploy and optionally enforce as a standard version for this group.

Let’s navigate to the following:

1. From the app selector on the left pane, click Maintenance (MA)

2. Click on “Switch-Aruba” on the tabs line (the line under the large “FIRMWARE” title

3. Click on the “setting icon”

You will be presented with the “Firmware Compliance Setting” dialog shown in Figure 3.

Figure 3 – Firmware Compliance Setting Dialog

This is not a requirement but it is a good option that you might want to take advantage of, and this feature is worth explaining a bit here. This author highly recommends you look at and test out this feature to fully understand its operation. As this is only an option, you do not have to use it.

Since this is a completely new TG and at this point there are no devices assigned to it, selecting a firmware version now can be helpful. This will insure that all devices will be upgraded or downgraded to the selected firmware version when they join the TG for the first time. Therefore setting and enforcing a standard firmware version for the TG. Note that initially in this document we will check the “Auto Reboot” option. See Figure 4 below.

9


Figure 4 – Firmware Compliance Selection

Now a point on the “Auto Reboot”. This is great for all new devices, but you can use the firmware compliance feature to do a blanket upgrade of all devices in the TG! However it is likely that you would not want to distribute the new version and reboot the whole population of switches all at the same time. So if you uncheck the “auto reboot” and click save and upgrade, all of the switches will get the new version download to their primary flash, but they will not reboot. As the firmware upgrades complete the Status displayed in the Firmware listing will change, it hopefully will display “Upgrade successful. Reboot” (see Figure 5 below). This will preposition the new firmware and then you can selectively click on Reboot to reboot them and finalize the upgrade.

Once you have completed all of the reboots you should go back and re-check the “auto reboot” so any new devices joining the TG will be automatically up/down graded. Do not do this however until you have rebooted all the switches since doing this will re-push the new version and indeed Auto Reboot them.

One final note is, if a switch should reboot for some reason it will now come up on the new code – albeit that is fine, but just not when you had planned to reboot it!

Select 16.05.0007 And

Check “Auto Boot”

10


Figure 5 – Firmware Upgrade Status

Click to reboot an individual switch

11


Section 2 - Introduction to Templates This section introduces the reader to just what templates are and just how to use them. A template is nothing more than a switch configuration that utilizes variables. It will always have system variables and may or may not contain user defined variables – but likely it will. The lines in a template file are nothing more than CLI commands. And the user defined variables are provided from the variables file – covered in the next section.

Included in appendix A of this document are three templates. These are fully tested and functional templates that are provided here for the reader to work with and learn. However, there is a best practice method to start from scratch and also to follow when it is time to add more commands to your templates. This is covered at the end of this section.

One final note is, these templates set the password to, “arubarocks” (no quotes). To change this you can edit this line in the template:

password manager user-name "admin" sha1 "8db6741fec5628d6415719b59a9b0ddfd668c8a4"

Change this line to:

password manager user-name "admin" plaintext “newpassword”

Adding Templates to the Template Group Navigate to the newly created TG “switch-standalone-amer”. Click the app selector and choose “Wired Management” (WD). Then select the group filter for “TG switch-standalone-amer”, see Figure 6 below.

Figure 6 – Select the Template Group to add Templates

Then select the TG here

1st Click here

12


You will now be in the Wired Management Templates dialog shown below in Figure 7.

Figure 7 – Template Dialog

Click the blue plus sign in the templates dialog to add a new template. Here we are going to first do the 2920 template. Do the following referring to Figure 8:

1. Add the template name: 2920

2. Select the device: Aruba Switch

3. Select the Model (product family): 2920

4. Leave the Part Name as “ALL”, but take a look at this and you will see that you could in fact have templates for each deferent part number!

5. Select the Version: 16.05 – the latest as of the writing of this document.

6. Cut and paste the full text from the 2920_template provided in appendix A into the Template box.

7. Click save

Click to add a new template

13


Figure 8 – Enter Template Text and Modify Template Parameters

Repeat the above steps for the other two provided templates (2930F_template and 2930M_template). The resulting screen should look like Figure 9 below.

Figure 9 – Three Templates Created and Listed

14


Hover your mouse pointer over one of the listed templates and then off to the right click on the pencil icon. Notice that now there is an additional box in the dialog window labeled “Template Variables”. This is a listing of all the variables that are being referenced in the template on the left. See Figure 10 below.

Figure 10 – Template Variables Box

At this point the templates are ready to go. The next step is to upload a variables file outlined in the next section. However the follow text is worthwhile for the reader to review and understand.

Creating a Template File The three templates provided here are a good working baseline. However if you wanted to build your own template from scratch the proper procedure to do so is to:

1. Build the basic or full desired configuration on a switch.

2. Copy the running config to an editor

3. Add _sys and user defined variables

This file will now become your template – it is beyond the scope of this document to show the steps on just how to complete step 3 above. You can simply use the ones provided that have already been setup properly.

To understand the process of modifying a template see here.

15


Section 3 - Introduction to Variable Files Variable files are composed in JSON format and the example files provided in appendix B are working and usable files. If you chose to use them, you need to edit the serial numbers and MAC addresses, as well as the max_ports to match your switches. If you are creating your own, it is recommended that you validate the JSON syntax to avoid errors when uploading the variables file. An editor is found at https://jsoneditoronline.org

Variable files are used to upload and download variables designated for devices based on the device Serial Number and MAC address. A variable file has no limit to the number of devices it can contain and at a minimum it will contain at least one device. The variables for devices are stored on the Central service in a global container. When a variable file is uploaded to Central, each device and all of the variables for the device, are placed into this container. In the case of a new device all new data are added, in the case of an existing device the old data removed and replaced with the new data.

Examples of uploading and downloaded variable files follow. One interesting note, since all device data in a variable file are uploaded into the global container, devices in variable files can be uploaded into the service from any Template Group regardless of whether the devices will become actual members of the Template Group you are in when you upload. Whatever Template Group the devices are in, will get and display the variables for the devices provisioned in the group.

Uploading a Variables File Within the Template Group > Wired Management select Variables in the left navigation plane and then click on the blue “Upload Variables File (.json)” button. Navigate to wherever you saved the variables file and select it. If all goes well, you will see the “Variables file uploaded successfully” message, momentarily displayed as shown in Figure 11 below. If not refer to the Section 6 of this document. To understand how to modify the variables on a deployed device see Section 5.

Figure 11 – Variables File Upload Successful

Displayed momentarily

https://jsoneditoronline.org/

16


Section 4 - Putting It All Together Now that we have all of the preparation completed it is time to give it a try! In this section we will go through getting a switch into a template group and getting it up and running in a ZTP fashion. If you are using the examples in this document you now have one or more templates configured in a Template Group. You have uploaded a variables file that has been edited to use your switch(es) serial numbers and MAC addresses. Now if you take a look at your Template Group > Wired Management, click on Templates you will see the templates you created. Now click on Variables and since you have no switches yet assigned to this group you will have no variables listed in the tables as shown here in Figure 12.

Figure 12 – Blank Variables Window – No Devices yet Assigned to the Template Group

It is assumed this is a new ZTP of a switch that has never been seen by Central in the past. It is further assumed you have already added the device into your Central account and subscribed it. So navigate to Global Settings (GS) > Device Inventory select your switch(es) by clicking on them in the list (Ctrl click and Shift Click to select more than one). Then in the lower left click the “Assign Group” and assign your switch(es) to the Template Group.

Of course you can always move an existing device from one group into the Template Group.

Once you have added a device into the Template group you will now see a table of variables as shown below in Figure 13. Each and every device that you add into the Template Group will have its variables listed in this table.

17


Figure 13 – Group Level Device Variables Table

If you would like to see only the variables for a particular device, then you need to change your filter to the individual device as shown below in Figure 14 and Figure 15.

Figure 14 – Selecting an Individual Device

1st Click here

Then select the individual switch

18


Figure 15 – Device Level Variables Table

At this point you may be wondering, just what is the difference between Figure 13 and Figure 15? There is a very big one that relates to the ongoing manipulation of variables and it is all about what gets downloaded when you click on the “Download the Table data” icon

Clicking this icon will download the current variable data in a .json file. If you do this at the Group level (Figure 13) the file that gets downloaded will include the variables for all of the devices that are currently assigned to the group. If you do this at the device level (Figure 15) the file that gets downloaded contains only the variables for this individual device.

So which do you use? Well if you only need to make a variable change to a single device then doing it at the device level is the way to go, since you won’t have to search through a bigger file looking for the correct device to modify. Additionally you can be sure you are modifying the right device before you upload it back to make the changes take effect.

Bringing Up a Device At this point I recommend you have console access to the switch you are about to bring up. It is assumed you will be doing this for the first time in a lab environment so this should be available.

You certainly can move a switch into your Template Group from a UI based Group or from another Template Group. But here we are assuming a new switch and ZTP.

Recap:

• Switch is properly added and subscribed in Central

• Switch has been properly assigned to the Template Group

Note the filter!

19


• Switch is in a factory default state

With Direct Console Access It is suggested that from a learning point of view, you start with your switch completely disconnected from the network, so you won’t have to rush to get the debug statements in place.

Power up your switch and as soon as you can do so, get to a command prompt. Enable debugging with the following commands (underlined letters are all you need to type):

• debug destination session

• debug ztp

• debug event

• debug rest-interface

Once you have these debug commands set you can plug in your Ethernet uplink. You will begin to see many messages echoed to your console session. I find that just “debug event” is enough for me, but for learning purposes all of these debugs are useful.

Below shows the event lines of a good ZTP.

Figure 16 – Event Listing of a Good ZTP

Since the switch now has a real configuration on it, it now has things like Spanning Tree, a static IP etcetera. These will cause the switch to lose connectivity for a brief period and then it will reestablish its

20


connection to Central. This can be seen below in Figure 17, with the important line at the bottom which indicates all is well with the switch and Central.

Figure 17 – ZTP Complete

At this point your switch(es) are fully online with Central and in their Template Group. Life is good!

NOTE – sometimes for one reason or another the first ZTP pass to activate fails and the process seems to stall. This is normal behavior and the switch will retry to connect to Activate every 5 minutes. You can wait for the next attempt to occur or force it with the following command:

#activate provision force

With or Without Direct Console Access Obviously console access provides the most insight into just what is going on, however, when you are deploying many switches, possibly throughout the world, this can become not only unfeasible, but also undesirable. So the following provides guidance on how to monitor the first time ZTP of a switch without console access. The two key tools for this are Activate and of course the Central service. It is assumed that the reader is familiar with the Activate services and already has an account.

Before powering up your switch log onto your Activate and Central accounts. Start by looking at the device history in Activate. Do this by selecting your device and clicking on the “View Device History” link. As you can see in Figure 18 below, my device which has never been attach to Central does indeed already show Device History, yours may or may not. If you look closely to the Device History in figure

21


18 you will see this particular device has type “provision-update” occurring every 5 minutes. This is a clear sign that this device is a factory defaulted switch!

Figure 18 – Activate Pre-ZTP Device History

Now take a look at your Central account for this device.

• Click the app selector and choose “Global Settings” (GS)

• Then select “Device Inventory”

• Find your device. You may find it easier to simply set a filter based on serial number using the filter icon

In Figure 19 below you can see that I have filtered on the last four digits of the serial number “XMF6”. The whole point to this screen shot is to call out the small gray bullet icon immediately to the left of the device serial number. When this is gray, the device has never contacted Central, once it does contact Central this icon will turn green. This is one indicator to look at during the ZTP process.

Select the device

Click here

22


Figure 19 – Central Pre-ZTP Device Listing

Time to power up and ZTP your switch. With the switch plugged into the Ethernet uplink power it on. The first thing that should occur is the device should contact Activate and be redirected to Central. Once again look at your device in Activate and click the “View Device History”. You will need to do this each time to refresh the listing. A successful redirect is shown in Figure 20 below. The switch should be attempting to reach Activate every 5 minutes as shown above, so if after 10 minutes or so if you have no new entries in the history list, than something has gone wrong. NOTE – you should still take a look at the status in Central just to be sure. Sometimes, maybe browser related, the listing does not appear.

If indeed it is failing the things to verify are:

1. The device is indeed Factory Defaulted

2. The device gets an IP address and DNS

3. The Device does indeed have Internet access

4. The Device can ping device.arubanetworks.com

5. There is no Firewall blocking the device which only requires outbound HTTPS

Gray bullet will turn green once the device contacts

Central

23


Figure 20 – Successful Activate Redirection to Central

Once you see a successful redirect to Central check the device status on Central. Take a look at the Audit trail:

• Click the app selector and choose “Maintenance” (MA)

• Then select “Audit Trail”

Figure 21 below has a complete Audit Trail of a successful ZTP. You can see that the service automatically upgraded the firmware from16.04.0008 to 16.05.0007 as expected. It then auto reboots it, the process took about 2 minutes.

Once upgraded and rebooted, the correct template is applied and the configuration is pushed, ultimately finishing with a Config Audit which in this example is “good”.

One final note, if you once again take a look at the Device Inventory you will now see that this device now has a green bullet icon since it has now communicated with the Central service.

Athena is the Central service

24


Figure 21 – Central Audit Trail of a Successful ZTP

25


Section 5 – Ongoing Operations

Backup and Restore This is a new feature introduced in the 2.4.2 release. This feature allows you to back up configuration templates and variables, and restore a known working configuration on the devices that are deployed in template groups.

The backup and restore feature allows the administrators to perform the following functions:

• Back up templates and variable files that are applied to the devices in template groups. You can create and maintain up to 20 back up configuration files.

• Restore an earlier known working combination of the configuration template and device variables in the event of a failure.

For more information, see here.

Creating a Backup To create a backup navigate to:

• Click the app selector and choose “Wired Management” (WD)

• Set your Group filter to the Template Group you need to backup

• Then select “Configuration Audit”

• Under “Configuration Backup & Restore” click on the blue “Create New Backup” link

Figure 22 – Creating a New Template Group Backup

http://help.central.arubanetworks.com/2.4.2/documentation/online_help/content/public_cloud/config_restore.htm

26


Name the backup based on what best fits your methods. Since you can keep up to 20 backups and then the oldest will get replaced with the 21st you may want to mark one or all as “Do Not Delete”. How this ends up being handled will be completely up to your individual operational practices.

Click OK and follow the prompts to create your backup. You will be prompted to confirm this backup and you must check the box next to the notification message in order to proceed.

Restoring a Backup To perform a restore from a backup navigate to:


• Set your Group filter to the Template Group you need to backup

• Then select “Configuration Audit”

• Under “Configuration Backup & Restore” click on the blue “Restore from Backup” link

• Follow the prompts

IMPORTANT NOTE

Doing a restore will completely set the template group and the variables back in time to the point in which the backup was created. So any changes after the date of the backup will be lost!!

Modifying a Template It is recommended by Aruba that files in a template file match the actual running config from the viewpoint of the lines listed and their location in the listing!

The recommended best practice for modifying a template is to first take a switch that has a running config that is identical to the running config that would result from applying the current template. On this switch using the CLI, make your additions. Then use the new running config as your guide to just where in your template your newly added lines must be place. Once you have the correct location and syntax established make the appropriate additions to your actual template file.

Refer to Figure 8. Whether you modify the template line by line directly on Central in the template dialog, or you edit a text file and copy it into the template window is up to you, either way works. Just note that as soon as you click the “Save” button the changes will be pushed to all active device using this template.

Modifying Variables Variables are case sensitive, therefore for things like ports on/off or enable/disable, it may be preferred simply to use 1 and 0. When you need to modify a Variables file follow these steps:


• Set your Group filter to the switch you need to modify

• Then select “Variables”

• Click on the “Download the Table data” icon

• Edit this file as needed. Save the file.

• Now upload the file you just saved. Your changes will now automatically be pushed out to the device.

27


Replacing a Failed Switch This procedure if very straight forward. When a switch needs to be replaced and you want to have the exact same configuration on the replacement switch follows these steps:


• Set your Group filter to the failed switch – see Figure 14 – Selecting an Individual Device

• Then select “Variables”

• Click on the “Download the Table data” icon

• Edit this file by replacing the Serial number (in two places) and the MAC address in this file with the serial number and MAC address of the new switch. You should also check and change the max_ports variable if it is different for this switch. Also it is a best practice to clear all of the _sys variables that you do not have the correct values for. Simply set them as “”. Save the file.

• Now upload the file you just saved.

• Insure the new switch is properly added to Central and is provisioned for the correct template group.

• Power up the replacement.

Important Note

It is assumed you are doing a like-for-like replacement of switches, if they are not, this can still be done, but there are some things that you need to take into consideration and adjust for. This is beyond the scope of this document.

Factory Defaulting a Switch Using the CLI This command operates at any level except the Operator level. It deletes the startup-config file in flash so that the switch will reboot with its factory-default configuration.

Syntax:

#erase startup-configuration

Deletes the startup-config file in flash so that the switch will reboot with its factory-default configuration.

Using Clear/Reset Procedure

1. Using pointed objects, simultaneously press both the Reset and Clear buttons on the front of the switch.

2. Continue to press the Clear button while releasing the Reset button.

3. When the Self-Test LED begins to flash, release the Clear button.

The switch then completes its self-test and begins operating with the configuration restored to the factory default settings.

28


Section 6 – When Things Go Wrong In this section we present some of the more common mistakes that cause errors and also provide some guidance on how to troubleshooting them and figure out just what has gone wrong.

Configuration Change Failure Template and/or variable file changes were made yet the device is not reflecting the change. Check these:

- Maintenance > Audit Trail, what are the details?

- Wired Management > Configuration Audit, is it showing any Template errors or Failed Changes?

o If yes does “View Template Errors” or “Failed config difference” reveal anything?

- How about the switch console output for # show log –r, what might it show?

If after looking at these you still have not determined what is wrong, try the following:

- While logged into your Central account modify the Central Service HTTPS URL – these may vary so this is only an example of the URL but the modifications here are what is important

o Current URL = https://something.central.arubanetworks.com/....

o Replace everything after .com/ with this

config/device/the serial number of a failed device/config_details

Put only your serial number here

You will be prompted to save or open a file named device_donfig_details_deviceserialnumber.txt. Open up the file. There are four sections to this file. The first section has two important lines to review highlighted here:

"Device_serial": "SG54FLXMF6",

"Device_type": "ArubaSwitch",

"Group": "switch-standalone-amer",

"Configuration_error_status": true,

"Override_status": false,

"Template_name": "2920",

"Template_hash": "2030112758368d7f8d7cc1043809bd07",

"Template_error_status": false

In this example the configuration_error_status is true, other times the Template_error_status will show true.

The second section is the Device_running_config – this is the currently running config.

https://something.central.arubanetworks.com/

29


The third section is the Device_Central_side_config – this is the config that central has to push.

You can look through these and try to find the problem, but I find it is just easiest to scroll to the very bottom of this file and you will see the fourth section Configuration_error_details. It is here where you will get some details on your problem! In the case of this configuration_error_status : true I have the following in the error_details:

Recent log events from the device (20)<12>May 10 14:11:22 - 00158 update: line 14. Invalid input: nosntp

The nosntp is a typo in the template, it should be “no sntp”.

Some Things You Should Know Here are some timers and retries that are of value to understand.

Heartbeats and Websocket When a switch for whatever reason loses connection to the Central service it goes through a series of efforts to reconnect and Figure 23 below shows the heartbeat attempts the switch will go through.

Figure 23 – Switch Log – Heartbeats of a Disconnected Switch

Uplink disconnected, Heartbeat tries 5 times. Heartbeat interval is every 15 seconds

30


As you can see after the loss of 5 heartbeats (total of 75 seconds) the Websocket Config channel is lost and then it retires the config channel after 15 seconds.

This will continue for four iterations starting at 15 seconds and doubling each time, so 15, 30, 60, and finally 120 seconds. If the Websocket connection fails after the fourth try the switch will revert to trying to contact the Activate service, which is a try every 5 minutes.

NOTE: Figure 23 and Figure 24 were taken from test failures conducted at different times, so disregard the clock values!

Figure 24 – Switch Retrying to Establish the Websocket Connection to Central

15 seconds

15 seconds

15 seconds

15 seconds

Retry Activate

31


Appendix A – Template Files This appendix contains three Template files that are referenced in the document and are working, usable Templates. Each file is for a specific AOS-S family and each is structured to take into account the different port configurations of the models within each family. The key to accomplishing this is the max_ports variable.

2920_template: %_sys_template_header% hostname "%hostname%" %_sys_module_command% snmpv3 engineid "%_sys_snmpv3_engineid%" banner motd "Unauthorized use of this system can result in civil and criminal penalties!" no cwmp enable include-credentials password manager user-name "admin" sha1 "8db6741fec5628d6415719b59a9b0ddfd668c8a4" spanning-tree priority %stp.prio% timesync ntp no sntp ntp unicast ntp server 66.228.58.20 ntp enable time daylight-time-rule continental-us-and-canada time timezone -300 %if vlan.1.dhcp = 0% ip default-gateway %dfgw% ip dns server-address priority 1 %dns% %endif% interface 1 %if if.1.state=disable% disable %endif% %if if.1.name% name %if.1.name% %endif% %if if.1.poe = 0% no power-over-ethernet %endif% exit interface 2 %if if.2.state=disable% disable %endif% %if if.2.name% name %if.2.name% %endif% %if if.2.poe = 0% no power-over-ethernet %endif% exit

32


interface 3 %if if.3.state=disable% disable %endif% %if if.3.name% name %if.3.name% %endif% %if if.3.poe = 0% no power-over-ethernet %endif% exit interface 4 %if if.4.state=disable% disable %endif% %if if.4.name% name %if.4.name% %endif% %if if.4.poe = 0% no power-over-ethernet %endif% exit interface 5 %if if.5.state=disable% disable %endif% %if if.5.name% name %if.5.name% %endif% %if if.5.poe = 0% no power-over-ethernet %endif% exit interface 6 %if if.6.state=disable% disable %endif% %if if.6.name% name %if.6.name% %endif% %if if.6.poe = 0% no power-over-ethernet %endif% exit interface 7 %if if.7.state=disable% disable %endif% %if if.7.name% name %if.7.name% %endif% %if if.7.poe = 0%

33


no power-over-ethernet %endif% exit interface 8 %if if.8.state=disable% disable %endif% %if if.8.name% name %if.8.name% %endif% %if if.8.poe = 0% no power-over-ethernet %endif% exit interface 9 %if if.9.state=disable% disable %endif% %if if.9.name% name %if.9.name% %endif% %if if.9.poe = 0% no power-over-ethernet %endif% exit interface 10 %if if.10.state=disable% disable %endif% %if if.10.name% name %if.10.name% %endif% %if if.10.poe = 0% no power-over-ethernet %endif% exit interface 11 %if if.11.state=disable% disable %endif% %if if.11.name% name %if.11.name% %endif% %if if.11.poe = 0% no power-over-ethernet %endif% exit interface 12 %if if.12.state=disable% disable %endif% %if if.12.name%

34


name %if.12.name% %endif% %if if.12.poe = 0% no power-over-ethernet %endif% exit interface 13 %if if.13.state=disable% disable %endif% %if if.13.name% name %if.13.name% %endif% %if if.13.poe = 0% no power-over-ethernet %endif% exit interface 14 %if if.14.state=disable% disable %endif% %if if.14.name% name %if.14.name% %endif% %if if.14.poe = 0% no power-over-ethernet %endif% exit interface 15 %if if.15.state=disable% disable %endif% %if if.15.name% name %if.15.name% %endif% %if if.15.poe = 0% no power-over-ethernet %endif% exit interface 16 %if if.16.state=disable% disable %endif% %if if.16.name% name %if.16.name% %endif% %if if.16.poe = 0% no power-over-ethernet %endif% exit interface 17 %if if.17.state=disable%

35


disable %endif% %if if.17.name% name %if.17.name% %endif% %if if.17.poe = 0% no power-over-ethernet %endif% exit interface 18 %if if.18.state=disable% disable %endif% %if if.18.name% name %if.18.name% %endif% %if if.18.poe = 0% no power-over-ethernet %endif% exit interface 19 %if if.19.state=disable% disable %endif% %if if.19.name% name %if.19.name% %endif% %if if.19.poe = 0% no power-over-ethernet %endif% exit interface 20 %if if.20.state=disable% disable %endif% %if if.20.name% name %if.20.name% %endif% %if if.20.poe = 0% no power-over-ethernet %endif% exit interface 21 %if if.21.state=disable% disable %endif% %if if.21.name% name %if.21.name% %endif% %if if.21.poe = 0% no power-over-ethernet %endif%

36


exit interface 22 %if if.22.state=disable% disable %endif% %if if.22.name% name %if.22.name% %endif% %if if.22.poe = 0% no power-over-ethernet %endif% exit interface 23 %if if.23.state=disable% disable %endif% %if if.23.name% name %if.23.name% %endif% %if if.23.poe = 0% no power-over-ethernet %endif% exit interface 24 %if if.24.state=disable% disable %endif% %if if.24.name% name %if.24.name% %endif% %if if.24.poe = 0% no power-over-ethernet %endif% exit %if max_ports > 24% interface 25 %if if.25.state=disable% disable %endif% %if if.25.name% name %if.25.name% %endif% %if if.25.poe = 0% no power-over-ethernet %endif% exit interface 26 %if if.26.state=disable% disable %endif% %if if.26.name% name %if.26.name%

37


%endif% %if if.26.poe = 0% no power-over-ethernet %endif% exit interface 27 %if if.27.state=disable% disable %endif% %if if.27.name% name %if.27.name% %endif% %if if.27.poe = 0% no power-over-ethernet %endif% exit interface 28 %if if.28.state=disable% disable %endif% %if if.28.name% name %if.28.name% %endif% %if if.28.poe = 0% no power-over-ethernet %endif% exit interface 29 %if if.29.state=disable% disable %endif% %if if.29.name% name %if.29.name% %endif% %if if.29.poe = 0% no power-over-ethernet %endif% exit interface 30 %if if.30.state=disable% disable %endif% %if if.30.name% name %if.30.name% %endif% %if if.30.poe = 0% no power-over-ethernet %endif% exit interface 31 %if if.31.state=disable% disable

38


%endif% %if if.31.name% name %if.31.name% %endif% %if if.31.poe = 0% no power-over-ethernet %endif% exit interface 32 %if if.32.state=disable% disable %endif% %if if.32.name% name %if.32.name% %endif% %if if.32.poe = 0% no power-over-ethernet %endif% exit interface 33 %if if.33.state=disable% disable %endif% %if if.33.name% name %if.33.name% %endif% %if if.33.poe = 0% no power-over-ethernet %endif% exit interface 34 %if if.34.state=disable% disable %endif% %if if.34.name% name %if.34.name% %endif% %if if.34.poe = 0% no power-over-ethernet %endif% exit interface 35 %if if.35.state=disable% disable %endif% %if if.35.name% name %if.35.name% %endif% %if if.35.poe = 0% no power-over-ethernet %endif% exit

39



40



41


name %if.45.name% %endif% %if if.45.poe = 0% no power-over-ethernet %endif% exit interface 46 %if if.46.state=disable% disable %endif% %if if.46.name% name %if.46.name% %endif% %if if.46.poe = 0% no power-over-ethernet %endif% exit interface 47 %if if.47.state=disable% disable %endif% %if if.47.name% name %if.47.name% %endif% %if if.47.poe = 0% no power-over-ethernet %endif% exit interface 48 %if if.48.state=disable% disable %endif% %if if.48.name% name %if.48.name% %endif% %if if.48.poe = 0% no power-over-ethernet %endif% exit %endif% vlan 1 name "DEFAULT_VLAN" untagged %vlan.1.untagged% tagged %vlan.1.tagged% ip address %vlan.1.ip% exit vlan 270 name "Internet Wireless" untagged %vlan.270.untagged% tagged %vlan.270.tagged% no ip address exit

42


vlan 271 name "Internet Wired" untagged %vlan.271.untagged% tagged %vlan.271.tagged% no ip address exit vlan 272 name "DB Wired" untagged %vlan.272.untagged% tagged %vlan.272.tagged% no ip address exit vlan 273 name "DB Wireless" untagged %vlan.273.untagged% tagged %vlan.273.tagged% no ip address exit spanning-tree %if if.1.stp.edge.port=yes% spanning-tree 1 admin-edge-port %endif% %if if.1.stp.bpdu.protect=yes% spanning-tree 1 bpdu-protection %endif% %if if.2.stp.edge.port=yes% spanning-tree 2 admin-edge-port %endif% %if if.2.stp.bpdu.protect=yes% spanning-tree 2 bpdu-protection %endif% %if if.3.stp.edge.port=yes% spanning-tree 3 admin-edge-port %endif% %if if.3.stp.bpdu.protect=yes% spanning-tree 3 bpdu-protection %endif% %if if.4.stp.edge.port=yes% spanning-tree 4 admin-edge-port %endif% %if if.4.stp.bpdu.protect=yes% spanning-tree 4 bpdu-protection %endif% %if if.5.stp.edge.port=yes% spanning-tree 5 admin-edge-port %endif% %if if.5.stp.bpdu.protect=yes% spanning-tree 5 bpdu-protection %endif% %if if.6.stp.edge.port=yes% spanning-tree 6 admin-edge-port %endif%

43


%if if.6.stp.bpdu.protect=yes% spanning-tree 6 bpdu-protection %endif% %if if.7.stp.edge.port=yes% spanning-tree 7 admin-edge-port %endif% %if if.7.stp.bpdu.protect=yes% spanning-tree 7 bpdu-protection %endif% %if if.8.stp.edge.port=yes% spanning-tree 8 admin-edge-port %endif% %if if.8.stp.bpdu.protect=yes% spanning-tree 8 bpdu-protection %endif% %if if.9.stp.edge.port=yes% spanning-tree 9 admin-edge-port %endif% %if if.9.stp.bpdu.protect=yes% spanning-tree 9 bpdu-protection %endif% %if if.10.stp.edge.port=yes% spanning-tree 10 admin-edge-port %endif% %if if.10.stp.bpdu.protect=yes% spanning-tree 10 bpdu-protection %endif% %if if.11.stp.edge.port=yes% spanning-tree 11 admin-edge-port %endif% %if if.11.stp.bpdu.protect=yes% spanning-tree 11 bpdu-protection %endif% %if if.12.stp.edge.port=yes% spanning-tree 12 admin-edge-port %endif% %if if.12.stp.bpdu.protect=yes% spanning-tree 12 bpdu-protection %endif% %if if.13.stp.edge.port=yes% spanning-tree 13 admin-edge-port %endif% %if if.13.stp.bpdu.protect=yes% spanning-tree 13 bpdu-protection %endif% %if if.14.stp.edge.port=yes% spanning-tree 14 admin-edge-port %endif% %if if.14.stp.bpdu.protect=yes% spanning-tree 14 bpdu-protection %endif% %if if.15.stp.edge.port=yes%

44


spanning-tree 15 admin-edge-port %endif% %if if.15.stp.bpdu.protect=yes% spanning-tree 15 bpdu-protection %endif% %if if.16.stp.edge.port=yes% spanning-tree 16 admin-edge-port %endif% %if if.16.stp.bpdu.protect=yes% spanning-tree 16 bpdu-protection %endif% %if if.17.stp.edge.port=yes% spanning-tree 17 admin-edge-port %endif% %if if.17.stp.bpdu.protect=yes% spanning-tree 17 bpdu-protection %endif% %if if.18.stp.edge.port=yes% spanning-tree 18 admin-edge-port %endif% %if if.18.stp.bpdu.protect=yes% spanning-tree 18 bpdu-protection %endif% %if if.19.stp.edge.port=yes% spanning-tree 19 admin-edge-port %endif% %if if.19.stp.bpdu.protect=yes% spanning-tree 19 bpdu-protection %endif% %if if.20.stp.edge.port=yes% spanning-tree 20 admin-edge-port %endif% %if if.20.stp.bpdu.protect=yes% spanning-tree 20 bpdu-protection %endif% %if if.21.stp.edge.port=yes% spanning-tree 21 admin-edge-port %endif% %if if.21.stp.bpdu.protect=yes% spanning-tree 21 bpdu-protection %endif% %if if.22.stp.edge.port=yes% spanning-tree 22 admin-edge-port %endif% %if if.22.stp.bpdu.protect=yes% spanning-tree 22 bpdu-protection %endif% %if if.23.stp.edge.port=yes% spanning-tree 23 admin-edge-port %endif% %if if.23.stp.bpdu.protect=yes% spanning-tree 23 bpdu-protection

45


%endif% %if if.24.stp.edge.port=yes% spanning-tree 24 admin-edge-port %endif% %if if.24.stp.bpdu.protect=yes% spanning-tree 24 bpdu-protection %endif% %if if.25.stp.edge.port=yes% spanning-tree 25 admin-edge-port %endif% %if if.25.stp.bpdu.protect=yes% spanning-tree 25 bpdu-protection %endif% %if if.26.stp.edge.port=yes% spanning-tree 26 admin-edge-port %endif% %if if.26.stp.bpdu.protect=yes% spanning-tree 26 bpdu-protection %endif% %if if.27.stp.edge.port=yes% spanning-tree 27 admin-edge-port %endif% %if if.27.stp.bpdu.protect=yes% spanning-tree 27 bpdu-protection %endif% %if if.28.stp.edge.port=yes% spanning-tree 28 admin-edge-port %endif% %if if.28.stp.bpdu.protect=yes% spanning-tree 28 bpdu-protection %endif% %if if.29.stp.edge.port=yes% spanning-tree 29 admin-edge-port %endif% %if if.29.stp.bpdu.protect=yes% spanning-tree 29 bpdu-protection %endif% %if if.30.stp.edge.port=yes% spanning-tree 30 admin-edge-port %endif% %if if.30.stp.bpdu.protect=yes% spanning-tree 30 bpdu-protection %endif% %if if.31.stp.edge.port=yes% spanning-tree 31 admin-edge-port %endif% %if if.31.stp.bpdu.protect=yes% spanning-tree 31 bpdu-protection %endif% %if if.32.stp.edge.port=yes% spanning-tree 32 admin-edge-port %endif%

46



47


spanning-tree 41 admin-edge-port %endif% %if if.41.stp.bpdu.protect=yes% spanning-tree 41 bpdu-protection %endif% %if if.42.stp.edge.port=yes% spanning-tree 42 admin-edge-port %endif% %if if.42.stp.bpdu.protect=yes% spanning-tree 42 bpdu-protection %endif% %if if.43.stp.edge.port=yes% spanning-tree 43 admin-edge-port %endif% %if if.43.stp.bpdu.protect=yes% spanning-tree 43 bpdu-protection %endif% %if if.44.stp.edge.port=yes% spanning-tree 44 admin-edge-port %endif% %if if.44.stp.bpdu.protect=yes% spanning-tree 44 bpdu-protection %endif% %if if.45.stp.edge.port=yes% spanning-tree 45 admin-edge-port %endif% %if if.45.stp.bpdu.protect=yes% spanning-tree 45 bpdu-protection %endif% %if if.46.stp.edge.port=yes% spanning-tree 46 admin-edge-port %endif% %if if.46.stp.bpdu.protect=yes% spanning-tree 46 bpdu-protection %endif% %if if.47.stp.edge.port=yes% spanning-tree 47 admin-edge-port %endif% %if if.47.stp.bpdu.protect=yes% spanning-tree 47 bpdu-protection %endif% %if if.48.stp.edge.port=yes% spanning-tree 48 admin-edge-port %endif% %if if.48.stp.bpdu.protect=yes% spanning-tree 48 bpdu-protection %endif% spanning-tree config-name "DB" no tftp server no autorun no dhcp config-file-update no dhcp image-file-update

48


no dhcp tr69-acs-url device-profile name "default-ap-profile" tagged-vlan 270,273 exit device-profile type "aruba-ap" enable exit

49


2930F_template: %_sys_template_header% hostname "%hostname%" %_sys_module_command% snmpv3 engineid "%_sys_snmpv3_engineid%" banner motd "Unauthorized use of this system can result in civil and criminal penalties!" no cwmp enable include-credentials password manager user-name "admin" sha1 "8db6741fec5628d6415719b59a9b0ddfd668c8a4" spanning-tree priority %stp.prio% timesync ntp no sntp ntp unicast ntp server 66.228.58.20 ntp enable time daylight-time-rule continental-us-and-canada time timezone -300 %if vlan.1.dhcp = 0% ip default-gateway %dfgw% ip dns server-address priority 1 %dns% %endif% interface 1 %if if.1.state=disable% disable %endif% %if if.1.name% name %if.1.name% %endif% %if if.1.poe = 0% no power-over-ethernet %endif% exit interface 2 %if if.2.state=disable% disable %endif% %if if.2.name% name %if.2.name% %endif% %if if.2.poe = 0% no power-over-ethernet %endif% exit interface 3 %if if.3.state=disable% disable %endif% %if if.3.name% name %if.3.name% %endif% %if if.3.poe = 0%

50



51


name %if.8.name% %endif% %if if.8.poe = 0% no power-over-ethernet %endif% exit interface 9 %if if.9.state=disable% disable %endif% %if if.9.name% name %if.9.name% %endif% %if if.9.poe = 0% no power-over-ethernet %endif% exit interface 10 %if if.10.state=disable% disable %endif% %if if.10.name% name %if.10.name% %endif% %if if.10.poe = 0% no power-over-ethernet %endif% exit %if max_ports > 10% interface 11 %if if.11.state=disable% disable %endif% %if if.11.name% name %if.11.name% %endif% %if if.11.poe = 0% no power-over-ethernet %endif% exit interface 12 %if if.12.state=disable% disable %endif% %if if.12.name% name %if.12.name% %endif% %if if.12.poe = 0% no power-over-ethernet %endif% exit interface 13

52


%if if.13.state=disable% disable %endif% %if if.13.name% name %if.13.name% %endif% %if if.13.poe = 0% no power-over-ethernet %endif% exit interface 14 %if if.14.state=disable% disable %endif% %if if.14.name% name %if.14.name% %endif% %if if.14.poe = 0% no power-over-ethernet %endif% exit interface 15 %if if.15.state=disable% disable %endif% %if if.15.name% name %if.15.name% %endif% %if if.15.poe = 0% no power-over-ethernet %endif% exit interface 16 %if if.16.state=disable% disable %endif% %if if.16.name% name %if.16.name% %endif% %if if.16.poe = 0% no power-over-ethernet %endif% exit interface 17 %if if.17.state=disable% disable %endif% %if if.17.name% name %if.17.name% %endif% %if if.17.poe = 0% no power-over-ethernet

53


%endif% exit interface 18 %if if.18.state=disable% disable %endif% %if if.18.name% name %if.18.name% %endif% %if if.18.poe = 0% no power-over-ethernet %endif% exit interface 19 %if if.19.state=disable% disable %endif% %if if.19.name% name %if.19.name% %endif% %if if.19.poe = 0% no power-over-ethernet %endif% exit interface 20 %if if.20.state=disable% disable %endif% %if if.20.name% name %if.20.name% %endif% %if if.20.poe = 0% no power-over-ethernet %endif% exit interface 21 %if if.21.state=disable% disable %endif% %if if.21.name% name %if.21.name% %endif% %if if.21.poe = 0% no power-over-ethernet %endif% exit interface 22 %if if.22.state=disable% disable %endif% %if if.22.name% name %if.22.name%

54



55


%endif% %if if.27.name% name %if.27.name% %endif% %if if.27.poe = 0% no power-over-ethernet %endif% exit interface 28 %if if.28.state=disable% disable %endif% %if if.28.name% name %if.28.name% %endif% %if if.28.poe = 0% no power-over-ethernet %endif% exit %endif% %if max_ports > 28% interface 29 %if if.29.state=disable% disable %endif% %if if.29.name% name %if.29.name% %endif% %if if.29.poe = 0% no power-over-ethernet %endif% exit interface 30 %if if.30.state=disable% disable %endif% %if if.30.name% name %if.30.name% %endif% %if if.30.poe = 0% no power-over-ethernet %endif% exit interface 31 %if if.31.state=disable% disable %endif% %if if.31.name% name %if.31.name% %endif% %if if.31.poe = 0% no power-over-ethernet

56


%endif% exit interface 32 %if if.32.state=disable% disable %endif% %if if.32.name% name %if.32.name% %endif% %if if.32.poe = 0% no power-over-ethernet %endif% exit interface 33 %if if.33.state=disable% disable %endif% %if if.33.name% name %if.33.name% %endif% %if if.33.poe = 0% no power-over-ethernet %endif% exit interface 34 %if if.34.state=disable% disable %endif% %if if.34.name% name %if.34.name% %endif% %if if.34.poe = 0% no power-over-ethernet %endif% exit interface 35 %if if.35.state=disable% disable %endif% %if if.35.name% name %if.35.name% %endif% %if if.35.poe = 0% no power-over-ethernet %endif% exit interface 36 %if if.36.state=disable% disable %endif% %if if.36.name% name %if.36.name%

57



58



59



60


no power-over-ethernet %endif% exit interface 51 %if if.51.state=disable% disable %endif% %if if.51.name% name %if.51.name% %endif% %if if.51.poe = 0% no power-over-ethernet %endif% exit interface 52 %if if.52.state=disable% disable %endif% %if if.52.name% name %if.52.name% %endif% %if if.52.poe = 0% no power-over-ethernet %endif% exit %endif% vlan 1 name "DEFAULT_VLAN" untagged %vlan.1.untagged% tagged %vlan.1.tagged% ip address %vlan.1.ip% exit vlan 270 name "Internet Wireless" untagged %vlan.270.untagged% tagged %vlan.270.tagged% no ip address exit vlan 271 name "Internet Wired" untagged %vlan.271.untagged% tagged %vlan.271.tagged% no ip address exit vlan 272 name "DB Wired" untagged %vlan.272.untagged% tagged %vlan.272.tagged% no ip address exit vlan 273 name "DB Wireless"

61


untagged %vlan.273.untagged% tagged %vlan.273.tagged% no ip address exit spanning-tree %if if.1.stp.edge.port=yes% spanning-tree 1 admin-edge-port %endif% %if if.1.stp.bpdu.protect=yes% spanning-tree 1 bpdu-protection %endif% %if if.2.stp.edge.port=yes% spanning-tree 2 admin-edge-port %endif% %if if.2.stp.bpdu.protect=yes% spanning-tree 2 bpdu-protection %endif% %if if.3.stp.edge.port=yes% spanning-tree 3 admin-edge-port %endif% %if if.3.stp.bpdu.protect=yes% spanning-tree 3 bpdu-protection %endif% %if if.4.stp.edge.port=yes% spanning-tree 4 admin-edge-port %endif% %if if.4.stp.bpdu.protect=yes% spanning-tree 4 bpdu-protection %endif% %if if.5.stp.edge.port=yes% spanning-tree 5 admin-edge-port %endif% %if if.5.stp.bpdu.protect=yes% spanning-tree 5 bpdu-protection %endif% %if if.6.stp.edge.port=yes% spanning-tree 6 admin-edge-port %endif% %if if.6.stp.bpdu.protect=yes% spanning-tree 6 bpdu-protection %endif% %if if.7.stp.edge.port=yes% spanning-tree 7 admin-edge-port %endif% %if if.7.stp.bpdu.protect=yes% spanning-tree 7 bpdu-protection %endif% %if if.8.stp.edge.port=yes% spanning-tree 8 admin-edge-port %endif% %if if.8.stp.bpdu.protect=yes% spanning-tree 8 bpdu-protection

62



63



64



65



66



67


spanning-tree 48 admin-edge-port %endif% %if if.52.stp.bpdu.protect=yes% spanning-tree 48 bpdu-protection %endif% spanning-tree config-name "DB" no tftp server no autorun no dhcp config-file-update no dhcp image-file-update no dhcp tr69-acs-url device-profile name "default-ap-profile" tagged-vlan 270,273 exit device-profile type "aruba-ap" enable exit mac-delimiter colon

68


2930M_template: %_sys_template_header% hostname "%hostname%" %_sys_module_command% snmpv3 engineid "%_sys_snmpv3_engineid%" banner motd "Unauthorized use of this system can result in civil and criminal penalties!" no cwmp enable include-credentials password manager user-name "admin" sha1 "8db6741fec5628d6415719b59a9b0ddfd668c8a4" spanning-tree priority %stp.prio% timesync ntp no sntp ntp unicast ntp server 66.228.58.20 ntp enable time daylight-time-rule continental-us-and-canada time timezone -300 %if vlan.1.dhcp = 0% ip default-gateway %dfgw% ip dns server-address priority 1 %dns% %endif% interface 1 %if if.1.state=disable% disable %endif% %if if.1.name% name %if.1.name% %endif% %if if.1.poe = 0% no power-over-ethernet %endif% exit interface 2 %if if.2.state=disable% disable %endif% %if if.2.name% name %if.2.name% %endif% %if if.2.poe = 0% no power-over-ethernet %endif% exit interface 3 %if if.3.state=disable% disable %endif% %if if.3.name% name %if.3.name% %endif% %if if.3.poe = 0%

69



70



71


disable %endif% %if if.13.name% name %if.13.name% %endif% %if if.13.poe = 0% no power-over-ethernet %endif% exit interface 14 %if if.14.state=disable% disable %endif% %if if.14.name% name %if.14.name% %endif% %if if.14.poe = 0% no power-over-ethernet %endif% exit interface 15 %if if.15.state=disable% disable %endif% %if if.15.name% name %if.15.name% %endif% %if if.15.poe = 0% no power-over-ethernet %endif% exit interface 16 %if if.16.state=disable% disable %endif% %if if.16.name% name %if.16.name% %endif% %if if.16.poe = 0% no power-over-ethernet %endif% exit interface 17 %if if.17.state=disable% disable %endif% %if if.17.name% name %if.17.name% %endif% %if if.17.poe = 0% no power-over-ethernet %endif%

72


exit interface 18 %if if.18.state=disable% disable %endif% %if if.18.name% name %if.18.name% %endif% %if if.18.poe = 0% no power-over-ethernet %endif% exit interface 19 %if if.19.state=disable% disable %endif% %if if.19.name% name %if.19.name% %endif% %if if.19.poe = 0% no power-over-ethernet %endif% exit interface 20 %if if.20.state=disable% disable %endif% %if if.20.name% name %if.20.name% %endif% %if if.20.poe = 0% no power-over-ethernet %endif% exit interface 21 %if if.21.state=disable% disable %endif% %if if.21.name% name %if.21.name% %endif% %if if.21.poe = 0% no power-over-ethernet %endif% exit interface 22 %if if.22.state=disable% disable %endif% %if if.22.name% name %if.22.name% %endif%

73


%if if.22.poe = 0% no power-over-ethernet %endif% exit interface 23 %if if.23.state=disable% disable %endif% %if if.23.name% name %if.23.name% %endif% %if if.23.poe = 0% no power-over-ethernet %endif% exit interface 24 %if if.24.state=disable% disable %endif% %if if.24.name% name %if.24.name% %endif% %if if.24.poe = 0% no power-over-ethernet %endif% exit %if max_ports > 24% interface 25 %if if.25.state=disable% disable %endif% %if if.25.name% name %if.25.name% %endif% %if if.25.poe = 0% no power-over-ethernet %endif% exit interface 26 %if if.26.state=disable% disable %endif% %if if.26.name% name %if.26.name% %endif% %if if.26.poe = 0% no power-over-ethernet %endif% exit interface 27 %if if.27.state=disable% disable

74



75



76



77



78


disable %endif% %if if.46.name% name %if.46.name% %endif% %if if.46.poe = 0% no power-over-ethernet %endif% exit interface 47 %if if.47.state=disable% disable %endif% %if if.47.name% name %if.47.name% %endif% %if if.47.poe = 0% no power-over-ethernet %endif% exit interface 48 %if if.48.state=disable% disable %endif% %if if.48.name% name %if.48.name% %endif% %if if.48.poe = 0% no power-over-ethernet %endif% exit %endif% vlan 1 name "DEFAULT_VLAN" untagged %vlan.1.untagged% tagged %vlan.1.tagged% ip address %vlan.1.ip% exit vlan 270 name "Internet Wireless" untagged %vlan.270.untagged% tagged %vlan.270.tagged% no ip address exit vlan 271 name "Internet Wired" untagged %vlan.271.untagged% tagged %vlan.271.tagged% no ip address exit vlan 272 name "DB Wired"

79


untagged %vlan.272.untagged% tagged %vlan.272.tagged% no ip address exit vlan 273 name "DB Wireless" untagged %vlan.273.untagged% tagged %vlan.273.tagged% no ip address exit spanning-tree %if if.1.stp.edge.port=yes% spanning-tree 1 admin-edge-port %endif% %if if.1.stp.bpdu.protect=yes% spanning-tree 1 bpdu-protection %endif% %if if.2.stp.edge.port=yes% spanning-tree 2 admin-edge-port %endif% %if if.2.stp.bpdu.protect=yes% spanning-tree 2 bpdu-protection %endif% %if if.3.stp.edge.port=yes% spanning-tree 3 admin-edge-port %endif% %if if.3.stp.bpdu.protect=yes% spanning-tree 3 bpdu-protection %endif% %if if.4.stp.edge.port=yes% spanning-tree 4 admin-edge-port %endif% %if if.4.stp.bpdu.protect=yes% spanning-tree 4 bpdu-protection %endif% %if if.5.stp.edge.port=yes% spanning-tree 5 admin-edge-port %endif% %if if.5.stp.bpdu.protect=yes% spanning-tree 5 bpdu-protection %endif% %if if.6.stp.edge.port=yes% spanning-tree 6 admin-edge-port %endif% %if if.6.stp.bpdu.protect=yes% spanning-tree 6 bpdu-protection %endif% %if if.7.stp.edge.port=yes% spanning-tree 7 admin-edge-port %endif% %if if.7.stp.bpdu.protect=yes% spanning-tree 7 bpdu-protection

80



81



82



83



84


%if if.42.stp.bpdu.protect=yes% spanning-tree 42 bpdu-protection %endif% %if if.43.stp.edge.port=yes% spanning-tree 43 admin-edge-port %endif% %if if.43.stp.bpdu.protect=yes% spanning-tree 43 bpdu-protection %endif% %if if.44.stp.edge.port=yes% spanning-tree 44 admin-edge-port %endif% %if if.44.stp.bpdu.protect=yes% spanning-tree 44 bpdu-protection %endif% %if if.45.stp.edge.port=yes% spanning-tree 45 admin-edge-port %endif% %if if.45.stp.bpdu.protect=yes% spanning-tree 45 bpdu-protection %endif% %if if.46.stp.edge.port=yes% spanning-tree 46 admin-edge-port %endif% %if if.46.stp.bpdu.protect=yes% spanning-tree 46 bpdu-protection %endif% %if if.47.stp.edge.port=yes% spanning-tree 47 admin-edge-port %endif% %if if.47.stp.bpdu.protect=yes% spanning-tree 47 bpdu-protection %endif% %if if.48.stp.edge.port=yes% spanning-tree 48 admin-edge-port %endif% %if if.48.stp.bpdu.protect=yes% spanning-tree 48 bpdu-protection %endif% spanning-tree config-name "DB" no tftp server no autorun no dhcp config-file-update no dhcp image-file-update no dhcp tr69-acs-url device-profile name "default-ap-profile" tagged-vlan 270,273 exit device-profile type "aruba-ap" enable exit mac-delimiter colon

85


Appendix B – Variables File Included here are three variable files for the examples presented in this document. They are set for three specific switch models and of course you can use them as the basis for your own files. One of the key variables is the max_ports variable this will effect just how this device is processed within the template. Also note that in order to use these you must replace all of the RED Font data with your specific data – serial numbers and AMC addresses.

2920 24 port Copy from the first { to the last } and create a .txt or .json file with all this text so you can upload when needed.

{ "SERIAL_NUMBER": { "_sys_gateway": "", "_sys_hostname": "", "_sys_ip_address": "", "_sys_lan_mac": "ff:ff:ff:ff:ff:ff", "_sys_module_command": "", "_sys_netmask": "", "_sys_oobm_command": "", "_sys_serial": "SERIAL_NUMBER", "_sys_snmpv3_engineid": "", "_sys_stack_command": "", "_sys_template_header": "", "_sys_use_dhcp": "", "_sys_vlan_1_tag_command": "", "_sys_vlan_1_untag_command": "", "banner.motd": "Unauthorized use of this system can result in civil and criminal penalties! So if you are not a valid user stay out", "dfgw": "192.168.0.254", "dns": "75.75.75.75", "hostname": "db-2920-24", "if.1.name": "tets", "if.1.state": "enable", "if.1.stp.bpdu.protect": "no", "if.1.stp.edge.port": "no", "if.10.name": "", "if.10.state": "enable", "if.10.stp.bpdu.protect": "yes", "if.10.stp.edge.port": "yes", "if.11.name": "", "if.11.state": "enable", "if.11.stp.bpdu.protect": "yes", "if.11.stp.edge.port": "yes", "if.12.name": "", "if.12.state": "enable", "if.12.stp.bpdu.protect": "yes", "if.12.stp.edge.port": "yes",

86


"if.13.name": "", "if.13.state": "enable", "if.13.stp.bpdu.protect": "yes", "if.13.stp.edge.port": "yes", "if.14.name": "", "if.14.state": "enable", "if.14.stp.bpdu.protect": "yes", "if.14.stp.edge.port": "yes", "if.15.name": "", "if.15.state": "disable", "if.15.stp.bpdu.protect": "yes", "if.15.stp.edge.port": "yes", "if.16.name": "", "if.16.state": "disable", "if.16.stp.bpdu.protect": "yes", "if.16.stp.edge.port": "yes", "if.17.name": "", "if.17.state": "enable", "if.17.stp.bpdu.protect": "yes", "if.17.stp.edge.port": "yes", "if.18.name": "", "if.18.state": "enable", "if.18.stp.bpdu.protect": "yes", "if.18.stp.edge.port": "yes", "if.19.name": "", "if.19.state": "enable", "if.19.stp.bpdu.protect": "yes", "if.19.stp.edge.port": "yes", "if.2.name": "", "if.2.state": "enable", "if.2.stp.bpdu.protect": "yes", "if.2.stp.edge.port": "yes", "if.20.name": "", "if.20.state": "enable", "if.20.stp.bpdu.protect": "yes", "if.20.stp.edge.port": "yes", "if.21.name": "", "if.21.state": "enable", "if.21.stp.bpdu.protect": "yes", "if.21.stp.edge.port": "yes", "if.22.name": "", "if.22.state": "enable", "if.22.stp.bpdu.protect": "yes", "if.22.stp.edge.port": "yes", "if.23.name": "", "if.23.state": "enable", "if.23.stp.bpdu.protect": "yes", "if.23.stp.edge.port": "yes", "if.24.name": "", "if.24.state": "enable", "if.24.stp.bpdu.protect": "yes", "if.24.stp.edge.port": "yes",

87


"if.3.name": "", "if.3.state": "enable", "if.3.stp.bpdu.protect": "yes", "if.3.stp.edge.port": "yes", "if.4.name": "", "if.4.state": "enable", "if.4.stp.bpdu.protect": "yes", "if.4.stp.edge.port": "yes", "if.5.name": "", "if.5.state": "enable", "if.5.stp.bpdu.protect": "yes", "if.5.stp.edge.port": "yes", "if.6.name": "", "if.6.state": "disable", "if.6.stp.bpdu.protect": "yes", "if.6.stp.edge.port": "yes", "if.7.name": "", "if.7.state": "enable", "if.7.stp.bpdu.protect": "yes", "if.7.stp.edge.port": "yes", "if.8.name": "", "if.8.state": "enable", "if.8.stp.bpdu.protect": "yes", "if.8.stp.edge.port": "yes", "if.9.name": "", "if.9.state": "enable", "if.9.stp.bpdu.protect": "yes", "if.9.stp.edge.port": "yes", "max_ports": "24", "mgmt.vlan": "1", "stp.config.name": "DB", "stp.prio": "2", "vlan.1.dhcp": "0", "vlan.1.ip": "192.168.0.76 255.255.255.0", "vlan.1.tagged": "10", "vlan.1.untagged": "1,6-9", "vlan.270.tagged": "10", "vlan.270.untagged": "2", "vlan.271.tagged": "10", "vlan.271.untagged": "3", "vlan.272.tagged": "10", "vlan.272.untagged": "4", "vlan.273.tagged": "10", "vlan.273.untagged": "5,6" } }

88


2930F-8 10 port Copy from the first { to the last } and create a .txt or .json file with all this text so you can upload when needed.

{ "SERIAL_NUMBER": { "_sys_gateway": "", "_sys_hostname": "", "_sys_ip_address": "", "_sys_lan_mac": "ff:ff:ff:ff:ff:ff", "_sys_module_command": "", "_sys_netmask": "", "_sys_oobm_command": "", "_sys_serial": "SERIAL_NUMBER", "_sys_snmpv3_engineid": "", "_sys_stack_command": "", "_sys_template_header": "", "_sys_use_dhcp": "", "_sys_vlan_1_tag_command": "", "_sys_vlan_1_untag_command": "", "banner.motd": "Unauthorized use of this system can result in civil and criminal penalties!", "dfgw": "", "dns": "", "hostname": "db-2930F-8", "if.1.name": "", "if.1.state": "enable", "if.1.stp.bpdu.protect": "no", "if.1.stp.edge.port": "no", "if.10.name": "", "if.10.state": "enable", "if.10.stp.bpdu.protect": "yes", "if.10.stp.edge.port": "yes", "if.2.name": "", "if.2.state": "enable", "if.2.stp.bpdu.protect": "yes", "if.2.stp.edge.port": "yes", "if.3.name": "", "if.3.state": "disable", "if.3.stp.bpdu.protect": "yes", "if.3.stp.edge.port": "yes", "if.4.name": "", "if.4.state": "enable", "if.4.stp.bpdu.protect": "yes", "if.4.stp.edge.port": "yes", "if.5.name": "", "if.5.poe": "", "if.5.state": "enable", "if.5.stp.bpdu.protect": "yes", "if.5.stp.edge.port": "yes", "if.6.name": "", "if.6.state": "enable",

89


"if.6.stp.bpdu.protect": "yes", "if.6.stp.edge.port": "yes", "if.7.name": "", "if.7.state": "enable", "if.7.stp.bpdu.protect": "yes", "if.7.stp.edge.port": "yes", "if.8.name": "", "if.8.state": "enable", "if.8.stp.bpdu.protect": "yes", "if.8.stp.edge.port": "yes", "if.9.name": "nine", "if.9.state": "enable", "if.9.stp.bpdu.protect": "yes", "if.9.stp.edge.port": "yes", "max_ports": "10", "mgmt.vlan": "1", "stp.config.name": "DB", "stp.prio": "2", "vlan.1.dhcp": "1", "vlan.1.ip": "dhcp-bootp", "vlan.1.tagged": "10", "vlan.1.untagged": "1,6-9", "vlan.270.tagged": "10", "vlan.270.untagged": "2", "vlan.271.tagged": "10", "vlan.271.untagged": "3", "vlan.272.tagged": "10", "vlan.272.untagged": "4", "vlan.273.tagged": "10", "vlan.273.untagged": "5,6" } } 2930M 24 port Copy from the first { to the last } and create a .txt or .json file with all this text so you can upload when needed.

{ "SERIAL_NUMBER": { "_sys_gateway": "", "_sys_hostname": "", "_sys_ip_address": "", "_sys_lan_mac": "ff:ff:ff:ff:ff:ff", "_sys_module_command": "", "_sys_netmask": "", "_sys_oobm_command": "", "_sys_serial": "SERIAL_NUMBER", "_sys_snmpv3_engineid": "", "_sys_stack_command": "", "_sys_template_header": “",

90


"_sys_use_dhcp": "", "_sys_vlan_1_tag_command": "", "_sys_vlan_1_untag_command": "", "banner.motd": "Unauthorized use of this system can result in civil and criminal penalties! So if you are not a valid user stay out", "dfgw": "192.168.0.254", "dns": "75.75.75.75", "hostname": "db-2930M-24", "if.1.name": "", "if.1.state": "enable", "if.1.stp.bpdu.protect": "no", "if.1.stp.edge.port": "no", "if.10.name": "", "if.10.state": "enable", "if.10.stp.bpdu.protect": "yes", "if.10.stp.edge.port": "yes", "if.11.name": "", "if.11.state": "enable", "if.11.stp.bpdu.protect": "yes", "if.11.stp.edge.port": "yes", "if.12.name": "", "if.12.state": "enable", "if.12.stp.bpdu.protect": "yes", "if.12.stp.edge.port": "yes", "if.13.name": "", "if.13.state": "enable", "if.13.stp.bpdu.protect": "yes", "if.13.stp.edge.port": "yes", "if.14.name": "", "if.14.state": "enable", "if.14.stp.bpdu.protect": "yes", "if.14.stp.edge.port": "yes", "if.15.name": "", "if.15.state": "disable", "if.15.stp.bpdu.protect": "yes", "if.15.stp.edge.port": "yes", "if.16.name": "", "if.16.state": "disable", "if.16.stp.bpdu.protect": "yes", "if.16.stp.edge.port": "yes", "if.17.name": "", "if.17.state": "enable", "if.17.stp.bpdu.protect": "yes", "if.17.stp.edge.port": "yes", "if.18.name": "", "if.18.state": "enable", "if.18.stp.bpdu.protect": "yes", "if.18.stp.edge.port": "yes", "if.19.name": "", "if.19.state": "enable", "if.19.stp.bpdu.protect": "yes", "if.19.stp.edge.port": "yes",

91


"if.2.name": "", "if.2.state": "enable", "if.2.stp.bpdu.protect": "yes", "if.2.stp.edge.port": "yes", "if.20.name": "", "if.20.state": "enable", "if.20.stp.bpdu.protect": "yes", "if.20.stp.edge.port": "yes", "if.21.name": "", "if.21.state": "enable", "if.21.stp.bpdu.protect": "yes", "if.21.stp.edge.port": "yes", "if.22.name": "", "if.22.state": "enable", "if.22.stp.bpdu.protect": "yes", "if.22.stp.edge.port": "yes", "if.23.name": "", "if.23.state": "enable", "if.23.stp.bpdu.protect": "yes", "if.23.stp.edge.port": "yes", "if.24.name": "", "if.24.state": "enable", "if.24.stp.bpdu.protect": "yes", "if.24.stp.edge.port": "yes", "if.3.name": "", "if.3.state": "enable", "if.3.stp.bpdu.protect": "yes", "if.3.stp.edge.port": "yes", "if.4.name": "", "if.4.state": "enable", "if.4.stp.bpdu.protect": "yes", "if.4.stp.edge.port": "yes", "if.5.name": "", "if.5.state": "enable", "if.5.stp.bpdu.protect": "yes", "if.5.stp.edge.port": "yes", "if.6.name": "", "if.6.state": "disable", "if.6.stp.bpdu.protect": "yes", "if.6.stp.edge.port": "yes", "if.7.name": "", "if.7.state": "enable", "if.7.stp.bpdu.protect": "yes", "if.7.stp.edge.port": "yes", "if.8.name": "", "if.8.state": "enable", "if.8.stp.bpdu.protect": "yes", "if.8.stp.edge.port": "yes", "if.9.name": "", "if.9.state": "enable", "if.9.stp.bpdu.protect": "yes", "if.9.stp.edge.port": "yes",

92


"max_ports": "24", "mgmt.vlan": "1", "stp.config.name": "DB", "stp.prio": "2", "vlan.1.dhcp": "0", "vlan.1.ip": "192.168.0.177 255.255.255.0", "vlan.1.tagged": "10", "vlan.1.untagged": "1,6-9", "vlan.270.tagged": "10", "vlan.270.untagged": "2", "vlan.271.tagged": "10", "vlan.271.untagged": "3", "vlan.272.tagged": "10", "vlan.272.untagged": "4", "vlan.273.tagged": "10", "vlan.273.untagged": "5,6" } }

3333 SCOTT BLVD | SANTA CLARA, CA 9505 1.866.55.ARUBA | T: 1.408.227.4500 | FAX: 1.408.227.4550 | [email protected]

www.arubanetworks.com

ERROR! NO TEXT OF SPECIFIED STYLE IN DOCUMENT.

Documents

community.arubanetworks.comcommunity.arubanetworks.com/aruba/attachments/aruba/CloudMan… · TEMPLATES AND STANDA LONE ARUBAOS-SWITCHES (AOS-S) CONTENTS DOCUMENT REVISION HISTORY