H3C WX Access Controller Software Maintenance Guide

Abstract
This document details the software maintenance information for the WX access controllers.

Hangzhou H3C Technologies Co., Ltd. [Link]

Copyright 2003-2010, Hangzhou H3C Technologies Co., Ltd. and its licensors

No part of this manual may be reproduced or transmitted in any form or by any means without the prior written consent of Hangzhou H3C Technologies Co., Ltd.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents. However, the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Hangzhou H3C Technologies Co., Ltd. and its licensors shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments
H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean,

NeoVTL, SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this guide are the property of their respective owners.

Environmental protection
This product has been designed to comply with the environmental protection requirements. The storage, use, and disposal of this product must meet the applicable national laws and regulations.

Contents
1 Software maintenance 5
About this guide 5 Product overview 5 Files managed by the WX5002 access controller 5 BootWare program file 5 Application files 6 Configuration files 7 Approaches for software maintenance 8 BootWare and Application File Upgrade Flow 9 BootWare menus 9 BootWare main menu 9 BootWare submenus 11 Upgrading the BootWare through an Ethernet/serial interface 12 Modifying serial interface parameters 13 Upgrading the BootWare through an Ethernet interface 15 Upgrading the BootWare through a serial interface 18 Upgrading applications through a serial interface on the BootWare menu 20 Upgrading applications through an Ethernet interface on the BootWare menu 21 Configuring Ethernet interface parameters 21 Upgrading Applications through an Ethernet interface 22 Maintaining the application and configuration files through the CLI 23 Maintaining the access controller through TFTP 23 Maintaining the access controller through FTP 25 Maintaining application and configuration files 28 Displaying all files 29 Setting an application file type 29 Specifying a startup configuration file 30

Delete a File 31 Dealing with password loss 32 User Password Loss 32 BootWare password loss 33 Super password loss 33 Backing up and restoring the BootWare 33 Using the BootWare menu 33 Using the CLI 34

2 Troubleshooting 35
Software Loading Failure 35 Power supply failure 35 Configuration system failure 36 No display on the terminal 36 Illegible characters on the terminal 36

1 Software maintenance
About this guide
This guide provides software maintenance information for the WX access controllers. Installation and configuration procedures are available in the specific access controller installation guide.

Product overview
The H3C WX access controllers are new-generation wireless access controller products. They provide two groups of combo ports. They also provide an expansion slot for an additional card. This provides not only strong processing capability but also flexible system configuration schemes. In terms of reliability, the WX access controllers use pluggable power supply units (PSU). Thus, you can choose to use double PSUs for high reliability or use a single PSU to be economical.

Files managed by the WX access controllers

The WX access controllers manage the following types of files:

BootWare program file Application file Configuration file

BootWare program file

The extended BootWare menu is referred to as the BootWare main menu in this manual unless otherwise specified. The BootWare program file is used to boot the applications when the access controller is started up. The complete BootWare program file consists of two segments: basic and extended.

Basic BootWare implements the basic system initialization.

Extended BootWare provides abundant human-computer interaction (HCI) functions. It is used for interface initialization for upgrading applications and booting the system.

The full BootWare refers to the combination of the two segments. After the basic BootWare is booted, you can load or upgrade the extended BootWare on the menu of the basic BootWare.

WARNING! Do not power off or restart the access controller during BootWare upgrade process; otherwise, the BootWare program may be damaged and the access controller may fail to operate normally.

Application files
The WX access controllers support the Dual Image function. By default, the following application files are defined for system boot:

Main application file (main file) Backup application file (backup file) Secure application file (secure file)

These files are stored on the built-in CF card, with the extension .bin. Typically, the default application file is written into the built-in CF card of an access controller before it is delivered. If you have loaded the three application files to the CF card, the system uses these three files to boot the access controller in the sequence of [Link], [Link], and [Link]. For information about how to set the application file types, see Maintaining application and configuration files on page 28. The default names and types of the application files and their loading priorities for booting are:

Main application file. The default name is [Link], and the file type is M. It is the default application file used for booting. Backup application file. The default name is [Link], and the file type is B. When the boot using the main application file fails, the system boots using the backup application file.

Secure application file. The default name is [Link], and the file type is S. When boot using the backup application file fails, the system tries the secure application file. If the boot using the secure application file fails, the system prompts a boot failure.

Note that:

The application files for system boot can be type M, B and S, but not type N/A. After the application program is loaded, you can rename the application files through the command line interface (CLI) or change the file type (M, B or N/A) through the BootWare menu or the CLI. However, you cannot change the file type of the S-type application file.

Because the secure application file is the last resort for system boot, you cannot change the type of the secure application file, or change other types of files to the secure application file. You can only download it by selecting the Update Secure Application File option on the BootWare menu.

Only one file of the same type (M, B, or S) can exist on the CF card. For instance, if an application file of type M+B exists on the CF card, another file of type M or B cannot exist. If the type of another file is changed to B, the existing type M+B file changes to a file of type M.

Configuration files
Configuration files store configuration information of the access controller, with the extension of .cfg. Typically, the access controller has no configuration file when it is delivered. The configuration files generated by users are saved in the built-in CF card, with the default name [Link].

