Data Collection Guide

Lanamark Explorer
March 2018

Abstract
Infrastructure design can be optimized by leveraging workload metrics from physical and
virtual machines that will depend on the new storage architecture. This guide outlines
the steps for discovering and profiling server workloads across physical and virtual
infrastructure using the Lanamark Explorer data collector, which is an integral part of the
Lanamark One systems engineering automation platform.
Contents
1 Introduction 3
1.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Outbound Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Target Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Data Collection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Data Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Target System Requirements 6

2.1 Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Linux / Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Installation 8
3.1 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3 Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4 Installation Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5 Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.6 Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Credential Management 12
4.1 Global Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2 Individual Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3 Applying Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5 Discovery 16
5.1 Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2 List of Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3 Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4 IP Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6 Monitoring 20
6.1 Starting and Stopping Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.2 Terminating Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7 Settings 22
7.1 Monitoring Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.2 Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.3 Automatic Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.4 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Lanamark Explorer 1 Data Collection Guide

List of Tables
1 OS and Network Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . 3
2 Processor, Memory and Disk Space Requirements . . . . . . . . . . . . . . . . . . . . 3
3 Lanamark Explorer data collection workflow. . . . . . . . . . . . . . . . . . . . . . . . 5
4 Microsoft Windows system requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
5 Linux / Unix system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6 Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7 Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8 Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Lanamark Explorer 2 Data Collection Guide

1 Introduction
Lanamark Explorer is a light-weight, agent-less data collector that discovers and profiles server work-
loads across physical and virtual infrastructure from a single, dedicated Microsoft Windows Server
machine. Daily snapshots of workload metrics are securely transmitted to Lanamark so that Lana-
mark partner Systems Engineers ("Systems Engineers") can perform analysis, reporting, performance
modeling and storage infrastructure design

1.1 System Requirements

Lanamark Explorer should be deployed in a dedicated physical or virtual machine meeting the follow-
ing system requirements:

Table 1: OS and Network Connectivity Requirements

Requirement Description

Operating System Microsoft Windows Server 2008 R2, 2012, 2012 R2 or 2016

Application Components Microsoft .NET Framework 4.0 Client Profile (or higher)

Network Outbound Internet connectivity via port 443 (SSL)

Security The user is responsible for installing patches and updates to the .NET
Framework and the underlying operating system.

Table 2: Processor, Memory and Disk Space Requirements

Requirement vCPUs/Cores Memory (GB) Free Disk Space (GB)

Up to 100 machines 2 2 2

100 - 499 machines 4 4 10

500 - 999 machines 4 8 20

1,000 - 2500 machines 8 16 50

1.2 Outbound Connectivity

Lanamark Explorer uploads data to *.lanamark.one over port 443. Please use nslookup to determine
the IP address.

Lanamark Explorer 3 Data Collection Guide

1.3 Target Platforms
Discovery and server workload profiling are supported for Microsoft Windows Server and Linux oper-
ating systems.

Discovery
Workload discovery can be performed via Active Directory, NetBIOS domain name, IP range or subnet,
Standalone Microsoft Hyper-V and VMware vCenter.

Best Practice: import hostnames / IPs from a .csv file if the target systems are known in advance.

Note: Performance statistics can only be collected from directly-connected or SAN-attached disks and
not from volumes accessed via file protocols such as NFS and CIFS/SMB.

1.4 Data Collection Overview

Lanamark Explorer queries server workloads specified during discovery by the client representative
for two weeks at 5-minute intervals. Data collection may continue for up to 45 days if additional work-
loads need to be profiled. It is highly recommended that all workloads be discovered at the beginning
of the assessment to avoid delaying storage infrastructure solution design.
Inventory and performance data is transmitted to Lanamark daily, allowing the Systems Engineer who
created the client engagement to analyze server workloads, generate a workload assessment reports
and commence performance modeling. The information in this report is then used for designing an
optimal infrastructure solution based on measured workload resource demands. Table 3 illustrates
the data collection workflow.

1.5 Data Collected

Lanamark One data collector captures performance and inventory metrics for applications, services,
processes, workloads, desktops, servers, storage arrays, network devices and other systems. It does
not inspect or collect data stored on the actual endpoints. This is outlined in the End User License
Agreement (EULA) of each Lanamark One data collector.

Lanamark Explorer 4 Data Collection Guide

Table 3: Lanamark Explorer data collection workflow.

Step Description

Download the Lanamark Explorer and install it on a dedicated physi-

1. Install Lanamark Explorer cal or virtual machine meeting system requirements outlined above.

