HP Vm200 User Manual

							Wireless configuration
Viewing wireless information
5-21
Tx single retry frames
The number of MSDUs successfully transmitted after one (and only one) retransmission (on 
the total of all associated fragments). May be due to collisions, noise, or interference. Large 
numbers of single retries can indicate that too many computers are using the wireless 
network or that something is interfering with transmissions.
Tx deferred transmissions
The number of MSDUs for which (one of) the (fragment) transmission attempt(s) was one or 
more times deferred to avoid a collision. Large numbers of deferred transmissions can 
indicate that too many computers are using the wireless network.
QoS low priority tx
Total number of QoS low priority packets that have been sent.
QoS medium priority tx
Total number of QoS medium priority packets that have been sent.
QoS high priority tx
Total number of QoS high priority packets that have been sent.
QoS very high priority tx
Total number of QoS very high priority packets that have been sent.
Rx discards no buffer
The number of received MPDUs that were discarded because of lack of buffer space.
Rx discards WEP excluded
The number of discarded packets, excluding WEP-related errors.
Rx discards WEP ICV error 
The number of received MPDUs that were discarded due to malformed WEP packets.
Rx MSG in bad msg fragments
The number of MPDUs of type Data or Management received successfully, while there was 
another reception going on above the carrier detect threshold but with bad or incomplete 
PLCP Preamble and Header (the message-in-message path #2 in the modem).
Rx MSG in msg fragments
The number of MPDUs of type Data or Management received successfully, while there was 
another good reception going on above the carrier detect threshold (the message-in-message 
path #2 in the modem).
Rx WEP undecryptable
The number of received MPDUs, with the WEP subfield in the Frame Control field set to one, 
that were discarded because they should not have been encrypted or due to the receiving 
station not implementing the privacy option. 
						

							Wireless configuration
Viewing wireless information
5-22
Rx FCS errors
The number of MPDUs, considered to be destined for this station (Address matches), 
received with an FCS error. Note that this does not include data received with an incorrect 
CRC in the PLCP header. These are not considered to be MPDUs.
Clear counters
Click this button to reset all counters to zero. 
Viewing throughput for wireless clients
Select Status > Wireless rates.
This page indicates the volume of traffic sent and received at each data rate for each 
connected user.
Legacy rate traffic: Displays information for clients using 802.11 a/b/g modes. The size 
of the bar indicates the amount of traffic sent at each rate.
High Throughput rate traffic: Displays information for clients using 802.11n modes for 
each supported MCS (modulation coding scheme). The size of the bar indicates the 
amount of traffic sent at each MCS. For the V-M200, supported rates are as follows: 
MCS
Data rate in Mbps 
based on channel width
20 MHz40 MHz
0 6.50 13.50
1 13.00 27.00
2 19.50 40.50
3 26.00 54.00
4 39.00 81.00
5 52.00 108.00 
						

							Wireless configuration
Viewing wireless information
5-23
6 58.50 121.50
7 65.00 135.00
8 13.00 27.00
9 26.00 54.00
10 39.00 81.00
11 52.00 108.00
12 78.00 162.00
13 104.00 216.00
14 117.00 243.00
15 130.00 270.00
MCS
Data rate in Mbps 
based on channel width
20 MHz40 MHz 
						

							Wireless configuration
Viewing wireless information
5-24 
						

							Chapter 6: Configuring network settings and VLANs
6
Configuring network settings and VLANs
Contents
Assigning an IP address to the V-M200 ...................................................................... 6-2
Automatically assigning an IP address (default method)................................. 6-2
Manually assigning an IP address........................................................................ 6-2
Ethernet port link settings .......................................................................................... 6-4
Working with VLANs.................................................................................................... 6-4
VLAN assignment via wireless community ........................................................ 6-5
VLAN assignment via RADIUS............................................................................. 6-5
Bridging traffic between wireless communities with VLANs .......................... 6-6
Discovery protocols ..................................................................................................... 6-7
CDP ......................................................................................................................... 6-7
LLDP........................................................................................................................ 6-7
Bridge spanning tree protocol .................................................................................... 6-9
DNS server configuration.......................................................................................... 6-10 
						

							Configuring network settings and VLANs
Assigning an IP address to the V-M200
6-2
Assigning an IP address to the V-M200
There are several ways to assign an IP address to the Ethernet port on the V-M200.
Automatically assigning an IP address (default 
method)
By default the V-M200 operates as a DHCP client. This means that if the network has a DHCP 
server, the V-M200 will automatically receive a new IP address in place of its default IP 
address (192.168.1.1) upon connecting to the network.
The DHCP server will assign an address from its pool of available addresses. You can find the 
IP address of the V-M200 by looking for its Ethernet base MAC address in the DHCP server 
log. The Ethernet MAC address is printed on the V-M200 label identified as Ethernet Base 
MAC, or listed on the management tool Home page as Ethernet MAC address. 
To have the DHCP server assign a specific IP address to the V-M200, you need to pre-
configure the DHCP to associate the IP address you want to use with the MAC address of the 
Ethernet port on the V-M200. 
Manually assigning an IP address
You can manually assign an IP address to the Ethernet port. This requires that you also define 
the address of the DNS server and default gateway that are in use on your network.
1.Select Network > DNS. The DNS page opens. 
						

							Configuring network settings and VLANs
Assigning an IP address to the V-M200
6-3
2.Select the checkbox next to Override dynamically assigned DNS servers.
3.Define an IP address for at least Server 1. Define values for Server 2 and Server 3 if 
available on your network.
4.Select the checkbox next to DNS cache.
5.Select Save. 
6.Select Network > IP. The IP configuration page opens.
7.Under Assign IP address via, select Static and then select Configure. The Static 
configuration page opens.
8.Configure the following settings:
IP address: Set an address that is on the same subnet as the network to which the 
V-M200 will connect once installed. Respect any DHCP server-mandated static 
address ranges.
Subnet mask: Set the corresponding mask for the IP address.
Default gateway: Set the IP address of the gateway on the network.
9.Select Save. Your connection to the management tool will be lost. 
10.You can now connect the Ethernet port on the V-M200 to your network. 
						

							Configuring network settings and VLANs
Ethernet port link settings
6-4
Ethernet port link settings
If required, you can adjust the link settings by selecting Network > Ethernet.
If you do not use the Auto setting for Speed or Duplex, make sure that the device to which 
the V-M200 is connected has a matching configuration. If there is a speed mismatch, the link 
will not be established. If there is a duplex mismatch, the link may be established but with 
transmission errors and reduced connectivity.
Speed 
Auto: Lets the V-M200 automatically set port speed based on the type of equipment it is 
connected to. 
10: Forces the port to operate at 10 Mbps. 
100: Forces the port to operate at 100 Mbps. 
1000: Forces the port to operate at 1000 Mbps. 
Duplex 
Auto: Lets the V-M200 automatically set duplex mode based on the type of equipment to 
which it is connected.
Full: Forces the port to operate in full duplex mode. 
Half: Forces the port to operate in half duplex mode.
Working with VLANs
The V-M200 provides a robust and flexible VLAN implementation that enables you to group 
wireless clients by functionality, workgroup, or application rather than by their physical 
location. 
VLANs enable you to effectively send traffic from wireless users onto different logical 
segments on the same physical network connected to the Ethernet port. 
VLANs can be assigned globally to all users on a wireless community, or individually on a per-
user basis when using a RADIUS server for authentication. The following sections explain 
how to configure both options.  
						

							Configuring network settings and VLANs
Working with VLANs
6-5
VLAN assignment via wireless community
The easiest way to assign user traffic to a VLAN is to configure the Ethernet VLAN setting in 
a wireless community (See Ethernet VLAN on page 4-7). This puts all the traffic from users 
that connect to the wireless community onto the specified VLAN via the V-M200 Ethernet 
port.
In the following scenario, two wireless communities are defined, each with its own VLAN.
The Employee wireless community is configured with VLAN 10. All employee traffic exits 
the V-M200 on VLAN 10, providing access to the company file server, shared printer, and 
the Internet. 
The Guest wireless community is configured with VLAN 20. All guest traffic exits the 
V-M200 on VLAN20, providing access to the shared printer and the Internet. 
NoteIf two wireless communities are assigned to the same VLAN, wireless users may be able to 
communicate with each other. See Communication between users on different wireless 
communities on page 4-6. 
VLAN assignment via RADIUS
VLANs can also be assigned on a per-user basis by setting VLAN attributes in a user’s RADIUS 
account. To use this option you need to do the following:
Configure a wireless community with Security method set to WPA or 802.1X. If using 
WPA, Key source must be set to RADIUS. For configuration details, see Wireless 
protection on page 4-7.
Configure a RADIUS profile to connect with the RADIUS server. For configuration 
details, see Defining a RADIUS client profile on the V-M200 on page 7-2.
Define RADIUS user accounts with the appropriate VLAN attributes (Tunnel-Medium-
Type, Tunnel-Private-Group-ID, and Tunnel-Type). For configuration details, see 
Configuring user accounts on a RADIUS server on page 7-5.
wireless community
Employee
Employee #1Employee #2
wireless communityGuest
Guest #1
Guest #2
VLAN 10
VLAN 10, 20Company
file server
Shared
printer
DHCP server
VLAN 10, 20
Switch
V-M200
VLAN 10, 20
No VLAN
VLAN = 10
VLAN = 20 
						

							Configuring network settings and VLANs
Working with VLANs
6-6
NoteWhen a VLAN is defined in a user’s RADIUS account it always overrides the Ethernet VLAN 
defined for a wireless community. This enables you to define an Ethernet VLAN setting for a 
community and then override it on a per-user basis as required.
Example
In the following scenario, RADIUS user accounts are configured to assign employees to 
different VLANs depending on the workgroup to which an employee belongs. 
Employee wireless community
R&D employees are assigned to VLAN 10 via attributes in their RADIUS account. 
Accounting employees are assigned to VLAN 15 via attributes in their RADIUS account.
Employees without a VLAN assignment in their RADIUS account get assigned to the 
VLAN that is configured for the wireless community, which in this example is 20. This 
enables these employees to access the shared printer and the Internet. 
Guest wireless community
The Guest community does not use RADIUS. All traffic on the Guest community is 
assigned to VLAN 20, providing access to the shared printer and the Internet. 
Bridging traffic between wireless communities with 
VLANs
When users on two different wireless communities are assigned to the same VLAN, they may 
be able to communicate with each other depending on the setting of the Allow traffic 
between all/no wireless clients option. See Communication between users on different 
wireless communities on page 4-6 for details.
Wireless community
Employee
R&D
Employee
VLAN = 10Accounting
Employee
VLAN = 15
Wireless communityGuest
Guest #1
Guest #2
R&D
file server
VLAN 10
VLAN 15
Accounting
file server
Shared
printer
RADIUS server
DHCP server
VLAN 10, 15, 20
Switch
VLAN 10, 15, 20
No VLAN
VLAN = 20
VLAN = 20VLAN 10, 15, 20
V-M200