Reference Manual

Discover and Manage Access Points
154
ProSAFE Wireless Controller WC9500
How you must configure DHCP option 43 depends on the type of external DHCP server:
- Layer 3 switch as a DHCP server. If you use a Layer 3 switch as a DHCP server,
specify the wireless controller’
s IP address in hexadecimal format to allow the access
points to receive the wireless controller’s IP address and to allow the DHCP server to
assign IP addresses to the access points. The vendor-specific octets 02:04: must
precede the hexadecimal address.
To compose the address, start with 02:04: and then add each of the four address
octets in hexadecimal format, separated by colons. For example:
192.168.33.27 in decimal format equals c0:a8:21:1b in hexadecimal format. After
you add the vendor-specific octets, the complete address is 02:04:c0:a8:21:1b.
- Linux-based or W
indows-based DHCP server. If you use a Linux-based or
Windows-based DHCP server
, configure the IP address in decimal format and
NETGEAR_WNC_AP as the vendor class identifier.
Discover Access Points with the Discovery Wizard
The Discovery Wizard provides two methods to find access points that are not yet on the
managed access point list. These methods are described in the following sections:
Discover Access Points in Factory Default State and Access Points in a Layer 2 Subnet
Discover Access Points Installed and Working in Standalone Mode in Different Layer 3
Networks
CAUTION:
If security is not set up, or is set up incorrectly, when the wireless controller
pushes the configurations to the access points, you could accidentally
wipe out all security, leaving your entire network open to access. Be sure
that you set up security correctly (see Chapter 6, Manage Security Profiles
and Profile Groups).
Discover Access Points in Factory Default State and Access
Points in a Layer 2 Subnet
Access points in the factory default state are access points “out of the box” that were never
employed. Access points in a Layer 2 subnet are access points that are installed and
functioning in the same IP subnet as the wireless controller and that are connected to the
wireless controller through a back-end Layer 2 switch.