CAUTION: The length of a configuration file name must not exceed 64 characters (including the drive name and the string terminator). For example, if the drive name is cfa0:/, the maximum length of a file name is [6416] = 57 characters. If the length of a file name exceeds 57 characters, error occurs in file operations on that file. Generally, it is recommended to keep the file name within 16 characters. There is a limitation on the length of file name that can be displayed in BootWare. If a file name is shorter than 30 characters, all the characters of the file name can be displayed; if a file name has or exceeds 30 characters, only the first 26 characters of the file name can be displayed, followed by a tilde (~) and a serial number. The serial number identifies position in sequence of the file. For example, if three files, file A, file B and file C, have a file name longer than 30 characters, the name of file A will appear as the first 26 characters plus ~001, that of file B will appear as the first 26 characters plus ~002, and that of file C will appear as the first 26 characters plus ~003.

Approaches for software maintenance

You can maintain the access controller in one of the following ways:

Upgrade BootWare and application files using the XMODEM protocol through a serial interface. Upgrade application files using TFTP/FTP through an Ethernet interface on the BootWare menu. Upload/download application files and configuration files using TFTP/FTP through command lines.

NOTE: The BootWare program is upgraded together with the host software program version. That is, the system automatically upgrades the BootWare program when you upgrade the host software program. Before upgrading the software of your access controller, check the current BootWare version and application program version to make sure that the correct file is used for the upgrade. For the association between the host software version and the BootWare version, refer to the version compatibility matrix in Release Notes.

BootWare and Application File Upgrade Flow

Figure 1 BootWare and application file upgrade flow
Start

Check the Comware application version

Does the Comware application need to be updated ? Yes Select the correct Comware application file No

Select the update method

Load the Comware application through an Ethernet interface

BootWare menus
BootWare main menu
1.

Usi ng Xmod e m

Through the BootWare menu

After you power on or restart the device, the terminal first displays the following information:

Usi ng TF T P

U sing FT P

Through the CLI

Update

End

System is starting...

Then, the system displays the following:

Booting Normal Extend BootWare.... The Extend BootWare is self-decompressing.................. Done! **************************************************************************** * * * Copyright (c) 2004-2009 Hangzhou H3C Technologies Co., Ltd. Compiled Date CPU Type CPU L1 Cache CPU Clock Speed Memory Type Memory Size Memory Speed BootWare Size Flash Size cfa0 Size CPLD Version PCB Version : Nov : 32KB : 800MHz : DDR2 SDRAM : 1024MB : 533MHz : 512KB : 4MB : 259MB : 008 : Ver.A 9 2009 H3C WX5002 BootWare, Version 1.06 * * *

****************************************************************************

: XLR716

BootWare Validating... Press Ctrl+B to enter extended boot menu...

2.

Press Ctrl + B when the system prompts Press Ctrl+B to enter extended boot menu. Then, the system prompts you to enter the BootWare password:
Please input BootWare password:

3.

You have three chances to enter the BootWare password (the initial password is null). If you fail to enter the correct password three times in a row, the system is halted and you can only restart the system. After you provide the correct password, the system enters the BootWare main menu:

Note: The current operating device is cfa0 Enter < Storage Device Operation > to select device. ===========================<EXTEND-BOOTWARE MENU>============================= |<1> Boot System |<2> Enter Serial SubMenu

10

|<3> Enter Ethernet SubMenu |<4> File Control |<5> Modify BootWare Password |<6> Skip Current System Configuration |<7> BootWare Operation Menu |<8> Clear Super Password |<9> Storage Device Operation |<0> Reboot ============================================================================= Enter your choice(0-9):

BootWare submenus
Serial submenu
You can upgrade application files, change the serial interface baud rate, and so on through the serial submenu. Enter 2 on the BootWare main menu to enter the serial submenu. The system displays:
===========================<Enter Serial SubMenu>============================= |Note:the operating device is cfa0 |<1> Download Application Program To SDRAM And Run |<2> Update Main Application File |<3> Update Backup Application File |<4> Update Secure Application File |<5> Modify Serial Interface Parameter |<0> Exit To Main Menu ============================================================================== Enter your choice(0-5):

Ethernet submenu
Enter 3 on the BootWare main menu to enter the Ethernet submenu. The system displays:
========================<Enter Ethernet SubMenu>============================ |Note:the operating device is cfa0 |<1> Download Application Program To SDRAM And Run |<2> Update Main Application File |<3> Update Backup Application File |<4> Update Secure Application File |<5> Modify Ethernet Parameter |<0> Exit To Main Menu |<Ensure The Parameter Be Modified Before Downloading!> ============================================================================== Enter your choice(0-5):

Items in this submenu are described in the following table.

11

File control submenu

Enter 4 on the BootWare main menu to enter the file control submenu. The following information is displayed:
===============================<File CONTROL>================================= |Note:the operating device is cfa0 |<1> Display All File(s) |<2> Set Application File type |<3> Delete File |<0> Exit To Main Menu ============================================================================== Enter your choice(0-3):

BootWare operation submenu

Enter 7 on the BootWare main menu to enter the BootWare operation submenu. The system displays:
=========================<BootWare Operation Menu>============================ |Note:the operating device is cfa0 |<1> Backup Full BootWare |<2> Restore Full BootWare |<3> Update BootWare By Serial |<4> Update BootWare By Ethernet |<0> Exit To Main Menu ============================================================================== Enter your choice(0-4):

Storage device operation submenu

