User's Manual

Configuring the HiPath Wireless Controller
hwc_startup.fm
Performing the first time setup of the HiPath Wireless Controller
A31003-W1050-U100-2-7619
, March 2008
52 HiPath Wireless Controller, Access Points and Convergence Software V5 R1 , C20/C2400 User Guide
To confirm that ports are set for OSPF:
1. To confirm that the ports are set up for OSPF, and that advertised routes from
the upstream router are recognized, click View Forwarding Table. The
Forwarding Table is displayed.
The following additional reports display OSPF information when the protocol
is in operation:
OSPF Neighbor – Displays the current neighbors for OSPF (routers that
have interfaces to a common network)
OSPF Linkstate – Displays the Link State Advertisements (LSAs)
received by the currently running OSPF process. The LSAs describe the
local state of a router or network, including the state of the router’s
interfaces and adjacencies.
2. To update the display, click Refresh.
3.2.7 Filtering at the interface level
The HiPath Wireless solution has a number of built-in filters that protect the
system from unauthorized traffic. These filters are specific only to the HiPath
Wireless Controller. These filters are applied at the network interface level and
are automatically invoked. By default, these filters provide stringent-level rules to
allow only access to the system's externally visible services. In addition to these
built-in filters, the administrator can define specific exception filters at the
interface-level to customize network access. These filters do not depend on a
VNS definition.
3.2.8 Built-in port-based exception filters
On the HiPath Wireless Controller, various port-based exception filters are built
in and invoked automatically. These filters protect the HiPath Wireless Controller
from unauthorized access to system management functions and services via the
ports. Access to system management functions is granted if the administrator
selects the allow management option.
Allow management traffic is now specific to the interface being allowed. For
example, if allow management is allowed on a physical port (esa0), only users
connected through ESA0 will be able to get access to the system. Users
connecting on any other interface such as a VNS (esa6) will no longer be able to
target ESA0 to gain management access to the system. In order to allow access