User guide

Controller, Access Points and Convergence Software configuration
A31003-W1010-A100-1-7619, July 2005
34 HiPath Wireless Controller, Access Points and Convergence Software V3.0: User Guide
HWC_SoftwareConfig.fm
Setting up the data ports
4. For the highlighted port, select its Function from the drop-down list: Host Port, 3rd Party
AP, Router (defined below).
For OSPF routing on a port, that port must be configured as a “Router” Port. No more than
one port should be configured as a router port.
5. To allow Management traffic on a highlighted port, click the Mgmt checkbox on. This choice
must be used carefully since it overrides the built-in protection filters on the port.
6. For the highlighted port, click the SLP checkbox on to allow SLP protocol on this port for
Wireless APs using this port for discovery and registration.
7. To save the port configuration, click Save.
To cancel the entries without saving, click Cancel.
Port Type or Function
A new HiPath Wireless Controller is shipped from the factory with all its data ports set up as
“Host ports’, and support of management traffic disabled on all data ports. In the HiPath
Wireless Controller Configuration – IP Addresses screen, you can redefine the data ports to
function as one of three types:
Host Port
Use ”Host Port” for connecting Wireless APs, with no dynamic routing. A “Host Port” has
dynamic routing disabled to ensure that the port does not participate in dynamic routing
operations, such as OSPF, to advertise the availability of Virtual Network Segments (VNS)
hosted by the HiPath Wireless Controller. “Host Ports” may still be used as the target for
static route definitions.
Third-Party AP Port
Define as “3rd-Party AP” a port to which you will connect third-party access points. No
more than one port can be configured for third-party APs.
Selecting this option prepares the port to support a third-party AP setup that allows the
mapping of a VNS to the physical port. The VNS settings then permit the definition of policy,
such as filters and Captive Portal, that manage the traffic flow for wireless users connected
to these access points.
The third-party access points must be operating as layer-2 bridges. The “third-party AP”
VNS is isolated from the rest of the network. The HiPath Wireless Controller assumes
control over the layer-3 functions such as DHCP.
>
In a “Branch Office” scenario, where the Wireless AP is configured statically on
a local network whose MTU is lower than 1500, the HiPath Wireless Controller
automatically adjusts the MTU size to prevent packet fragmentation.