Warnings call attention to a procedure or practice that could result in
personal injury if not correctly performed. Do not proceed until you fully
understand and meet the required conditions.
Cautions call attention to an operation procedure or practice that could
damage the product, or degrade performance if not correctly performed.
Do not proceed until understanding and meeting these required
conditions.
Notes provide information that can be helpful in understanding the
operation of the product.
___________________________________________________________________________ 2
User’s Guide, WhereLAN III draft D1675 rev F
This document describes the basic configuration and recommendations on
physical installation of the WhereLAN III product, which is part of the
Location Sensor product line. The site design and placement is detailed in the
Location Sensor Placement Guide D0406 and WhereLAN III Instruction
Sheet (26913), provide with each unit.
2 PRODUCT DESCRIPTION AND FEATURES
The WhereLAN III is the next generation of WhereLAN product that receives
the signals transmitted by WhereTags (ISO 24730-2), and provides data to the
Location Algorithm processor. The received tag blinks are decoded, time
stamped, and routed to a Windows Server or ZLA (Zebra Location Appliance)
for additional processing. The locate algorithm running on the Windows
Server or ZLA calculates the tag position based on the time stamps of multiple
Location Sensors, and reports that position to the database where it is
displayed by Resource Manager.
The WhereLAN III Location Sensor supports the same Real Time Locating
System (RTLS) functions as the previous sensor, known as the WhereLAN
Location Sensor (LOS). WhereLAN III is fully backwards compatible and
may be used, as outlined herein, as a drop-in replacement for any existing
LOS. However, the WhereLAN III incorporates modern and patent-pending
techniques that result in superior accuracy performance over the current LOS
product. In addition, WhereLAN III supports a number of other value-added
features, as follows:
Time Synchronization: Like the LOS, WhereLAN III supports wireless and
wired time synchronization. However, the product can operate in two distinct
time synchronization modes, known as “Legacy” and “Time Synch II” As
shipped, the product defaults to Legacy time synchronization. In Legacy
mode, WhereLAN III is drop-in compatible with LOS and is backwards
compatible with VSS release 3.8. The Legacy Time service relies on various
user-defined entities, such as Line-of-Sight lists and Timing Islands. Time
Synch II no longer exposes these entities to the end user. A site must run
either the Legacy Time service or the Time Synch II service, but not both. In
Time Synch II mode, WhereLAN III furnishes additional data required by a
new Time Synchronization Process, scheduled for release in Q4 2012, which
runs on the Windows Server or ZLA. The Time Synch II service reduces site
design complexity and post-install support. It accomplishes this by being
“self-configuring” and “self-adjusting”; it hides its configuration details from
___________________________________________________________________________ 8
User’s Guide, WhereLAN III draft D1675 rev F
the end user, automatically self configures and automatically adjusts to a wide
range of Radio Frequency environmental changes. The new Time Synch II
service is substantially different from and is not backwards compatible with
the Legacy Time Synch service. In Legacy mode, the embedded wireless time
beacons are transmitted over the right channel whereas both the left and right
channels are used in Time Synch II mode. Time Synch II can operate in an all
WhereLAN IIIs network, an all LOSs network, or a network with mixed
WhereLAN IIIs and LOSs. However, in order for Time Synch II to work with
LOSs, they must operate in “dual-posting” mode.
Wi-Fi: A variant of the LOS, known as a Locating Access Point (LAP),
supports an integral 802.11 b/g/a Access Point. WhereLAN III does not
support an integral Access Point. Instead, a variant of WhereLAN III supports
establishing an 802.11 b/g Wi-Fi client side connection to any industrystandard Access Point. Unlike WhereLAN III, the LOS does not support
establishing Wi-Fi client side connections.
Network Auto-Configuration (DHCP) and IPv6: The WhereLAN III, with the
release of VSS 4.0.5.2 support both DHCP IP and IPv6 address assignment.
However, the methods used by system software to establish connectivity with
the sensors on start-up preclude the full use of (dynamic) DHCP IP addresses.
This restriction is being eliminated, in the VSS 4.0.5.2 release, for WhereLAN
III sensors by a new process, referred to as Network AutoConfig. This
process conveys the IP address of the RTLS server to the WhereLAN IIIs as
part of the standard DHCP IP address assignment message exchange. In turn,
the WhereLAN IIIs “check-in” with the RTLS server by passing it the MAC
address of their Ethernet port. The RTLS server uses the MAC address to
“authenticate” the identity of the WhereLAN IIIs by checking for the MAC
addresses to be present in the site configuration file.
IEEE 802.3af Power of Ethernet (PoE): WhereLAN III supports industrystandard PoE. This allows for easier installation as it removes the need to run
DC power cabling to the unit. PoE may be supplied by any standardscompliant network switch. Alternatively, Zebra offers a single-line PoE
injector.
Power Consumption: WhereLAN III consumes just 12 watts, a 31% and 57%
reduction relative to the LOS and LAP, respectively.
___________________________________________________________________________ 9
User’s Guide, WhereLAN III draft D1675 rev F
The WhereLAN III product line contains the following product skews:
LOS-5000-00AA: This is a “base” WhereLAN III unit, with an integral
802.3af compliant Ethernet interface, supporting wireless and wired timing
options.
LOS-5000-00AB: This version adds 802.11 b/g Wi-Fi support, in client
mode, to the base unit. This part number is approved for sale to U.S. Federal
Government procurements.
LOS-5000-00CA: This is a “base” WhereLAN III unit approved for sale to
U.S. Federal Government procurements.
LOS-5000-01AA: This is a “base” WhereLAN III unit incapable of
transmitting a wireless time beacon and is approved for sale to U.S. Federal
Government procurements.
___________________________________________________________________________ 10
User’s Guide, WhereLAN III draft D1675 rev F
Antenna (2): MCX (Jack)
DC Power: 2.5 ID/ 5.5 OD mm (Jack)
Opt. Wi-Fi Antenna: SMB (Jack)
Ethernet: RJ45 (Jack) 10/100 and 802.3af POE
Timing (3): RJ-22 (4 wire telephone handset, Jack)
With the exception of the LOS-5000-00AB model (Wi-Fi backhaul), the
WhereLAN III must be wired to a nearby 10/100BaseT Ethernet switch or
hub. In addition, the network to which the switch or hub connects must allow
full access to a number of standard communication protocols and port ranges
(TCP/IP, UDP, ftp, etc). See the Zebra VSS Software Installation Guide for
further detail on the interconnecting network requirements. The maximum
Ethernet cable run is 328 ft (100 m). If additional distance is required, hubs,
repeaters, and fiber (with 10baseT converters) can be used to extend the
distance. Refer to IEEE guidelines for Ethernet cabling. The LOS-500000AB must be configured to connect to an IEEE 802.11 b/g Wi-Fi network, as
outlined in this document.
___________________________________________________________________________ 12
User’s Guide, WhereLAN III draft D1675 rev F
Upon power up, WhereLAN III executes a self-boot process. The boot
process takes between 45 to 60 seconds. If a fault occurs during the boot
process, the unit may reset and restart the boot process. During that process,
the four LEDs blink in a sequence to indicate the current stage of the power
up boot process. The LED Process is as follows after initial power is applied.
• 1 LED (Power): The Boot Loader is loading the Kernel.
• 4 LED’s : The Kernel is initialized and is loading the applications,
JFFS2 and CRAM File system
• 1 LED (Power): The Application is loading the FPGA’s and DSP’s
• 2 LED’s (Power and Tag Reception): The unit is initializing the
FPGA’s and DSP’s.
• 1 LED (Power): Unit is booted and ready for operations.
Location Sensor
ower/
ealth
Tag
Reception
Ethernet
WLAN
Outdoor
Omni
Antenna
Figure 1 LOS-5000 LED's
___________________________________________________________________________ 14
User’s Guide, WhereLAN III draft D1675 rev F
Once the boot process is complete, the LEDs revert to their standard
functions indicating power/health, tag status, Ethernet, and Wi-Fi.
Power
Ethernet
Tag Reception
WLAN
•Power/Health LED: Indicates unit has power and general health of
unit.
o State 1 Steady ON: When the Power LED is steady on, the
unit is healthy and sitedata has been received and is correct.
o State 2 80% Duty Cycle: The Power LED is ON for close to
80% of the time and OFF for a brief period. This indicates
either sitedata has not been received or that there is a
problem with site data.
o State 3 50% Duty Cycle: The Power LED blinks ON for 1
Second and OFF for 1 Second. This indicates a health check
has failed and possible hardware problem. For example, the
unit is either not blinking its embedded tag or is not receiving
its embedded tag.
• Tag Reception LED: Blinks when WhereTag signals are received.
• Ethernet LED:Is on solid when has connection to an Ethernet
network.
• WLAN LED:Is on solid when Wi-Fi connection is established.
See Appendix F
: For Complete Boot Sequence details.
___________________________________________________________________________ 15
User’s Guide, WhereLAN III draft D1675 rev F
After the WhereLAN III has completed its boot process, it is possible to
communicate with the unit via the following methods.
____________
Note
____________
Do not attempt to communicate with the WhereLAN III it has completed
the first stage of the boot process (i.e., left LED is solid). Doing so will
stop the boot process. The unit must be reset to clear this condition.
These units are configured using:
• SSH (Secure Shell 2) via Ethernet (preferred)
____________
Note
____________
• WhereWand
• Hyperterminal (or any terminal emulation software) via serial port
SSH is the preferred method of communicating with the WhereLAN III.
Use the HyperTerminal is for initial set-up before being installed on a
network for setting static IP addresses, if DHCP is not used. In addition
to SSH, WhereLAN III also supports Telnet, but this protocol is disabled
by default. To use Telnet, you must first enable it via accessing the
WhereLAN III configuration menu via SSH or a serial port connection.
However, enabling Telnet is not recommended as it sends user name and
passwords across the network in the clear.
The Ethernet Communication Parameters are:
• 10/100 Mb/s
• CAT 5 cable/ RJ-45 plug
___________________________________________________________________________ 16
User’s Guide, WhereLAN III draft D1675 rev F
• 8 data bits, 1 stop bit, no parity, no hardware flow control
HyperTerminal may be used to configure the sensor before connecting it to a
network with a DHCP server, or when a rare fault occurs during the first stage
of the boot process, or if visibility to the boot process is needed for debugging
installation problems.
5.2.1 Establishing an SSH Connection
WhereLAN III supports Secure Shell (SSH), SSH2 being preferred over
SSH1. Either the IP address or host name of the unit must be known in order
to establish an SSH session.
An SSH session may be established using a freely available application called
OpenSSH (supplied by your Zebra Professional Services staff or visit
http://openssh.com for further details, but requires the ssh_zebra_rsa_key
available from Professional Services). Alternatively, other applications, such
as PuTTY, may be used as well, but will require the conversion on the
ssh_zebra_rsa_key into the appropriate format.
To establish the SSH session, you must use Zebra-supplied key, called
“ssh_host_rsa_key” and the “blowfish” passphrase.
The following section shows how to use the OpenSSH application.
___________________________________________________________________________ 17
User’s Guide, WhereLAN III draft D1675 rev F
4. WhereLAN III then presents secure access to its Configuration menu.
5.2.2 Enabling Telnet
The WhereLAN-III comes shipped with Telnet Disabled as added network
security. However for certain installation and/or customers Telnet may be
Enabled via the Menu System.
The enabling of Telnet is done via the numbered menu system either through
HyperTerminal or SHH, either will method will provide the same Menu
structure. The following example is shown using a direct connection with a
Null Modem Serial cable and HyperTerminal Session.
• From the Main Menu select the number that corresponds to ‘Ethernet
Settings’. The WhereLAN III application shows the following submenu:
___________________________________________________________________________ 20
User’s Guide, WhereLAN III draft D1675 rev F
Press the ESC key and enter the “ff2” password when prompted. The unit
will update NVRAM, save your changes, and ask if you wish to reset the unit.
After reset, the unit will boot with Telnet support.
Note Telnet User and Password are as follows.
User: root
Password: password
___________________________________________________________________________ 22
User’s Guide, WhereLAN III draft D1675 rev F
WhereLAN IIIs connect to an IP network over an Ethernet or Wi-Fi interface
using TCP/IP, UDP, and other standard network protocols. For the LOS5000-00AB, both the Location Sensor and the embedded Client Card must be
independently configured with its own unique IP addresses or for DHCP
address assignment. The IP address of each LS must be recorded and entered
into the site configuration file, which contains the configuration information
for each LS, including its location, and MAC address. This is for versions of
VSS prior to the 4.0.5.2 release.
5.3.1 Activating IPv6 Transport
The WhereLAN-III device, running appropriate firmware V5.0.1 or later, will
automatically generate a link-local IPv6 address after booting up. However,
in order to acquire a global IPv6 address, which is needed for IPv6
communication with the VSS server, there must be an IPv6 router on the
network having the following configuration:
• Allow local IPv6 traffic with a global.
• IPv6 network prefix (such as, for example, 2001:470:87c4:1000::/64)
NOTE: The global IPv6 network prefix is a globally unique address and
can be used inside or outside of internal networks. You need to apply for
and obtain a global IPv6 network prefix for your network (for example,
see www.tunnelbroker.net
personnel responsible for the network.
If additionally you would like to assign a fixed IPv4 address to a
WhereLAN-III, you can do so via the sensor menu, which can be accessed
via Telnet (if enabled) or SSH client, or direct connect with serial cable.
). This is a task typically performed by IT
___________________________________________________________________________ 23
User’s Guide, WhereLAN III draft D1675 rev F
In order to have IPv6 network traffic (blinks, status information, etc.) between
the WhereLAN-III devices and the VSS server, the following requirements
must be fulfilled:
• The WhereLAN-III device must be able to acquire a global IPv6
address as described above.
• IPv6 must be enabled in the operating system (Windows) on the VSS
server.
• The following steps must be followed in System Builder, which is the
tool that generates the sitedata.dat configuration file parsed by the VSS
services and the WhereLAN-III devices:
• Activate IPv6 in the ‘Change Site Attributes’ dialog window and enter the
global IPv6 network prefix that the IPv6 router on that network is using:
___________________________________________________________________________ 25
User’s Guide, WhereLAN III draft D1675 rev F
The resulting sitedata.dat generated by System Builder will include the following:
o A site define ipv6prefix specifying the global IPv6 network prefix used by
the IPv6 router on that network
o 0 (zero) IP address for all WhereLAN-III units that will communicate using IPv6
An example sitedata.dat is shown in the screenshot below:
NOTE: As usual, you need to restart the VSS services on the VSS server for
changes in sitedata.dat to take effect. Some changes require rebooting the
WhereLAN-III devices as well.
___________________________________________________________________________ 27
User’s Guide, WhereLAN III draft D1675 rev F
Once IPv6 transport between the VSS server and the WhereLAN-III devices
has been activated as described above, you can use the VSS diagnostics and
status tools as usual, but you will notice that the IPv6 address is used for
devices configured with the IPv6 option in System builder, as shown in the
Sensor Analyzer screenshot below:
___________________________________________________________________________ 28
User’s Guide, WhereLAN III draft D1675 rev F
5.3.3 IPv4 DHCP Dynamic IP for WhreLAN-III Devices
It is possible to have a WhereLAN-III device automatically acquire an IPv4
address from a DHCP server. This IP assignment is dynamic and therefore the
assigned IP may change the next time the device is rebooted. To enable the
device to do so, the following steps are required:
o The DHCP option in the sensor menu needs to be turned ON:
o On the DHCP server, add scope option 151 (IP Address type) and point it to the IP
address of the VSS server:
___________________________________________________________________________ 29
User’s Guide, WhereLAN III draft D1675 rev F