-
Contents
Introduction
Prerequisites
Requirements
Components
Used
Conventions
Background Information
Configure
Network Diagram
Configure the
WLC for Basic Operation
Configure the Switch for
the WLC
Configure the Switch for the
APs
Verify
Troubleshoot
Commands
Controller Does
Not Defend AP-Manager IP Address
Troubleshoot
a
Lightweight
Access
Point
Not
Joining
a Wireless LAN
Controller
Cisco Support
Community - Featured Conversations
Related Information
Introduction
This document
provides a basic configuration example of a
lightweight
access point (AP) that is
connected to a Cisco Wireless LAN (WLAN)
Controller (WLC) through a Cisco
Catalyst Switch.
Prerequisites
Requirements
Ensure that you
meet these requirements before you attempt this
configuration:
Basic
knowledge of the configuration of lightweight APs
and Cisco
WLCs
?
Basic knowledge of Lightweight AP
Protocol (LWAPP)
?
Knowledge of the configuration of an
external DHCP server and/or
domain name
server (DNS)
?
Basic configuration knowledge of Cisco
switches
?
Components Used
The
information
in
this
document
is
based
on
these
software
and
hardware
versions:
Cisco Aironet 1232AG Series Lightweight
AP
?
Cisco 4402
Series WLC that runs firmware 5.2.178.0
?
Microsoft
Windows Server 2003 Enterprise DHCP server
?
This
configuration
works
with
any
other
Cisco
WLC
and
any
lightweight
AP.
The
information
in
this
document
was
created
from
the
devices
in
a
specific
lab environment.
All of the devices used in this document started
with
a
cleared
(default)
configuration.
If
your
network
is
live,
make
sure
that
you
understand the potential impact of any command.
Conventions
Refer to the
Cisco Technical Tips
Conventions
for more information on
document conventions.
Background Information
In
order
for
the
WLC
to
be
able
to
manage
the
LAP,
the
LAP
should
discover
the
controller
and
register
with
the
WLC.
There
are
different
methods
that
an
LAP
uses
in
order
to
discover
the
WLC.
For
detailed
information
on
the
different methods the
LAPs use to register to the WLCs, refer to
Lightweight AP (LAP) Registration to a
Wireless LAN Controller (WLC)
This document describes the
configuration steps needed to register the
LAP to the WLC and for basic operation
of the LWAPP wireless network.
Configure
In order to
register the LAP to the WLC and for basic
operation of the
LWAPP wireless
network, complete these steps:
1.
Have a DHCP
server present so that the APs can acquire a
network
address.
Note:
Option 43 is used if the APs reside in
a different subnet.
2.
Configure the WLC for basic
operation
.
3.
Configure the switch for the
WLC
.
4.
Configure the switch for the
APs
.
5.
Register the lightweight APs to the
WLCs.
Note:
Use the
Command Lookup Tool
(
registered
customers only)
in order
to obtain more information on
the commands used in this section.
Network Diagram
This
document uses this network setup:
Configure the WLC for Basic Operation
When
the
controller
boots
at
factory
defaults,
the
bootup
script
runs
the
configuration wizard, which prompts the
installer for initial
configuration
settings. This procedure describes how to use the
configuration
wizard
on
the
command-
line
interface
(CLI)
in
order
to
enter
initial configuration
settings.
Note:
Be sure that
you understand how to configure an external DHCP
server and/or DNS.
Complete
these steps in order to configure the WLC for
basic
operation:
1.
Connect
your
computer
to
the
WLC
with
a
DB-9
null
modem
serial
cable.
2.
Open a terminal emulator session with
these settings:
o
9600 baud
8 data bits
o
1 stop bit
o
No parity
o
No hardware
flow control
3.
At the prompt, log in to the CLI.
o
The default
username is
admin
, and the
default password is
admin
.
4.
If necessary,
enter
reset system
in order
to reboot the unit and
start the
wizard.
5.
At the
first wizard prompt, enter a system name. The
system name
can include up to 32
printable ASCII characters.
6.
Enter an
administrator user name and password. The user
name and
password can include up to 24
printable ASCII characters.
7.
Enter
the
service-port
interface
IP
configuration
protocol,
either
none
or
DHCP
.
Enter
none
if
you
do
not
want
to
use
the
service
port
or
if
you
want
to assign a static IP
address to the service port.
8.
If
you
entered
none
in
step
7
and
need
to
enter
a
static
IP
address
for
the service port, enter the service-port interface
IP address
and netmask for the next two
prompts.
If you do not want to use the
service port, enter
0.0.0.0
for the
IP address and netmask.
9.
Enter values
for these options:
o
Management interface IP address
o
Netmask
o
Default router
IP address
o
Optional VLAN identifier
You
can use a valid VLAN identifier or 0 for untagged.
10.
Note:
When the
management interface on the controller is
configured
as
part
of
the
'native
vlan'
on
the
switchport
to
which
it connects, the
controller should
NOT
tag
the frames. Therefore,
you must set the
VLAN to be zero (on the controller).
the Network Interface (Distribution System)
Physical Port
number.
For
the WLC, the possible ports are 1 through 4 for a
front-panel
gigabit Ethernet port.
the IP address of the default DHCP
server that supplies IP
addresses to
clients, the management interface, and the
service-port interface, if you use one.
the LWAPP Transport Mode, either
LAYER2
or
LAYER3
.
Note:
If you configure the WLC 4402 via
Wizard and select AP
transport Mode
LAYER2
, the Wizard does not
ask the details of AP
Manager.
the Virtual Gateway IP Address.
This
address
can
be
any
fictitious,
unassigned
IP
address,
such
as
1.1.1.1, for the Layer 3
Security and Mobility managers to use.
Note:
Usually the Virtual
Gateway IP Address that is used is a
private address.
the Cisco
WLAN Solution Mobility Group/RF Group name.
the WLAN 1 service set identifier
(SSID) or network name.
This identifier
is the default SSID that lightweight APs use in
order to associate to a WLC.
or disallow Static IP Addresses for
clients.
Enter
yes
in
order
to
allow
clients
to
supply
their
own
IP
addresses.
Enter
no
in
order to
require clients
to request an
IP address from
a DHCP
server.
you need to configure a RADIUS
server on the WLC, enter
yes
and
enter this information:
o
RADIUS server
IP address
o
The
communication port
o
The shared secret
If you do
not need to configure a RADIUS server or you want
to
configure the server later, enter
no
.
a country
code for the unit.
Enter
help
in order to see a list
of the supported countries.
and
disable
support
for
IEEE
802.11b,
IEEE
802.11a,
and
IEEE
802.11g.
or disable radio
resource management (RRM) (auto RF).
WLC
4402
—
Configuration Wizard
Welcome to the Cisco Wizard
Configuration
Tool
Use the
'-' character to backup
System Name
[Cisco_43:eb:22]:
c4402
Enter Administrative User Name (24
characters max):
admin
Enter
Administrative Password (24
characters
max):
*****
Service Interface IP Address
Configuration
[none][DHCP]:
none
Enable
Link
Aggregation
(LAG)
[yes][NO]:
No
Management Interface IP
Address:
192.168.60.2
Management Interface Netmask:
255.255.255.0
Management
Interface Default Router:
192.168.60.1
Management Interface VLAN Identifier (0
=
untagged):
60
Management Interface Port Num [1 to 2]:
1
Management
Interface DHCP Server IP
Address:
192.168.60.25
AP
Transport Mode [layer2][LAYER3]:
LAYER3
AP Manager Interface IP Address:
192.168.60.3
AP-
Manager is on Management subnet, using
same values
AP Manager
Interface DHCP Server
(192.168.50.3):
192.168.60.25
Virtual Gateway IP
Address:
1.1.1.1
Mobility/RF Group Name:
RFgroupname
Network Name (SSID):
SSID
Allow Static
IP Addresses [YES][no]:
yes
Configure
a
RADIUS
Server
now?
[YES][no]:
no
Enter
Country
Code
(enter
'help'
for
a
list
of
countries) [US]:
US
Enable 802.11b Network [YES][no]:
yes
Enable
802.11a Network [YES][no]:
yes
Enable
802.11g Network [YES][no]:
yes
Enable Auto-
RF [YES][no]:
yes
Note:
The management
interface on the WLC is the only consistently
pingable
interface
from
outside
of
the
WLC.
So
it
is
an
expected
behavior
if you are not able to ping the AP
manager interface from outside of the
WLC.
Note:
You
must configure the AP manager interface in order
for the APs
to associate with the WLC.
Configure the Switch for the WLC
This example uses a Catalyst 3750
switch that uses only one port. The
example tags the AP-manager and
management interfaces and places these
interfaces on VLAN 60. The switch port
is configured as an IEEE 802.1Q
trunk
and only the appropriate VLANs, which are VLANs 2
through 4 and 60
in
this
case,
are
allowed
on
the
trunk.
The
management
and
AP-manager
VLAN
(VLAN
60)
is
tagged
and
is
not
configured
as
the
native
VLAN
of
the
trunk.
So
when
the
example
configures
those
interfaces
on
the
WLC,
the
interfaces
are assigned a
VLAN identifier.
This is an example
802.1Q switch port configuration:
interface GigabitEthernet1/0/1
description Trunk Port to Cisco WLC
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2-4,60
switchport mode trunk
no shutdown
Note:
When you connect the WLC gigabit port,
make sure it is connected
to the switch
gigabit
port only. If
you
connect the
WLC gigabit Ethernet
to the Switch FastEthernet port then it
will not work.
Notice that this
configuration example configures the neighbor
switch
port in a way that only allows
relevant VLANs on the 802.1Q trunk. All
other
VLANs
are
pruned.
This
type
of
configuration
is
not
necessary,
but
it is a deployment best
practice. When you prune irrelevant VLANs, the
WLC only processes relevant frames,
which optimizes performance.
Configure
the Switch for the APs
This is an
example VLAN interface configuration from the
Catalyst 3750:
interface VLAN5
-
-
-
-
-
-
-
-
-
上一篇:颜色英文代码大全!!
下一篇:食物名称