Netgear WC7520 - ProSafe 20-AP Wireless Controller 参照マニュアル
System Planning and Deployment Scenarios
28
ProSafe 20-AP Wireless Controller WC7520
After the survey is complete, use the collected data to set up an RF plan. For more
information, see
information, see
Before You Configure a Wireless Controller
These sections assume that you have deployed at least one wireless controller in your
network and are ready to configure the wireless controller. For information about how to
deploy the wireless controller in your network, see the WC7520 ProSafe Wireless Controller
Installation Guide that you can access from
network and are ready to configure the wireless controller. For information about how to
deploy the wireless controller in your network, see the WC7520 ProSafe Wireless Controller
Installation Guide that you can access from
.
For many configurations, you can use the default wireless settings. The IP address, VLAN,
DHCP server, client authentication, and data encryption settings are specific to your
environment. Following are short sections that discuss these settings (with the exception of
IP address settings, which are self-explanatory). For information about how to configure
these settings, see the relevant sections.
DHCP server, client authentication, and data encryption settings are specific to your
environment. Following are short sections that discuss these settings (with the exception of
IP address settings, which are self-explanatory). For information about how to configure
these settings, see the relevant sections.
VLANs
The management VLAN is the dedicated VLAN for access to the wireless controller. All traffic
that is directed to the wireless controller, including HTTP, HTTPS, SNMP, and SSH traffic, is
carried over the management VLAN.
that is directed to the wireless controller, including HTTP, HTTPS, SNMP, and SSH traffic, is
carried over the management VLAN.
If the management VLAN is also configured as a tagged VLAN (the most common
configuration), the packets to and from the wireless controller carry the 802.1Q VLAN header
with the assigned VLAN number. If the management VLAN is marked as untagged, the
packets that are sent from the wireless controller do not carry the 802.1Q header, and all
untagged packets that are sent to the wireless controller are treated as management VLAN
traffic.
configuration), the packets to and from the wireless controller carry the 802.1Q VLAN header
with the assigned VLAN number. If the management VLAN is marked as untagged, the
packets that are sent from the wireless controller do not carry the 802.1Q header, and all
untagged packets that are sent to the wireless controller are treated as management VLAN
traffic.
Note:
Use a tagged VLAN or change the tagged VLAN ID only if the hubs
and switches on your LAN support 802.1Q. If they do not, and you
have not specifically configured a tagged VLAN with the same VLAN
ID on the hubs and switches in your network, IP connectivity might
be lost.
have not specifically configured a tagged VLAN with the same VLAN
ID on the hubs and switches in your network, IP connectivity might
be lost.
The wireless controller needs to have IP connectivity with the access points through the
management VLAN. If the wireless controller and the access points are on different
management VLANs, external VLAN routing needs to allow IP connectivity between the
wireless controller and the access points.
management VLAN. If the wireless controller and the access points are on different
management VLANs, external VLAN routing needs to allow IP connectivity between the
wireless controller and the access points.
For information about how to configure management VLANs, see