Specify global credentials for target systems using the Credential

2. Specify credentials Manager.

Note: Use Domain Admin credentials for Microsoft Windows

machines and root / sudo account for Linux machines. Discovery via
VMware vCenter requires a read-only account.

If the list of target machines is known, then it can be imported from

3. Discover machines a .csv file via the Individual Machines discovery method. Usernames
and passwords can be omitted unless they are custom.

If the list of target machines is not known, exploratory discov-

ery can be performed via Active Director, Domain Name, IP range /
subnet.

Server workload metrics are automatically and securely transmitted

4. Synchronize snapshots to Lanamark servers on a daily basis for fourteen (14) days. After-
wards, snapshot uploads can be manually forced for up to forty-five
(45) days.

Note: Credentials are encrypted when they are entered into the
collection tool and are never transmitted by the Lanamark Explorer.

A Systems Engineer will analyze profiled server workloads and review

5. Review report the Workload Assessment Report with the client while commencing
storage performance modeling and infrastructure design.

Lanamark Explorer 5 Data Collection Guide

2 Target System Requirements
2.1 Microsoft Windows
The following system requirements must be met on Microsoft Windows target systems to enable in-
ventory and performance data collection:

Table 4: Microsoft Windows system requirements

Area Description

Microsoft Windows Server 2016

Supported Operating
Systems Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012

Microsoft Windows Server 2008 R2 (SP1)

Microsoft Windows Server 2008 (SP1, SP2)

Microsoft Windows Server 2003 R2 (SP1, SP2)

Microsoft Windows Server 2003 (SP1, SP2)

Domain or local administrator account with permissions to access

Permissions WMI and Remote Registry.

Note: As a best practice create a dedicated Domain Admins ac-

count to use exclusively for data collection. Use local administrator
account for machines that are not joined to the domain.

The following OS instrumentation must be enabled:

Configuration
Windows Management Instrumentation (WMI)
File and Print Sharing
Remote Registry

Ports 135, 139 and 445 as well as ports used by WMI must be open.
Network
In Microsoft Windows, firewall rules must be specified to allow
this type of communication.

A network path must exist between target systems and the Lanamark
Explorer assigned to monitor them.

Note: Monitoring the machine hosting the Lanamark Explorer is not supported.

Lanamark Explorer 6 Data Collection Guide

2.2 Linux / Unix
The following system requirements must be met on Linux / Unix target systems to enable inventory
and performance data collection. Lanamark Explorer supports data collection from native and LVM2
volumes. Btrfs (B-tree file system) is not supported.

Table 5: Linux / Unix system requirements

Area Description

CentOS 4 - 7.3
Supported Operating Debian 3.1 - 8.7
Systems Fedora 6 - 25
FreeBSD 6.1 - 10.2
Novell SUSE Linux Enterprise 10 - 12
openSUSE 10.2 - 42.2
Oracle Linux 4.5 - 7.3
Red Hat Enterprise Linux 4 - 7.3
Ubuntu 6.06 - 16.10

Note: During discovery, machines supporting SSH may appear

as target systems running Linux / Unix. Unless these systems are
running a standard release of one of the above operating systems,
Explorer will not be able to inventory them and they should be
excluded from data collection.

Note: Novell SUSE Linux Enterprise 12.x uses Btrfs by default.

Btrfs is not supported.

root or sudo level access

Permissions
Note: Recursive read access to /dev, /etc and /proc folders

Port 22 must be open. SSH2 and SSH1 are supported.

Network
A network path must exist between target systems and the
Lanamark Explorer assigned to monitor them.

Lanamark Explorer 7 Data Collection Guide

3 Installation
After receiving a welcome email containing download link, click on this link to download the Lanamark
Explorer data collector. Lanamark Explorer is automatically associated with the engagement created
by the Systems Engineer and should only be used to collect inventory and performance data from your
IT environment.

3.1 Welcome
The Welcome screen contains your company name and contact details of your account manager or
systems engineer. If the client name does not correspond to your company’s name, the installation
should be aborted.

Lanamark Explorer 8 Data Collection Guide

3.2 End User License Agreement
Please read and accept the End User License Agreement to proceed.

3.3 Connection Settings

If the Lanamark Explorer is unable to establish a connection with Lanamark One, the following screen
will be displayed. Data captured by the data collector will be securely uploaded to Lanamark One via
SSL on a daily basis.

Lanamark Explorer 9 Data Collection Guide

3.4 Installation Path
Lanamark Explorer should be installed on the same drive as the operating system.

