Guest

CiscoWorks Wireless LAN Solution Engine (WLSE)

Backing up the Wireless LAN Solution Engine Software

Document ID: 41888

Updated: Oct 26, 2005

   Print

Introduction

This document describes how to back up the Wireless LAN Solution Engine (WLSE) prior to an upgrade.

Prerequisites

Requirements

There are no specific prerequisites for this document.

Components Used

The information in this document is based on the software and hardware versions WLSE 1.0 through 1.3.1.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Back up the WLSE

Before you upgrade, you should back up the WLSE. The WLSE 1.3 upgrade attempts to preserve the WLSE database, but you must back up if something goes wrong with the upgrade.

Data backed up includes:

  • WLSE role and user information

  • Discovery configuration information

  • Other configuration information

The WLSE backs up its configuration and database to an FTP server. You can perform the backup from the WLSE GUI or CLI.

With both the CLI and GUI backup methods, the WLSE creates a directory on the FTP server, named by concatenating the WLSE hostname with a time and date stamp. There are two files inside the directory - a tar ball archive and .inf file - each with the same name as the directory. The file names are hostname_date_time.tar and hostname_date_time.inf, respectively.

Before you can use a Windows 2000 or Windows XP system for backups, you must configure it for UNIX directory mode.

Complete these steps:

  1. On the server, select Start > Settings > Control Panel > Administrative Tools > Internet Services Manager. If this option is not available on the server, enable it as described here:

    1. Select Start > Settings > Control Panel > Add/Remove Programs.

    2. On the left side of the Add/Remove window, click Add/Remove Windows Components. The Windows Components wizard starts.

    3. Check the checkbox for Internet Information Services.

    4. Click Next, and complete the screens for the install.

  2. If IIS is installed, from the Tree panel on the left side of the window, select the Windows 2000 or Windows XP system name.

    1. In the Description panel, verify that the State for Default FTP Site shows as Running.

    2. Right-click Default FTP Site and select Properties.

    3. Under the Home Directory tab, complete these steps:

      1. Under FTP Site Directory, verify that Write box is checked.

      2. Under Directory Listing Style, select the UNIX radio button.

      3. Click Apply/OK in order to save the changes.

Back Up the WLSE from the GUI

In order to configure the FTP server in the WLSE GUI, complete these steps:

  1. Log in as admin.

  2. Navigate to Administration > Appliance > Backup and Restore > Configure.

  3. Enter these values:

    • Hostname or IP address of the FTP server

    • Appropriate username and passwords

    • Path to the FTP directory if other than the default of the FTP server

  4. Click Save in order to complete the backup FTP server configuration.

  5. Navigate to Administration > Appliance > Backup and Restore > Backup.

  6. Click Backup. A warning screen displays stating that the WLSE needs to shutdown the Tomcat servlet engine in order to complete the backup.

  7. At the warning screen, select OK in order to start the backup.

  8. Once the backup is complete, log in to the WLSE again.

    Note: It can take a few minutes for the servlet engine to reinitialize. During this time, you can see web page errors. After a few minutes, you have full WLSE GUI access.

    Note: The time required for a WLSE backup is related to the amount of data to backup and network latency between the WLSE and the FTP server. The backup may take 10-15 minutes if there are several hundred devices across a LAN.

Back Up the WLSE from the CLI

In order to back up the WLSE using the CLI, complete these steps:

  1. Log in to the console as an administrative user, typically admin.

  2. Use the backupconfig command in order to configure the backup FTP server. The command syntax is:

    backupconfig {hostname} {username} {password} [directory]
    

    where:

    • hostname is the hostname or IP address of the FTP server where backup data is saved.

    • username is a valid username on the FTP server.

    • password is the password for the above username.

    • directory parameter is only required if the backup location is not in the FTP root directory (optional).

    Example:

    admin@wlse:show backupconfig 
     Hostname: 172.16.96.44 
     Username: cse 
     Directory: /var/tmp
    
  3. Next, do a show backupconfig to verify that the values are taken correctly by the WLSE:

    Example:

    admin@wlse:show backupconfig 
     Hostname: 172.16.96.44 
     Username: cse 
     Directory: /var/tmp 
    
  4. Perform a backup test in order to verify that the WLSE accesses the target location with the username/password defined to write the data. If this fails, then the backup fails. A failed test indicates that either the username/password is incorrect or that you do not have permissions to write at the target location/directory.

    Example:

    admin@wlse:backup test 
     Test OK
    
  5. If the result is anything but Test OK, then the backup fails.

    Perform a backup for the actual backup. The length of time the backup takes to complete depends upon the quantity of data requiring backup and network latency between the WLSE and FTP server. If there are several hundred devices on the LAN the backup can take 10-15 minutes. During this time, there is no status indicator available in the CLI. Once the backup is completed, the backup file name displays and the CLI prompt becomes available.

    Example:

     admin@wlse:backup 
    
     backupfile:  wlse_12162002_140840.tar wlse_12162002_140840.inf 
    
     admin@wlse: 
    
    

Related Information

Updated: Oct 26, 2005
Document ID: 41888