User's Guide

Table Of Contents
Configuring a VNS
hwc_vnsconfiguration.fm
Configuring a Topology
9034530-02, March 2010
298 HiPath Wireless Controller, Access Points and Convergence Software V7.11, User Guide
Bridge Traffic Locally at HWC – Requires Layer 2 configuration. May
optionally have Layer 3 configuration. Layer 3 configuration would be
necessary if services (such as DHCP, captive portal, etc.) are required
over the configured network segment, or if controller management
operations are intended to be done through the configured interface.
5. Configure the Layer 2 parameters, depending on the previously selected
Mode.
For Bridge Traffic Locally at HWC, enter a VLAN identifier that is valid
for your system and enter the port to which this VLAN is attached to,
according to the networking deployment model pre-established during
planning.
For Bridge Traffic Locally at AP, enter a VLAN identifier that is valid for
your system, and specify whether the VLAN configuration is Tagged or
Untagged.
6. Click Save to save your changes.
These steps are sufficient to create and save a topology. The following
configuration options are optional and depend on the mode of the topology.
6.8.1.1 Physical Port Topologies
Starting with V7.0, "Physical Ports" refers to the data plane physical ports. The
attributes of a physical port are:
Administrative status (read-write)
Name (read-only)
MAC address (read-only)
MTU size
Multicast Support for Routed VNS
Physical port topologies are pre-defined by the HiPath Wireless Controller and
cannot be removed from the HiPath Wireless Controller configuration. By default,
all physical ports are set with multicast support for Routed VNS disabled. At most,
one non-management plane port can be enabled for the multicast support for
Routed VNS. This can be configured on the new physical port GUI.
6.8.1.2 Enabling management traffic
If management traffic is enabled for a VNS, it overrides the built-in exception
filters that prohibit traffic on the HiPath Wireless Controller data interfaces. For
more information, see Section 6.10, “Configuring Policy”, on page 350.