3.5 Confirmation
Click Install to complete the Lanamark Explorer installation.

Lanamark Explorer 10 Data Collection Guide

3.6 Launch
Launch the Lanamark Explorer after installation to start discovering server workloads across physical
and virtual infrastructure. If the Lanamark Explorer does not launch right away, click on the desktop
icon or launch it from the Start menu.

Lanamark Explorer 11 Data Collection Guide

4 Credential Management
Lanamark Explorer uses global and individual credentials to collect inventory and performance data
from target systems. Global credentials should be used when they are applicable to multiple machines
and individual credentials should only be applied to target systems with custom credentials. All cre-
dentials are encrypted using AES-256 bit encryption and stored securely by the Lanamark Explorer.

Note: Credentials are never transmitted outside of the IT environment.

4.1 Global Credentials

Global credentials can be managed via the Credential Manager, which is accessible from the top left
corner of the Lanamark Explorer console:

To create new global credentials, select the type of credentials to create and then click new or use the
button in the top left corner of the Credential Manager.

Lanamark Explorer 12 Data Collection Guide

Microsoft Windows Credentials
As a best practice domain credentials for target systems running Microsoft Windows that are joined to
the domain should be used. Domain attribute should be specified for these credentials. Both FQDN
and NetBIOS domain names are supported. If this attribute is left blank the credentials are treated as
local to the target system.

Lanamark Explorer 13 Data Collection Guide

Linux Credentials
For target systems running Linux operating systems, a separate user account should be set up with
sudo rights for data collection commands requiring elevated privileges.
Lanamark Explorer also supports key-based authentication. A private key file can be imported via the
import private key button.

4.2 Individual Credentials

If a target system has individual credentials, they can be specified in the Discover Individual Machines
dialog. If individual credentials were not specified during discovery, they can be applied by select-
ing one or more machines in the Lanamark Explorer and clicking assign in the top right corner of the
machine(s) summary.

Lanamark Explorer 14 Data Collection Guide

4.3 Applying Credentials
If there are no credentials for one or more target systems, Lanamark Explorer will show these target
systems in the Not Inventoried tab with Inventory - No credentials status. To apply credentials, select
the target systems and then click on assign credentials.

Lanamark Explorer 15 Data Collection Guide

5 Discovery
Lanamark Explorer supports target system discovery via:
• Active Directory and Microsoft Windows Domains
• Hostnames or IPs (including CSV file import)
• IP range or subnet

All discovery methods can be accessed by clicking on Discover in the top left corner of the Lanamark
Explorer console.

Lanamark Explorer 16 Data Collection Guide

5.1 Microsoft Windows
For Microsoft Windows environments, it is recommended that Discover Active Directory option be used
for discovering target systems. Legacy Microsoft Windows environments can be discovered via Dis-
cover Domains method.

Active Directory
1. To discover target systems via Active Directory, specify the Active Directory domain, username and
password. Then click Connect to select organizational units (OUs) in scope for discovery.
2. If the specified credentials can be used for target systems in this domain, then select Use this cre-
dential for Windows machines in this domain in the bottom left corner. These credentials will be
automatically added to the Credential Manager.
3. Once applicable OUs are selected in the Active Directory tree on the right side, click Discover in the
bottom right corner of the dialog.

Lanamark Explorer 17 Data Collection Guide

Domains
For legacy Microsoft Windows environments or if access to Active Directory is not available, target sys-
tems can be discovered by specifying one or more domain (NetBIOS) names. Usernames and pass-
words are optional but if specified, they will be automatically stored in the Credential Manager and
applied to Microsoft Windows systems in each respective domain.

5.2 List of Machines

If a list of hostnames or IP addresses is available for target systems, it can be specified via Discover
Individual Machines. Usernames and passwords are optional but should be specified for machines
using individual credentials so that they can be automatically applied.

CSV File Import

A CSV file can be imported via the Discover Individual Machines dialog. The format for this file should
be as follows:
Hostname or IP address, username (optional), passwords (optional)

Lanamark Explorer 18 Data Collection Guide

5.3 Subnet
A subnet containing target systems can be discovered via Discover IP Subnet option. Click Discover in
the bottom right corner after specifying the IP address and the corresponding IP mask:

Note: Subnet discovery is limited to class C subnets (maximum of 254 addresses). Multiple subnet
discoveries can be executed in parallel.

5.4 IP Range
To discover target systems via an IP range, click on the Discover IP Range discovery option and specify
the starting and the ending IP address in the same class C subnet. Then click Discover in the bottom
right corner:

