Mudanças entre as edições de "Backup Aruba"

De Slacam_Wiki
Ir para: navegação, pesquisa
Linha 1: Linha 1:
 +
How do I backup a controller?
 +
Question
 +
What to back up on a Master or Local controllers to recover from a flash failure? And how to do the backup?
  
| How do I backup a controller?
+
Answer
|-
+
|
+
|-
+
| class="subtitle" |
+
| class="subtitle" | Question
+
|-
+
| class="textcell" |  
+
| class="textcell" id="desc" | <div><font face="Arial, Helvetica">What to back up on a Master or Local controllers to recover from a flash failure? And how to do the backup?</font></div>
+
|-
+
| [[Image:]]
+
|-
+
| class="subtitle" | &nbsp;
+
| class="subtitle" | Answer
+
 
|-
 
|-
 
| class="textcell" | &nbsp;  
 
| class="textcell" | &nbsp;  

Edição das 13h08min de 22 de novembro de 2010

How do I backup a controller?

Question

What to back up on a Master or Local controllers to recover from a flash failure? And how to do the backup?

Answer |- | class="textcell" |  

| class="textcell" id="soln" |

Product and Software: This article applies to all Aruba controllers and ArubaOS 2.5 and later.

On the Master:

  1. License database: #license export <filename>
  2. Local user database: #local-userdb export <filename>
  3. WMS database: #wms export-db <filename>
  4. WMS classification: #wms export-class <filename-prefix>

This command generates two files for the APs and for the wifi stations.

  1. Global AP database: #export gap-db <filename> // 3.x only (optional)
  2. RF Plan: The export is done through the WebUI only:

(ArubaOS 2.5): Plan > Export // wms-cgi.export file by Building

(ArubaOS 3.x): Plan > Export // wms.cgi file by Campus

  1. Customized Captive Portal: #backup flash

This command creates the file backupflash.tar.gz on the flash that can be retrieved to a TFTP server as follows:

#copy flash: backupflash.tar.gz tftp: <tftp_server_IP> backupflash.tar.gz

The customized CP files would be available under the upload directory.

  1. Configuration: The configuration file used by the boot process could be checked using the following command:

#show boot //default is: default.cfg

It could be copied to a TFTP server or retrieved from the config folder after backing up the flash.

On the Local:

  1. License database: #license export <filename>
  2. Local user database: #local-userdb export <filename>
  3. Customized Captive Portal: #backup flash

This command creates the file backupflash.tar.gz on the flash that can be retrieved to a TFTP server as follows:

#copy flash: backupflash.tar.gz tftp: <tftp_server_IP> backupflash.tar.gz

The customized CP files would be available under the upload directory.

  1. Configuration: The configuration file used by the boot process could be checked using the following command:

#show boot //default is: default.cfg

It could be copied to a TFTP server or retrieved from the config folder after backing up the flash.

|}