ArubaNetworks - Course and Lab Tips

Certificate errors during login to Student Lab ArubaOS Controllers this one from Microsoft's Edge browser. This can happen with any browser depending on the state of your controllers server certificate. First you should try to click the bottom link that says: "Continue to this webpage (not recommended)" This will try to bypass the fact that your browser might not trust the signing authority of the CA that signed the certificate used for SSL by your Controllers web server. If you are using the default certificate included in the ArubaOS firmware, it may be a revoked certificate, and if your browser has determined that, you may not be able to continue to the web site unless you disable certificate checking altogether on your browser. Click here to read about this issue from Aruba's community support web site. If this is the case, some times when you click on the "Continue" link, nothing will happen. Warning: it is NOT recommended to di

Lab 2.1 2.1 Section "The Aruba Controller Initial Script" Step 3. a. Situation: You are asked to select the default hostname in the initial startup wizard. Problem: If you don't see a question about Hostname, your initialisation script has probably progressed past the initial question of the script. Solution: press "Control-X" to restart the initialisation wizard. You should now see the script restart from the beginning: Restarting from beginning... Enter System name [Aruba7030]: 2.1 Section "Adding Licenses" From step 2 to step 4 of "Adding Licenses" section you are asked to access VDI2 and find your license folder to copy and paste licences into your controller CLI".  In most cases you can retrieve these licences from from a file where they have been previously stored on the controller (by your lab administrator) more quickly and easily as follows with "license import VTC-Licenses" : (controller) # dir -

If your working in a lab environment and you want to have easy quick access to your equipment without hassle of repeated logon requests, you can do the following: (controller) #configure t Enter Configuration commands, one per line. End with CNTL/Z (controller) (config) #enable bypass (controller) (config) #loginsession timeout 0 (controller) (config) #web-server profile (controller) (Web Server Configuration) #session-timeout 3600 (controller) (Web Server Configuration) #write memory you can copy and paste this into your controller: configure terminal enable bypass loginsession timeout 0 web-server profile session-timeout 3600 exit exit write memory

If your working in a lab environment and you want to have easy quick access to your equipment without hassle of repeated logon requests, you can do the following: (MM-1) [mynode] #cd /mm (MM-1) [mm] #configure t Enter Configuration commands, one per line. End with CNTL/Z (MM-1) [mm] (config) #loginsession timeout 0 (MM-1) [mm] (config) #web-server profile (MM-1) [mm] (Web Server Configuration) #session-timeout 3600 (MM-1) [mm] (Web Server Configuration) #cd /md (MM-1) [md] (config) #loginsession timeout 0 (MM-1) [md] (config) #web-server profile (MM-1) [md] (Web Server Configuration) #session-timeout 3600 (MM-1) [md] (Web Server Configuration) #write memory you can copy and paste this into your Mobility Master: cd /mm configure terminal loginsession timeout 0 web-server profile session-timeout 3600 write memory cd /md loginsession timeout 0 web-server profile session-timeout 3600 exit exit write memory In order to gain access to your AP, you may have to disable or set you