IP range discovery will run as a background task. If any target systems are discovered in the specified
IP range, they will appear under the Not Inventoried tab in the Lanamark Explorer.

Note: IP range discovery is limited to class C subnets (maximum of 254 addresses). Multiple IP range
discoveries can be executed in parallel.

Lanamark Explorer 19 Data Collection Guide

6 Monitoring
Once Lanamark Explorer can use global or individual credentials to access a target system, it will au-
tomatically start collecting inventory and performance metrics.

Each monitored target system will appear under Machine and the applicable Physical Machine or Vir-
tual Machine tab. For example, if there are 10 physical machines and 50 virtual machines, Lanamark
Explorer will show 60 Machines, 10 Physical Machines and 50 Virtual Machines.
Target systems without credentials or that do not meet data collection requirements will appear under
the Not Inventoried tab.

Lanamark Explorer 20 Data Collection Guide

6.1 Starting and Stopping Monitoring
Target systems should be monitored throughout the data collection cycle and it is not recommended
that monitoring be manually stopped. If it is necessary to stop monitoring, select applicable target
systems and click stop in the Monitoring section of the dashboard in the top right corner:

To restart monitoring, select applicable target systems and click start in the Monitoring section of the
dashboard in the top right corner:

6.2 Terminating Data Collection

If the user interface console is not functional and data collection for all target systems needs to be
terminated without uninstalling the Lanamark Explorer, it is possible to do so by stopping the Lana-
mark Explorer Local Service in the Windows Services console. This operation will also disable the user
interface console, which connects to the Local Service.

Note: If the user interface console is not operational, Lanamark Explorer Local Service should be al-
lowed to carry on with data collection.

Lanamark Explorer 21 Data Collection Guide

7 Settings
The machine running the Lanamark Explorer is indicated on the tab to the right of Discover and Cre-
dentials buttons in the top left corner.

Settings Manager is used to view and modify Lanamark Explorer settings. It can be opened by clicking
on the gears icon to the right of the tab indicating the hostname running Lanamark Explorer. Settings
are organized under Information, Connection Settings and Host & Service Statistics tabs:

7.1 Monitoring Frequency

By default, performance metrics are automatically collected from target systems every five minutes
once they are inventoried. It is not advisable that these settings be changed but if it is necessary to
do so, they can be modified in the Settings Manager under the Monitoring section in the Information
tab.

Lanamark Explorer 22 Data Collection Guide

7.2 Data Synchronization
Inventory and performance data is aggregated in snapshots and securely uploaded to Lanamark One
daily so that systems engineers can perform analysis, reporting, performance modeling, converged
and storage infrastructure design.

Automatic Synchronization
Heartbeat and snapshots will be automatically synchronized for two weeks from the first point of data
collection. Lanamark Explorer will stop collecting data 45 days from the first point of data collection.

Upload Schedule
By default, snapshots are uploaded daily starting at 12:00 am plus a random increment of up to 5 hours.
The setting can be modified in the Settings Manager under the Delivery section in the Information
tab. The Systems Engineer will not have access to collected data until the following day, unless data
synchronization is forced.
Example: If snapshot delivery is set to 2:00 am, snapshots may be uploaded between 2:00 and 7:00
am.

Forcing Data Synchronization

It is recommended that Lanamark Explorer uploads snapshots at a configured schedule. If target sys-
tems have been monitored for at least an hour, it is possible to force data synchronization by clicking
upload now. Since uploaded data requires processing, the Systems Engineer may not have access to
new data right away.

Lanamark Explorer 23 Data Collection Guide

7.3 Automatic Updates
Updates to the Lanamark Explorer are made automatically when they become available and the ver-
sion is incremented accordingly.

7.4 Connectivity
Connectivity between Lanamark Explorer and Lanamark One is established during installation. If con-
nection settings are changed during the course of data collection, they can be updated in the Settings
Manager under Proxy Settings in the Connection Settings tab:

Connection settings should be validated before being saved using Validate button in the bottom right
corner of the Connection Settings view.

Lanamark Explorer 24 Data Collection Guide

Appendix A:Data Collected
Lanamark Explorer collects inventory and performance data from target systems. It does not install
agents or copy any files to or from target systems.

Inventory Data
Inventory data is collected and updated for each machine once a day to ensure accuracy of hardware,
software and performance metrics for each target system.

Table 6: Inventory Data

Operating System Inventory Data

Microsoft Windows WMI: Hardware and software information

Remote Registry: Installed software products and hardware infor-

mation

