Truview Install Software Guide

TruView SW Installation Guide
March 2016, Rev 1

© 2016 NetScout Systems, Inc.
All product names are trademarks of their respective companies.
End User License Agreement (EULA)
BY USING THIS PRODUCT IN ANY MANNER, YOU ARE AGREEING TO ACCEPT THE FOLLOWING TERMS AND
CONDITIONS. IF YOU DO NOT AGREE TO THESE CONDITIONS, DO NOT DOWNLOAD OR USE THE SOFTWARE OR
PRODUCT. THE TERMS OF AN END USER LICENSE AGREEMENT ACCOMPANYING PARTICULAR SOFTWARE FILE UPON
INSTALLATION OR DOWNLOAD OF THE SOFTWARE, IF ANY, SHALL SUPERSEDE THE TERMS PRESENTED HERE.
For purposes of this EULA, the following definitions will apply:

“Agreement” means this EULA or the terms of an End User License Agreement accompanying a particular Software
file.
NETSCOUT means NETSCOUT SYSTEMS, INC.
"Documentation" means any installation guides, reference guides, operation manuals and release notes provided
with the Product in printed, electronic, or online form.
“Software” means any software on NETSCOUT then-current price list or otherwise made available including (i)
software provided on a stand-alone basis, (ii) software provided on or with any Hardware, (iii) any upgrades,
updates, patches, enhancements, or fixes to any of the foregoing made available by NETSCOUT and provided to
customers having purchased support and maintenance services on the Software (“Updates”).
“Hardware” means hardware products generally available on NETSCOUT then-current price list.
“Product” means, collectively, the Hardware and/or Software and all Documentation associated therewith.
“You” and “Your” means the commercial entity authorized by NETSCOUT to utilize the Product.
1. GRANT OF LICENSE
NETSCOUT grants You a non-exclusive right to use the Product subject to the terms and conditions set forth in this
End User License Agreement. You acknowledge and agree that the Product may use a network to send and receive
data, and that Your service providers may bill You airtime, data or usage fees and that You are solely responsible for
such charges.
2. TITLE, COPYRIGHT AND TRADEMARK

NETSCOUT retains all right, title, and interest in and to the Software, including without limitation the all Updates,
Documentation, and permitted copies, and all patents, copyrights, trade secrets, trademarks, and other intellectual
property rights therein. NETSCOUT retains all rights to the intellectual property associated with the Hardware
except as expressly granted in this Agreement. The Software and Documentation are protected under copyright
laws; any permitted copies must include all copyright, government-restricted rights, and other proprietary notices
or legends included on the Software when it was shipped or first provided to You.
3. RESTRICTIONS
This grant of license does not include the right to copy other than for archival purposes, modify, rent, lease, sell,
transfer or distribute the Product or any portion thereof. You may not reverse engineer, decompile, or disassemble
the Product.
This grant of license allows use of Product on a single computer or smart device at a time for use with only the MAC
address/Unique identifier for Wi-Fi/Ethernet/specialized adapter for which it was uniquely licensed, if a license key
binding to the MAC address/ Unique identifier for Wi-Fi/Ethernet/specialized adapter was required during
installation.
This Product is controlled by the U.S. Department of Commerce Bureau of Industry and Security. You may not sell,
transfer, export, or re-export the Product, directly or indirectly, to anyone in any country in which such sale,
transfer, export, or re-export is restricted by U.S. law or regulation, or any other government having jurisdiction. You
specifically certify that You are not a national of a country under U.S. Government sanctions, or a person who is
included on any U.S. Government restricted parties lists.
4. TERM
This license is effective upon Your acceptance of the Agreement or first use of the Product and shall remain in effect
until terminated by (a) written notification to NETSCOUT or (b) a failure on Your part to comply with the Agreement.
Upon termination of the Agreement, You shall return to NETSCOUT or destroy all copies of the Product and
associated written materials.
5. OTHER AGREEMENTS
The Software may contain third party technology. NETSCOUT licenses such third party technology and
iii
documentation ("Third Party Materials") for use with the Software only. In the event the Software contains Third
Party Materials, or in the event You have the option to use the Software in conjunction with Third Party Materials (as
identified by NETSCOUT in the applicable Documentation), then such Third Party Materials are provided or
accessible subject to a third-party license. You agree to abide by the terms of said licenses and to obtain any
additional licenses that may be required to use the Third Party Materials, including but not limited to patent
licenses. Your use of the Third Party Materials in conjunction with the Software in a manner consistent with the
terms of the Agreement is permitted, however, You may have broader rights under the applicable Third Party
Materials license and nothing in the Agreement is intended to impose further restrictions on Your use of such Third
Party Materials. You agree to indemnify, defend and hold NETSCOUT harmless against any action arising from
failure to obtain, or breach of, such Third Party Material licenses. To the extent the Software includes Third Party
Materials licensed to NETSCOUT by third parties, those third parties are third party beneficiaries of, and may
enforce, the applicable provisions of this Agreement.
Where terms or conditions of the Agreement conflict with terms or conditions of other agreements, unless
otherwise specifically stated, the Agreement supersedes other agreements.
6. LIMITED WARRANTY AND LIMITATION OF LIABILITY

