Virtual Network Services
A31003-W1040-U101-1-7619, July 2006 DRAFT
108
HiPath Wireless Controller, Access Points and Convergence Software V4.0, C10/C100/C1000 User Guide
hwc_vnsintro.fm
Setting up a VNS checklist
These IP addresses are not virtual IP addresses. They are regular IP addresses and are
unique over the network. These IP addresses are advertised to other hosts on the network
to exchange traffic with the wireless devices in the VNS.
●
A single overall filtering policy applies to all the wireless devices within the VNS. Additional
filtering can be applied when the wireless user is authenticated by the Remote
Authentication Dial-In User Service (RADIUS) server. This does not apply for a bridged
VNS.
●
When the HiPath Wireless Controller creates a VNS, it also creates a virtual IP subnet for
that VNS. This does not apply for a bridged VNS.
●
Each VNS represents a mobility group that, when configured, can be carried across
multiple HiPath Wireless Controllers. This does not apply for a bridged VNS.
●
Each VNS also offers unique Authentication, Authorization and Accounting (AAA) services.
This does not apply for a bridged VNS.
6.2
Setting up a VNS checklist
VNS provides a versatile means of mapping wireless networks to the topology of an existing
wired network. When you set up a VNS on the HiPath Wireless Controller, you are defining a
subnet for a group of wireless device users. The VNS definition creates a virtual IP subnet
where the HiPath Wireless Controller acts as a default gateway to wireless devices.
In addition you can determine if the VNS is to apply for traffic bridging at the AP. This type of
VNS requires specification of RF parameters and authentication parameters (if AAA type),
although filtering specifications and topology specifications do not apply.
The HiPath Wireless Controller C2400 provides the option to define a VNS as locally bridged
to a VLAN at the controller. To support that configuration, you must define which VLAN the VNS
should bride to. With this configuration, it is possible that the controller is not involved in the IP
address assignment for user addresses. Instead, the IP addresses for users are assigned
directly by the DHCP infrastructure that services the VLAN.
Before defining a VNS, the following properties must be determined:
●
A user access plan for both individual users and user groups
●
The RADIUS attribute values that support the user access plan
●
The location and identity of the Wireless APs that will be used on the VNS
>
In a VLAN-bridged VNS, the default configuration dictates that the controller is not
the DHCP server for that segment. However, DHCP services can selectively be
enabled, including DHCP Relay, allowing you to use the controller to become the
default DHCP server for the VLAN, if applicable.