Enter 9 on the BootWare main menu to enter the storage device operation submenu. The system displays:
==============================<DEVICE CONTROL>================================ |<1> Display All Available Nonvolatile Storage Device(s) |<2> Set The Operating Device |<3> Set The Default Boot Device |<0> Exit To Main Menu ============================================================================== Enter your choice(0-3):

Upgrading the BootWare through an Ethernet/serial interface

To upgrade the BootWare through a serial interface, use the XMODEM protocol. XMODEM is a file transfer protocol that is widely used due to its simplicity and good performance. XMODEM transfers files through serial interfaces. It supports two types of

12

data packets (128 bytes and 1 KB), two check methods (checksum and CRC), and error packet retransmission mechanism (generally the maximum number of retransmission attempts is ten). The XMODEM transmission procedure is completed by the cooperation of a receiving program and a sending program. The receiving program sends a negotiation character to negotiate a packet check method. After the negotiation, the sending program starts to send data packets. Upon receiving a complete packet, the receiving program checks the packet using the agreed check method.

When the check succeeds, the receiving program sends an acknowledgement character and the sending program proceeds to send another packet. When the check fails, the receiving program sends a negative acknowledgement character and then the sending program retransmits the packet.

Modifying serial interface parameters

Sometimes, you need a high serial interface baud rate to save the update time, or a low baud rate to ensure transmission reliability. This section introduces how to adjust the serial interface baud rate.
1. 2.

Enter the BootWare main menu and enter 2 to go to the serial submenu. Enter 5 on the submenu to modify the baud rate. The system displays the following:
| | | | | | | | |

=================================<BAUDRATE SET>============================= |Note:'*'indicates the current baudrate | Change The HyperTerminal's Baudrate Accordingly |---------------------------<Baudrate Available>------------------------|<1> 9600(Default)* |<2> 19200 |<3> 38400 |<4> 57600 |<5> 115200 |<0> Exit Enter your choice(0-5): 3.

============================================================================

Select a proper baud rate. For example, enter 5 for a baud rate of 115200 bps and the system displays the following information:

Baudrate has been changed to 115200 bps. Please change the terminal's baudrate to 115200 bps, press ENTER when ready. 4.

At this time, the serial interface baud rate of the access controller is modified to 115200 bps, while that of the terminal is still 9600 bps. The access controller and the

13

terminal cannot communicate with each other. Change the baud rate to 115200 bps on the terminal.

Perform the following operations on the terminal:

1.

