H3C LSWM1WCM10 User Manual
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Document version: 5PW101-20110308
H3C Access Controller Modules
Software Upgrade Guide
Copyright © 2009-2011, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
Notice
H3C,
, Aolynk, , H3Care,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V
, TOP G, , IRF, NetPilot, Neocean, NeoVTL,
2
G, 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 manual are the property of their respective owners
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, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Preface
The H3C Access Controller Modules Software Upgrade Guide describes how to upgrade various types
of access controller modules through the web interface or at the command line interface (CLI).
The Appendix describes how to upgrade the software of access controller modules at the BootWare
menu.
This preface includes:
•
Audience
Conventions
•
Obtaining documentation
•
Technical support
•
Documentation feedback
•
Audience
This documentation is intended for:
• Network planners
• Field technical support and servicing engineers
• Network administrators working with the access controller modules
Conventions
This section describes the conventions used in this guide.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... } *
[ x | y | ... ] *
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n>
The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
Convention Description
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Description
Symbols
Boldface
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
Convention Description
< > Button names are inside angle brackets. For example, click <OK>.
[ ]
/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].
Window names, menu items, data table and field names are inside square brackets. For
example, pop up the [New User] window.
Convention Description
WARNING
CAUTION
IMPORTANT
NOTE
An alert that calls attention to important information that if not understood or followed can
result in personal injury.
An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
An alert that calls attention to essential information.
An alert that contains additional or supplementary information.
TIP
An alert that provides helpful information.
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web at
http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents]—Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions]—Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download]—Provides the documentation released with the
software version.
Technical support
customer_service@h3c.com
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to info@h3c.com.
We appreciate your comments.
Contents
Access controller module overview·····························································································································1
Software upgrade methods ········································································································································· 2
Software upgrade through the web interface············································································································ 3
Setting up a web-based configuration environment ······································································································3
Configuring software upgrade ········································································································································6
Software upgrade at the CLI ······································································································································· 9
Preparations·······································································································································································9
Setting up a configuration environment ·················································································································9
Connecting the console cable······························································································································ 10
Setting terminal parameters·································································································································· 10
Logging in to the access controller module ········································································································ 13
Software upgrade through FTP at the CLI···················································································································· 14
Using the access controller module as the FTP server ······················································································· 14
Using the access controller module as the FTP client························································································· 16
Upgrade through TFTP at the CLI·································································································································· 17
Maintaining application and configuration files at the CLI·····················································································19
Displaying all files at the CLI································································································································ 19
Setting the application file type at the CLI ·········································································································· 19
Deleting a File at the CLI ······································································································································19
Backing up and restoring the BootWare at the CLI·································································································20
Backing up the BootWare ···································································································································· 20
Restoring the BootWare········································································································································ 20
Appendix Introduction to software maintenance·····································································································21
BootWare program file ········································································································································ 21
Application files····················································································································································· 21
Configuration files ················································································································································· 22
Appendix Upgrading software through the BootWare menu·················································································23
Preparations···································································································································································· 23
Introduction to the BootWare menu ····························································································································· 23
Main menu ····························································································································································· 23
Serial submenu ······················································································································································ 24
Ethernet submenu ··················································································································································25
File control submenu ············································································································································· 25
BootWare operation submenu····························································································································· 25
Storage device operation submenu····················································································································· 26
Upgrading BootWare through the management Ethernet port ················································································· 26
Upgrading an application program through TFTP in BootWare menu···································································· 28
Upgrading an application program through FTP in BootWare menu······································································ 30
Upgrading BootWare and applications through a serial port·················································································· 32
XMODEM overview ·············································································································································· 32
Modifying serial port parameters ························································································································ 32
Upgrading the BootWare program····················································································································· 34
Upgrading applications········································································································································ 37
Appendix Maintaining application and configuration files at the BootWare menu·············································38
Displaying all files at the BootWare menu·················································································································· 38
i
Setting the application file type at the BootWare menu ···························································································· 38
Deleting a file at the BootWare menu ························································································································· 39
Appendix Dealing with password loss·····················································································································40
User password loss ························································································································································ 40
BootWare password loss ·············································································································································· 40
Super password loss······················································································································································ 41
Appendix Backing up and restoring BootWare······································································································42
Index ···········································································································································································43
ii
Access controller module overview
Access controller modules are access controller products independently developed by Hangzhou H3C
Technologies Co., Ltd (hereinafter referred to as H3C). H3C access controller modules feature optional
capacities, high reliability, and abundant service types. Adapted to various H3C network products, such
as Fit APs, the access controller modules can be used in most wireless applications. Targeting the wireless
local area network (WLAN) access of enterprise networks and metropolitan area networks (MANs),
H3C access controller modules are ideal access controllers for such application scenarios as WLAN
access of large-sized, medium-sized, and small-sized enterprise campuses, wireless MAN coverage, and
hot spot coverage.
Table 1 Types of access controller modules
Model
LSQM1WCMB0 Yes Yes CF card
LSQM1WCMD0 Yes Yes CF card
LSBM1WCM2A0 Yes Yes CF card
LSRM1WCM2A1 Yes Yes CF card
LSRM1WCM3A1 Yes Yes CF card
LSWM1WCM10 No Yes CF card
LSWM1WCM20 No Yes Flash
Serial port
(Console port)
Management
Ethernet port
Storage
medium
Applicable to…
S7502E/S7503E/S7503ES/S7506E/S7506E-S/S75
06E-V/S7510E Ethernet
switch
S7502E/S7503E/S7503ES/S7506E-V/S7506E/S75
06E-S/S7510E Ethernet
switch
S9512/S9508/S9508V/S
9505 Ethernet switch
S9505E/S9508E/S9508EV/S9512E Ethernet switch
S9505E/S9508E/S9508EV/S9512E Ethernet switch
S5800-60C-PWR/S5820X28C Ethernet switch
S5800-60C-PWR/S5800-3
2F/S5800-56C/S5800-32
C/S5800-32C-PWR/S580
0-56C-PWR Ethernet switch
EWPX1WCMD0 Yes Yes CF card WX6103 access controller
1
Software upgrade methods
You can upgrade the software of the access control modules through the web interface or at the
command line interface (CLI).
NOTE:
• If you boot an access controller module and the prompt Press Ctrl+B to enter extend boot menu...
appears, you can press Ctrl+B to enter the BootWare menu and upgrade the software of the module.
• Only a technical engineer can upgrade the software of the module at the BootWare menu.
• For more information about software upgrade at the BootWare menu, see “
Appendix Upgrading
software through the BootWare menu.”
If multiple application files exist in the storage medium, use the boot-loader file file-url { main | backup }
command to specify a boot file to be used for next boot of the device. In the command,
• file file-url: Name of the boot file, consisting of 1 to 64 characters.
• main: Main application file.
• backup: Backup application file.
The main application file is used to boot the device. The backup application file is used to boot and start
the device when the main application file is unavailable. For detailed configuration, see “
application file type at the CLI.”
CAUTION:
Because access controller modules must work with Fit APs, you need to load Fit AP application
Setting the
files and
licenses to access controller modules. For information about how to load the files, see “Software upgrade
through the web interface” and “
Software upgrade at the CLI.”
2
t
Software upgrade through the web interface
NOTE:
• This chapter takes software upgrade of access controller module LSQM1WCMB0 on an S7500E switch
and LSWM1WCM20 on an S5800 switch as examples. Unless otherwise specified, the software
upgrade procedures of all access controller modules are the same.
• You can log in to an access controller module through the console port of the module or redirect to the
module from a switch. If an access controller module does not have a console port, you can only redirec
to it from a switch.
• The display of web interface varies with device models.
The web-based network management function allows an administrator to conveniently manage and
maintain network devices through the web interface.
Setting up a web-based configuration environment
1. Set up a web-based network management environment as shown in Figure 1.
Set up the web-based configuration environment by using one of the following two network connection
methods:
• Co nnect the E th ern et port of th e switch to the PC wi th an Ethernet cable and ensure that a route from
the PC to the access controller module is active.
• Connect t he ma nage ment Ethe rnet p ort of t he ac cess cont ro ller modu le to the PC an d ens ure a ro ute
from the PC to the access controller module is active.
As these two upgrade methods are similar, this document describes only the first method.
Figure 1 Set up a web-based configuration environment
2. Configure the switch
• Configuration on an S7500E switch with access controller module LSQM1WCMB0
# Configure interface Ten-GigabitEthernet 2/0/1 that connects the switch and LSQM1WCMB0 as a
trunk port and to permit all VLANs. In this example, LSQM1WCMB0 is inserted in slot 2.
[S7500]interface ten-gigabitethernet2/0/1
[S7500-Ten-GigabitEthernet2/0/1]port link-type trunk
[S7500-Ten-GigabitEthernet2/0/1]port trunk permit vlan all
[S7500]quit
3
• Configuration on an S5800 switch with access controller module LSWM1WCM20
# Create Layer 2 aggregate interface Bridge-Aggregation 1.
<S5800>system-view
[S5800]interface Bridge-Aggregation 1
[S5800-Bridge-Aggregation1]quit
# Add interfaces GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2 that connect the switch and
LSWM1WCM20 to Bridge-Aggregation 1.
[S5800]interface GigabitEthernet 1/1/1
[S5800-GigabitEthernet1/1/1]port link-aggregation group 1
[S5800-GigabitEthernet1/1/1]quit
[S5800]interface GigabitEthernet 1/1/2
[S5800-GigabitEthernet1/1/2]port link-aggregation group 1
[S5800-GigabitEthernet1/1/2]quit
# Configure aggregate interface Bridge-Aggregation 1 as a trunk port and to permit all VLANs.
[S5800]interface Bridge-Aggregation 1
[S5800-Bridge-Aggregation1]port link-type trunk
[S5800-Bridge-Aggregation1]port trunk permit vlan all
[S5800]quit
3. Configure the access control module
CAUTION:
Before you redirect to an access controller module from the switch, make sure the AUX port on the access
controller module is in none authentication mode, which is the factory defaults. For how to configure an
AUX port in none authentication mode, see Table 3.
• Configuration for the access controller module LSQM1WCMB0 on an S7500E switch
# Redirect to LSQM1WCMB0 from the switch. In this example, LSQM1WCMB0 is inserted in slot 2.
<S7500>oap connect slot 2
Press CTRL+K to quit.
Connected to OAP!
<H3C>
# Configure interface Ten-GigabitEthernet 1/0/1 that connects LSQM1WCMB0 and the switch as a
trunk port and to permit all VLANs.
<H3C>system-view
[H3C]interface ten-gigabitEthernet 1/0/1
[H3C-Ten-GigabitEthernet1/0/1]port link-type trunk
[H3C-Ten-GigabitEthernet1/0/1]port trunk permit vlan all
[H3C]quit
• Configuration for the access controller module LSWM1WCM20 on an S5800 switch
# Redirect to LSWM1WCM20 from the switch.
<S5800>oap connect slot 1 system SubSlot1
Press CTRL+K to quit.
Connected to SubSlot1!
<H3C>
# Create Layer 2 aggregate interface Bridge-Aggregation 1.
<H3C>system-view
4
g
System View: return to User View with Ctrl+Z.
[H3C]interface Bridge-Aggregation 1
[H3C-Bridge-Aggregation1]quit
# Add interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 that connect the switch and
LSWM1WCM20 to aggregate interface Bridge-Aggregation 1.
[H3C]interface GigabitEthernet 1/0/1
[H3C-GigabitEthernet1/0/1]port link-aggregation group 1
[H3C-GigabitEthernet1/0/1]quit
[H3C]interface GigabitEthernet 1/0/2
[H3C-GigabitEthernet1/0/2]port link-aggregation group 1
[H3C-GigabitEthernet1/0/2]quit
# Configure aggregate interface Bridge-Aggregation 1 as a trunk port and to permit all VLANs.
[H3C]interface Bridge-Aggregation 1
[H3C-Bridge-Aggregation1]port link-type trunk
[H3C-Bridge-Aggregation1]port trunk permit vlan all
[H3C]quit
# Configure the IP address of VLAN-interface 1 of the access controller module as 192.168.0.100/24.
<H3C> system-view
[H3C] interface Vlan-interface 1
[H3C-Vlan-interface1] ip address 192.168.0.100 24
[H3C-Vlan-interface1] quit
# Configure the web username as admin, password as admin, and user level as 3, namely, administrator
level.
[H3C] local-user admin
[H3C-luser-admin] service-type telnet
[H3C-luser-admin] authorization-attribute level 3
[H3C-luser-admin] password simple admin
[H3C-luser-admin] quit
NOTE:
The device carries default web lo
in information when delivered. You can use the default information to
log in to the web interface. The default web login information includes username admin, password
admin, and the IP address 192.168.0.100/24 of VLAN-interface 1 of the access controller module.
4. Configure an IP address, such as 192.168.0.200/24, for the PC so that the PC can communicate
with the access controller module.
5. On the web-based network management terminal (the PC), start the browser. In the address box of
the browser, type http://192.168.0.100 and press Enter (check that a route active between the
PC and access controller module). The browser displays the login authentication page of
web-based network management, as shown in
Figure 2. Enter username admin, password admin
and the verification code, select a language (Chinese or English), and then click Login.
5
Figure 2 Web user login interface
NOTE:
Web-based network management supports the following browsers: Microsoft Internet Explorer 6.0 SP2,
Mozilla Firefox 3.0, Google Chrome 2.0.174.0, and their later versions.
Configuring software upgrade
1. After logging in to the web interface, select Device > File Management from the navigation tree to
view the free space of the disk. If the free space is not big enough, remove useless files, as shown
in
Figure 3.
Figure 3 File management interface
2. Select Device > Device Maintenance from the navigation tree to enter the software upgrade
configuration page, as shown in
Figure 4.
6
Figure 4 Software upgrade interface
3. Click Browse to locate the local upgrade files. After specifying the file type, you can select the
options If a file with the same name already exists, overwrite it without any prompts and Reboot
after the upgrade is finished. Click Apply.
Figure 5 Software upgrade in progress
Table 2 lists the detailed software upgrade configuration items.
Table 2 Detailed software upgrade configuration items
Item Description
File Browses for a local application program which has the extension .bin.
Sets the file name of the application program after it is uploaded to the
Filename
File Type
If a file with the same name already
exists, overwrite it without any
prompt.
device. The file name must have an extension the same as that of the
application program to be uploaded.
Sets the file boot type.
Main: Main boot file for the next boot.
Backup: Backup boot file for the next boot.
Specifies whether to overwrite a file with the same name.
If this option is not selected, when a file with the same name exists on the
device, the File already exists prompt is displayed and the upgrade
cannot begin.
7
Item Description
Reboot after the upgrade is
finished.
CAUTION:
Specifies whether to reboot the device so that the software upgrade takes
effect when the file is uploaded successfully.
Software upgrade may take a while. Do not perform any operations on the web interface when software
is being upgraded. Otherwise, the software upgrade is interrupted.
8
Loading...