Linux SSH: awk, cat, df, dmidecode, dpkg-query, fdisk, free, grep, hal-find-
by-capability, hal-find-byproperty, hal-get-property, hwinfo, ifconfig,
kudzu, lsb_release, lshw, lspci, rpm, sed

Note: not all commands are applicable to all Linux distributions

Performance Data
Workload performance metrics are collected from target systems at the specified monitoring interval,
which is five (5) minutes by default.

Table 7: Performance Data

Operating System Inventory Data

Microsoft Windows Perfmon: CPU, memory, disk IO, network IO, etcâĂę

Linux SSH: awk, cat, df, free, grep, sed

Recursive read access to /proc folders is required

Note: not all commands are applicable to all Linux distributions

Lanamark Explorer 25 Data Collection Guide

Network Impact

Inventory
Each target system generates 250-500 KB of data during inventory data collection and the number of
concurrent inventories is limited to 20. Since each inventory operation can take several minutes, the
network load from inventory ranges from 0.5 to 1.0 Mbps.

Performance
Lanamark Explorer collects 50-100 KB of data from each target system per monitoring interval. If the
monitoring interval is kept at a default of five (5) minutes, performance data collection will generate a
network load between 0.15 to 0.3 Mbps.

Lanamark Explorer 26 Data Collection Guide

Appendix B: Security
Credentials
Passwords entered into the Lanamark Snap are encrypted using AES-256 and are never displayed in
plaintext or transmitted externally.

Data Synchronization
Lanamark Explorer takes daily inventory and performance data snapshots and uploads them securely
to Lanamark One using HTTPS (port 443).

Data Storage
Inventory and performance data is stored on encrypted storage infrastructure and is only available to
the Lanamark partner performing the assessment.

Lanamark Explorer 27 Data Collection Guide

Version History
Table 8: Version History

Version Date Document Version History

Version 3.6 February 28, 2018 Copyright information updated.

Version 3.5 December 27, 2017 Updated formatting

Version 3.0 March 14, 2017 Updated Outbound Connectivity require-

ments.

Added Microsoft Windows Server 2016

support to System Requirements.

Updated Target System Requirements to

include support of the latest Microsoft
Windows and Linux operating systems.

Version 2.0 February 15, 2016 Reviewed and updated all content

Version 1.3 March 27, 2015 Added Outbound Connectivity section with in-
formation where the data is uploaded

Version 1.2 September 2, 2014 Added system requirements for up to 2,500

machines

Version 1.1 August 19, 2014 Added additional Linux commands used for
post-processing inventory and performance
data to Appendix A: awk, cat, free, grep, sed

Version 0.5 May 5, 2014 Draft

Version 0.1 April 15, 2014 Initial version

Lanamark Explorer 28 Data Collection Guide

Legal Disclaimer

c Copyright 2018, Lanamark Inc.
This document is copyrighted. This document may not, in whole or part, be copied, duplicated, re-
produced, translated, used in services other than those delivered by authorized Lanamark partners
using Lanamark One, electronically stored, or reduced to machine readable form nor transferred to
any third party without prior written consent from Lanamark Inc.
Lanamark Inc. does not warrant this document to be free of errors or omissions. Lanamark Inc. re-
serves the right to make corrections, updates, revisions, or changes to the information contained
herein, but are not obligated to do so. Lanamark Inc. does not warrant the material described herein
to be free of patent or other intellectual property infringement.
UNLESS PROVIDED OTHERWISE IN WRITING BY LANAMARK INC., THE DOCUMENT AND INFORMATION
AND PROGRAMS DESCRIBED HEREIN ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, IN-
CLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PAR-
TICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT WILL LANAMARK INC. OR ITS OFFICERS, DI-
RECTORS, OR EMPLOYEES OR AFFILIATES BE LIABLE TO ANY ENTITY FOR ANY SPECIAL, COLLATERAL,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT ANY LIMITATION, FOR ANY LOST
PROFITS OR LOST SAVINGS, RELATED OR ARISING IN ANY WAY FROM OR OUT OF THE USE OR INABIL-
ITY TO USE THE INFORMATION OR PROGRAMS SET FORTH HEREIN, EVEN IF IT HAS BEEN NOTIFIED OF
THE POSSIBILITY OF SUCH DAMAGE BY THE PURCHASER OR ANY THIRD PARTY AND NOTWITHSTAND-
ING THE FAILURE OF ESSENTIAL PURPOSE OF ANY REMEDY.

Lanamark Explorer 29 Data Collection Guide