Each NETSCOUT Hardware product is warranted to be free from defects in material and workmanship under
normal use during the applicable warranty period. The warranty period for Hardware is one year and begins on the
date of purchase. The warranty period for parts and accessories is 90 days from date of purchase. Ni-Cad, Ni-MH
and Li-Ion batteries, cables or other peripherals are all considered parts or accessories. The warranty extends only
to the original buyer or end user customer of a NETSCOUT authorized reseller, and does not apply to any Product
which, in NETSCOUT’ opinion, has been misused, abused, altered, neglected, contaminated, or damaged by accident
or abnormal conditions of operation or handling. NETSCOUT warrants that Software will operate substantially in
accordance with its functional specifications as set forth in the Documentation and that it has been properly
recorded on non-defective media. The warranty period for Software is 90 days from the date of purchase.
NETSCOUT does not warrant that Software will be error free or operate without interruption.
NETSCOUT authorized resellers shall extend this warranty on new and unused Products to end-user customers only
but have no authority to extend a greater or different warranty or warranty period on behalf of NETSCOUT.
Warranty support is available only if Product is purchased through a NETSCOUT authorized sales outlet or if You
have paid the applicable international price. To the extent permitted by law, NETSCOUT reserves the right to
invoice You for repair/replacement when a Product purchased in one country is submitted for repair in another
country.
NETSCOUT warranty obligation is limited, at NETSCOUT option, to repair, or replacement of a defective Product
which is returned to a NETSCOUT authorized service center within the warranty period.
To obtain warranty service, contact Your nearest NETSCOUT authorized service center to obtain return
authorization information, then send the Product to that service center, with a description of the difficulty, postage
and insurance prepaid (FOB destination). NETSCOUT assumes no risk for damage in transit. Following warranty
repair, the Product will be returned to You, transportation prepaid (FOB destination). If NETSCOUT determines that
failure was caused by neglect, misuse, contamination, alteration, accident or abnormal condition of operation or
handling, or normal wear and tear of mechanical components, NETSCOUT will provide an estimate of repair costs
and obtain authorization before commencing the work. Following repair, the Product will be returned
transportation prepaid and You will be billed for the repair and return transportation charges (FOB Shipping point).
THIS WARRANTY IS YOUR SOLE AND EXCLUSIVE REMEDY AND IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. NETSCOUT SHALL NOT BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL DAMAGES OR LOSSES, INCLUDING LOSS OF DATA, ARISING FROM ANY CAUSE OR THEORY.
Since some countries or states do not allow limitation of the term of an implied warranty, or exclusion or limitation
of incidental or consequential damages, the limitations and exclusions of this warranty may not apply in those
countries or states. If any provision of this Warranty is held invalid or unenforceable by a court or other decision-
maker of competent jurisdiction, such holding will not affect the validity or enforceability of any other provision.
7. NO OTHER WARRANTIES
NETSCOUT DISCLAIMS THE WARRANTY OF NON-FRINGEMENT AND ALL OTHER WARRANTIES, EITHER EXPRESS OR
iv
IMPLIED BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, WITH RESPECT TO THE SOFTWARE AND THE ACCOMPANYING WRITTEN MATERIALS. In no event shall
NETSCOUT be liable for any damages whatsoever (including, without limitation, indirect, consequential, or incidental
damages, damages for loss of business profits, business interruption, loss of business information, or other
pecuniary loss) arising out of the use of or inability to use this Product, even if NETSCOUT has been advised of the
possibility of such damages.
8. APPLICABLE LAW
This Agreement will be governed by the laws of the Commonwealth of Massachusetts without regard to choice of
law rules, and you hereby submit to the jurisdiction of the federal and state courts located in said Commonwealth
and the applicable service of process. The parties agree that the United Nations Convention on International Sale of
Goods Acts will not apply to this Agreement. 9. U.S. GOVERNMENT RESTRICTED RIGHTS.
The Software and documentation are provided with restricted rights. Use, duplication, or disclosure by the United
States Government is subject to restrictions as set forth in subparagraphs (c)(1)(ii) of the Rights in Technical Data
and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer
Software - Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Netscout Systems, Inc. 310 Littleton
Road, Westford, Massachusetts 01886
Main Phone: 978-614-4000 / Main Fax: 978-614-4004
v
3rd Party Licensing Information
This product includes the following software from third party providers:
• MySQL Enterprise Pro
• Microsoft - Server 2003 OS and SQL Server 2005
• Dundas CHART for ASP.NET Professional Edition
• Dundas CHART for Reporting Services. http://www.dundas.com/Products/Chart/RS/Licensing/OEM-
ISV.aspx.
• Visual Mining, Inc. NetCharts Java Graphing applet.
• Hifn MeterFlow.
• MatrixSSL™ security software licensed from PeerSec Networks Inc., http://www.peersec.com.
• ComponentArt: Web.UI for ASP.NET - Enterprise License (version 2007.2)
http://www.componentart.com/store/licenseagreements.aspx.
This product contains open source code from the following sources:
• Adobe Acrobat reader. Copyright © 2007 Adobe Systems Incorporated.
http://www.adobe.com/products/acrobat/acrruela.html.
• The following sources are distributed under Apache Software License.
http://www.apache.org/LICENSE.
Apache Tomcat v2.2.4.
Apache Xerces Java v2.9.0 (http://xerces.apache.org/xerces2-j/)
Jakarta Log4j v1.1.3 (http://logging.apache.org/log4j/).
Jakarta Tomcat v3.3.2 (http://tomcat.apache.org/).
Xerces C++ Version 2.8.0. Copyright © 2007 The Apache Software Foundation. Licensed under the
Apache License, Version 2.0.
Xerces XML parser. http://www.apache.org/licenses/LICENSE-2.0.html.
• Fedora Core Linux distributed under GNU General Public License
(http://www.gnu.org/licenses/gpl.txt) and GNU Less General Public License
(http://www.gnu.org/licenses/lgpl.txt). Copyright © 2003, 2004, 2005, 2006 Fedora Project.
• IE5.5+ PNG Alpha Fix v1.0RC4 (http://www.twinhelix.com/css/iepngfix/demo/), distributed under
the CC-GNU Lesser GNU Public License, a copy of which is available at
http://creativecommons.org/licenses/LGPL/2.1/deed.en.
• Java Runtime Environment distributed under Sun Microsystems’ Binary Code License Agreement.
Copyright © 2002 Sun Microsystems, Inc. http://java.com/en/download/license.jsp.
• joeSNMP v0.2.6
(http://opennms.svn.sourceforge.net/viewvc/opennms/opennms/branches/OPENNMS/src/joesnm
p/), distributed under the Lesser GNU Public License, a copy of which is available at
http://www.gnu.org/licenses/lgpl.html.
• jspSmartUpload v2.1, which is no longer available, is distributed under the Advantys Freeware
license contract, a copy of which is available at
http://web.archive.org/web/20031209160524/http://www.jspsmart.com/liblocal/docs/legal.htm.
• libpcap. Copyright © 2000-2008 Free Software Foundation, Licensed under BSDAdClause.
http://www.filewatcher.com/p/nmap-3.93.tar.bz2.2029943/nmap-3.93/libpcap/LICENSE.html.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
vi
TruView
Software Installation Guide
1. Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The names of the authors may not be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED `ÀS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE.
• Log4cpp. Copyright © 2000, LifeLine Networks BV (www.lifeline.nl). All rights reserved. Copyright ©
2000, Bastiaan Bakker. All rights reserved. http://www.gnu.org/licenses/lgpl.txt.
• monit (GPL) available from http://www.tildeslash.com/monit/ license:
http://www.gnu.org/licenses/gpl.html.
• MySQL++ Copyright © 1998 by Kevin Atkinson, (c) 1999, 2000 and 2001 by MySQL AB, and (c) 2004-
2007 by Educational Technology Resources, Inc. distributed under GNU Lesser General Public
License: http://www.gnu.org/licenses/lgpl.txt.
• OpenSSL. Copyright © 1998-2007 The OpenSSL Project. This product includes cryptographic
software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim
Hudson (tjh@cryptsoft.com). http://www.openssl.org/source/license.html.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgment: "This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote
products derived from this software without prior written permission. For written permission,
please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may “OpenSSL” appear in
their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment: “This
product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/).”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT `ÀS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL
PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
vii
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
• PE Builder. Copyright (c) 2002-2005 Bart Lagerweij. All rights reserved. This program is free
software. Use and/or distribute it under the terms of the PE Builder license (see below). Please note
that this license is for pebuilder.exe, bartpe.exe, netconfig.exe and scangui.exe! More information
about PE Builder: http://www.nu2.nu/pebuilder/.
1. By using and/or opening any packaging enclosing this software, expanding any compressed file
containing this software or by utilizing this software, you agree to be bound by the terms of this
license agreement.
2. The software, documentation and any other materials accompanying this License whether on
disk, in read only memory, on any other media or in any other form (collectively the "Software") are
licensed, not sold, to you by Bart Lagerweij, as well as his respective members, agents, directors,
officers, servants and representatives, if any, (collectively "Licensor") for use only under the terms
of this License, and Licensor reserves all rights not expressly granted to you. The rights granted
herein are limited to Licensor's intellectual property rights in the Software and do not include any
other patents or intellectual property rights. You own the media on which the Software is recorded
but Licensor retains ownership of the Software itself. The rights granted under the terms of this
License include any software upgrades that replace and/or supplement the original Software
product, unless such upgrade contains a separate license.
3. Permission is hereby granted, free of charge, to any person obtaining a copy of the Software to
use, copy, publish and distribute the Software, subject to the conditions of this License.
4. This license must be included with all copies of the Software, and may not be modified from its
original format as created by the Licensor. The Software may not be distributed subject to any
other license.
5. This License is effective until terminated. Your rights under this License will terminate
automatically without notice from Licensor or if you fail to comply with any term(s) of this License.
Upon the termination of this License, you shall cease all use of the Software and destroy all copies
of it, whether full or partial.
6. Selling or charging a fee for the Software is prohibited, although a fee may be charged for the act
of transferring a copy and/or for the distribution media, but not for the Software itself.
7. The Software, in whole or in part, may not be incorporated with or into any other software
product without written permission from Licensor. Publishing or distributing The Software is only
allowed when The Software is in the original archive, adding or remove files from The Software
archive is not allowed!
8. You expressly acknowledge and agree that use of the software is at your sole risk and that the
entire risk as to satisfactory quality, performance, accuracy and effort is with you. Licensor does not
warrant against interference with your enjoyment of the software, that the functions contained in
the software will meet your requirements, that the operation of the software will be uninterrupted
or error-free, or that defects in the software will be corrected. Should the software prove defective,
you assume the entire cost of all necessary servicing, repair or correction.
9. THE SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. No oral or written advice given by Licensor or by
an authorized representative of Licensor shall create a warranty.
viii
TruView
10. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING BUT NOT LIMITED TO PERSONAL INJURY,
OR ANY INCIDENTAL, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING
WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION
OR ANY OTHER COMMERCIAL DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE
OR INABILITY TO USE THE SOFTWARE, HOWEVER CAUSED, REGARDLESS OF THE THEORY OF
LIABILITY (CONTRACT, TORT OR OTHERWISE) AND EVEN IF LICENSOR HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
11. THIS SOFTWARE IS NOT INTENDED FOR USE IN ANY APPLICATION IN WHICH THE FAILURE OF
THE SOFTWARE COULD LEAD TO DEATH, PERSONAL INJURY OR SEVERE PHYSICAL OR
ENVIRONMENTAL DAMAGE.
12. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, LIABILITY OR
LIMITATIONS ON APPLICABLE STATUTORY RIGHTS OF A CONSUMER, SO THE ABOVE EXCLUSIONS
AND LIMITATIONS MAY NOT APPLY TO YOU. IF SUCH EXCLUSIONS FROM LIABILITY APPLY TO YOU,
DO NOT USE THIS SOFTWARE.
13. In no event shall Licensor's total liability to you for all damages exceed the amount of $50.00.
The foregoing limitations will apply even if the above stated remedy fails in its essential purpose.
14. This License constitutes the entire agreement between the parties with respect to the use of the
Software licensed hereunder and supersedes all prior or contemporaneous understandings
regarding such subject matter. No amendment to or modification of this License will be binding
unless in writing and signed by Licensor. Any translation of this License is done for local
requirements and in the event of a dispute between the English and any non-English versions, the
English version of this License shall govern.
15. This License will be governed by and construed in accordance with the laws of the Netherlands,
as applied to agreements entered into and to be performed entirely within the Netherlands
between Dutch residents. This License shall not be governed by the United Nations Convention on
Contracts for the International Sale of Goods, the application of which is expressly excluded.
16. If for any reason a court of competent jurisdiction finds any provision, or portion thereof, to be
unenforceable, the remainder of this License shall continue in full force and effect.
U.S. GOVERNMENT RESTRICTED RIGHTS. The Software and documentation are provided with
RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as
set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software-
Restricted Rights at 48 CFR 52.227-19, as applicable.
• RSA MD5 code. Copyright © 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.
http://www.faqs.org/rfcs/rfc1321.html.
License to copy and use this software is granted provided that it is identified as the “RSA Data
Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing this
software or this function.
License is also granted to make and use derivative works provided that such works are identified as
“derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning
or referencing the derived work.
RSA Data Security, Inc. makes no representations concerning either the merchantability of this
software or the suitability of this software for any particular purpose. It is provided "as is" without
express or implied warranty of any kind.
ix
These notices must be retained in any copies of any part of this documentation and/or software.
• SNMP stack. Copyright 1997 by Carnegie Mellon University. All Rights Reserved.
http://www.cisco.com/en/US/docs/net_mgmt/provisioning_center/4.0/user/guide/about.html#wp4
66106.
Permission to use, copy, modify, and distribute this software and its documentation for any
purpose and without fee is hereby granted, provided that the above copyright notice appear in all
copies and that both that copyright notice and this permission notice appear in supporting
documentation, and that the name of CMU not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission.
CMU DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CMU BE LIABLE FOR ANY
SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
OF THIS SOFTWARE.
• Webmin. Copyright © Jamie Cameron All rights reserved. Redistribution and use in source and
binary forms, with or without modification, are permitted provided that the following conditions
are met:
distribution.
3. Neither the name of the developer nor the names of contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE DEVELOPER `ÀS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE DEVELOPER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
• Zlib compression libraries. Copyright © 1995-2004 Jean-loup Gailly and Mark Adler.
http://www.zlib.net/zlib_license.html.
x
TruView
xi
1. Software Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 TruView System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Software Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 TruView System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Optimizing TruView Server Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.6 Upgrading the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.7 Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1.8 PAC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.9 Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Installation Overview
This chapter helps you understand the TruView Central installation process and system requirements. Topics
include:
System Architecture
Software Installation Process
TruView System Requirements
Software Installation
Optimizing TruView Server Performance
Upgrading the Server
Firewall Configuration
PAC Software
Server Setup
Prior to beginning the installation and configuration of your TruView Server, check with NETSCOUT (enterprise.nets
cout.com) for the latest installation instructions.
TruView System Architecture

The TruView system includes the following components:
Analysis Service Elements (ASEs)—Devices installed on the network that collect application and network
performance data. These include both Visual UpTime ASEs and partner devices equipped with agent
software. ASEs on both ends of a physical access line form an end-to-end managed circuit.
TruView Packet Appliances (TVPs)—Devices installed at the data center that monitor data passing through
core switches. TVPs monitor application traffic and measure application performance and usage.
TruView Flow Appliances (TVFs)—Devices installed at key points on the network that collect IP traffic
(NetFlow) data from Cisco routers and managed switches.
Server—The TruView Central server stores system and performance data and provides interfaces for clients
to access this data. A Web server may be installed on the server machine or as a stand-alone Web server.
Web portal—Web-based client applications, accessed through a single logon, that present data for analysis
and provide tools for configuring devices.
PAC—The PAC (Platform Applicable Client) is a Windows-based client used primarily for Visual UpTime
network configuration.
In TruView, TVFs and network probe (ASE) hardware devices are deployed throughout the network and TVPs are
deployed at the data center. Users access the data through the Web portal. The TruView database and Web server
includes administration and database management tools, including PAC software.
TruView Central System Components

For a full overview of TruView, see "TruView Overview," in the System Administration Guide.
Server
The TruView server is the database server and default Web server for the system.
Database
The TruView server is a dedicated, uniquely configured database and Web server that stores application and
network performance data from ASEs, NetFlow data from TruView Flow Appliances, application performance data
from TruView Packet Appliances, network configuration data, and access control settings for users.
The TruView server runs Microsoft Windows Server and Microsoft SQL Server. A single server can support multiple
Web portal users and PAC clients.
You can purchase a turnkey server with installed software or install the software on a computer that meets defined
server requirements. PAC software is also installed on the TruView server.
The server computer typically resides in a central location, such as an enterprise's data center or service provider's
NOC, from which a WAN or set of WANs is managed. For an enterprise hosted system, the data center for
managing the enterprise network is at a designated site outside the WAN. For the service provider, the NOC is
inside the WAN managing all service subscribers' networks.
All communication between clients and TruView data sources passes through the TruView server. The server
requests data collection and status updates from ASEs, TVFs, TVPs, and software pollers. Web portal users access
data through the Web server, which may be hosted on the same machine as the server or on a separate system. A
stand-alone Web server communicates with the TruView server using Transmission Control Protocol (TCP) and
User Datagram Protocol (UDP) over a configurable port.
System Communication with Stand-Alone Web Server

Web Server
Web portal users access data over an IP network using HTTP or HTTPS connections to the Web server. The Web
server is a Microsoft IIS Server that may be installed on the same system as the TruView server or on a separate
machine.
You can separate the Web server from users and/or the TruView server by a firewall. A stand-alone Web server
positioned behind a firewall limits Web portal user direct access to the TruView server. It can also serve as a single
Web portal for users to access multiple servers.
The stand-alone Web server requires direct access to all TruView Flow Appliances configured on different TruView
servers.
Web Portal
The TruView Web portal is the single access point through which users interact with data. From the Web portal,
users can create and organize personalized views of data based on their workflow, interact with data from a range of
perspectives, and access data from multiple sources. For example, the Web portal can host a system, or can be
launched from another system.
The Web portal supports HTTP and HTTPS connections to the Web server.
PAC
The Platform Applicable Client (PAC) runs on a Microsoft Windows PC. It is used primarily for network and event
configuration when using ASEs as the TruView data source.
PAC software is installed on the TruView server. More than one PAC can connect to a single server. A single PAC
can also connect to multiple TruView servers.
Software Installation Process

Your TruView system must be at version v8.0, v8.1, or 8.3 prior to installing v9.0. Refer to the Software Installation
Guide for each version for information on upgrading your system to the appropriate version.
TruView installation consists of these stages:
1. Determine the locations of your server, Web server, and clients. For more information, see TruView System
1.
Requirements.
2. Install the server.
If you are upgrading from a previous version of TruView, back up your data, make any necessary
updates to Microsoft Windows and to Microsoft SQL Server. Then upgrade the TruView server
software.
If you are installing the server software yourself on a computer of your choice, you must prepare the
computer and install the software. See Software Installation.
If you have purchased a turnkey server computer from NETSCOUT (delivered with Windows Server
2008 R2 Standard Edition, the TruView server software, and other required software already installed),
you only need to connect it to your network and begin configuring TruView. See Server Setup.
3. Install the clients (if using ASEs as a TruView data source).
4. Install TVFs, and TVPs.
5. Configure Windows Firewall and any network firewall software to allow the TruView components to
communicate. See the Firewall Port Settings table in Firewall Configuration.
TruView System Requirements

Make sure that your target computer meets the minimum requirements before you install or upgrade TruView.
Topics include:
Hardware
Disk Space Requirements (C: Drive)
Networking
External Media
Reporting Services
Software
Stand Alone Web Server Requirements
Web Portal Requirements
Web Browser and Operating System Requirements
PAC Requirements
VoIP Requirements
TVP and TVF Requirements
IP SLA Reporting Router Requirements
Third Party Software
Hardware
You can run the TruView server software on a single-processor or dual-processor computer. The Server Capacity
and Minimum Hardware Requirements table shows the recommended specifications for a server type system using
ASE and TVF data only.
Notes
To monitor application performance data from TVPs, a TruView dual-processor computer or equivalent is required.
For more information about TruView server specifications and setting up and optimizing TruView with TVPs, see the
TAC Knowledge Base.
For suggestions on increasing the security level of the TruView server, see the TAC Knowledge Base.
Capacity or Requirement Recommended Configuration

ASE Support Up to 1,000 ASEs
Collector Up to 10
Domain Support 1-250 domains
Computer Dell R720xd server or equivalent with dual Intel Xeon

ES-2620 2.00 GHz, 15M Cache
Memory (RAM) 32 GB minimum
Disk Space 6-8 1TB 10K rpm Hard Drive minimum, attached to
integrated PERC5/i RAID 1 (mirrored)
Ethernet card 10/100/1000. See Network Partitioning.
In addition to these requirements, you need a DVD-ROM drive, monitor, mouse, and keyboard.
Disk Space Requirements (C: Drive)

In order to determine the amount of disk space needed on the system partition ( C: drive), you need to evaluate your
current hardware configuration. Microsoft recommends a minimum of 32 GB of disk space for Windows Server and
6 GB of disk space for SQL Server. Also, Windows automatically sets a swap file size equal to the total amount of
physical memory installed in the machine. The size and location of the swap file can be changed, but that is not
recommended. NETSCOUT recommends an additional 20 GB of disk space to allow for the installation of TruView
and Windows Updates. Use the following formula to calculate the amount of disk space needed on the system
partition:
Total amount of disk space needed = 32 GB + 6 GB + 20 GB + amount of physical memory
Use the following Microsoft link to help determine the appropriate swap file size and monitor its usage:
http://support.microsoft.com/kb/889654 .
The most physical memory that you can install in Windows Server 2008 R2 Standard is 32 GB, therefore you will
need no more than 90 GB of disk space. While it is possible to perform this upgrade with less space allocated to the
system partition, NETSCOUT does not support this configuration.
If you do not have enough disk space available:
Remove all software you have installed that is not related to TruView, SQL Server, or Windows Server. Do
not install extraneous software on the TruView server.
Remove any unneeded, saved reports that were previously scheduled.
Contact your TruView vendor technical support for advice on other ways to free up disk space.
If there is not enough disk space, you need to determine if the system partition consumes the whole disk or
are there multiple partitions on the disk:
If the system partition uses the whole disk, then a larger disk of sufficient size must be installed
If all there is sufficient disk space across all partitions combined, then record existing partition information
including the amount of free space. The disk will have to be re-partitioned to allow for the larger system
partition.
Networking
Your server must have IP connectivity to ASEs, TVPs, TVFs, and clients.
Note
You do not need to establish network connectivity until after the server software is installed. If your organization's
security policies are more restrictive than the security settings recommended for this installation, install the server
software with the computer disconnected from the network, then adjust the security settings as needed and connect
the computer to the network.
Your server must use a static IP address. Configure the TCP/IP Properties of the network connection to use a static
IP address, subnet mask, default gateway address, and a DNS server address.
Network Partitioning
For a large TruView server (a server supporting several hundred or more devices) at least three Ethernet ports are
recommended. You can configure network isolation as follows:
One port for access from the Internet through the Web server. You can also put remote Windows PACs on
this port.
One port for internal users, such as those within the NOC.
One port for network devices, such as ASEs.
With a fourth port, consider partitioning the devices to share the load, by placing TVFs on one port, TVPs on
another, ASEs on a third or splitting the ASEs into segments.
External Media
Turnkey servers come with a system recovery DVD.
Reporting Services
TruView Web-based and administrative reports utilize Microsoft SQL Reporting Services. For requirements needed
to run SQL Server 2008 R2 Standard Reporting Services, visit: http://www.microsoft.com/sql/reporting/productinfo/s
ysreqs.mspx.
Software
Your TruView system must meet the software requirements listed in the table below.
Software Requirements for the TruView Server
Requirement Software
Operating system Windows Server 2008 R2 with SP1 (Standard or

Enterprise)
Client access licenses Customer is responsible for additional client access

licenses.
Other components SQL Server 2008 R2 Standard (Default)
or SQL Server 2008 R2 Enterprise
Customer is responsible for additional licenses.
Internet Information Server (IIS) 7.0
Internet Explorer v9/10/11, Firefox v28, Chrome v44
(or less)
For Chrome v45 and higher, install IE Tab extension.
Adobe Acrobat Reader 9.0 or later
.NET Framework 4.0
Microsoft Silverlight
Notes
Windows Server 2008 is not included with your TruView v9.0 software. You must download it from Microsoft (https://
www.microsoft.com/en-us/download/details.aspx?id=5023).
In addition to the software listed above, Microsoft ASP.NET 4.0 and Oracle Java Runtime Environment 8 are
required. However, these are automatically installed as part of the server software installation procedure. You do not
need to install these separately.
Stand-Alone Web Server Recommendations

The TruView Web server provides web portal users with a safe access point to TruView data. It comes installed on a
TruView server or can be installed on a stand-alone server machine.
Hardware
Your Web server system must meet the following hardware requirements:
Intel Xenon processor (or higher)

RAM: 1 GB minimum. 2 GB or more recommended.
1 GB available hard drive space.
SVGA 1280 x 1024 monitor
Video card and driver supporting at least 64K colors
DVD-ROM drive
Software
Your stand-alone Web server system must meet the following software requirements:
Windows Server 2008 R2 Standard Edition with SP1

Internet Information Server (IIS) 7.0
Internet Explorer v9/10/11, Firefox v28, or Chrome v44 (or less), and if v45 (or more) then install the IE Tab
extension
Adobe Acrobat Reader 9.0 or later for viewing system manuals. For upgrades, the user can upgrade or install
Acrobat Reader.
Web Portal Requirements

Computers accessing the TruView Web portal must meet the following hardware requirements:
Pentium IV processor (or higher)
RAM: 512 MB minimum
200 MB available hard drive space. (This includes space for Adobe Acrobat Reader and the Java virtual
machine. If the target computer already has these installed, the disk space requirement is smaller.)
Web Browser and Operating System Requirements

Supported Operating Systems
Requirement Software
TruView server/ Web server Windows Server 2008 R2 Standard Edition with SP1
Windows Server 2008 Enterprise
Visual UpTime Select PAC Windows Server 2008 R2 with SP1 Windows 7
Professional (32-bit) and Windows 7 Professional
(32-bit) SP1
PAC Requirements (when ASEs are used as a TruView data source)

Your PAC computer must meet the following hardware requirements:
Pentium IV processor (or higher)

RAM: 256 MB minimum, 512 MB recommended
200 MB available hard drive space. (This includes space for Adobe Acrobat Reader and the Java virtual
machine. If the target computer already has these installed, the disk space requirement is smaller.)
CD-ROM drive
Notes
For best performance when running Web applications, set your screen resolution to 1280 x 1024 pixels or higher.
Oracle JRE 8 is required. When installing or upgrading browsers, make sure that Java is supported and that you
have installed the correct Java version, which is available from the Web portal Support page and the TruView
server's Visual UpTime Select home page.
Help is HTML-based with JavaScript enhancements. Enable JavaScript in your browser options.
To run more than one browser session at the same time, open a new instance of the browser. This ensures that
each session refreshes independently. Do not use File > New > Window to open a new window.
Do not use the browser Back button to return to a previous view.
VoIP Requirements
To monitor VoIP using TruView, your system must meet the following requirements:
VoIP-capable IP Transport ASEs deployed at logical locations in network.
Supported VoIP vendor phones: Cisco phones using SIP, Skinny, and H.323 protocols; Avaya H.225 and
Lync RTP detection.
For the ASE to report latency for VoIP calls, VoIP endpoints (phones, gateways) must support exchanging RTCP
packets containing "Sender Reports" as defined in RFC 3550, section 6.4.1. If the endpoints on a VoIP call have not
implemented RTCP, the ASE cannot measure the delay without adding additional traffic to the user circuit. When
RTCP is not implemented in the end points, the ASE sets delay to zero for the purposes of call quality calculations.
When deploying VoIP-capable ASEs in a network, at least one VoIP-capable ASE at a site must be a WAN IP
Transport ASE.
Any call manager (PBX) running a supported session setup protocol is acceptable.
TVP and TVF Requirements

LAN connectivity is recommended between the TruView server, TVPs, and TVFs.
Notes
If a stand-alone Web server is used, it requires direct access to all TVPs and TVFs configured on different TruView
servers.
For more information about TruView server specifications and setting up and optimizing TruView with TVPs, see the
TAC Knowledge Base.
Third Party Software

To maintain system security you may need to apply patches to Windows and related system software. The Policy
on Additional Third Party Software table below identifies these and presents recommended courses of action.
Warning
DO NOT install other software applications on the TruView server other than those approved by NETSCOUT.
The installation of other software, particularly network management applications, can use critical resources,
may degrade integrity and performance, and may void the sales and service/support warranty.
Subscribe to the Microsoft Product Security Notification Service to receive alerts from Microsoft regarding new
security information. Visit: http://technet.microsoft.com/en-us/security/cc307424.
Policy on Additional Third Party Software
Software Action
Critical security updates for Microsoft Windows, IIS, Approved—Install.

and Internet Explorer
Non-critical security updates for Microsoft Windows,

IIS, and Internet Explorer
Contact NETSCOUT Customer Support at:
Supported Windows, SQL Server, IIS, or Internet 844-833-3713 US only
Explorer service packs 978-320-2150 International
E-mail: techsupport@netscout.com
Virus checking software
Remote backup software
System management tools
Remote management software Windows Terminal Server is approved.
Software Installation
This chapter explains how to prepare a computer for use as a TruView server, and how to install the server software
on that computer. Use these instructions for a new installation of TruView v10.0. To upgrade an existing version,
refer to Upgrading the Server.
Topics include:
Installation and Setup Requirements

Install Windows Server 2008 R2 Standard with SP1
Install SQL Server 2008 R2 Standard
Install Server Software
Apply Windows Security Updates
If you have purchased a pre-built server computer from NETSCOUT, you need only connect it to your network and
begin configuring TruView. See Server Setup.
Warning
Do not change the TruView server name after installing Reporting Services. Reporting Services may not
work properly if the name is changed. If you must change the name, consult technical support.
Installation and Setup Requirements

Software and basic server requirements for TruView server installation are listed below.
Software Requirements
Required software includes:
Windows Server 2008 R2 with SP1 (Standard or Enterprise)

SQL Server 2008 R2 (Standard or Enterprise)
.NET Framework 4.0 (included on TruView CD)
Internet Explorer v9/10/11, Firefox v28, or Chrome v44 (or less), and if Chrome v45 or more then install the IE
Tab extension
Server Requirements
Requirements for TruView server installation and setup include:
a static IP address that is approved

a static server name that is approved by your company policies
a Server Administrator password that is approved by company policies
Windows Server license
SQL Server license
A TruView server domain name
Install Windows Server 2008 R2 Standard with SP1

Read Disk Space Requirements (C: Drive) in TruView System Requirements prior to installing Windows Server
2008 R2 Standard. It is recommended that data files are stored on a different partition.
To install Windows Server 2008 R2 Standard:
1. Boot the PC from the Windows Server DVD. You may need to change the BIOS settings to enable booting
from DVD. The following screen is displayed:
2. Set the Language to install to English.
Note
Do not change these settings during the installation or afterwards. Regional settings must be in English for
TruView reports to work.
3. Set the Time and Currency format field to English (United States).
4. Set the Keyboard or input method field to the appropriate setting for your keyboard.
5. Select Next followed by Install now.
6. Accept the license terms.
The following screen is displayed:

7. Choose Custom (advanced). Do not select Upgrade.
8. Adjust the system partition based on the information in Disk Space Requirements (C: Drive) in TruView
System Requirements. You may need to delete other partitions on the disk. Select the partition with Type = S
ystem.
Note
All data and applications will be lost when a disk is repartitioned.
9. Select Drive Options on the Install Windows screen.

10. Extend the system partition and set the size as appropriate.
11. Format the system partition. This may take one hour or more and include one or more reboots of the system.
12. After format is complete, select Next.
13. Windows will now be installed. This may take 15 minutes or more. Reboot the server when prompted (Reboot
from disk if asked). After the installation is completed, reboot the server.
14. Change the Administrator password. Create a password (suggested VPM@dmin1).
15. The Initial Configuration Tasks window is displayed:
Select Activate Windows.
16. Enter the Windows Server Product key (license key) and select Next.
17. Select Set Time Zone. Set the time zone, date, and time for the TruView server.
18. Select Configure Networking,
19. Select the NIC and then Properties.
20. Select Internet Protocol Version 4 (TCP/IPv4) and then select Properties.
21. Configure a static IP address and DNS server(s). Return to the Initial Configuration Tasks screen.
22. Select Provide computer name and domain.
23. Select Change.
24. Enter the name for the TruView server.
Warning
Do not use an underscore "_" in the server name. Once you apply a name, do not change it.
Reporting Services may not work properly if the name is changed.
Note
Do not add the server to an Active Directory domain at this time.
25. Select More.

26. On the DNS Suffix and NetBIOS Computer Name window enter the DNS suffix and NetBIOS name of the
server.
27. Select OK.
28. Restart the server.
29. The Initial Configuration Tasks window is displayed. Select Enable automatic updating and feedback.
30. Select Manually configure settings.
31. Select Change Settings for Windows automatic updating.
32. Select the update method (recommended is Download updates but let me choose whether to install
them). Do not enable the Give me recommended updates the same way I receive important updates ch
eckbox.
33. Enable Allow all users to install updates on this computer.
34. Select OK.
35. Select Close.
36. Select Download and Install updates.
37. Install updates.
Add Web Server role:
1. On the Initial Configuration Tasks screen, under Customize This Server, select Add Roles
2. Select Server Roles.
3. Select the Application Server role.
4. Select Add Required Features on the Add Rules Wizard popup.
5. Select Next (twice).
6. Select Web Server (IIS) Support.
7. Select Add Required Role Services on the Add Rules Wizard popup.
8. Select Next (two times).
9. Scroll down and enable IIS 6 Metabase Compatibility.
10. Select Next.
11. Select Install.
Enable the remote desktop:
On the Initial Configuration Tasks screen, under Customize This Server, select Enable Remote Desktop.
Select the Remote tab.
Enable the Allow connections from computers running any version of Remote Desktop.
Select OK (twice).
Close the Initial Configuration Tasks window.
Add the "vuptime" user:
1. Open the Server Manager.

2.
2. Select Configuration > Local Users and Groups > Users.
3. Right-click Users.
4. On the New User popup enter the following:
User Name vuptime

Full name TruView vuptime
Password Visual1
Warning
Do not leave the vuptime user account password blank. Reporting Services will not work if the
password is blank.
5. Enable User cannot change password and Password never expires.

6. Select Create.
7. Right-click on the vuptime user and select Properties.
8. Select the Member Of tab.
9. Select Add...
10. On the Select Groups popup, select Groups as the Object Types...
11. Enter administrators in the Enter the object names to select field.
12. Select Check Names, and then click OK.
Install SQL Server 2008 R2 Standard

To install SQL Server 2008 R2 Standard:
1. Insert the SQL Server 2008 R2 Standard disk and reboot the server.
2. Log in as Administrator and run setup.exe.
3. Click the Installation link on the left-hand side.
4. Click New Installation or add feature to an existing installation on the right-hand side.
5. Verify that all the Rules have Passed and then select the OK button.
6. Enter the product license key on the Product Key screen, and click Next.
7. Accept the license terms and select Next.
7.
8. Click the Install button.

9. When the Setup Support Rules screen appears, verify that all of the Rules have Passed (it is acceptable to
have a Warning for the Windows Firewall rule).
10. Click Next.

11. Select the SQL Server Feature Installation radio button and click Next.

12. Select the following features:
Database Engine Services
Reporting Services
Management Tools-Basic
Management Tools-Complete
13. Click Next.

All rules should have a Status of Passed or Not applicable.
14. Click Next.

15. Select the Default instance radio button and all other entries in the default state.
16. Change the drive letter of the Instance root directory to the drive letter of the location of the default
database.
17. Click Next.

18. Verify that the requirements have been met and click Next.
19. Make the following changes:
Change the Account Name to NT AUTHORITY\SYSTEM (use the pull-down menu) for SQL Server
Agent, SQL Server Database Engine, and SQL Server Reporting Services.
For the SQL Server Agent change the Startup Type to Automatic .
Leave all other settings at the default.
20. Click Next.
The following screen will appear:

21. Make the following changes:
Select Mixed Mode (SQL Server authentication and Window authentication)
Enter VPM@dmin1 as the password for the sa account.
Leave all other entries on all tabs at the default values.
22. Click Add Current User to add the current user as a SQL Server Administrator.
23. Click Next.
24. Select the Install the native mode default configuration on the Reporting Services Configuration screen
.
25. Click Next.

26. Verify that all of the rules have either Passed or are Not applicable.
27. Click Next.

28. This is a summary of all the SQL Server settings. Review the summary and if it is correct, click Install.
29. After installation is done, you will see the Complete screen. Click Close.
30. Open SQL Server Management Studio (SSMS)
31. Enter the following:
Server Type: Database Engine

Server name: localhost
Authentication: SQL Server Authentication
Login: sa
Password: VPM@dmin1
32. Click Connect.
33. Expand the Security folder, right-click on the Logins folder, and select New Login.
34. On the Login screen, enter BUILTIN\Administrators for the Login name.
35. Click on Server Roles in the Select a Page window, and enable the sysadmin checkbox.
36. Click OK. If you get an error about not being able to find the BUILTIN\Administrators login name, click on
General in the Select a Page window and click the Search button next to the Login name field. Select the <C
omputerName>\Administrators account and change <ComputerName> to BUILTIN and click OK.
Enable the xp_cmdshell Extended Stored Procedure in SQL Server

TruView requires the xp_cmdshell extended stored procedure in SQL Server 2008 to be enabled. This extended
stored procedure runs operating system commands from within the database engine.
To allow advanced options to be changed:
1. In the SQL Server Management Studio, select New Query.

2. Enter the following commands:
--To allow advanced options to be changed
EXEC sp_configure 'show advanced options', 1
GO--To update the currently configured value for advanced options
RECONFIGURE
GO
– To enable the feature
EXEC sp_configure 'xp_cmdshell', 1
GO
--To update the currently configured value for this feature
RECONFIGURE
GO
3. Select Execute.
Run the TruView Prerequisite Tool

Run the TruView Prerequisite tool prior to installing TruView Server software. The prerequisite tool checks for
software components required by the TruView server and launches installation for these software components. The
prerequisite installer also configures SQL Reporting Services for the TruView server. The tool
(TruView-Prerequisite.exe) can be found on the installation CD in the \ServicePacks directory.
The tool performs the following functions:
Verifies that the PC is running the correct system software and version (OS version, .NET, MS-SQL). If an
update is needed and available on the CD, the tool will load it.
Verifies TruView Server language and regional settings.
Configures MS Reporting Services. If system changes have been made that impact Reporting Services, the
tool will attempt to fix the problem.* The Microsoft ASP.NET 4.0 and the Sun Microsystems Java 2 Standard
Edition 7.0 Runtime Environment are automatically installed as part of the server software installation
procedure. For a full list of required software included on the TruView CD, see ServicePacks_Description.htm
in the ServicePacks folder.
Required software not included on the TruView CD (such as the Windows Operating System and SQL
Server) must be provided by the person performing installation.
To run the prerequisite installer:
1. Insert the TruView CD into your computer. The readme is shown.

2. From Windows Explorer, navigate to the CD drive and open VisualPerformanceManager-Prerequisite.exe i
n the ServicePacks folder.
2.
Note
Always launch the prerequisite installer from the TruView CD. If you have copied it to another location, make
sure that you copy all service pack files included in the source directory.
3. Click OK to begin prerequisite software installation. The installer launches required software component
installations in the order in which they must be installed. Follow on-screen messages to launch software
component installations. Refer to the following sections for specific installation steps for software
components.
4. Run the prerequisite installer until a message indicates that the server is ready for the new server installation.
No manual configuration of SQL Server Reporting Services is required.
Install TruView Server Software

To install the TruView server software:
1. Insert the TruView CD into your computer.

2. Close all programs.
3. Run D:\server\setup.exe (where D: is the drive letter of your CD-ROM drive, network directory, or installation
path).
4. On the Welcome screen, click Next.
5. On the License Agreement screen, accept the license agreement and click Next.
6. On the Setup Type screen, select Complete. This installs the software and database. (If you are accessing
the CD from another computer as a network drive, be sure that the drive is set to reconnect at login, or else
your installation may not complete properly.) Click Next.
7. On the Choose Destination Location screen, select a drive location for the TruView program installation
and click Next.
8. On the Database Location and Size screen:

a. Enter the sa account password (VPM@dmin1)
b. Change the path to the drive with the most available free space.
c.
8.
c. Click Next.
9. The TruView databases are not present in SQL Server. To create the databases, click Next.
Note
To reduce the installation time, you can reduce the database sizes from the default settings. Also, make sure
that databases are installed on the second partitioned drive created during Windows installation and specified
during SQL Server installation.
10. Follow the prompts to install the Adobe Acrobat Reader.

11. Follow the prompts to install the the Sun Java Run-Time Environment.
12. Click Finish to restart the computer.
After installation, note:
The PAC is installed during the server software installation. There is no need to install the PAC
separately.
In addition to standard SQL Server administrator logins, do not remove the BUILTIN\Administrators
login and any logins created by TruView, including: vup1, VUpAdmin, WebAdmin,
UptimeSelectReporter, and logins for each domain (for example, domain_name and
domain_nameRprtr logins).
The two Windows services for TruView, the TruView Server and Visual UpTime Select Web
Application services, run by default under the Local System account. You can run these under a local
user or domain account in the Administrators group.
To use an alternate account, modify the services' Log On tab properties after you complete installation
and restart the computer. The Administrators group must also have write access to the folders used by
TruView. These include:
Config and Log folders for TruView Server and Visual UpTime Select Web in: C:\Documents
and Settings\All Users\Application Data\Fluke Networks
The TruView Server folder and its children in: <Drive>:\Program Files\Fluke Networks
To install TruView Server Health:
1. When the TruViewServerHealth Installshield Wizard appears, select Next.

2. Accept the license terms.
3. Enter customer information and select Next.
4. On the Custom Setup screen, select Change.
5. Change the Install to drive letter to a drive other than the system drive and select OK.
6. Select Next (3 times).
7. Select Install.
8. Select Finish and then reboot the server.
Apply Windows Security Updates

After the TruView databases are created, you must apply critical security updates to Windows and IIS.
To apply updates:
1. See http://windowsupdate.microsoft.com/ and under the Product Updates section, get all the Critical
Updates.
2. When you finish, reboot the server.
After installing Windows Server, you can run Security Configuration Wizard (SCW), an attack surface reduction tool
added with Service Pack 1. For more information, see Security Configuration Wizard for Windows Server at the
Microsoft Support website.
Warning
Review the firewall configuration and open ports required by the server. See Firewall Configuration. Make
sure that Windows Firewall is not blocking the ports mentioned in these sections.
For suggestions on increasing the security level of the TruView server, see the TAC Knowledge Base.
Optimizing TruView Server Performance

You can improve TruView server performance by using an external storage array, optimizing the placement of
database files, and increasing RAM. These enhancements will increase the number of TVPs that the TruView server
supports and dramatically decrease the amount of time it takes for data aggregation. In addition, overall database
performance for TVP, ASE, and TVF integration will improve.
You have the following options for improving TruView server performance:
Increase the TruView server memory to 8 GB or more—This option significantly improves the performance of
TVP data aggregation and overall database performance.
Use an external storage array such as the Dell PowerVault MD1000, a 15 bay external SAS/SATA storage
array included with the TruView 300 server.
Move tempdb database files to a better drive and relocate databases if necessary.
Optimize existing storage drives.
Combine these options to further enhance performance. For example, increasing RAM and using an external
storage array will dramatically improve data aggregation for TVPs, increase the number of TVPs supported, and
contribute to overall improvements in database performance.
For detailed information, see the TAC Knowledge Base article, "Optimizing TruView Server Performance".
Upgrading the Server

Topics include:
Upgrade Checklist
Preparing the Server Upgrade
Upgrading TruView
Upgrading a System with a Backup Server
Upgrading PAC and ASE Software
Upgrading the TVP or TVF
Optimizing TruView for Upgrade Users
Note
Your TruView system must be at version v8.0, v8.1, or 8.3 prior to installing v9.0. Refer to the Software Installation
Guide for each version for information on upgrading your system to the appropriate version.
Upgrade Checklist
To upgrade to TruView 9.0, follow the tasks listed in Upgrade Task Checklist.
Upgrade Task Checklist
Task See...
Your TruView system must be at version v8.0, v8.1, or If your TruView version is less than v7.1, refer to the
8.3 prior to installing v9.0. v7.1 (or later) TruView Software Installation Guide for
information on upgrading your system
Make sure that your server computer meets the TruView System Requirements
hardware and software requirements for a TruView
server.
Run the server prerequisite installation tool. This See Run the TruView Prerequisite Tool in Software
notifies you of missing software before installing Installation
TruView software.
Determine requirements, inventory your TruView Upgrading to TruView v9.0

system, repartition your disk if necessary.
Determine whether you need to rename the server. If Appendix B, "Renaming the Server," in the TruView
so, complete the upgrade and then rename the server. System Administration Guide
Verify from the TruView server (previous revision) that Verifying ASE Data Collection and Database
ASE data collection and database maintenance have Maintenance
been completed recently. You can collect ASE data
collection and perform database maintenance from the
PAC through Network Configuration or Domain
Options.
Back up the TruView databases and configuration Backing Up TruView Databases

before upgrading. The TruView server can be active
and accessible to system client users during the
database backup. However, services are stopped and
unavailable to clients during an upgrade. Notify client
users of this in advance.
Install v4.0 .NET Framework Software Installation
Make sure that the xp_cmdshell stored procedure is Software Installation

enabled in SQL Server 2005.
Configure Windows Services. Make sure the Windows Configuring Windows Services for Upgrade
Installer service is not disabled. Stop and disable the
TruView Server and Visual UpTime Select Web
Application services.
Upgrade server software. For systems with backup Upgrading_TruView

servers, see Upgrading a System with a Backup Server
If provisioning TVFs or TVPs in TruView, enable the Upgrading_TruView

Windows NTP Server.
Upgrade client software. Upgrading PAC and ASE Software

Complete setup and manage licenses. If a permanent "Managing Licenses in an Upgrade System," in
VoIP feature license is enabled at the time of the "Configuring Server Settings," in the TruView System
upgrade, VoIP will be enabled on all active Administration Guide.
VoIP-capable ASEs on a server. For domain licensing,
the checkbox will be enabled for all VoIP-capable ASEs
if the domain has a permanent VoIP license enabled.
If the VoIP feature is enabled, then the VoIP Call
Quality CQ MOS, LQ MOS, and R-Factor report
settings will be available by default in the Server
Administration Report Settings tab. These can be set
independently.
If you have applied a custom logo in TruView, when the In the TruView System Administration Guide:
new version is installed, reapply the custom logo using
"Configuring General Settings," in "Configuring
the Server Administration tool.
Server Settings"
"Changing the Logo for Reports on a Domain," in
"Managing Domains and User Accounts"
Preparing the Server Upgrade

Before upgrading the TruView server software, perform the tasks as described in the following subsections.
The time required to perform a server software upgrade is based on the amount of data in the databases, the
processing speed and RAM of the server, and the type of tape drive system used. In addition, you must back up
your databases before you begin the upgrade. See Time Estimates for Server Upgrade for database backup and
server upgrade time estimates.
Time Estimates for Server Upgrade
Installation Task Estimated Time Required
Back up databases 15 minutes to two hours (varies with database size)
Upgrade server software 15 minutes to four hours (varies with database size, at
least one minute per domain)
To reduce the amount of data in the short term (VUpTime) database, and therefore the amount of time a database
backup requires, you may perform database maintenance from the PAC before you start. To reduce the amount of
data in the long term (VUpTimeLT) database, in database maintenance on the PAC, select the option to remove
deleted network elements from reporting data. In addition, delete any unnecessary domains using Server
Administration.
Warning
Use these options to reduce the amount of data in the databases only if you are certain you do not need the
extra data for historical purposes.
For information about database maintenance and deleting domains, see the TruView System Administration Guide.
Requirements
In order to determine the amount of space needed on the system partition (C: drive), you need to evaluate your
current hardware configuration. Microsoft recommends a minimum of 32 GB of space for Windows Server 2008 R2
Standard and 6 GB of space for SQL Server 2008 R2 Standard. Also, Windows automatically sets a swap file size
equal to the total amount of physical memory installed in the machine. The size and location of the swap file can be
changed, but that is not recommended. NETSCOUT recommends an additional 20 GB of space to allow for the
installation of TruView and Windows Updates.
Use the following formula to calculate the amount of space needed on the system partition:
Total amount of space needed = 32 GB + 6 GB + 20 GB + amount of physical memory
Use the following Microsoft link to help determine the appropriate swap file size and monitor its usage: http://support.
microsoft.com/kb/889654.
The most physical memory that you can install in Windows Server 2008 R2 Standard is 32 GB, therefore you will
need no more than 90 GB of space. While it is possible to perform this upgrade with less space allocated to the
system partition, NETSCOUT does not support this configuration.
Upgrading TruView
The TruView server software upgrade may require that you restart your server computer. Close all programs before
installing. The upgrade process needs files on the CD after the reboot. If your CD drive is on another computer on
the network, that drive must be automatically mapped on reboot.
Notes
PAC software is installed with the TruView server. You cannot install or uninstall the PAC separately on the server
computer.
When using a stand-alone Web server, set it and the TruView server to the same time zone, even if they are located
in different time zones.
To upgrade the server software:
1. Make sure that the server has the date and time set to its local time zone. Select Start > Settings> Control
Panel > Date/Time to verify the date and time settings.
2. Insert the new TruView CD. The Readme is shown.
3. In the Windows Start menu, select Run, type d:\Server\setup.exe (where d: is the drive letter of your
CD-ROM drive, network directory, or installation path), and press Enter.
4. Click Next to continue the installation. Accept the License Agreement.
5. In the Select Setup Type window:
For a server installation, select Complete (the default setting).

For a Web server installation, select Web Server.
6. Reboot your system when prompted at the end of installation.
Note
To ensure timely data collection from ASEs and continuous data availability to clients, leave server services
running at all times other than during an upgrade. The upgrade continues after rebooting.
7. If you are provisioning TVFs or TVPs with TruView, enable the Windows NTP Server to synchronize the time
7.
between the server and TVFs. Open the TruView Server Administration program. Make sure that the server
icon in the Server Administration window is green. If it is not, select Action > Refresh Status. If polling does
not change the icon to green, call technical support at your TruView vendor.
8. To log in to the Server Administration tool, use the new administrative user. Username: TVadmin. Password:
tv.
Warning
Once you log on as the TVadmin user, change the password immediately to prevent unauthorized
access to this account. Save the new password in a secure place.
9. After the upgrade, check the license status.
For more information about managing licenses in an upgrade system, monitoring servers, and establishing
users, see the TruView System Administration Guide.
Verifying ASE Data Collection and Database Maintenance
Verify ASE data collection for all domains on your server before the upgrade as well as after the upgrade.
Note
Data collection and database maintenance for all domains on the server may take from one to eight hours. The time
required depends on the configuration of your networks, the number of domains on the server, the speed of the
ASE-to-server connection, and the server machine's processor speed. Check the log file to determine how long
these tasks have taken in the past. It is common practice to run Identify ASE before starting the data collection.
To verify ASE data collection and database maintenance for all domains:
1. In Server Administration, select the server.

2. Select Action > Collect Data. Click OK.
3. In Server Administration, select the server.
4. Select Action > DB Maintenance. Click OK.
For more information, see "Maintaining the Databases," in the TruView System Administration Guide.
Backing Up TruView Databases
Back up the TruView databases before upgrading. The TruView server can be active and accessible to system client
users during the database backup. However, services are stopped and unavailable to clients during an upgrade.
Notify client users of this in advance.
Back up the following databases:
VUpTime—TruView short term database

VUpTimeLT—TruView long term database
VUpTimeNF—TVF database
VUpTimeDC—Application Performance Management database
VAdmin—TruView server configuration database
fnet_portal—Web portal database
ReportServer—Reporting Services database
ReportServerTempDB—Reporting Services temporary database
master—SQL Server master category of users
msdb—Jobs and alerts scheduled in SQL Server
For information about backing up Reporting Services databases, see Microsoft SQL Server 2005 Reporting Services
documentation on the Microsoft MSDN website.
The total time required to back up the databases may be up to two hours. Label the backup tapes "TruView v x.x –
Before Upgrade to TruView v y.y".
For more information, see "Maintaining the Databases," in the System Administration Guide.
Configuring Windows Services for Upgrade
Before you upgrade the TruView server software, configure Windows Services as described below.
To configure the Windows Services:
1. From the Windows Start menu, select Run and type: services.msc
2. In the Services control panel, double-click the Windows Installer service. Make sure that the Startup Type is
set to Manual or Automatic, and not set to Disabled. Click OK to save the change and return to the
Services control panel.
3. Double-click the TruView Server service. Set the Startup Type to Disabled. Under Server Status, click Stop
. Click OK to save the change and return to the Services control panel.
4. Double-click the Visual UpTime Select Web Application service. Set the Startup Type to Disabled. Under
Server Status, click Stop. Click OK to save the change and return to the Services control panel.
5. Close the Component Services window.
Upgrading a System with a Backup Server

You cannot upgrade a server while it is operating as a backup. Upgrade the primary server first and then upgrade
the backup server.
To upgrade your backup system when using a backup server:
1. Upgrade the primary server to the new version of TruView. See Upgrading TruView.
2. In Server Administration on the previous version server, set up licenses. For example, turn on new features or
switch to domain flexible. For more information, see the "Configuring Server Settings, in the System
Administration Guide.
3. To shorten the time to upgrade the backup server, delete the domains on the backup server prior to
upgrading. Because the data is loaded from the primary server, the current contents of the backup server
need not be upgraded.
4. Upgrade the backup server to the new version of TruView. Restore data from primary to backup server,
transferring the keys and features to the backup server.
Upgrading PAC and ASE Software

The PAC client software must be at the same version level as the TruView server for system access. To upgrade,
install the PAC software. For more information about installing the PAC software, see Installing PAC Software.
When you install the PAC or server software, the latest available ASE software files are also installed. You can
update ASEs on your network with the latest software whether you are a new or upgrade customer. You can also
download new ASE software from the PAC. Whether you update ASE software depends on the software version
loaded on the ASEs when they were purchased, and whether your WAN service provider (if you are a subscriber)
has already updated the ASEs.
Note
Updating the ASE software version requires an ASE reboot. To upgrade ASE software, your user account must
have that permission granted in Server Administration.
For information about updating ASE software, "Network Configuration" in the PAC User Guide.
Upgrading the TVP or TVF

When upgrading your TruView Flow Appliance or TruView Flow Appliance, note the following:
Your TruView Flow Appliance(s) and TruView Flow Appliance(s) must be at the same software revision as
the TruView Server.
You can either upgrade or reimage your TVF. You can only reimage your TVP. An upgrade installs a new OS
and installs the new application. Application data, network data, and user configuration data remains intact. A
reimage erases the system hard drive and installs a new OS and application. All data is lost.
To upgrade/reimage your TVF/TVP, you can use the System Recovery DVD that came with the new release,
or you can download the TVPSR-CentOS.iso (TVP) or TVFSR-CentOS.iso N(TVF) image from
the NETSCOUT Customer Support website (you must be a gold member).
If you use the System Recovery Disk, follow the instructions that are displayed when you run the recovery
application.
If you download the image from the website, you must burn the image to a DVD and use it to
upgrade/reimage the appliance.
To download and upgrade/reimage your TVP or TVF software:
1. Open a Web browser and go to enterprise.netscout.com.

2. Sign in as a Gold Member.
3. Under the Downloads and Updates link, use the Select a registered product drop-down menu and select
TruView for an TVP update, or NetFlow Tracker for an TVF update.
4. Select the appropriate update image and follow the instructions to download the zipped file.
5. Unpack the zip file to its own directory. There should be a single .iso file in the directory.
6. You must burn the image to a DVD-R media (CD, DVD-RW, and others will not work).
Verify that your media creation software supports burning DVD image (.iso) files. Use "verify after write"
option in the media creation software if available.
7. After you have created the DVD, insert it into your TVP or TVF, reboot the appliance and follow the
instructions for upgrading/reimaging the appliance.
Optimizing TruView for Upgrade Users

Because the TruView Web portal provides an expanded platform for viewing data, users upgrading from Visual
UpTime Select will find a new user interface. Topics in this section include:
Administrative Tasks for Upgrade

Applying User Group Templates after an Upgrade
User Options for Upgrade
Administrative Tasks for Upgrade
Upon upgrade, administrators can choose what feature modules to make available and how users interact with
TruView. Options include:
Remove Network Performance Management and Application Performance Management features if you do
not have TVFs or TVPs. In Server Administration for a domain, under the Configuration tab, you can turn off
NPM and APM feature support. For more information, see "Managing Domains and User Accounts," in the Tr
uView System Administration Guide.
Set up access control for user groups. In Server Administration, select a group. Under the Group
Capabilities tab, you can set Portal Administration for groups who will access Panel Permissions and User
Group Templates administrative tools on the Web portal. You can also set TVF Reports and TVF
Configuration capabilities if applicable. For more information, see "Managing Domains and User Accounts" in
the TruView System Administration Guide.
In the Panel Permissions administrative tool on the Web portal, review panel permissions for user groups.
By default, all existing groups will have all four default tabs and all panels available.
In the User Group Template administrative tool on the Web portal, set up template pages with specific data
views and assign these to groups based on user roles and tasks. For example, a service provider may set up
different template pages for administrators, data center workers, and service subscribers.
If you have existing templates created in your current TruView version and you want to update these, see Ap
plying User Group Templates after an Upgrade.
If you have TVFs deployed on your network, configure these and the devices and interfaces they monitor.
Note that all licenses from Visual UpTime Select are automatically applied in TruView. The Application
Performance Management feature and the Network Performance Management feature each require a
license.
Applying User Group Templates after an Upgrade

On an upgrade, existing user site maps and user group templates are maintained. New user group templates
included in the TruView upgrade are not applied. As a result, new pages such as the Application Performance tab
are not present in a user's site map when they log in.
To get the new pages, you must load the TruView portal template file (portal_template.xml) to the Web portal. This
file is installed with TruView software on the TruView server. It defines the pages for the given release. On a new
installation, it is loaded when the Web portal is run for the first time. After that, it is ignored.
The portal_templates.xml file contains the page layout and content and defines the site map for each user group in
the system. It contains each tab name, the pages within the tab, and the panels on each page of the site map. It also
has properties that control whether the user can edit or delete the page from the site map. This enables
administrators to create "read-only" page configurations that users cannot modify.
Upgrading Templates for the Default Groups
The portal_templates.xml file contains templates only for the default groups: Administrators, Advanced Users, Basic
Users, and Domain Administrators.
To upgrade templates for default groups:
1. Copy the portal_templates.xml file on the TruView server to a location accessible via your browser. The
default location on the server is:
C:\Documents and Settings\All Users\Application Data\Fluke Networks\Visual

UpTime Select Web\config\portal_templates.xml
2. On the Web portal, select to Admin > User Group Templates.

3. Click Import.
4. Select portal_templates.xml.
If the customer has added user groups to the system and you want to apply the new templates to those
groups see below.
To replace the templates for a subset of the groups, edit the portal_templates.xml file and remove the
templates for the groups you do not want to update.
Upgrading Templates for Non-Default User Groups
If an administrator has added user groups to the system in addition to the four default groups, then you must update
the templates for those new groups. You have two options:
Manually edit the portal_templates.xml file and add template entries for the new groups. Copy and paste from
one of the default groups whose layout most closely matches the new group.
In the User Group Templates tool, click Copy from another template.
Merging Existing User Group Templates with New Portal Templates
If an administrator has modified the templates for the default groups and wants to merge those changes with the
new pages that are contained in the upgrade, then you must manually edit the portal_templates.xml file.
To merge existing and new templates:
1. In the User Groups Templates tool, export the current portal templates and save it to a file.
2. Copy the portal_templates.xml file from the TruView server to a file.
3. Copy the page definitions that you want to keep from the first file and place them in the second file.
4. Update the second file.
Note
You cannot merge a new user group template with a user's customized site map. You must accept the new user
group template and manually re-create pages.
Importing User Group Templates—How it Works
Template Behavior
When a user logs into the system for the first time, the group template for the group to which the user belongs is
copied to the user's site map. The user can then add or modify custom pages that do not affect other users or
groups. Those changes are private.
The administrator can change a group template, in which case users in the group are notified the next time they log
in that a new site map template is available. When a user of a group with an updated template then logs into the
Web portal, he or she is prompted to:
1. Replace his or her site map with the updated template,

2. Ignore the update and keep the existing site map
or
3. Be reminded the next time they log in. If the user chooses the first option, then any customized pages and
tabs that the user created are lost. If the modified group template was read-only, a message indicates that the
site map will be updated.
Importing Templates
When a portal_templates.xml file is imported via the User Group Templates administrative tool, only templates for
the groups named in the XML file are updated. For example, if the file has a definition for a group named
"Administrators" and that group exists in the TruView server, then the template for that group is loaded. If the
portal_templates.xml file has a definition for a group that is not in the TruView server, then the template for that
group is not loaded. The portal_templates xml file may contain groups that are not in the system, or it may contain a
subset of groups in the system.
For more information about portal templates see "Administration Tools," in the TruView User Guide.
User Options for Upgrade
As an upgrade user, you will find the following differences between the TruView Web portal interface and Visual
UpTime Select:
By default, the TruView server URL opens to the Web portal instead of the server's Visual UpTime Select
home page.
In the Web portal, the UpTime Select tab includes the Service Summary, Application Summary,
Troubleshooting, VoIP Summary, and Traffic Capture applications. It does not include Reports or Tools.
The Reports tab includes all available reports.
To access Administration tools, click the Admin link in the toolbar.
To access the domain list, click the Domain link in the toolbar.
To access context-sensitive help, click ? at the application level.
To access user preferences, click User Settings in Visual UpTime Select.
You can modify the Web portal interface or access Visual UpTime Select through its stand-alone interface.
Set up Visual UpTime Select as your Web portal home page. To do so, select UpTime Select and then
select Edit Page. Under Page Properties, select Home Page.
Use the arrow buttons on the Web portal interface to expand the viewing area.
Access the stand-alone Visual UpTime Select Web client interface. To do so, add /uptime.htm to the server
URL and select Start Visual UpTime Select from the server's page.
Firewall Configuration
TruView deployment in a WAN service provider environment can present security challenges not present in a WAN
service subscriber environment. This chapter describes recommended configurations for servers protected behind
network operation center (NOC) firewalls. These security settings are designed to simplify server administration
while maximizing network security.
Within a typical WAN service provider NOC, a firewall provides added security between the service providers
servers and open (publicly registered) IP access by the service subscribers. Therefore, each server has at least two
network connections:
One connection provides access to the service provider's closed ASE collection network using private IP
addressing (to simplify assignment and conserve registered IP address space).
The other connection provides access to the open client access network using publicly registered IP
addressing.
Setting Server Port Numbers

By default, the server uses random TCP port numbers for its side of the communication with PACs. (The Web portal
uses port 80 when it connects to the server.)
To simplify firewall configuration, set these port numbers to fixed values using the Windows Registry on the server
computer.
To set the port numbers used by the RPC server:
1. Click Start > Run, enter regedit and click OK.

2. If not already expanded, open the sub-tree folders in the left pane of the Registry Editor window, and then
expand the HKEY_LOCAL_MACHINE sub-tree.
3. Continue expanding through the key and sub-key registry folders through the following path:
HKEY_LOCAL_MACHINE\Software\Fluke Networks\UpTime\RPCServer\
4.
4. Click the RPC Server folder, and select Edit > New > DWORD Value. The Registry Editor creates a new
value in the RPC Server folder.
5. Enter Port as the name of the new value. Double-click the value. The Edit DWORD Value dialog appears.
6. In Value Data, enter the port number you want to use for the RPC server. This value must be a decimal
integer between 1026 and 65535.
7. In Base, select Decimal. Click OK.
8. Exit from the Registry Editor.
9. Configure your firewall to allow incoming access to the server's RPC server on the specified port.
10. Restart the TruView services.
Firewall Port Settings

If your system includes firewalls between servers, the ASE data collection network, Web servers, and TruView
clients, then you must configure these firewalls to match the communication port settings shown in the Firewall Port
Settings table.
Notes
All communication to ASEs goes through the server.

If Windows Firewall is enabled on server, make sure all ports listed in Firewall Port Settings are open. If you
cannot connect to the server, turn off the firewall and test the connectivity. Once connectivity is established,
reconfigure the firewall settings.
Open the secure and non-secure TCP and SSH ports between the TruView server and TVPs. By default
these ports are 80, 443, and 22 but they can be reconfigured on the TVP.
For communication between the server and the PAC and Web server, you can configure the port range for
proxied SNMP and TFTP communication and set the RPC port to static by modifying a registry setting (the
default is dynamic). See the TAC Knowledge Base for more information.
When using secured ASE communications, if a firewall is configured to block Transport Layer Security (TLS)
communications to an ASE, you may see response time issues when identifying ASEs on the PAC. To
resolve this, open port 2359 on the firewall.
Firewall Port Settings

Settings Application Layer 4 Port Source Destination
Between...
Web Client and HTTP TCP 80 Web server

Server
Web Client and HTTP TCP 80 Web Web server

stand-alone
Web Server
PAC and Server Portmapper TCP 111 PAC server
RPC TCP <selected port> PAC server
Proxied SNMP UDP 1024-65535 PAC server

and TFTP1
PAC UDP 1024-65535 server PAC

Notifications2
ASE and Server SNMP UDP 161 server ASE
SNMP Traps UDP 162 ASE server
TFTP3 UDP 69 server ASE
SSL TCP 2359 server ASE
ASE and Client Telnet4 TCP 23 client ASE
SSH4 TCP 22 Web ASE
TVP and Server Non-secure TCP TCP 80 server TVP

or stand-alone
Web Server
Secure TCP TCP 443 server TVP
TVP and Client SSH TCP 22 client TVP
Web TCP 80 client TVP

Administration
TVF and Server TCP TVF port server TVF

or stand-alone configured for
Web Server5 Web access
NTP Time UDP 123 Internet time server
Synchronization server
Remote Server SQL Server TCP 1433 Remote Server server

Administration Administration
and Server PC
Microsoft RPC TCP 135

endpoint
mapper
Microsoft RPC TCP <selected ports>

over port
numbers
returned by
endpoint
mapper6
Server and Proxied SNMP UDP 1024-65535 Web server

stand-alone and TFTP1 server
Web Server
Microsoft RPC TCP 135

endpoint
mapper
Microsoft RPC TCP <selected ports>

over port
numbers
returned by
endpoint
mapper5
SQL Server TCP 1433
.NET Remoting TCP 8086
WCF Services TCP 8005

1 You can
configure and
limit the proxied
SNMP and
TFTP port range
via registry
settings. For
more
information, see
the TAC
Knowledge
Base.
2 The PAC still

operates if these
ports are
blocked, but
"Collect Data
Now," "ASE
Setup," and
"Identify ASEs"
take longer.
3 ASE models
200-203 switch
UDP ports after
the initial
request is
received on port
69, so that
subsequent
traffic uses UDP
1024 or above
on the ASE side.
4ASEs support
SSH or Telnet
connectivity, but
not both at the
same time.
5 To use HTTPS
for all TruView
server to TVF
communication,
use port 443 or
8443.
6 You can
configure port
numbers for
RPC via registry
settings. For
more
information, see
the TAC
Knowledge
Base.
PAC Software
Topics include:
Installing PAC Software

Uninstalling PAC Software
Installing PAC Software

On a TruView server provided by NETSCOUT, the PAC software is pre-installed. For an upgraded server, PAC
software is upgraded when you install the server software.
You can upgrade PAC software locally from the TruView CD or remotely by using your Web browser. You can also
install or upgrade the PAC software on a separate computer.
Note
You can upgrade PAC software from any previous version directly to the current version. The upgrade appears as a
new installation into the same folder that has the current PAC.
Installing PAC Software from the CD
Warning
If you are upgrading the PAC from a previous release, do not change the existing location for the
installation of the PAC software.
To install the PAC software locally:
1. Make sure that your user account has administrator privileges. (You can use the user name administrator.)
2. Insert the TruView CD into your computer and select Start > Run.
3. In the Run dialog, type x:\pac\setup.exe (where x: is the letter of your CD-ROM drive) and press Enter.
4. The Welcome screen appears, followed by the License Agreement. Accept the license terms and click Next.
5. In the Choose Destination Location screen, click Browse to install your PAC software in a directory other
than the default directory shown.
Note
For an upgrade installation, you must install PAC software in the same location as the existing TruView PAC.
6. Click Next to begin copying PAC software files and ASE software files.
7. If the setup program needs to reboot your system, a message prompts you to reboot. Do not remove your
CD prior to rebooting. Click Yes to restart your PC.
8. Make sure that the PAC has the date and time set to its local time zone. Select Start > Settings > Control
Panel > Date/Time to verify the date and time settings.
Remotely Installing PAC Software
You can install the PAC software from a remote location using your Web browser.
To install the PAC software remotely using a Web browser:
1. Point your Web browser to the IP address of your TruView server.

2. Access the PAC software download:
From the Web portal interface, click Support. From the Support page, click Download UpTime Select
PAC Software.
From the standalone Visual UpTime Select Web client, type the following URL in the address field:
http://<TruView server name or IP address>/uptime.htm
From the server's Visual UpTime Select home page, click Install PAC Software from the Web.
3. When the download is complete, open your temp directory (or the directory in which you downloaded the
software) and double-click the file PACw32.exe to launch the PAC setup. If you are upgrading the PAC from
TruView, follow steps 4 through 8 in the section Installing PAC Software from the CD.
4. Verify that the PAC computer has the date and time set to its local time zone. Select Start > Settings >
Control Panel > Date/Time to verify the date and time settings.
Uninstalling PAC Software

You can uninstall PAC software using Windows Add/Remove Programs.
To uninstall PAC software, your logon must have administrator privileges.
Note
If you uninstall the PAC software and install an older version in its place, the older version may not work
properly. (This happens when Windows does not replace shared components from the newer PAC software
with components from the older version.) If you install an older version and it does not work, uninstall again,
reboot, remove any remaining files in the directory where the PAC was installed, and try to install the older
version again.
To uninstall PAC software from a non-server machine:
Select Start > Settings > Control Panel.

Double-click Add/Remove Programs.
Select Visual UpTime Select PAC.
Click Add/Remove, and click Yes to confirm the deletion.
Server Setup
Once you have purchased a TruView server from NETSCOUT or completed software installation of a server as
explained in Software Installation, you are ready to complete server setup.
Topics include:
Starting the TruView Server

Requesting Your Software License Key—You have 30 days after installation to request a license key.
Adjusting Security Settings
Installing Certificates
Installing Optional Server Software
Starting the TruView Server

You must ensure the TruView server's IP connectivity, set the date and time, and verify that the server software
applications are functioning normally.
Note
For new TruView servers, see the System Administration Guide for system administration tasks, such as
administering security, applying server-wide settings, adding and configuring domains, and provisioning ASEs after
you have set up your server.
From the Server Administration program, you can check server status, add users, configure licensing, users, and
group permissions, and perform other administrative tasks.
When you close the Server Administration program, servers are not monitored. TruView services, however, continue
to run, and the server continues to collect ASE and TVF data. In addition, Web portal users can still connect to the
server. For more information, see the System Administration Guide.
Checking Server Status in Server Administration
To set up the server:
1. Connect and power on the server.

a. Connect a keyboard-video-mouse (KVM) switch or a mouse, keyboard, and monitor to the server.
b. Using the supplied Ethernet cable, connect the server to your LAN.
c. Power on the server and log in. The default Windows login name is vuptime. The default password is
1.
c.
Visual1.
2. Set the date and time locally or to an NTP server:
a. To set time locally, right-click the Windows clock. Select Adjust Date/Time to view or change the Date
& Time settings to the local time
b. To synchronize the local date and time with an Internet time server, right-click the Windows clock.
Click Internet Time and then define the IP address of the local NTP server.
Note
It is highly recommended that you use an NTP server to synchronize your TruView server, TVP, and
TVF devices.
3. Set the TCP/IP address:

a. Select Start > Settings > Network Connections > Local Area Connection .
b. On the General tab, click Properties. Select Internet Protocol (TCP/IP).
c. Click Use the following IP address. Specify the server's IP address, subnet mask, and default
gateway. If DNS is available, specify the DNS server(s) IP address.
d. Click Advanced and set other values appropriate for your network.
e. Click OK.
f. If prompted, restart the server.
4. Confirm network connectivity:
a. Select Start > Programs > Accessories > Command Prompt.
b. Ping a router or device in your network to verify IP connectivity. For example, enter: ping
xxx.xxx.xxx.xxx. If the Ping test succeeds, your server is accepting active connections.
5. Verify that you can log in to the server:
a. Open a Web browser and enter the IP address of the server. The TruView login screen is shown.
b. Enter the login name and password. The default login name is TVadmin. The default password is tv.
c. Log out.
6. Run the Server Administration program:
a. If the Server Administration program is not running, select Start > Programs > Fluke Networks >
TruView Server > Server Administration.
b. Click the server icon in the Windows task bar to log into the server.
c. Accept the license agreement, and then enter the user name and password. The default login name is
TVadmin. The default password is tv.
7. Connect to the server from a remote PC:
a. Open a Web browser.
b. Enter the IP address or DNS-resolved name of the server. The login screen is shown.
c. Enter the login name and password. The default login name is TVadmin. The default password is tv. If
you can log in successfully, others users in your network can also reach the server.
8. Leave the server running at all times to ensure timely collection of data from TVFs, TVPs, ASEs, and PACs
and to ensure continuous availability of data to all clients.
9. (Optional) Review the security conventions for the server covered in "Configuring Server Settings," in the Syst
em Administration Guide.
Requesting Your Software License Key

On a new TruView installation, once you start the server software, you have 30 days before a software license key is
required. For more information about licensing, see "Configuring Server Settings," in the System Administration
Guide.
Note
To get the Server ID, run the Server Administration program (Start > Programs > Fluke Networks > TruView
Server > Server Administration). Expand the server and select Licenses. For information about default login,
see "Administering System Security," in the System Administration Guide.
Determining the Server ID
Adjusting Security Settings

SSH is enabled by default during installation and ports 80 and 443 are opened. You can close port 80 (non-secure
TCP communication) if you wish. Port settings can be modified in the Windows firewall settings.
Notes
Implement any additional policy changes one at a time and test the TruView application after each change.
This lets you back out of a change if it interferes with the operation of TruView.
Port 22 should be opened for SSH access (off by default)
Installing Certificates
SSL authentication is enabled during TruView installation and self-signed security certificates are installed. It is
recommended that you install your own secure certificates on the TruView Server.
Because the TruView server is a service that runs in a Local System context, install client certificates on the Local
System account.
You can find information on configuring SSL and installing certificates at http://www.iis.net/learn/manage/configuring
-security/how-to-set-up-ssl-on-iis.
To install certificates:
1. From the Windows Start menu, select Run.

2. Type mmc.exe. An MMC console opens.
3. Click File > Add/Remove Snap-in.
4. In the dialog box, click Add > Certificates > Add. In the Certificates Snap-in dialog, select Computer
Account. Click Next >" > Finish > Close > OK. Expand the Certificates node.
5. Click Trusted Root Certification Authorities. Right-click All Tasks > Import. At the certificate request, point
to the Root CA's certificate.
6. Click Personal. Right-click All Tasks -> Import. At the certificate request, point to the client identification
certificate.
6.
If the same certificate holds the root certificate and client certificate, then install this to both places.
Changing the TruView Central Port
By default, SSL uses port 443 for communication. To change the communication port from port 80, which is usually
blocked on systems using SSL, do the following:
1. Using Windows explorer, navigate to C:\Program Files (x86)\Fluke Networks\NodeJS\config\env

2. Copy the file file production.js to production_overrides.js.
3. Edit production_overrides.js using a plain text editor such as Microsoft Notepad.
4. Change the file as shown:
'use strict';
module.exports = {
/**
* @cfg {string} truviewProtocol the protocol that the main
IIS server is using. This can be either http or https
*/
truviewProtocol: 'http', <<<<<<<<<<< change from http to https
/**
* @cfg {number} truviewPort the port that the main IIS server is using.
*/
truviewPort: 80, <<<<<<<<<<<<<< change 80 to 443
<<<<<<<<<< Delete all below this line >>>>>>>>>>
/**
* PRIVATE do not modify below this line
*/
portalBasePath: './Portal/Portal',
localesBasePath: '../Portal/Portal/json/locales',
authenticationUrl: '/Portal/Authentication.ashx',
emailConfigUrl: '/Portal/Portal/Services/FilterData.ashx',
utilUrl: '/Portal/Portal/Services/Util.ashx',
dataBaseUrl: '/Portal/Portal'
<<<<<<<<<< Stop deletion >>>>>>>>>>
};
The resulting file should look like this:
'use strict';
module.exports = {
/**
* @cfg {string} truviewProtocol the protocol that the main
IIS server is using. This can be either http or https
*/
truviewProtocol: 'https',
/**
* @cfg {number} truviewPort the port that the main IIS server is using.
*/
truviewPort: 443
};
5. Save the production_overrides.js file.
6.
6. Restart the TruView-NodeJS-Application-Server service on the TruView Central appliance.
Installing Optional Server Software

This section describes how to install a TruView Web server on a separate computer and Server Administration on a
remote workstation.
Installing a Stand-Alone Web Server
The TruView Web Server comes installed on the TruView server computer. You can also install the TruView Web
Server on a stand-alone server. This computer must meet the requirements specified in Stand-Alone Web Server
Requirements in TruView System Requirements.
Once you install the Web server software, set the TruView server that the Web server will use.
To install the TruView Web server:
1. Insert the TruView CD into your computer.

2. Navigate to the Server folder and double-click Setup.exe.
3. At the Welcome screen, click Next. Accept the License Agreement by clicking Next.
4. At the Installation screen, select TruView Web Server.
5. Complete the remaining installation steps.
6. Select Start >Fluke Networks > TruView Server > Web System Management.
7. Enter the server name and IP address and click Add.
Note
The stand-alone web server's clock must be synchronized with the TruView server's clock. More than 5
minutes difference between the two server's clocks can cause the stand-alone server to crash.
Configuring Virus Scanning Software
If you have virus scanning or checking software on the TruView server, note:
To avoid disrupting Web sessions, configure the virus scanner to leave certain content alone. This is a known
issue with ASP.NET. Disable the virus scan for the following folders and their subfolders:
Exclude the Visual UpTime Select Web application directory (and all subdirectories) for reading only.
Exclude the entire .NET application cache directory (and all subdirectories) for reading and writing.
This is normally found at: \WINNT\Microsoft.NET\Framework\v4.0.xxxx\Temporary ASP.NET Files.
After disabling virus scan, open the statistics window of the virus scanner. Open the website and log in. The "last file
scanned" in the statistics window should not at any time show the paths excluded. If it does, stop the ASP.NET
worker process (aspnet_wp.exe) and try again.
The virus scanner may block SMTP port 25, which is used by SQL Server Reporting Services to send emails
for report subscriptions.
Microsoft recommends excluding or stopping real time monitoring on the virus scanner. However, it is better
to exclude real time monitoring. For more information, see: http://support.microsoft.com/default.aspx?scid=kb
;en-us;312592.
Installing Remote Server Administration
To monitor and control TruView servers from a non-server computer, install and run the Server Administration
application on that computer. This can be a PAC computer, or any PC with network access and the proper
configuration.
Prerequisites:
The target machine must be using an operating system supported by the TruView server or PAC.
To install Microsoft .NET Framework with Service Pack 1, place the TruView CD in the target machine's CD
drive. In Windows Explorer, open the ServicePacks folder on the CD and select .NET Framework 4.0
dotNetFix40_Full_x86_x64.exe. The program is self-installing.
The target machine must have an ODBC Data Source driver for SQL Server.
The target machine must have the Windows Management Instrumentation service running.
Note
Some TruView server Administration functions, such as deleting a TruView domain, require the server to
restart. To restart the server remotely, your Windows user account must have Administrator privileges on the
target server. At a minimum, your Windows user account must have permission to stop and start Windows
services. See "Administering System Security," in the System Administration Guide and the Windows Server
online help for instructions on setting security in Windows.
To install Remote Server Administration:
1. Insert the TruView CD into your computer. Locate and start this setup program: [CD-ROM drive]:\RemoteSe
rverAdmin\setup.exe
2. Click Next to begin the installation wizard.
3. On the License Agreement screen, select I accept the terms of the license agreement. To print the license
agreement, click Print. Click Next to continue the installation.
4. In the Select Setup Type window:
To install only Remote Server Administration, select Compact (the default setting). Help files are not
installed.
To install Remote Server Administration with Help files, select Complete.
5. On the Choose Destination Location screen, confirm the folder location for installation. To change the
folder, click Browse and select the folder you want. Click Next to continue.
The setup program copies the program files and creates shortcuts in the Windows Start menu.
6. Click Finish to close the setup program. To run Remote Server Administration, select Start > Programs >
Fluke Networks > TruView > Remote Server Administration.* If you are using Administrative reports from
Remote Server Administration, complete the steps in Configuring Virus Scanning Software.
Uninstalling Server Software

The computer on which server software resides is a dedicated computer that runs only the server components of
TruView. Upgrading server software overwrites older versions of the server components so that there is usually no
need to uninstall the software. You can, however, uninstall Remote Server Administration.
To remove Remote Server Administration:
1. Select Start > Programs > Fluke Networks > TruView > Uninstall Remote Server Administration .
2. Click Yes to confirm. The setup program removes Remote Server Administration from the computer.

Truview Install Software Guide

Uploaded by

Copyright:

Available Formats

Truview Install Software Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Truview Install Software Guide

Uploaded by

Copyright:

Available Formats

What are the prerequisites for installing Remote Server Administration?

What are the prerequisites for installing Remote Server Administration?

What steps are required to install Remote Server Administration?

What steps are required to install Remote Server Administration?

TruView SW Installation Guide

March 2016, Rev 1

For purposes of this EULA, the following definitions will apply:

2. TITLE, COPYRIGHT AND TRADEMARK

6. LIMITED WARRANTY AND LIMITATION OF LIABILITY

TruView System Architecture

TruView Central System Components

System Communication with Stand-Alone Web Server

Software Installation Process

TruView installation consists of these stages:

TruView System Requirements

Capacity or Requirement Recommended Configuration

Domain Support 1-250 domains

Computer Dell R720xd server or equivalent with dual Intel Xeon

Memory (RAM) 32 GB minimum

Ethernet card 10/100/1000. See Network Partitioning.

Disk Space Requirements (C: Drive)

Turnkey servers come with a system recovery DVD.

Software Requirements for the TruView Server

Operating system Windows Server 2008 R2 with SP1 (Standard or

Client access licenses Customer is responsible for additional client access

Stand-Alone Web Server Recommendations

Intel Xenon processor (or higher)

Windows Server 2008 R2 Standard Edition with SP1

Web Portal Requirements

Web Browser and Operating System Requirements

PAC Requirements (when ASEs are used as a TruView data source)

Pentium IV processor (or higher)

Do not use the browser Back button to return to a previous view.

TVP and TVF Requirements

Third Party Software

Policy on Additional Third Party Software

Critical security updates for Microsoft Windows, IIS, Approved—Install.

Non-critical security updates for Microsoft Windows,

Remote backup software

System management tools

Remote management software Windows Terminal Server is approved.

Installation and Setup Requirements

Installation and Setup Requirements

Required software includes:

Windows Server 2008 R2 with SP1 (Standard or Enterprise)

Requirements for TruView server installation and setup include:

a static IP address that is approved

Install Windows Server 2008 R2 Standard with SP1

To install Windows Server 2008 R2 Standard:

2. Set the Language to install to English.

The following screen is displayed:

9. Select Drive Options on the Install Windows screen.

25. Select More.

Add Web Server role:

Enable the remote desktop:

Add the "vuptime" user:

1. Open the Server Manager.

User Name vuptime

5. Enable User cannot change password and Password never expires.

Install SQL Server 2008 R2 Standard