Cisco Cisco 2504 Wireless Controller 문제 해결 가이드
Controller
These tools and information are needed before you can install the controller:
Wireless Controller hardware:Controller with factory-supplied power cord and mounting
hardwareNetwork, operating system service network, and AP cables as required for the CLI
consoleVT-100 terminal emulator on the CLI console (PC, laptop, or palmtop)Null modem
serial cable to connect the CLI console and controller
hardwareNetwork, operating system service network, and AP cables as required for the CLI
consoleVT-100 terminal emulator on the CLI console (PC, laptop, or palmtop)Null modem
serial cable to connect the CLI console and controller
●
Local TFTP server (required in order to download the operating system software updates).
Cisco uses an integral TFTP server. This means that third-party TFTP servers cannot run on
the same workstation as the Cisco WCS because Cisco WCS and third-party TFTP servers
use the same communication port.
Cisco uses an integral TFTP server. This means that third-party TFTP servers cannot run on
the same workstation as the Cisco WCS because Cisco WCS and third-party TFTP servers
use the same communication port.
●
If the controller is brought up for the first time with no prior configuration, it automatically enters
into a wizard which asks you a series of configuration information. The wizard first will first prompt
for user ID and password. This wizard cannot be bypassed and you must enter all the information
it asks.
into a wizard which asks you a series of configuration information. The wizard first will first prompt
for user ID and password. This wizard cannot be bypassed and you must enter all the information
it asks.
Caution: Do not connect a PoE cable to the console port. This action damages the
controller.
controller.
Controller Configuration through the CLI
Before you can configure the controller for basic operations, you need to connect it to a PC that
uses a VT-100 terminal emulator (such as HyperTerminal, ProComm, Minicom, or Tip). Complete
these steps in order to connect the PC to the controller's console port:
uses a VT-100 terminal emulator (such as HyperTerminal, ProComm, Minicom, or Tip). Complete
these steps in order to connect the PC to the controller's console port:
Plug the RJ-45 connector on a null-modem serial cable into the controller's console port and
the other end of the cable into the PC's serial port.
the other end of the cable into the PC's serial port.
1.
Start the PC's terminal emulation program.
2.
Configure the terminal emulation program for these parameters:9600 baud8 data bitsNo flow
control1 stop bitNo parity
control1 stop bitNo parity
3.
The Cisco 2500 Series Wireless Controller has 4 Gigabit Ethernet ports. Each port is, by default,
an 802.1Q VLAN trunk port. The VLAN trunking characteristics of the port are not configurable.
an 802.1Q VLAN trunk port. The VLAN trunking characteristics of the port are not configurable.
An interface is a logical entity on the controller. An interface has multiple parameters associated
with it; which iinclude the IP address, default-gateway (for the IP subnet), primary physical port,
secondary physical port, VLAN tag, and DHCP server. Since LAG is not used, each interface is
mapped to at least one primary physical port and an optional secondary port. Multiple interfaces
can be mapped to a single Wireless Controller port.
with it; which iinclude the IP address, default-gateway (for the IP subnet), primary physical port,
secondary physical port, VLAN tag, and DHCP server. Since LAG is not used, each interface is
mapped to at least one primary physical port and an optional secondary port. Multiple interfaces
can be mapped to a single Wireless Controller port.
There are multiple types of interfaces on the Wireless Controller, four of which are static types that
must be present and are configured at setup time:
must be present and are configured at setup time:
Management interface (static and configured at setup time; mandatory)
●
AP-manager interface - Not required for the Cisco 2500 Series Wireless Controller
●
Virtual interface (static and configured at setup time; mandatory)
●
Dynamic interface (user-defined)
●