Disconnect the terminal (see Figure 2

Figure 2 Disconnect the terminal

2.

Select File > Properties, In the Properties dialog box, click Configure and then Set the Bits per second to 115200.

Figure 3 Modify the baud rate

14

3.

Select Call > Call to establish a new connection.

Figure 4 Re-establish a call connection

4.

Press the Enter key, and the system prompts the current baud rate.

The current baudrate is 115200 bps ==============================<BAUDRATE SET>============================= |Note:'*'indicates the current baudrate | Change The HyperTerminal's Baudrate Accordingly | | | | | | | |

|---------------------------<Baudrate Available>-------------------------| |<1> 9600(Default) |<2> 19200 |<3> 38400 |<4> 57600 |<5> 115200* |<0> Exit Enter your choice(0-5):

==========================================================================

NOTE: After downloading files with a changed baud rate, timely change the baud rate back to 9,600 bps in HyperTerminal to ensure the normal display on the console screen when the system boots or reboots.

Upgrading the BootWare through an Ethernet interface

Enter the BootWare main menu (see BootWare main menu on page 9).
1.

On the BootWare main menu, enter 7. The system enters the BootWare operation submenu, where you can perform all BootWare operations. For details about this menu, see BootWare operation submenu on page 12. Enter 4 on the BootWare operation submenu to enter the BootWare operation Ethernet submenu:

2.

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=====================

15

|<1> Update Full BootWare |<2> Update Extend BootWare |<3> Update Basic BootWare |<4> Modify Ethernet Parameter |<0> Exit To Main Menu ============================================================================== Enter your choice(0-4): 3.

Enter 4 on the BootWare operation Ethernet submenu. The system prompts you to modify the network parameters.

==========================<ETHERNET PARAMETER SET>============================ |Note: | | | | | '.' = Clear field. '-' = Go to previous field. Ctrl+D = Quit.

============================================================================== Protocol (FTP or TFTP) :tftp Load File Name Target File Name Server IP Address Local IP Address Gateway IP Address :host :[Link] :target :[Link] :[Link] :[Link] :[Link]

NOTE: The load file name and the target file name must not exceed 50 bytes. After modification of the parameters, the system display returns to the BootWare operation Ethernet submenu.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================== |<1> Update Full BootWare |<2> Update Extend BootWare |<3> Update Basic BootWare |<4> Modify Ethernet Parameter |<0> Exit To Main Menu ============================================================================== Enter your choice(0-4): 4.

Enter 1 on the BootWare operation Ethernet submenu. The system displays:

16

Loading................................................................... .........................................................Done! 20710792 bytes downloaded! Updating Basic BootWare? [Y/N]Y Updating Basic BootWare................Done! Updating Extend BootWare? [Y/N]Y Updating Extend BootWare..............Done!

After download of the BootWare program file, the system display returns to the BootWare operation Ethernet submenu.
===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== |<1> Update Full BootWare |<2> Update Extend BootWare |<3> Update Basic BootWare |<4> Modify Ethernet Parameter |<0> Exit To Main Menu Enter your choice(0-4): 5. | | | | |

============================================================================

Enter 0 on this menu to return to the BootWare operation submenu:

| | | | | |

=========================<BootWare Operation Menu>========================== |Note:the operating device is cfa0 |<1> Backup Full BootWare |<2> Restore Full BootWare |<3> Update BootWare By Serial |<4> Update BootWare By Ethernet |<0> Exit To Main Menu Enter your choice(0-4): 6.

===========================================================================

Enter 0 on the BootWare operation submenu to return to the BootWare main menu:

===========================<EXTEND-BOOTWARE MENU>=========================== |<1> Boot System |<2> Enter Serial SubMenu |<3> Enter Ethernet SubMenu |<4> File Control |<5> Modify BootWare Password |<6> Skip Current System Configuration |<7> BootWare Operation Menu |<8> Clear Super Password |<9> Storage Device Operation |<0> Reboot Enter your choice(0-9): 0 7. | | | | | | | | | |

============================================================================

Enter 0 on the BootWare main menu to reboot the access controller.

17

Upgrading the BootWare through a serial interface

Enter the BootWare main menu (see BootWare main menu on page 9).
1.

On the BootWare main menu, enter 7. The system enters the BootWare operation submenu, where you can perform all BootWare operations. For detail description on this submenu, see section BootWare operation submenu on page 12. Enter 3 on the BootWare operation submenu to enter the BootWare operation serial submenu:

2.

====================<BOOTWARE OPERATION SERIAL SUB-MENU>====================== |<1> Update Full BootWare |<2> Update Extend BootWare |<3> Update Basic BootWare |<4> Modify Serial Interface Parameter |<0> Exit To Main Menu ============================================================================== Enter your choice(0-4): 3.

Enter 4 on the BootWare operation serial submenu. The system prompts you to modify the baud rate:

===============================<BAUDRATE SET>================================= |Note:'*'indicates the current baudrate | | | Change The HyperTerminal's Baudrate Accordingly

|-----------------------------<Baudrate Available>---------------------------|<1> 9600(Default)* |<2> 19200 |<3> 38400 |<4> 57600 |<5> 115200 |<0> Exit ============================================================================== Enter your choice(0-5): 4.

Change the communication baud rate. For the detailed modification procedure, see Modifying serial interface parameters on page 13. After the modification, the system displays the following information:

Baudrate has been changed to 115200 bps. Please change the terminal's baudrate to 115200 bps, press ENTER when ready. The current baudrate is 115200 bps =================================<BAUDRATE SET>============================= |Note:'*'indicates the current baudrate | Change The HyperTerminal's Baudrate Accordingly | |

|---------------------------<Baudrate Available>---------------------------|

18

|<1> 9600(Default) |<2> 19200 |<3> 38400 |<4> 57600 |<5> 115200* |<0> Exit Enter your choice(0-5): 5.

| | | | | |

============================================================================

Enter 0 to return to the BootWare operation serial submenu.

====================<BOOTWARE OPERATION SERIAL SUB-MENU>====================== |<1> Update Full BootWare |<2> Update Extend BootWare |<3> Update Basic BootWare |<4> Modify Serial Interface Parameter |<0> Exit To Main Menu ============================================================================== Enter your choice(0-4): 6.

Enter 1 on the BootWare operation serial submenu. The system displays the following information:

Please Start To Transfer File, Press <Ctrl+C> To Exit. Waiting ...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC 7.

Select Transfer > Send file on the terminal window. The following dialog box appears:

Figure 5 Send File dialog box

8.

Click Browse to select the application file to be downloaded, and select Xmodem from the Protocol drop-down list. Then click Send. The file dialog box appears (see Figure 6

19

Figure 6 Sending file dialog box

Upon successful download, the system displays the following information:

Download successfully! 10323456 bytes downloaded! Updating Basic BootWare? [Y/N]Y Updating Basic BootWare.................Done! Updating Extend BootWare? [Y/N]Y Updating Extend BootWare...........Done! 9.

Change the baud rate on the configuration terminal from 115200 bps to 9600 bps, and then reboot the access controller.

NOTE: The actual file name, size and path may differ from what are shown in Figure 6 Before upgrading the software of your access controller, check the current BootWare version and the application program version to ensure that the correct file is used for the upgrade. After you download files with a changed baud rate, timely change the baud rate in the HyperTerminal to 9600 bps to ensure the normal display on the console screen when the system boots or reboots.

Upgrading applications through a serial interface on the BootWare menu

The application file upgrade through a serial port is implemented on the serial submenu. Enter 2 on the BootWare main menu to enter the serial submenu. For a detailed description of this submenu, see Serial submenu on page 11. The following example shows how to upgrade the main application file.

20

To improve the upgrading speed, you can modify the serial interface baud rate before upgrading the file (see Modifying serial interface parameters on page 13).
1.

Enter 2 on the serial submenu. The system displays the following information:
Please Start To Transfer File, Press <Ctrl+C> To Exit. Waiting ...CCCCCCCCCC

2.

Select and send the application file. The procedure for upgrading an application file through a serial interface is the same as upgrading the BootWare. For details, see Upgrading the BootWare through an Ethernet/serial interface on page 12.

NOTE: The size of an application program is typically over 10 MB. Even at the maximum baud rate of 115200 bps, the upgrade will take a long time. Therefore, it is recommended to upgrade application files through an Ethernet interface.

Upgrading applications through an Ethernet interface on the BootWare menu

Enter 3 on the BootWare main menu to enter the Ethernet submenu. For details, see Ethernet submenu on page 11.

Configuring Ethernet interface parameters

Before upgrading an application program through an Ethernet interface, you must configure the Ethernet interface of the access controller:
1. 2.

Enter 3 on the BootWare main menu to enter the Ethernet submenu. Enter 5 on the submenu to enter the Ethernet interface configuration interface:
'.' = Clear field. '-' = Go to previous field. Ctrl+D = Quit.

==========================<ETHERNET PARAMETER SET>============================ |Note: | | | | |

============================================================================== Protocol (FTP or TFTP) :tftp Load File Name Target File Name :host :[Link] :target

21

:[Link] Server IP Address Server IP Address Local IP Address Gateway IP Address :[Link] :[Link] :[Link] :[Link]

NOTE: When configuring a parameter, you can enter a new value directly, or press Enter to accept the default value, which is after the colon. Type a dot (.) to clear the input, a hyphen (-) to return to the previous parameter field, and a combination of ^D (namely, Ctrl+D) to exit the parameter configuration interface. The WX access controllers support only GigabitEthernet 1/0/1 for application upgrade.

Upgrading Applications through an Ethernet interface

The Trivial File Transfer Protocol (TFTP) is a TCP/IP protocol used for file transfer between client and server. It provides a simple and low-cost file transfer service. TFTP provides unreliable data transfer over UDP and does not provide any access authorization and authentication mechanism. It employs the timeout retransmission method to implement best-effort delivery of data. Compared with FTP, TFTP has a much smaller software size. For details about the application file types, see Application files on page 6. Follow these steps to upgrade an application file through the management Ethernet interface (10/100 Base-TX):
1.

Set up a software upgrade environment.

Figure 7 Set up a software upgrade environment

PC TFTP Server Console AC TFTP Client

Ethernet

2.

Connect GigabitEthernet 1/0/1 to a PC with an Ethernet cable. Run TFTP Server on the PC, and set the path of the application file to be downloaded.

NOTE: The TFTP server software is not provided with the WX access controllers.

22

3.

Modify the Ethernet interface parameters. For details, see Configuring Ethernet interface parameters on page 21. Enter 3 on the BootWare main menu to enter the Ethernet submenu. This example shows how to upgrade the main application file. Enter 2 on the Ethernet submenu. The following information appears:

4. 5.

Loading....................................................................... .............................Done! 10323352 bytes downloaded! Updating File cfa0:/[Link] The file is exist,will you overwrite it? [Y/N]Y.............................................. ............................................................. ..........................Done! 6. 7. ...

Enter 0 to return to the BootWare main menu. Enter 1 on the BootWare main menu to reboot the access controller.

CAUTION: If the downloaded file has the same name with an existing file on the CF card, the system prompts The file is exist, will you overwrite it? [Y/N]. If you choose Y, the existing file is overwritten. Make sure that sufficient space is available on the CF card. In case of insufficient space, the system presents a prompt. The new application file directly replaces the existing file of the same type. In this example, the downloaded file [Link] replaces the existing application file of type M and becomes the only main application file.

Maintaining the application and configuration files through the CLI

After the access controller is normally started, you can back up and restore the application and configuration files through the CLI.

Maintaining the access controller through TFTP

You can use the WX access controller as a TFTP client and a file server as the TFTP server. Use commands on the configuration terminal, which can be the same file

23

server, to upload the application and configuration files from the access controller to the file server or download the files from the file server to the access controller.

Setting up a configuration environment

Set up a network environment (for the procedure, see Upgrading Applications through an Ethernet interface on page 22). Run the TFTP Server on the file server and set the file path. Figure 8 Network diagram for software maintenance through the CLI
PC TFTP Server Console AC TFTP Client

Ethernet

Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP address of the TFTP server to [Link], and that of the access controllers management interface to [Link]. Then use ping to verify the network connectivity.

Backing up and restoring application and configuration files

The operations in this section are performed in user view. After setting up the environment, perform the following operations on the PC: CAUTION: When you back up a file to the server and if a file with the same name already exists on the server, the existing file is overwritten without a prompt.
1.

View the files in the current file system with the dir command.
<H3C>dir Directory of cfa0:/ 0 1 2 3 -rw-rw-rw-rw10295948 33 802 76960 Sep 11 2053 02:17:14 Aug 20 2008 09:58:44 Aug 20 2008 09:58:44 Aug 15 2008 15:58:02 [Link] [Link] [Link] [Link]

252434 KB total (243028 KB free) File system type of cfa0: FAT32

24

<H3C>

For example, to back up the file [Link] on the access controller and save it as [Link] on the TFTP server, use the following command:
<H3C>tftp [Link] put [Link] [Link] File will be transferred in binary mode Sending file to remote TFTP server. Please wait... \ TFTP: 2. 802 bytes sent in 10 second(s). File uploaded successfully.

To download [Link] from the TFTP server to the access controller, use the following command:
<H3C>tftp [Link] get [Link] [Link] File will be transferred in binary mode Downloading file from remote TFTP server, please wait... TFTP: 842 bytes received in 1 second(s) File downloaded successfully.

If a file with the same name already exists on the access controller, the system prompts whether to replace the existing file. Enter Y to replace it, or N to abort. The backup configuration file can be modified by using a text editor. To update the system configuration of the access controller, you can modify the backup configuration file on the file server, and then download the modified configuration file to the access controller. Your update takes effect on the access controller after it is restarted. Likewise, you can download a new application file to the access controller to overwrite the existing main application file to update the application.

Maintaining the access controller through FTP

The access controller as the FTP server
The File Transfer Protocol (FTP) is an application layer protocol in the TCP/IP suite. It is mainly used for file transfer between remote hosts. FTP provides a reliable, connectionoriented data transfer service over TCP. The access controller can serve as the FTP server. In this case, you can use your PC as an FTP client to log in to the access controller for file operations. Before using FTP, you must install the FTP client application on your PC. The FTP client software is not provided with the access controller. You must prepare it yourself. In the following example, the FTP client program is the one that comes with Microsoft Windows XP. To maintain the software of your access controller through FTP with the access controller as the FTP server:

25

Set up a network environment

1.

Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP address of the FTP client (PC) to [Link], while that of the access controllers Ethernet interface to [Link]. Then use the ping command to verify the network connectivity.

Figure 9 Set up a software maintenance environment (the access controller as the FTP server)
PC FTP Client Console AC FTP Server

Ethernet

2.

Enable the FTP service. Configure FTP server authentication and authorization and enable FTP. The FTP server supports multi-client access. When a remote FTP client sends a request to the FTP server, the FTP server executes an action accordingly and returns the execution result to the client. Use the following command to enable the FTP service.
[H3C]ftp server enable

3.

Add an authorized FTP username and password:

//Create user account guest. //Set user type to FTP. //Set password to 123456 for the //Set the user level to 3.

[H3C]local-user guest [H3C-luser-guest]service-type ftp [H3C-luser-guest]password simple 123456 user. [H3C-luser-guest]authorization-attribute level 3

Maintain the access controller

1.

After enabling the FTP service and configuring the username and password, start the FTP client program on the PC. Open a DOS window, and enter ftp at the DOS prompt:

C:\Documents and Settings\Administrator>ftp ftp> ftp> open [Link] Connected to [Link]. 220 FTP service ready. User ([Link]:(none)): guest 331 Password required for guest Password: //Enter the password 123456. //Enter the user name guest. //The system prompt changed to ftp>. //Connect to the access controller.

26

230 User logged in. 2.

//Successfully connected to the server.

Back up [Link] on the access controller to the PC:

//Specify the transfer mode as binary. //Change the local path. //Back up the file to the PC.

ftp> binary 200 Type set to I. ftp> lcd c:\temp Local directory now C:\temp. ftp> get [Link] [Link] 200 Port command okay.

150 Opening BINARY mode data connection for /[Link]. 226 Transfer complete. ftp: 14323376 bytes received in 16.81Seconds 851.87Kbytes/sec. 3.

Restore the backup file to the access controller:

//Download the backup file to the access controller.

ftp> put [Link] [Link] 200 Port command okay.

150 Opening BINARY mode data connection for /[Link]. 226 Transfer complete. ftp: 14323376 bytes sent in 8.29Seconds 1727.37Kbytes/sec. ftp> quit 221 Server closing. //Quit FTP.

The access controller as an FTP client

You can also maintain the file system of your access controller through FTP with the access controller as an FTP client.

Set up a maintenance environment.

Figure 10 Set up a software maintenance environment (access controller as an FTP client)
PC FTP Server Console AC FTP Client

Ethernet

1.

Run the FTP server program on the PC, set the file path, and set the username and password for the access controller. Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP address of the FTP server (PC) to [Link], while that of the access controllers Ethernet interface to [Link]. Then use ping to verify the network connectivity.

2.

27

3.

Maintain the access controller using the terminal connected to the console port of the access controller.

<H3C>ftp [Link] Trying [Link] ... Press CTRL+K to abort Connected to [Link]. 220 3Com 3CDaemon FTP Server Version 2.0 User([Link]:(none)):guest 331 User name ok, need password Password: 230 User logged in [ftp] 4. //Enter the password. //Connection succeeded. //Enter the username set on the server.

Download and back up files using the get and put commands.
//Download the file from the server to the access controller. //Overwrite the existing

[ftp]get [Link] [Link]

cfa0:/[Link] has been existing. Overwrite it?[Y/N]:y file or not? 227 Entering passive mode (192,168,0,1,5,60) 125 Using existing data connection 226 Closing data connection; File transfer successful.

FTP: 10323352 byte(s) received in 13.234 second(s), 780.00K byte(s)/sec. [ftp]put [Link] [Link] 125 Using existing data connection 226 Closing data connection; File transfer successful. FTP: 10323352 byte(s) sent in 7.342 second(s), 1406.00Kbyte(s)/sec. [ftp]quit 221 Service closing control connection //Quit FTP. //Back up the file on the access controller to the server. 227 Entering passive mode (192,168,0,1,5,90)

Maintaining application and configuration files

You can modify and display file types by using the file control submenu or the CLI. Enter 4 on the BootWare main menu to enter the file control submenu. The system displays the following:
===============================<File CONTROL>================================= |Note:the operating device is cfa0 |<1> Display All File(s) |<2> Set Application File type |<3> Delete File |<0> Exit To Main Menu ============================================================================== Enter your choice(0-3):

28

Displaying all files

Displaying all files on BootWare menu
Enter 1 on the file control submenu, and the system displays the following information:
Display all file(s) in cfa0: 'M' = MAIN |NO. Size(B) |1 |2 |3 |4 10323352 33 842 76960 'B' = BACKUP Time 'S' = SECURE Type Name cfa0:/[Link] cfa0:/[Link] cfa0:/[Link] cfa0:/[Link] 'N/A' = NOT ASSIGNED | | | | | ========================================================================== Aug/20/2008 10:42:42 M Aug/20/2008 10:06:24 N/A Aug/20/2008 10:23:56 N/A Aug/15/2008 15:58:02 N/A

==========================================================================

Displaying all files on the CLI

<H3C>dir Directory of cfa0:/ 0 1 2 3 -rw-rw-rw-rw10323352 33 802 76960 Sep 11 2053 02:17:14 Aug 28 2008 10:22:50 Aug 28 2008 10:22:50 Aug 15 2008 15:58:02 [Link] [Link] [Link] [Link]

252434 KB total (242996 KB free) File system type of cfa0: FAT32

Setting an application file type

Using the BootWare menu
1.

Enter 2 on the file control submenu, and the system displays the following information:
'B' = BACKUP Time 'S' = SECURE Type Name cfa0:/[Link] 'N/A' = NOT ASSIGNED | | |

'M' = MAIN |NO. Size(B) |1 |0 10323352 Exit

========================================================================== Aug/20/2008 10:42:42 M

========================================================================== Enter file No: 2.

Enter the file sequence number at the prompt above. In this example, type 1 for file [Link] and press Enter. The system prompts you to modify the file type:

Modify the file attribute:

29

============================================================================== |<1> +Main |<2> -Main |<3> +Backup |<4> -Backup |<0> Exit ============================================================================== Enter your choice(0-4) 3.

Enter 1 for +Main (set to type M), 2 for Main (remove the M type), 3 for +Backup (set to type B), or 4 for Backup (remove the B type). For details about the file types, see Application files on page 6.

Using the CLI

Change the type of file [Link] from type B to type M+B:
<H3C> boot-loader file [Link] main This command will set the boot file. Continue? [Y/N]:y The specified file will be used as the main boot file at the next reboot on slot 1!

The type of file [Link] is modified as M+B, and the file is specified as the main boot file to be used at the next startup of the access controller. If a file of type M already exists on the access controller, the type of the file automatically changes to N/A.

Specifying a startup configuration file

Using the CLI
You can use the startup saved-configuration cfgfile command to specify the configure file to be used for the next startup of the access controller. cfgfile represents the name of the configuration file to be specified.
1.

Specify the configuration file to be used for the next startup of the access controller.
<H3C> startup saved-configuration [Link] Please wait ... ... Done!

2.

Display the configuration file used for the current startup and that to be used for the next startup of the access controller.
<H3C>display startup Current startup saved-configuration file: cfa0:/[Link] Next startup saved-configuration file: cfa0:/[Link]

3.

Cancel the configuration file specified for the next startup of the access controller.
<H3C>undo startup saved-configuration Please wait ...... Done!

30

<H3C>display startup Current startup saved-configuration file: cfa0:/[Link] Next startup saved-configuration file: NULL

Delete a File
Using the BootWare menu
1.

Enter 3 on the file control submenu, and the system displays the following information:

Deleting the file in cfa0: 'M' = MAIN |NO. Size(B) |1 |2 |3 |4 |0 10323352 33 842 76960 Exit 'B' = BACKUP Time 'S' = SECURE Type Name cfa0:/[Link] cfa0:/[Link] cfa0:/[Link] cfa0:/[Link] 'N/A' = NOT ASSIGNED | | | | | | ============================================================================ Aug/20/2008 10:42:42 M Aug/20/2008 10:06:24 N/A Aug/20/2008 10:23:56 N/A Aug/15/2008 15:58:02 N/A

============================================================================ Enter file No: 2.

Type a file sequence number and press Enter. The system asks you to confirm your operation:

The file you selected is cfa0:/[Link],Delete it? [Y/N] 3.

Enter Y for confirmation. The following message appears, indicating the file was successfully deleted.
Deleting..........Done!

Using the CLI

Execute the delete [ /unreserved ] file-url command in user view to delete a file, where:

1.

/unreserved: Permanently deletes the specified file, and the deleted file can never be restored. file-url: Name of the file to be deleted. Delete file [Link] in the root directory:
<H3C> delete [Link] Delete cfa0:/[Link]?[Y/N]:y %Delete file cfa0:/[Link]...Done.

At this time, file [Link] is removed to the recycle bin. If you want to restore the file, you can use the undelete command.
2.

Restore file [Link] from the recycle bin.

31

<H3C> undelete [Link] Undelete cfa0:/[Link]? [Y/N]:y % Undeleted file cfa0:/[Link].

Dealing with password loss

This section describes what to do when a password is lost.

User Password Loss

Your login is refused if you have forgotten the user password. In this case, set a new user password:
1.

Enter the BootWare main menu, and enter 6 to bypass the current configuration in system startup. The system prompts the following information, which indicates that your setting succeeds.
Flag Set Success.

2.

When the BootWare main menu appears again, enter 0 to reboot the system.
System starts booting ...

3.

Set a new password in system view.

[H3C]user-interface console 0 [H3C-ui-console0]authentication-mode password [H3C-ui-console0]set authentication password simple 123456

The above output information indicates that password authentication is used for console port login, the password is set to 123456 in plain text.
4.

Save the new password.

[H3C] save

After reboot, the system runs with the default configuration, while the original configuration file is kept on the CF card. To restore the original configuration, use the display saved-configuration command to locate the configuration file, and then copy and run it. If the password is stored in plain text, you can use the display current-configuration command to view the password in the current configuration. If you use the set authentication password cipher 123456 command to set your password, the password is stored in cipher text.

32

BootWare password loss

Contact your local dealer if you forget the BootWare password. The technical support staff will help you log in to the access controller and set a new password. To change the BootWare password:
1. 2.

Enter the BootWare main menu. Enter 5 on the BootWare main menu, and follow the prompts. The BootWare password can consist of a maximum of 32 printable characters, such as letters, numerals, and punctuations.
please input old password: Please input new password: Please input new password again: Password Set Successfully.

If you enter a wrong old password or different new passwords in this step, the password modification operation fails and the system exits this operation.

Super password loss

The super password enables you to switch between four super levels. Without a super password, you cannot perform higher privilege operations. Enter 8 from the BootWare main menu to clear the super password. Then, reboot the access controller. You will directly enter system view after the access controller restarts. This setting works only once. When the access controller is restarted for a second time, the super password is restored.

Backing up and restoring the BootWare

Using the BootWare menu
You can back up and restore the BootWare on the BootWare operation submenu. After the BootWare is backed up on a storage device, if the normal BootWare is lost, you can restore it using the backup BootWare to boot the device. Enter 7 on the BootWare main menu to enter the BootWare operation submenu. For details of this submenu, see BootWare operation submenu on page 12. To back up the basic and extended BootWare to the CF card, enter 1 on the BootWare operation submenu and follow the prompts:
Will you backup the Basic BootWare? [Y/N]Y

33

Begin to backup the Basic BootWare...................Done! Will you backup the Extend BootWare? [Y/N]Y Begin to backup the Extend BootWare...................Done!

To restore the backup BootWare from the CF card, enter 2 on the BootWare operation submenu and follow the prompts:
Will you restore the Basic BootWare? [Y/N]Y Begin to restore Normal Basic BootWare...Done! Will you restore the Extend BootWare? [Y/N]Y Begin to restore Normal Extend BootWare....Done!

Using the CLI

You can also use bootrom commands to back up and restore the BootWare.

Backing up the BootWare

Back up the complete BootWare to the Flash:

<H3C>bootrom backup all Now backuping bootrom, please wait... Backup bootrom completed!

Back up the extended BootWare to the Flash:

<H3C>bootrom backup part Now backuping bootrom, please wait... Backup bootrom completed!

Restoring the BootWare

Restore the complete BootWare backed up on the Flash to the system:

<H3C>bootrom restore all This command will restore bootrom file, Continue? [Y/N]:y Now restoring bootrom, please wait... Restore bootrom completed!

Restore the extended BootWare backed up on the Flash card to the system:
<H3C>bootrom restore part This command will restore bootrom file, Continue? [Y/N]:y Now restoring bootrom, please wait... Restore bootrom completed!

34

2 Troubleshooting
Software Loading Failure
If software loading fails, the system runs the old version of the software. The following information appears:
=========================<Enter Ethernet SubMenu>=========================== |Note:the operating device is cfa0 |<1> Download Application Program To SDRAM And Run |<2> Update Main Application File |<3> Update Backup Application File |<4> Update Secure Application File |<5> Modify Ethernet Parameter |<0> Exit To Main Menu |<Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-5): 2 Loading...Failed! | | | | | | | |

============================================================================

In this case, check whether the physical interfaces are properly connected.

If the interfaces are not properly connected, reconnect them correctly and restart the loading process. If the interfaces are properly connected, check the loading process information displayed on the configuration terminal for input errors. In case of any input error, restart the loading process with correct inputs.

Input errors include:

A baud rate other than 9600 bps selected for BootWare loading using XMODEM An improper baud rate setting in HyperTerminal A wrong IP address, file name, or TFTP Server work path specified for software loading using TFTP A wrong IP address, file name, username, or password specified for software loading using FTP

If the cause cannot be located, contact your local agent for help.

Power supply failure

You can check whether the power system of the access controller works normally by observing the PWR LED on the front panel. The PWR LED is solid green when the power system works normally. When the PWR LED is off, check whether:

The power cord of the access controller is properly connected. The voltage of the power input is correct.
35

Configuration system failure

If the access controller is operational upon power-on, the configuration terminal displays the boot information; otherwise, you may see nothing or illegible characters on the configuration terminal.

No display on the terminal

If there is no information display on the configuration terminal after the access controller is powered on, check:

Whether the power LED is solid green. Whether all LEDs are off or blinking. If so, the main control board is abnormal. Whether the console cable is connected to the console port of the main control board.

If the cause cannot be located in the steps above, the possible reasons may be:

The serial interface to which the console cable is connected is not the one specified in the terminal emulation program. Terminal settings are incorrect. The required settings are as follows: 9600 bits per second, 8 data bits, no parity check, 1 stop bit, no flow control, and VT100 for terminal emulation type. The console cable is not in good condition.

Illegible characters on the terminal

If illegible characters are displayed, check whether the connection of the console cable is loose.

36