Cisco 4402 Configuration Guide - Page 8

The wireless controller WLC

Get Cisco 4402 - Wireless LAN Controller PDF manuals and user guides
UPC - 882658039997
View all Cisco 4402 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 8 highlights

Figure 1 provides a summary. Each network cloud represents an IP subnet with the exception of the eduroam hierarchy which for the sake of simplicity is given its own network cloud. The arrows between the clouds indicate the necessary traffic pattern and form the basis for deciding which ports must be opened in package filters (if the units are located in different subnets). One must select a configuration in which, for example, the operating network and services are in the same subnet. In any event it is recommended that the access points be located in a dedicated subnet, since these network points are exposed in open premises and risk being tapped. The controller(s) (WLC(s)) should also be separated from the service or server network, but may for example be located in a general management network for switches. Figure 1: Proposed subnets and necessary traffic pattern 1.3 The wireless controller (WLC) The 5500 controller has one administrative IP address (Management), while the 4400 controller requires two administrative IP addresses (Management and AP Manager). A WiSM module consists of two 4400 controllers and consequently requires four administrative IP addresses. The Management IP address is the one which is used for general administration of the controller and is the contact address to and from other systems such as WCS and RADIUS server. The Management address is also used for communication with the access points, but here the 4400 controller also has the AP Manager address which is used in communication with the access points after the initial contact has been 8

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
8
Figure 1 provides a summary. Each network cloud represents an IP subnet with the exception of the
eduroam hierarchy which for the sake of simplicity is given its own network cloud. The arrows between
the clouds indicate the necessary traffic pattern and form the basis for deciding which ports must be
opened in package filters (if the units are located in different subnets). One must select a configuration
in which, for example, the operating network and services are in the same subnet. In any event it is
recommended that the access points be located in a dedicated subnet, since these network points are
exposed in open premises and risk being tapped. The controller(s) (WLC(s)) should also be separated
from the service or server network, but may for example be located in a general management network
for switches.
Figure 1: Proposed subnets and necessary traffic pattern
1.3
The wireless controller (WLC)
The 5500 controller has one administrative IP address (Management), while the 4400 controller
requires two administrative IP addresses (Management and AP Manager). A WiSM module consists of
two 4400 controllers and consequently requires four administrative IP addresses. The Management IP
address is the one which is used for general administration of the controller and is the contact address
to and from other systems such as WCS and RADIUS server. The Management address is also used
for communication with the access points, but here the 4400 controller also has the AP Manager
address which is used in communication with the access points after the initial contact has been