VPM v8.0 - Admin Guide

Visual Performance Manager
System Administration Guide
PN 3397397
January 2009, Rev 9 7/2012
2009-2012 Fluke Corporation. All rights reserved.
All product names are trademarks of their respective companies.

User Guide
Licensing Information
1997-2012 Fluke Corporation
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, by photocopying, by recording, or otherwise, without prior written permission from Fluke Networks.
Fluke, Fluke Networks, Visual Network Systems, Visual UpTime, Visual IP InSight, and other trademarks are trademarks or
registered trademarks of Fluke Corporation in the United States and other countries. Fluke Corporations trademarks may be used
publicly with permission only from Fluke Corporation. Other names and brands may be claimed as the property of others.
Fluke Networks, a division of Fluke Electronics Corporation, is an ISO 9001:2000 registered company.
This product includes the following software from third party providers:
VMware Workstation (VPM Xpress only) http://www.vmware.com/download/eula/workstation71.html
MySQL Enterprise Advanced
Microsoft - Windows Server 2008 R2 and SQL Server 2008 R2
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.
Copyright 19962010 Flexera Software, Inc. and/or InstallShield Co. Inc. All Rights Reserved.
This product contains proprietary and confidential technology, information and creative works owned by Flexera
Software, Inc. and/or
InstallShield Co. Inc. and their respective licensors, if any. Any use, copying, publication, distribution, display,
modification, or transmission of
such technology in whole or in part in any form or by any means without the prior express written permission of
Flexera Software, Inc. and/or
InstallShield Co. Inc. is strictly prohibited. Except where expressly provided by Flexera Software, Inc. and/or
InstallShield Co. Inc. in writing,
possession of this technology shall not be construed to confer any license or rights under any Flexera Software, Inc.
and/or InstallShield Co. Inc.
intellectual property rights, whether by estoppel, implication, or otherwise.
Adobe Acrobat reader. Copyright 2011 Adobe Systems Incorporated.
http://www.adobe.com/products/acrobat/acrruela.html.
This product contains open source code from the following sources:
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.
commons-collections http://commons.apache.org/collections
commons-dbcp http://commons.apache.org/dbcp
commons-lang http://commons.apache.org/lang
commons-logging http://commons.apache.org/logging
commons-math http://commons.apache.org/math
commons-pool http://commons.apache.org/pool
log4j http://logging.apache.org/log4j
quartz http:www.opensymphony.com/quartz
snmp4j http://snmp4j.org
CentOS Linux distributed under GNU General Public License (http://www.gnu.org/licenses/gpl.txt)
7-Zip is open source software. Most of the source code is under the GNU LGPL license. The unRar code is under a
mixed license: GNU LGPL and unRar Restrictions. License information can be found at http://www.7zip.org/license.txt.
WinSCP is free software: you can use it, redistribute it and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later
version (http://www.gnu.org/licenses/gpl.txt).
Dell OpenManage Server Administrator includes two device drivers for Linux: Dell Systems Management Base Driver
(dcdbas) and Dell BIOS Update Driver (dell_rbu). Server Administrator uses these drivers to perform its systems
management functions. Depending on the system, Server Administrator loads one or both of these drivers if
required. These drivers have been released as open source under the GNU General Public License v2.0. They are
available in Linux kernels from http://kernel.org starting with kernel 2.6.14.
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.
PostgreSQL is distributed under the following BSD-type license: Portions Copyright (c) 1996-2010, The PostgreSQL
Global Development Group. Portions Copyright (c) 1994, The Regents of the University of California Permission to
use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a
written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following
two paragraphs appear in all copies.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF
THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE. THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND
THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
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/joesnmp/),
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:
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.

User Guide
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-2008 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.
disclaimer.
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 opensslcore@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
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) 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.
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.

User Guide
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.
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#wp466106.
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:
disclaimer.
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.
This software contains a derivative work consisting of ported open source Java Radius client code to a Radius C++
static library. A machine-readable copy of the corresponding source code is available for the cost of distribution.
Please contact the Fluke Networks Technical Assistance Center (1-800-283-5853) and visit the GNU LESSER
GENERAL PUBLIC LICENSE website (http://www.gnu.org/copyleft/lesser.html) for more information.
Wireshark Version 1.0.7 Copyright 1998-2009 Gerald Combs <gerald@wireshark.org> and contributors. This is free
software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.
Wireshark is Open Source Software release under the GNU General Public License. See http://www.wireshark.org for
more information.
itext. Copyright 1999-2007 Bruno Lowagie, Adolf Baeyensstraat 121, 9040 Gent, Belgium.
(http://www.lowagie.com/iText) Distributed under the Lesser GNU Public License, a copy of which is available at
http://www.gnu.org/copyleft/lesser.html
jna. http://jna.dev.java.net Distributed under the Lesser GNU Public License, a copy of which is available at
http://www.gnu.org/copyleft/lesser.html
jna-posix. http://kenai.com/projects/jna-posix Distributed under the Lesser GNU Public License, a copy of which is
available at http://www.gnu.org/copyleft/lesser.html
xom. Copyright 2002-2006, 2009 Elliotte Rusty Harold http://www.xom.nu Distributed under the Lesser GNU Public
License, a copy of which is available at http://www.gnu.org/copyleft/lesser.html
CentOS Linux. Distributed under the GNU General Public License
Copyright 2001-2012 Python Software Foundation; All Rights Reserved
1. This LICENSE AGREEMENT is between the Python Software Foundation (PSF), and the Individual or Organization
(Licensee) accessing and otherwise using Python 2.7.2 software in source or binary form and its associated
documentation.
2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive,
royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works,
distribute, and otherwise use Python 2.7.2 alone or in any derivative version, provided, however, that PSFs License
Agreement and PSFs notice of copyright, i.e., Copyright 2001-2012 Python Software Foundation; All Rights
Reserved are retained in Python 2.7.2 alone or in any derivative version prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on or incorporates Python 2.7.2 or any part thereof,
and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include
in any such work a brief summary of the changes made to Python 2.7.2.
4. PSF is making Python 2.7.2 available to Licensee on an AS IS basis. PSF MAKES NO REPRESENTATIONS OR
WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR
PURPOSE OR THAT THE USE OF PYTHON 2.7.2 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 2.7.2 FOR ANY INCIDENTAL,
SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE
USING PYTHON 2.7.2, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material breach of its terms and conditions.
7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint
venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or
trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party.
8. By copying, installing or otherwise using Python 2.7.2, Licensee agrees to be bound by the terms and conditions of
this License Agreement.
WinPcap 4.1.2
Copyright (c) 1999 - 2005 NetGroup, Politecnico di Torino (Italy).
Copyright (c) 2005 - 2010 CACE Technologies, Davis (California).
All rights reserved.
disclaimer.
3. Neither the name of the Politecnico di Torino, CACE Technologies nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS 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 COPYRIGHT OWNER OR
OF SUCH DAMAGE.
This product includes software developed by the University of California, Lawrence Berkeley Laboratory and its
contributors.
This product includes software developed by the Kungliga Tekniska Hgskolan and its contributors.

User Guide
This product includes software developed by Yen Yen Lim and North Dakota State University.
-----------------------------------------Portions Copyright (c) 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997 The Regents of the University of California. All
rights reserved.
disclaimer.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes software developed by the University of California, Berkeley and its contributors."
4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products
THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
OF SUCH DAMAGE.
-----------------------------------------Portions Copyright (c) 1983 Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this
paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials
related to such distribution and use acknowledge that the software was developed by the University of California,
Berkeley. The name of the University 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 MERCHANTIBILITY AND
FITNESS FOR A PARTICULAR PURPOSE.
-----------------------------------------Portions Copyright (c) 1995, 1996, 1997 Kungliga Tekniska Hgskolan (Royal Institute of Technology, Stockholm,
Sweden). All rights reserved.
disclaimer.
"This product includes software developed by the Kungliga Tekniska Hgskolan and its contributors."
4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products
THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR
OF SUCH DAMAGE.
-----------------------------------------Portions Copyright (c) 1997 Yen Yen Lim and North Dakota State University. All rights reserved.
disclaimer.
"This product includes software developed by Yen Yen Lim and North Dakota State University"
4. The name of the author may not be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR `À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 AUTHOR 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.
-----------------------------------------Portions Copyright (c) 1993 by Digital Equipment Corporation.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted,
provided that the above copyright notice and this permission notice appear in all copies, and that the name of Digital
Equipment Corporation not be used in advertising or publicity pertaining to distribution of the document or software
without specific, written prior permission.
THE SOFTWARE IS PROVIDED "AS IS" AND DIGITAL EQUIPMENT CORP. DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN
NO EVENT SHALL DIGITAL EQUIPMENT CORPORATION BE LIABLE FOR ANY SPECIAL, DIRECT, 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.
-----------------------------------------Portions Copyright (C) 1995, 1996, 1997, 1998, and 1999 WIDE Project. All rights reserved.
disclaimer.
3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products

User Guide
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR
OF SUCH DAMAGE.
-----------------------------------------Portions Copyright (c) 1996 Juniper Networks, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that: (1)
source code distributions retain the above copyright notice and this paragraph in its entirety, (2) distributions
including binary code include the above copyright notice and this paragraph in its entirety in the documentation or
other materials provided with the distribution. The name of Juniper Networks 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.
-----------------------------------------Portions Copyright (c) 2001 Daniel Hartmeier All rights reserved.
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTOR "AS 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 COPYRIGHT HOLDERS OR
OF SUCH DAMAGE.
-----------------------------------------Portions Copyright 1989 by Carnegie Mellon.
Permission to use, copy, modify, and distribute this program for any purpose and without fee is hereby granted,
provided that this copyright and permission notice appear on all copies and supporting documentation, the name of
Carnegie Mellon not be used in advertising or publicity pertaining to distribution of the program without specific prior
permission, and notice be given in supporting documentation that copying and distribution is by permission of
Carnegie Mellon and Stanford University. Carnegie Mellon makes no representations about the suitability of this
software for any purpose. It is provided "as is" without express or implied warranty.
Software License Agreement

YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS SOFTWARE.
10
USING THIS SOFTWARE INDICATES YOUR ACCEPTANCE OF THESE TERMS AND CONDITIONS. IF YOU DO NOT AGREE
WITH THEM, YOU SHOULD PROMPTLY RETURN THE SOFTWARE PACKAGE AND YOUR PAYMENT WILL BE REFUNDED.
This Agreement is between you and Fluke Networks, a division of Fluke Electronics Corporation.
This Software License Agreement (the "Agreement") grants you a non-exclusive license to use the software supplied to you by
Fluke Networks, including the software supplied to you on CD-ROM, on-line, and/or as part of the equipment supplied by Fluke
Networks (collectively the "Software") in return for payment of a license fee. This Agreement imposes certain restrictions on the use
of the Software. Fluke Networks retains ownership of the Software and no rights are granted to you other than a license to use the
Software on the terms expressly set forth in this Agreement.
Permitted Uses
You may install and use one copy of Fluke Networks server products. You must reproduce and place all copyright/proprietary/patent
notices on the backup copy, as indicated on the original. Per the conditions of your specific purchase agreement with Fluke
Networks, you may install multiple copies of the client code component of Fluke Networks product, but copies are limited to one
server. If the Software is an upgrade, you may now use that upgraded product only in accordance with this Agreement.
Restricted Uses
Without the express written consent of Fluke Networks, you may not:
1. Use, copy (other than described above), modify, distribute, reverse engineer, reverse assemble, or reverse compile the Software
or accompanying documentation except as expressly allowed in this Agreement.
2. Transfer or assign your rights to use the Software except upon a transfer of any Fluke Networks equipment with which or for
which it was supplied, and then only if Fluke Networks receives written agreement of the transferee to be bound by all of the terms
of this Agreement.
3. Sublicense or lease this program or its documentation.
Term
This license is effective from your date of purchase and shall remain in force until terminated. You may terminate this license and
Agreement by destroying the Software and its documentation, together with all copies in any form, or by returning to Fluke Networks
the Software and its documentation, together with all copies in any form. This Agreement will also terminate if you fail to comply with
any term of this Agreement. You agree upon any such termination to either (i) destroy the Software and documentation, together
with all copies in any form or (ii) return to Fluke Networks the Software and its documentation, together with all copies in any form.
Warranty
Fluke Networks warrants that the Software will operate substantially in accordance with its functional specifications for 90 days and
that it has been properly recorded on non-defective media. Fluke Networks does not warrant that software will be error free or
operate without interruption. If, within the Warranty period, You notify Fluke Networks of any defect or fault in the Software where
the Software does not perform substantially in accordance with its functional specifications and such defect or fault does not result
from You, or anyone acting with your authority, having amended, modified or used the Software for a purpose other than for what it
was designed, Fluke Networks shall, at its sole option, do one of the following:
(I) REPAIR OR REPLACEMENT OF THE SOFTWARE, OR
(II) RETURN OF THE MONIES PAID BY YOU TO FLUKE NETWORKS FOR THE SOFTWARE. THIS WARRANTY IS
CUSTOMER'S SOLE AND EXCLUSIVE REMEDY AND IS IN LIEU OF ALL OTHER WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Limitation on Liability
IN NO EVENT SHALL FLUKE NETWORKS, ITS SELLING REPRESENTATIVES, DEALERS, OR DISTRIBUTORS BE LIABLE
FOR LOST PROFITS, DATA, OR INFORMATION OF ANY KIND OR FOR CONSEQUENTIAL, SPECIAL, INDIRECT,
INCIDENTAL, PUNITIVE OR OTHER DAMAGES THAT MAY ARISE THROUGH THE SALE OF, USE OF, OR INABILITY TO USE
ANY FLUKE NETWORKS PRODUCT, SOFTWARE OR SERVICE, EVEN IF FLUKE NETWORKS HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

User Guide
Applicable Law
This Agreement will be governed by the laws of the state of Washington.
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 Fluke Networks, a division of Fluke Electronics Corporation, PO Box 777, Everett,
Washington, 98206-0777, USA.
1995-2012 Fluke Corporation.
12
Contents
Contents ..................................................................................................................................... i
Preface ..................................................................................................................................... ix
About this Guide .................................................................................................................... ix
User Documentation .............................................................................................................. ix
Guides and Other Documents ............................................................................................ ix
Accessing Documentation .................................................................................................. xi
Launching Online Help .......................................................................................................xii
Supported Web Browsers and Operating Systems .............................................................xii
Product Services ................................................................................................................... xiii
Technical Support.............................................................................................................. xiii
Professional Services ........................................................................................................xiv
Product Training ................................................................................................................xiv
1.
Visual Performance Manager Overview ......................................................................... 15

What is Visual Performance Manager? ................................................................................. 15
Visual Performance Manager Features ................................................................................. 17
Application Performance Management Features ............................................................... 18
Network Performance Manager Features .......................................................................... 20
Visual UpTime Select Features ......................................................................................... 21
Flexible Licensing Options ................................................................................................. 23
System Architecture .............................................................................................................. 24
i

User Guide
Application Performance Appliances ................................................................................. 25

Network Performance Appliances ...................................................................................... 26
ASEs ................................................................................................................................. 28
Server................................................................................................................................ 29
Web Portal......................................................................................................................... 31
PAC ................................................................................................................................... 31
Network Models .................................................................................................................... 33
Enterprise Hosted System ................................................................................................. 33
Service Provider Hosted System ....................................................................................... 33
Data Management ................................................................................................................ 35
Data Collection and Storage .............................................................................................. 35
Application Performance Data from APAs ......................................................................... 38
Application Performance Data from ASEs ......................................................................... 38
NetFlow Data from NPAs................................................................................................... 39
Network Performance Data from ASEs.............................................................................. 39
2.
Server Overview .............................................................................................................. 42

Visual Performance Manager Services ................................................................................. 42
Server Integrity and Performance ...................................................................................... 43
Data Storage ..................................................................................................................... 44
Server Applications ............................................................................................................... 45
Administrative Tasks ............................................................................................................. 45
Starting and Stopping Services ............................................................................................. 47
3.
Administering System Security ...................................................................................... 49

Server Security ..................................................................................................................... 49
Default User Accounts ....................................................................................................... 49
Password Policy ................................................................................................................ 51
Password Lockout Policy ................................................................................................... 53
Audit Policy........................................................................................................................ 53
ii
Critical Files ....................................................................................................................... 55

Enabling Registry Access .................................................................................................. 57
Configuring Firewalls............................................................................................................. 58
Setting Server Port Numbers ............................................................................................. 59
Firewall Port Settings ......................................................................................................... 60
4.
Monitoring Servers .......................................................................................................... 61

Running Server Administration.............................................................................................. 61
Running Remote Server Administration ............................................................................. 64
Closing Server Administration ........................................................................................... 64
Managing the Server Monitor List.......................................................................................... 65
Viewing Detailed Server Status ............................................................................................. 65
Polling Server Status............................................................................................................. 68
Logging in to Server Administration....................................................................................... 69
Identifying Active Users......................................................................................................... 70
Generating Administrative Reports........................................................................................ 71
Generating an On-Demand Report .................................................................................... 71
Scheduling Reports ........................................................................................................... 71
Administrative Reports ...................................................................................................... 73
Monitoring APA Data Flow .................................................................................................... 82
5.
Managing Domains.......................................................................................................... 84
About Domains ..................................................................................................................... 84
Creating Domains ................................................................................................................. 85
Setting Domain Options ........................................................................................................ 87
Collecting ASE Data .......................................................................................................... 87
Performing Database Maintenance for a Domain .............................................................. 88
Configuring Domain-Wide Event Priorities ......................................................................... 91
Configuring Domains............................................................................................................. 92
Setting the SNMP Community Name ................................................................................. 93
iii

User Guide
Setting the TFTP Authentication String .............................................................................. 93

Setting a Router Polling Interval ........................................................................................ 94
Setting an Application Summary Orientation...................................................................... 94
Domain May Not be Deleted .............................................................................................. 95
Creating a Service Summary Domain ................................................................................ 95
BGP Exclusion List ............................................................................................................ 95
Configuring Secure ASE Communications ........................................................................ 96
Turning Off Module Support .............................................................................................. 98
Restricting IP Addresses of ASEs ...................................................................................... 98
Changing the Logo for Reports on a Domain ..................................................................... 98
Configuring an IP Class of Service Template ........................................................................ 99
Delete an IP CoS Template ............................................................................................. 102
Associate an IP CoS Template with a Domain .................................................................... 102
Forwarding Events and Alarms ........................................................................................... 103
Configuring User and Group Associations........................................................................... 103
Configuring Report Permissions .......................................................................................... 104
Domain and Network Reports .......................................................................................... 105
Port Reports .................................................................................................................... 107
Site Reports..................................................................................................................... 108
NPM Reports ................................................................................................................... 109
APM Reports ................................................................................................................... 109
Managing Licenses for a Domain ........................................................................................ 109
Adding a Feature Evaluation License .............................................................................. 111
System Log Forwarding ...................................................................................................... 111
Copying Domain Settings .................................................................................................... 112
Enabling and Disabling Domains ........................................................................................ 114
Deleting Domains................................................................................................................ 114
Identifying ASEs.................................................................................................................. 115
iv
6.
Managing Users ............................................................................................................. 118

Controlling Access to VPM Features ................................................................................... 118
Managing User Groups ....................................................................................................... 119
Setting Group Capabilities ............................................................................................... 119
Viewing Members of a User Group .................................................................................. 124
Creating User Groups...................................................................................................... 125
Editing User Groups ........................................................................................................ 125
Deleting User Groups ...................................................................................................... 126
Managing User Accounts .................................................................................................... 126
Creating User Accounts ................................................................................................... 128
Editing User Account Passwords ..................................................................................... 129
Assigning User Accounts to Domains .............................................................................. 130
Restricting Access by IP Address .................................................................................... 132
Locking and Unlocking User Accounts............................................................................. 132
Designating Power Users ................................................................................................ 132
Specifying Authentication ................................................................................................ 133
Deleting User Accounts ................................................................................................... 133
7.
Configuring Server Settings ......................................................................................... 134

Configuring Login and Password Policies ........................................................................... 134
Configuring Password Expiration ..................................................................................... 135
Configuring Password Text Restrictions .......................................................................... 136
Configuring User Lockout Policies ................................................................................... 137
Configuring General Settings .............................................................................................. 138
Configuring Report Publishing Settings ........................................................................... 139
Deactivating the Feature License Expiration Warning ...................................................... 140
Setting a Database Log File Size Warning ...................................................................... 140
Reversing the NPA Interface Orientation ......................................................................... 140
Changing the VoIP Call Quality Metric ............................................................................. 140
v

User Guide
Changing the Logo for Reports ........................................................................................ 141

Changing E-Mail Delivery Settings .................................................................................. 141
Configuring ATM Class of Service Settings ......................................................................... 142
Enabling External Authentication ........................................................................................ 143
Configuring Licenses........................................................................................................... 146
Licensing Modes ............................................................................................................. 147
Managing Feature Licenses ............................................................................................ 150
Managing ASE Evaluation Licenses ................................................................................ 152
Managing Agent Licenses ............................................................................................... 154
Using LAN Visibility Licenses .......................................................................................... 156
Configuring a Backup Server License .............................................................................. 157
Identifying the Server ID .................................................................................................. 159
8.
Managing Web Access .................................................................................................. 160

Configuring Service Summary Settings ............................................................................... 161
Configuring a Web Server ................................................................................................... 162
Logging in to a Web Server ............................................................................................. 163
Controlling Web Server Access to Servers ...................................................................... 163
Customizing Global Web User Settings ........................................................................... 166
Accessing the Web Portal from Other Software .................................................................. 168
9.
Frequently Asked Questions ........................................................................................ 171

System Configuration and Operation .................................................................................. 171
Server Administration FAQs ................................................................................................ 172
ASE on Multiple Servers ..................................................................................................... 173
Licensing FAQs................................................................................................................... 174
Server ID............................................................................................................................. 174
Upgrade and New System Questions ................................................................................. 174
ASE Limits .......................................................................................................................... 175
Evaluation and Temporary Licenses ................................................................................... 176
vi
License Key Backup and Recovery ..................................................................................... 176

Power Users ....................................................................................................................... 176
Sharing Licenses ................................................................................................................ 177
Domain-Fixed and Flexible Licensing .................................................................................. 177
Backup Server Licensing .................................................................................................... 177
Restoring Databases........................................................................................................... 178
10. Maintaining the Databases ........................................................................................... 180
Scheduling Data Collection and Database Maintenance ..................................................... 180
About the Databases ....................................................................................................... 181
Collecting ASE Data in All Domains ................................................................................ 182
Performing Database Maintenance in All Domains .......................................................... 182
Checking the Database Maintenance Log ....................................................................... 182
Resolving Database Space Issues .................................................................................. 183
Moving a Domain to a Different Server ............................................................................... 184
Backing Up and Restoring Databases ................................................................................. 184
Using Backup Tapes ....................................................................................................... 187
Windows Emergency Repair Disks .................................................................................. 187
A.
Open Ports for Firewall Configuration ......................................................................... 188
B. Reestablish Reporting on a Renamed Server ............................................................. 191

C. Supported Standards .................................................................................................... 193
Glossary ................................................................................................................................ 196
Index ...................................................................................................................................... 205
vii

User Guide
viii
Preface
About this Guide

The System Administration Guide explains how to use the Visual Performance Manager (VPM) server. A
VPM server is a dedicated, uniquely configured database server running Microsoft Windows Server and
Microsoft SQL Server software. A server stores, manages, and interprets data collected in a VPMmonitored data network. This guide discusses how to use the server to configure and manage Analysis
Service Elements (ASEs), collect performance data from ASEs, and maintain the network performance
database.
This guide also explains how the server communicates with ASEs and clients, how to use the server to
provision and manage VPM user accounts and secure user access to VPM, and how to monitor system
agent/license usage.
This guide is intended for network administrators and management professionals who perform WAN
configuration and/or WAN performance monitoring and analysis. The reader is expected to have
background knowledge in one or more of the following WAN access technologies: frame relay, ATM,
HDLC, IP/Internet, Ethernet, VPN. Users should also have a working knowledge of Structured Query
Language (SQL) and Microsoft SQL Server systems.
Throughout this guide, the word server refers to the server software component of VPM.
User Documentation
The VPM documentation set includes online guides and administrative and Web portal Help systems.
Documents are installed with server and PAC software by default as Adobe Acrobat portable document
format (PDF) files. On the server, the documentation is installed in:
[drive]:inetpub\wwwroot\Manuals
On the PAC, the documentation is installed in:
...\Fluke Networks\Visual UpTime Select PAC\Manuals
Guides and Other Documents

The following documents (PDF format) can be found on the server in the

User Guide
[drive]:inetpub\wwwroot\Manuals directory.
New Features Summary
This document describes changes in the latest version of the product.
Readme
For Gold Support users of the VPM system, this document describes resolved and known issues in
the current release. The Readme file is available on the Fluke Networks website under the Product
Manuals heading for Visual Performance Management.
Visual Performance Manager Turnkey Server Installation and Setup Guide
For customers who purchased a VPM turnkey server from Fluke Networks, this document explains
how to install the server and set it up for use.
Software Installation Guide
For any user who is installing VPM server software, this guide provides system requirements,
information about preparing servers for VPM software installation, and instructions for installing or
upgrading server and PAC software.
System Administration Guide
For WAN and system administrators, this guide provides information about managing the server,
managing client connections to the server, applying server-wide and domain-specific settings, and
using SQL Server database management utilities.
Visual Performance Manager User Guide
For users of the VPM Web portal, this guide explains how to organize data views and use settings
tools available from the Web portal. It also explains how to configure the Network Performance
Appliance and Application Performance Appliance, manage devices and interfaces, and access
report views.
Visual UpTime Select User Guide
For users of the Visual UpTime Select toolset, this guide explains how to use the Web-based
network, application, and VoIP performance monitoring, analysis, and reporting tools.
Visual UpTime Select ASE User Guide
For network management professionals who perform ASE and network setup, this guide provides
information on ASE features, commands, communication methods, physical connections, and
hardware specifications.
Visual UpTime Select PAC User Guide
For network management professionals who perform network configuration and management
functions within a domain, this guide describes how to use the Visual UpTime Select PAC tools.
Visual Performance Manager Customization Guide
Product Services
For system integrators responsible for integrating VPM into a service provider or enterprise
environment.
Application Performance Appliance Installation and Setup Guide
For field technicians who install Application Performance Appliances (APAs) and network
professionals who manage them, this guide explains how to install the APA, perform basic
configuration tasks to ensure connectivity, and to perform software updates.
Network Performance Appliance Installation and Setup Guide
For field technicians who install Network Performance Appliances and network professionals who
manage them, this guide explains how to install the appliance, perform basic configuration tasks to
ensure connectivity, and to perform software updates.
Visual Performance Manager / Application Performance Appliance External Storage Array Installation
and Setup Guide
The External Storage Array (ESA) is an external storage device that connects to a Visual
Performance Manager (VPM) server or an Application Performance Appliance (APA) and enables
expansion of the storage capacity of the VPM Server or the APA.
This setup guide shows you how to connect the ESA to a VPM Server or an APA.
ASE Installation Instructions (vary by ASE model)
For field technicians who install Visual UpTime Select ASEs, these documents explain how to install
the ASE, connect the physical interfaces, and perform basic configuration tasks to ensure ASE
connectivity to the VPM server.
VPM Connex User Guide
VPM Connex provides a web based programmable interface for accessing the Visual Performance
Manger (VPM) performance database and for accessing and publishing VPM configuration data.
Accessing Documentation
All guides are included on the VPM CD along with a Windows version of Adobe Acrobat Reader 8.1. The
guides and Acrobat Reader are pre-installed on new servers. Acrobat Reader 6.0 or later is required. The
Acrobat Reader is available for free from Adobes website, www.adobe.com.
Any user with IP connectivity to the VPM server can view or download all or selected guides from the
Web server.
To access documentation from the Web portal:
In the Web portal interface, click Support.
To access documentation from the servers Visual UpTime Select home page:
1
Launch your Web browser, and type the following URL in the address field:
http://<VPM server name or IP address>/uptime.htm
xi

User Guide
2
Click Download Documentation.
To view a PDF document, click its title. To download a document, right-click its title and choose Save
Link As (Firefox) or Save Target As (Internet Explorer).
To access documentation from your local drive:

Select Start > Programs > Fluke Networks > Visual Performance Manager Manuals. This
connects you to a documentation Web page that contains hypertext links to this and other
documentation.
Updated versions of user manuals are available online at: www.flukenetworks.com.
Launching Online Help

VPM Help is context-sensitive. Help systems are HTML-based and are launched by your default browser.
A navigation frame in the Help window provides easy access to the table of contents, index, and search
capabilities.
Launching Help from the Web Portal

Help from the VPM Web portal includes information from the Visual Performance Manager User Guide
and Visual UpTime Select User Guide. To launch Help, click Help in the top right corner of the Web page
or from a panel.
Launching Help from the Server or PAC

To launch Help from the VPM PAC or server:
From the PAC or the Server Administration tool, choose Help > Visual Performance Manager Help.
To open Help directly to a related topic, press the F1 key.
To open Help on a given dialog box, click the Help button or question mark (?) icon.
Supported Web Browsers and Operating Systems

Table 1 Supported Operating Systems
Component
Operating Systems
VPM 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 Vista Business (32-bit) SP1 and Vista
Enterprise (32-bit) SP1
xii
Product Services
VPM supports the following Web browsers on the operating systems listed above.
MS Internet Explorer (IE) 8.0 or 9.0
Firefox 5.0
Note
Other browsers may run but have not been tested.
For best performance when running Web applications, set your screen resolution to 1280 x 1024
pixels or higher.
Sun JRE 6.0 (1.6.0) 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 VPM servers 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.
Product Services
For VPM product information, see: www.flukenetworks.com.
Technical Support
For VPM technical support, contact your vendor technical support representative or contact Fluke
Networks Technical Assistance Center (TAC) at the points listed below:
Phone: 1 888-293-5853 (U.S. only) or 1 425-446-4519 (international)
E-mail: support@flukenetworks.com
Supervision Gold support packages are available from the Fluke Networks website.
VPM software updates are available from the Fluke Networks website. You must be a Gold Support
customer to get updates.
To get VPM software updates:
1
Go to www.flukenetworks.com.
Select Resources > Downloads and Updates.
Select the update that you want.
Do one of the following:

a
If you already have an account, sign in.

xiii

User Guide
b
5
If you need to create an account, click the Create an Account link. Fill out the form and submit it.
Click the Download link to the right of the software that you want to download.
Professional Services
Fluke Networks has certified consultants who can assist you with the planning, installation,
implementation, and deployment of the product. Contact Professional Services at the points listed below:
Phone: 1 888-293-5853 (U.S. only) or 425-446-4600
Fax: 421-446-4839
E-mail: professionalservices@flukenetworks.com
Product Training
Training is available. Direct training requests to your product vendor or the training coordinator at the
contact points listed below:
Phone: 301-296-2300
Fax: 301-296-2651
E-mail: training@flukenetworks.com
xiv
Visual Performance Manager Overview

Visual Performance Manager Features
1. Visual Performance Manager

Overview
Topics in this chapter include:
What is Visual Performance Manager?
Visual Performance Manager software features
System architecture components
How the Visual Performance Manager system is deployed
How data is managed in the Visual Performance Manager system
What is Visual Performance Manager?

Visual Performance Manager (VPM) is a comprehensive system that enables the
successful delivery of enterprise applications over converged networks. This
system provides unique views and a range of ways to analyze application, VoIP,
and network performance. It manages the delivery of advanced application
services to the business, enabling broad enterprise visibility, deep analysis, and
troubleshooting in an integrated way. As a comprehensive solution, it provides
everything from proactive management to reactive troubleshooting.
VPM supports converged IP networks. It provides a single integrated framework
for monitoring and analyzing data from a multitude of sources, including:
Application performance data gathered by Application Performance
Appliances (APAs) at the data center or hub sites.
NetFlow data gathered by Network Performance Appliances from Cisco
routers and switches.
IP SLA data from Cisco routers.
Physical, link, and upper layer data from network probes (ASEs).
Data from these sources is analyzed based on a single model using a domain,
network, site, and port hierarchy.
15

User Guide
Users interact with data through a single access point. From the VPM Web
portal, users can create and organize personalized views of data based on their
workflow. Users can also view data from multiple sources. For example, the Web
portal can host a system or can be launched from another system.
Through the inclusion of Application Performance Manager, Network
Performance Manager, and Visual UpTime Select feature sets, the Web portal
provides a range of interactive views, from domain-wide daily summaries (for
VoIP and application performance) to port-specific troubleshooting. Deep
analysis of applications (from Citrix to voice and video) is supported. NetFlow
devices and interfaces are tracked in detail. Reports are available at the domain,
site, and port levels.
VPM users include IT departments in enterprises that manage their own
networks, enterprise subscribers of network services, and service providers.
VPM can be implemented directly by an enterprise, or as a hosted solution from
a service provider, where the enterprise subscriber accesses network information
over the Web. It is also used by service provider operations staff to proactively
manage multiple networks and to provide value services to subscribers.
In the VPM system, APAs are deployed at the data center, NPAs and ASEs are
deployed throughout the network. Users access the data through the Web portal.
The VPM database and Web server includes administration and database
management tools. This is shown, in a simplified way, in Figure 1.
Figure 1 VPM Components
As a standards-based open system, VPM also supports integration with thirdparty interfaces. For more information about system components, see System
Architecture.
16


VPM includes a core set of features for managing application and network
performance. You can also add feature modules based on your specific needs.
Key features include Web portal access to data, Application Performance views,
NetFlow management through Network Performance Manager features, and
service monitoring, event management, and troubleshooting views through
Visual UpTime Select.
VPM features let you:
View data from a range of perspectives through the Web portal. Create
custom views for the data you want to see. View sites by name.
Access a wide range of data, including utilization, throughput, top talkers,
response time, availability, and error rates for data over IP-switched networks
and frame relay, ATM, and private line (HDLC/PPP) networks.
Monitor response times for critical n-tier applications from the end user to the
server farm and back. Analyze application, site, server, and client data
gathered by APAs at 1-minute granularity. (Available with the Application
Performance Management license.)
Manage NetFlow data using the Network Performance Manager. Access
data from multiple Network Performance Appliances (NPAs) in a single view.
Create data views from devices and interfaces monitored by individual NPAs,
directly access the NPA user interface, and run domain-wide NetFlow data
reports.
Troubleshoot in real time using Visual UpTime Select. Assess sites impacted
by service problems and view port and circuit status events at those sites.
View and acknowledge physical, link, and upper layer events reported by
Analysis Service Elements (ASEs) at locations throughout the network.
Launch Troubleshooting for specific events.
Set up alarms issued for applications, sites, and servers performance events
at 15-minute intervals. (Available with the Application Performance
Management license.)
Configure and view threshold events by which ASEs report network failures
and performance degradations at the physical, port, and circuit layers.
Create domain-wide, site-specific, and port-level reports on data gathered by
APAs, NPAs, and ASEs from a single view.
Forward events to third-party event management software from the VPM
server.
Set up and manage APAs, ASEs, and NPAs on the network. Set up
monitored applications.
17

User Guide
Generate server-wide and domain-based administrative reports from the
server.
Figure 2 Web PortalMy Applications Overview
Application Performance Management

Features
The Application Performance Management feature in VPM provides flexible
views into data gathered by APAs. With this toolset, users can troubleshoot enduser performance problems, isolate problem sources, set up accurate alarms,
and generate reports.
18

Figure 3 Application Performance Management
Monitor response times for critical n-tier applications from the end user to the
server farm and back. Analyze application, site, and server data gathered by
APAs at 1-minute granularity. Drill down to individual client and transaction
performance data. Analyze trends and response times. Rapidly drill down on
unusual response times to view the problem from multiple points of
reference.
Corroborate end-user performance complaints to quickly identify the problem
domain and quantify business impact. Use response time breakdown to
determine whether the problem is caused by the application, server, or
network. Compare an individual end user's experience to that of other users
at that site and quickly determine if a problem is isolated to the user or is
impacting many clients.
Correlate end user activity with the application backend. View the
performance of a multi-tier application from the web front end through the
application servers and to the database backend to quickly isolate
performance issues. Understand the relationships between the dependent
servers at the transaction level.
Back-in-time application performance troubleshootingGet the data view
that you need to solve a specific issue by applying time, application, site,
19

User Guide
server, and transaction filters. Reduce the mean time to resolution over
traditional troubleshooting approaches. Available data spans layers 1 through
7 in the OSI stack.
Create and run performance-based alarmsSet up End-user Response
Time, Network Round Trip Time, and Server Connect Time alarms on data
gathered by APAs. Alarms are generated at 15-minute frequency based on
the automatic configuration of thresholds drawn from performance baselines
or fixed threshold values. You can also restrict alarms to business hours.
Generate on-demand or scheduled application performance reports. You can
also restrict report data to business hours.
For more information about these features, see the Visual Performance Manager
User Guide.
Network Performance Manager Features

The Network Performance Manager (NPM) feature in Visual Performance
Manager lets you view NetFlow/IPFIX traffic information from Cisco routers and
managed switches and sFlow standards from other vendors. It provides both
domain-wide reports and deep access to individual devices and interfaces
monitored by Network Performance Appliances (NPA) installed on the network.
The NPM feature lets you:
Analyze application and protocol data in depth. This includes user, server
and applications activity. Traffic views by user, user group, conversation,
system and application are available.
Access data from multiple NPAs, including device and interface overviews,
from a single Web portal view.
Create domain-wide reports on NetFlow data gathered by all NPAs active in
that domain. This data includes: top devices, applications, interfaces, hosts,
and conversations on the domain.
Drill down into specific device and interface views through NPA panels.
Create comparative views of data using a range of filters.
Access the NPA user interface directly.
Manage the devices and interfaces monitored by NPAs on a domain.
Manage NPAs from a single user interface.
20

Figure 4 Network Performance Management
Network Overview shows

busiest sites, interfaces, and
applications monitored by
all NPAs on a domain
Visual UpTime Select Features

Visual UpTime Select feature moduleswhich you can add to the core feature
setextend your ability to manage application and network performance to
include data from Cisco router IP SLAs, IP classes of service, application flows,
VoIP, and LAN traffic.
Once you have identified problems in Service Summary, use the Troubleshooting
feature modules to identify the sources of current problems, observe patterns in
network usage that may contribute to present or future problems, and take
corrective and preventive actions. In addition, VoIP and AppSummary features
give you domain-wide and site-specific views into VoIP and application usage on
the network, and LAN Visibility extends your view of applications to the LAN.
21

User Guide
Figure 5 Visual UpTime Select User InterfaceService Summary
Use color-coded icons to

quickly see network
points of failure
Drill-down on problem
services to view port
and circuit events and 3
day performance
history
Use the Events tab to
respond to events on the
selected network
element
Open port or circ

troubleshooting v
(requires Networ
Troubleshooting
Time features)
The following are licensable features of Visual UpTime Select:
Select AppSummaryMonitor application and application server
performance on your network. Application Summary provides a picture of
traffic on the domain by displaying aggregated data drawn from all monitored
ports in a domain. Set up alarms indicating a significant change in conditions
affecting application performance.
VoIPAnalyze VoIP performance across the domain and at specific sites
and drill down on problem calls and other underlying causes of poorly
performing sites.
Network TroubleshootingView data for the most current 15 minutes at the
physical, port, and circuit layers in graph and statistical table formats. Views
include summary, applications, circuit status and connectivity, congestion,
and statistics.
22

Select Back-in-TimeView data for the past two weeks at physical, port,
and circuit layers in graph and statistical table formats. In addition to views
included in Network Troubleshooting, Back-in-Time includes Service
Advisor and Burst Advisor views. You can scroll through data, which is
collected in 15-minute intervals and viewable in 2-hour and 2-day modes.
Select AppFlowsView troubleshooting data for all IP application traffic on
a port for up to the past two weeks. This application flow traffic can be
between an application client (or user) and application server, or between
two clients (as in peer-to-peer applications).
Select Class of ServiceView IP class of service troubleshooting data at
the port and circuit levels in graph and statistical table formats. Monitor up to
eight classes of service. Track application utilization within each class of
service against a policing threshold. Measure and validate SLA parameters
for each individual class setting.
LAN VisibilityAccess data from LAN switch IP traffic from Ethernet ASEs
with LAN Visibility software installed. LAN Visibility ASEs are useful, for
example, in an enterprise customer data center where traffic between
servers within the data center can be monitored.
Traffic CaptureCapture and analyze packet traces gathered by ASEs on a
targeted physical line, getting detailed performance view of remote sites and
reducing costs associated with physical rollouts.
IP SLA Router PollingGenerate a report on IP service level agreement
(SLA) test data gathered by Cisco IOS-based routers on the domain. IP SLA
Router Polling extends VPM capabilities into sites where no ASE is currently
deployed or where a LAN Visibility ASE is deployed on the LAN.
Reports OnlyGenerate long term reports available through Back-in-Time,
without having to purchase the Back-in-Time feature. These reports help you
analyze daily and monthly network performance and usage.
For more information about these features, see the Visual UpTime Select User
Guide.
Flexible Licensing Options

In addition to providing feature-based purchasing options, VPM offers flexible
licensing options:
The Application Performance Management feature and the Network
Performance Management feature each require a license.
Permanent feature licenses can be purchased for the VPM system for use in
all domains supported by the server or for assignment to a specific domain.
ASE and feature evaluation licenses are also available.
23

User Guide
A power user license gives users (such as service provider operations staff)
access to features across all domains supported on a VPM server. By
contrast, standard user licenses are always operable within a domain.
A back-up VPM server license facilitates the temporary operation of a backup server without needing a full new set of license keys.
For more information about licensing, see Configuring Licenses.
System Architecture
The VPM 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 Select ASEs and partner devices equipped with agent software.
ASEs on both ends of a physical access line form an end-to-end managed
circuit.
Application Performance Appliances (APAs)Devices installed at the data
center that monitor data passing through core switches. APAs monitor
application traffic and measure application performance and usage.
Network Performance AppliancesDevices installed at key points on the
network that collect IP traffic (NetFlow) data from Cisco routers and managed
switches.
ServerThe VPM 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 portalWeb-based client applications, accessed through a single
logon, that present data for analysis and provide tools for configuring
devices.
PACThe PAC (Platform Applicable Client) is a Windows-based client used
primarily for Visual UpTime Select network configuration.
Figure 6 shows the location of VPM components relative to the WAN, customer
premises equipment (CPE) such as routers, and site local area networks. In this
example, the VPM server is located at the data center site, along with the PAC
and an NPA. Web portal users access the server (or a stand-alone Web server
with communication links to the server) over secure or non-secure Internet
connections. The corporate head office site has a WAN ASE, an Ethernet ASE
deployed on the LAN, and an NPA. All sites have WAN ASEs deployed at or
near the WAN demarcation point.
24

System Architecture
Figure 6 VPM System Components
Application Performance Appliances

The APA performs the deep analysis of applications, flows, and transactions at
the enterprise data center or other hub sites. APAs are available in a range of
capacities to meet your network needs for number of interfaces, processing,
memory, and transaction data storage.
A typical VPM server can support several APAs in a single deployment. The
number of APAs that a single VPM server can support is dependent on the
number of applications, servers, and sites being monitored.
The following scenario shows two APAs deployed at an enterprises data center.
Data is routed through two tiers of switches from the CPE router. APAs are
connected through a SPAN port on each second-tier switch through which
application and Web data is passing.
25

User Guide
Figure 7 APA Deployed at Enterprise Data Center
Network Performance Appliances

In the VPM system, Network Performance Appliance (NPA) devices are
deployed in the network to collect and report on NetFlow/IPFIX traffic information
from Cisco routers and managed switches, and flow standards from other
vendors. NPAs are typically deployed near large switches or tightly clustered
switches or routers where there is a high degree of NetFlow traffic.
In the VPM component hierarchy, NPAs are server-broad devices capable of
managing data on any selected domain on the server.
Figure 8 shows NPAs deployed in an enterprise network at the data center and
the corporate head office. The NPA located at the data center monitors NetFlow
data from routers at branch office sites, as well as from the router at the Data
Center site itself. The NPA at the corporate head office monitors NetFlow data
from the router and switches at that site. Data from the NPA is then uploaded to
the VPM server at hourly intervals. For more information on data processing, see
NetFlo.
26

System Architecture
Figure 8 NPA Deployment in an Enterprise Network
Figure 9 shows NPA deployment in a service provider network. NPAs are

positioned in proximity to provider edge routers in the service provider WAN.
NPA data is then uploaded to the VPM server(s) at the service providers network
operations center (NOC).
27

User Guide
Figure 9 NPA Deployment in a Service Provider System
ASEs
To get ASE software updates:
1
Open a Web browser and go to www.flukenetworks.com
Sign in as a Gold Member.
Select Resources > Downloads & Updates
Select the Analysis Service Element (ASE) Image Downloads (Log in to

View) link on the right hand side of the page.
Select the ASE software update that you want.
For detailed information on features and commands in each available ASE software
version, see the Visual UpTime ASE User Guide.
ASE software image files typically have the following filename format:
ISmmm_x_y_zzz.img
Where:
mmm = ASE Model Number
x = Major Software Version Number
y = Minor Software Version Number
zzz = Point Release Software Version Number
For example, the 3.1.051 software image file for a Model 165 ASE should have the
28

System Architecture
file name: IS165_3_1_051.img.
After downloading the software update, the preferred method of upgrading an ASE is
to use the PAC client. For more information, see the Visual UpTime PAC User Guide.
If you need to upgrade the ASE using a TFTP utility follow the instructions below:
To upgrade an ASE using TFTP:
1
A TFTP client is included on most Window platform installations (although it is

sometimes removed when systems are locked down), and can be easily
installed on Linux platforms. This client program will push the new image to the
ASE, where it will be committed to flash memory. Once stored, the ASE will
automatically reboot and begin running the new software. The upgrade
procedure usually takes less than 30 seconds.
Do not power off the ASE during an upgrade! Allow the ASE to commit the
new software image to disk and reboot itself.
When upgrading, it is important to ensure that the model number of the image file
matches the target ASE model number. To determine the model number of a given
ASE, telnet to the ASE and run the ID command. The first four digits of the serial
number is the units model number. Should you accidentally attempt to install an
incorrect image file, the ASE will reject the file.
Partner devices (such as CSU/DSUs, probes, routers, or access concentrators) that
are equipped with agent software can function as ASEs in the VPM system. These
devices are developed and produced by third-party companies in consultation with
Fluke Networks. The system software verifies whether such a device is licensed to be
managed by VPM. The capabilities available to a partner device are determined by
hardware limitations and the agent software implementation chosen by the partner.
Server
The VPM server consists of a Web server, which provides the web-based userinterface and security, and an Analysis server, which provides the data collection
from deployed devices, data storage, baselining, alarming, and notification.
The VPM server runs Microsoft Windows Server and Microsoft SQL Server. (For
supported operating systems for servers, see Table 1.) A single server can
support multiple Web portal users and PAC clients.
Server software can be provided on a pre-configured computer shipped by Fluke
Networks or installed by the customer on a computer that meets server
requirements defined in the Software Installation Guide.
The server computer typically resides in a central location, such as an
enterprises data center or service providers NOC, from which a WAN or set of
29

User Guide
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. For more information, see etwork Models .
All communication between clients and ASEs passes through the VPM server.
The server requests data collection and status updates from APAs, ASEs, and
NPAs. Web portal users access data through the Web server, which may be
hosted on the same machine or on a separate system. A stand-alone Web server
communicates with the VPM server using Transmission Control Protocol (TCP)
and User Datagram Protocol (UDP) over a configurable port. (See Figure 10)
Figure 10 System Communication with Stand-Alone Web server
Using VPM Server Administration and other tools on the server, a system
administrator can:
Administer multiple servers from a single user interface. Monitor server
status and configure server-wide and domain-level settings.
Control access to Application Performance Manager, Visual UpTime Select,
and Network Performance Manager features.
Control the access of users through group permissions to features.
Filter access to reports at the domain level.
Collect data and initiate database maintenance on one or all domains.
30

System Architecture
Perform large-scale configuration of ASEs and performance monitoring
settings using templates.
Maintain the license information that controls access to feature modules.
Create administrative reports that show information for server licenses,
domains and database usage, ASEs and NPAs, monitored applications, and
users and groups.
Data Analysis Server

In addition to system configuration information, VPM databases store application
performance data from APAs, application and network performance data from
ASEs, NetFlow data from NPAs, network configuration data, and access control
settings for users.
For more information about how data is managed in the databases, see Data
Management .
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 VPM server or on a separate
machine.
The Web server may be separated from users and/or the VPM server by a
firewall. A stand-alone Web server positioned behind a firewall limits Web portal
user direct access to the VPM server (see Figure 6). It can also serve as a single
Web portal for users to access multiple servers.
On the Web server, administrators use the System Management tool to configure
supported VPM servers.
Web Portal
The VPM 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 (see
Figure 6). For more information about Web portal features, see isual
Performance Manager Fe
31

User Guide
PAC
The Platform Applicable Client (PAC) runs on a Microsoft Windows PC. It is used
primarily for network and event configuration:
Add ASEs to the network and configure ASE physical, link, circuit, and
application monitoring settings.
Perform ASE data collection, update ASE software, and set event
destinations.
Configure state-change and network performance threshold events that
ASEs report.
Create and manage ASE templates.
PAC software is installed on the VPM server. More than one PAC can connect to
a single server. A single PAC can also connect to multiple VPM servers.
32

Network Models
Network Models
How VPM is deployed in a network varies according to customer needs. The
following typical customer scenarios are illustrated in this section:
an enterprise network hosting Visual Performance Manager
a WAN service provider and subscriber network
VPM can be implemented directly by an enterprise, or as a hosted solution from

a service provider, where the subscriber accesses network information over the
Internet or intranet. It is also used by service provider operations staff to
proactively manage multiple networks and to provide value services to
subscribers.
Enterprise Hosted System

For an enterprise hosted system the VPM server manages one networkthe
enterprises. Usually one domain is established on the server to securely hold
that enterprises network configuration and performance data. The server resides
at the enterprises data center, as does one or more APAs and an NPA. The APA
is deployed off a core switch or switches.
The enterprise owns and manages the ASEs and NPAs. ASEs are installed at
each end of a managed circuit and located on the CPE side of the WAN
connection, or demarcation point, and typically share the same IP address
space. Web portal users are connected via the Internet. See Error! Reference
source not found..
If the enterprise is using a service provider WAN for access across the network, it
may also use Visual UpTime Select feature modules to verify its service level
agreements with the provider. Ethernet ASEs may be deployed between a
customer edge router and LAN switch (as shown in Error! Reference source
not found.) or to a LAN switch SPAN port to analyze Ethernet traffic to and from
the WAN.
Service Provider Hosted System

Service providers use VPM to proactively monitor their networks and notify
subscribers of problems. Network operations staff also use VPM to provide
added value services to subscribers.
For a service provider, the VPM server manages many networksone for each
subscriber. The server is partitioned into multiple domains, one per subscriber, to
securely hold each subscribers network configuration and performance data.
The server machine and a PAC reside at the providers NOC inside the WAN.
33

User Guide
Subscribers access Visual UpTime Select data through the Web portal as part of
a service offering to verify the providers service. Each subscriber is assigned a
domain, and within each domain is a hierarchy of networks, sites, ports (on which
ASEs are located), and circuits (frame relay, ATM, or IP). Subscribers can
monitor the service providers network circuit using data provided by ASEs, which
are maintained by the provider.
In Figure 11, the provider has installed ASEs inside the WAN on all subscribers
circuits. In the figure, the VPM server has a separate domain for each subscriber
company. The provider can see data for each subscribers domain. Subscribers
A and B can view data simultaneously with the provider through the Web portal.
However, subscribers see data only for their own domain. Subscriber C has
purchased a level of service that does not include client access from the
provider.
NPAs are positioned in proximity to provider edge routers in the service provider
WAN. NPA data is then uploaded to the VPM server(s) at the service providers
NOC.
In a managed service offering scenario, APAs can be deployed when, for
example, a service provider manages and hosts data centers for multiple
companies. If a company has outsourced its data center it could either deploy its
own management infrastructure or buy monitoring services from the service
provider. Because VPM supports domain segmentation, different applications,
servers, and sites can be monitored in each domain by a single APA.
Figure 11 Service Provider Hosted System
34

Network Models
Data Management
As the database server, the VPM server stores several types of data gathered by
APAs, ASEs, and NPAs (see Figure 12):
Application performance data gathered by APAs
Application performance data gathered by ASEs
NetFlow data gathered by NPAs
Network performance data gathered by ASEs

Network configuration data
Access control settings for users
Figure 12 VPM Server Data Storage
Data Collection and Storage

Data collection on the VPM occurs at different intervals for APAs, NPAs, and
ASEs (see Figure 13).
Status and aggregated performance data from APAs is downloaded to the VPM
server once per minute. It is stored on the server in 1-minute granularity for 10
35

User Guide
days, 1-hour granularity for 2 months, and 1-day granularity for a year. APAs also
communicate transaction and client profile data through the server to be
available for display in the Web portal applications.
NPA data is collected hourly and stored for up to n
weeks (52 by default) in a long-term database on the
VPM server.
36

Data Management
Figure 13 Movement of Application and Network Performance Data
ASEs collect and store second-by-second application and network performance

data in memory in 15-minute increments for two days, with new data overwriting
the oldest so that the most recent data is always available. This historical data is
downloaded to a VPM server when it initiates ASE data collection. ASEs also
communicate current and real-time network performance data through the server
to be available for display by client applications.
The short-term database on the server stores 14 days of application and network
performance data gathered by ASEs in 15-minute increments. This data is
downloaded from the ASE each time ASE data collection occurs (daily by default
at 1:00 AM). Each time database maintenance occurs (daily by default at 2:00
AM), data is copied from the short-term database to the long-term database and
any data more than 14 days old is purged from the short-term database.
The short-term database also stores network configuration and statistical event
data for performance monitoring (entered from a PAC), and access control
settings (entered from the server). This information remains in the short-term
database and is updated when new information is entered through the PAC or
37

User Guide
server user interfaces.
The long-term database on the server stores up to n weeks (52 by default) of
network performance data in 1-hour increments for use in reports. The long-term
database capacity is determined for the server at the time of purchase.
ASE data collection and database maintenance, which trigger this data transfer,
can be scheduled and performed on demand from the PAC. Data collection can
also be performed from the Web portal. You can also modify the number of
weeks of data stored in the long-term database from the server.
See Managing ASEs.
Application Performance Data from APAs

Performance data gathered by APAs is aggregated across applications, servers,
subnets, and protocols. This data is available via Web portal Application
Performance Management Application, Server, and Site views and in reports. For
information on data aggregation, see Data Collection and Storage.
Application Performance Data from ASEs

When you purchase the Visual UpTime Select AppFlows feature module, ASEs
that support this feature collect and store port-level application flow data (octet
counts and application server network connect and application response times)
in memory in 15-minute increments for up to two days. They download this
information to the VPM server during data collection. ASEs also communicate
current and real-time application flow data through the server for display in
Application Flows real-time mode views.
Application flow history data is stored in the short-term database for up to two
weeks (see Service Summary Data ). This data is used to generate Application
Summary data during database maintenance.
Application flow data provides detailed information about the source host,
application, and destination host at a specific port. This data is shown in
Troubleshooting port Application Flows views.
Aggregated application performance data is shown in the Application Summary
Daily Summary, Application Usage, Alarms (new alarms, usage alarms and
performance alarms), Servers, and Reports views.
In Application Summary, daily data is stored for between 28 days and 8 weeks
depending on the type of data. In addition, weekly and monthly data used in
reports can be stored for up to 1 year. In other Application Summary views, port
application data is rolled up to provide a domain-wide view of application and
application server performance across the network by full day for up to the past
28 days and compared to the 28-day average.
38

Data Management
Note
Make sure each site hosting an application server has an ASE installed at
the site, so that you can monitor server performance.
NetFlow Data from NPAs

The Visual Performance Manager server and NPAs have IP connectivity. On the
server, the data collection process queries NPAs hourly for the following data:
Currently monitored devices and interfaces and changes in status.
Performance related data, including interface usage, application usage, and
top N data, used in domain-wide NPA reports.
This data from the NPA is then uploaded to the server (see Figure 14). Data
collection of a given hours data occurs at least 15 minutes after that hour has
completed.
Data that was not available during one polling cycle (for example, if the NPA was
unreachable) is collected during the next cycle. Data collection for a newly added
interface begins with the first regularly scheduled import after detection.
Performance data from previous hours is not retroactively collected.
Figure 14 Data Management
Once in the VUpTimeNF database, long-term data for NPA reports is stored by
default for up to 52 weeks. It is maintained at 1-hour granularity. You can
determine the number of weeks to keep long term data for all reports from the
server.
Network Performance Data from ASEs

A VPM server collects and stores network performance data from all ASEs that
have been configured from the Network Configuration tool on a PAC. This data is
stored in two databases on the serverthe short-term and long-term
databasescollectively referred to as the network performance database.
39

User Guide
Network performance data captured by ASEs and stored in the servers network
performance database include:
Physical layer dataExposes the integrity of the physical circuit between the
subscribers premises and the WAN service providers point of presence.
Collected data includes real-time transmission performance measurements
and historical trends of transmission attributes. It can be used to identify
customer edge router issues.
Link layer dataExposes the integrity of the WAN service and on isolating
problems from the subscribers equipment and applications. It also provides
views into the use of and errors in frame relay, HDLC, ATM, and Ethernet
links.
Payload dataExposes the integrity of the data traffic. Collected data
includes real-time statistics and historical trends of application activity.
Service level verification metricsExposes the efficiency of the data delivery.
Collected data includes round-trip delay, circuit availability, and data delivery
ratio measurements for frame relay circuits using Committed Information
Rate (CIR) and Excess Information Rate (EIR) metrics, and for ATM circuits
using Cell Transfer Delay (CTD) and Cell Delivery Ratio (CDR) metrics. For
IP circuits, round-trip delay and packet delivery ratio are measured for
classes of service using Committed Access Ratio (CAR) metrics.
Service Summary Data

Service Summary data, which is shown in Visual UpTime Select, includes:
Updates of layer 2 up/down status on ASE-monitored ports polled from ASEs
every 15 minutes and circuit up/down status polled every 2.5 hours.
Port history (link up/down status) stored in 1-hour intervals for the most
recent three days.
The five most recent port and circuit events uploaded by ASEs, updated
every 15 minutes or when you refresh the Port and Circuit Details page in
Service Summary. An ASE uploads recorded events as they occur to the
Service Summary process in the VPM server and to the network
performance database.
Up to 2 weeks of port and circuit events that have occurred on the domain.
Data shown for events includes event priority, description, location, time, and
type.
40

Data Management
Figure 15 Service Summary Data Flow
Service Summary Data Flow illustrates how Service Summary data is processed.
On the VPM server, the Service Summary process polls ASEs for status data
and received events every 15 minutes (this setting can be changed from the
server). A middleware component in the Service Summary requests updates
from the poller every 15 minutes, and interfaces with the Web server to make
detected ASE status changes available to Web portal users.
In response to a Web portal users refresh, the Web server initiates a check in
the Service Summary poller for status updates received from ASEs. For more
information, see Managing Web Access.
41
2. Server Overview
The VPM server is a dedicated, uniquely configured database and Web server that stores application and
network performance data from ASEs, NetFlow data from NPAs, network configuration data, and access
control settings for users.
Visual Performance Manager servicesOverview of services, server integrity and performance, and
databases.
Server applicationsOverview description of the three VPM applications on the server.
Administrative tasksSetup, configuration, and maintenance tasks that you will need to perform
when managing the system.
Starting and stopping servicesSteps for starting and stopping VPM and SQL Server services.
For a complete overview of the server and its relation to other system components, see Chapter 1, Visual
Performance Manager Overview.
Visual Performance Manager Services

The server stores and retrieves data for other components of the VPM system. The software that
performs this function is called Visual Performance Manager services. VPM services run as a Windows
service, which allows them to start automatically when the computer starts. These services do the
following:
Collect and store network and application performance data from ASEs.
Collect and store data from partner devices and manage associated license data for partner devices.
Partner devices are devices equipped with agent software that enables them to function as ASEs in a
VPM system. These devices are developed and produced by companies in consultation with Fluke
Networks.
Note
Partner devices may provide only some VPM features in their agent software. As a result, some
interfaces on the server may display differently or may be unavailable for partner devices. These
differences, when known, are noted.
Manage the network performance database (see Data Storage).
Server Overview
Visual Performance Manager Services
Provide communication with PACs through a Remote Procedure Call (RPC) server.
Provide managed user accounts, and thereby control access to network data and VPM capabilities.
Perform large-scale configuration of ASEs and network performance monitoring through the use of
templates.
Provide long-term data to clients.
Server Integrity and Performance

A server computer is a dedicated computer provided by Fluke Networks with factory-installed VPM
software or a server you have configured for the use of VPM software. Use a server computer only for:
Running VPM services.
Using the VPM Server Administration software.
Performing other VPM system administration tasks.
Running the PAC software.
To maintain system security you may need to apply patches to Windows and related system software.
Policy on Additional Third Party Software briefly identifies these and presents recommended courses of action.
For detailed information about supported third party software for the VPM server, including supported
Windows service packs and mandatory and allowed patches, see the TAC Customer Care website (see
Technical Support on page xiv).
After logging in, select Policies and click the Software Support Policy link.
Note
Check the TAC Customer Care website before loading any new service packs or patches.
Warning
DO NOT install other software applications on the VPM server other than those approved by
Fluke Networks. The installation of other software particularly network management
applicationscan use critical resources, may degrade integrity and performance, and may
void the sales and service/support warranty.
It is also recommended that you subscribe to the Microsoft Product Security Notification Service to
receive alerts from Microsoft regarding new security information. See the following URL:
http://www.microsoft.com/technet/security/notify.asp
Table 2
Policy on Additional Third Party Software
43

User Guide
Software
Action
Critical security updates for Microsoft

Windows, IIS, and Internet Explorer
ApprovedInstall.
Non-critical security updates for

Microsoft Windows, IIS, and Internet
Explorer
Consult the Customer Care website.
Supported Windows, SQL Server, IIS,

or Internet Explorer service packs
Consult the Customer Care website. In

most cases, new service packs are not
supported for existing releases.
Virus checking software
Consult the Customer Care website for

approved virus checkers and configuration
requirements.
Remote backup software
System management tools
Remote management software
Windows Terminal Server is approved.
Always upgrade server software versions sequentially to ensure thorough database conversions. Refer to
the Software Installation Guide for complete installation information.
Data Storage
A server collects and stores network performance data from ASEs that have been configured via the
Network Configuration tool on a PAC. This data is stored in two databases on the serverthe short-term
(VUpTime) and long-term (VUpTimeLT) databases.
Short-term databasestores 14 days of network performance data in 15-minute increments. A
server downloads these data packets from the ASE each time ASE data collection occurs. The
default is daily at 1:00 AM. Each time database maintenance occurs (by default, daily at 2:00 AM),
the server copies data from the short-term database to the long-term database. Any data more than
14 days old is purged from the short-term database.
The short-term database also stores network configuration and performance monitoring event
configuration data (entered from a PAC), and access control settings (entered from the server). This
information is updated when new information is entered through the PAC or server user interfaces.
Long-term databasestores up to n weeks (the default is 52) of network performance data in 1-hour
increments for use in reporting. Long-term database capacity is determined by the size of the server
computer at the time of purchase.
44
Server Overview
Server Applications
Both ASE data collection and database maintenance, which trigger this movement of data, can be
scheduled and performed on-demand from the server or PAC. Data collection can also be done from the
VPM portal. You also can change the number of weeks of data stored in the long-term database.
Server Applications
In addition to VPM services, the server includes the following applications that help you perform
administrative functions:
Server AdministrationCheck server connectivity and database usage, and monitor agent/license
usage. (See Chapter 4, Monitoring Servers.) Establish criteria for secure user access to VPM. (See
Chapter 6, Managing Users.) Configure server-wide settings such as Service Summary thresholds,
ATM Class of Service, and licensing.
Remote Server AdministrationRun the Server Administration application from a computer other
than the server computer. You can use Remote Server Administration from a different server
computer or from a computer that has network access and the proper configuration. For information
about installing Remote Server Administration, see the Software Installation Guide.
Administrative Tasks
Table 3 lists the administrative tasks involved in configuring and maintaining the VPM system.
Table 3 System Administrative Tasks
Task
Use...
See...
Install VPM software upgrades on server. (Users install new

or upgraded software on PACs.)
server
Manage licensing for VPM.
Local/Remote Server
Administration
Configuring Licenses
Transfer (or migrate) one or more VPM domains from one

server to another.
SQL Server on server

and ASE Trap
Destinations on PAC
Moving a Domain to a Different

Server on page 200
Update ASE software to ensure ASE compatibility with VPM.
PAC
Updating ASE Software on the

PAC in the PAC User Guide
Determine PVC requirements for Application Flows.
Server
Chapter 5, Provisioning
Management Communication in
the Visual UpTime ASE User
Guide
Monitor server connectivity, network performance database

utilization, and other status items.
Server Administration
Chapter 4, Monitoring Servers
45

User Guide
Table 3 System Administrative Tasks
Task
Use...
See...
Make sure that you have Web access to the server.
Chapter 6, Managing Users

Configure VPM domains, or subsets of data and users.
Local/Remote Server
Administration
Managing User Groups on

page 122
Configure user accounts and assign permissions within

domains.
Local/Remote Server
Administration
Chapter 6, Managing Users
Configure IP Class of Service settings for IP Transport ASEs. Local/Remote Server

Administration
Configuring an IP Class of
Service Template on page 98
Configure reporting capabilities for all users of the server.
Local/Remote Server
Administration
Configuring Report Permissions

on page 105
Configure the networks and sites in the network performance

database.
PAC Network
Configuration
Chapter 2, Network
Configuration in the PAC User
Guide
Configure access lines and circuits in the network

performance database. You can configure these one at a time
(for custom configurations) or many at a time across one or
more networks (for common configurations).
(one at a time) PAC

Network Configuration
Chapter 2, Network
Configuration in the PAC User
Guide
Configure the performance monitoring events for ASEs to

report. You can configure these one at a time (for custom
configurations) or many at a time across one or more
networks (for common configurations).
(one at a time) PAC

Chapter 3, Performance
Performance Monitoring Monitoring in the PAC User
Guide
(many at a time) PAC
Templates
Chapter 4, Using ASE

Templates in the PAC User
Guide
Configure a VPM Web server.
Web System
Management Utility, on
the Web server
Chapter 8, Managing Web

Access
Assign panel permissions to groups and set up user group

page templates for Web portal users and
Web portal
Chapter 3, Administration, in
the Visual Performance Manager
User Guide
Set priority levels for state-change events.
Configuring Domain-Wide Event

Priorities on page 89
Make sure that ASEs are functioning correctly.
Web portal
Performing an ASE Inventory in

the Visual UpTime Select User
(many at a time) PAC

Templates
Chapter 5, Using ASE

Templates in the PAC User
Guide
46
Server Overview
Starting and Stopping Services
Guide
Task
Use...
See...
Schedule routine data collection from ASEs. (Default time is

daily at 1:00 AM)
Setting a Default Data Collection

Time on page 84
Perform on-demand data collection from ASEs.
Performing Data Collection on

Demand on page 85
Schedule routine database maintenance. (Default time is daily Server Administration

at 2:00 AM)
Scheduling Daily Database

Maintenance on page 87
Perform on-demand database maintenance.
Performing Database
Maintenance for a Domain on
page 85
Perform routine backups of the performance database and

perform on-demand backups when required by certain other
tasks.
Server Administration,
SQL Functions on the
server
Backing Up and Restoring

Databases on page 200
Restore the database from backup when necessary.
SQL Functions on the

server
Backing Up and Restoring

Databases on page 200
Consult FAQs when troubleshooting and contact the VPM

vendors technical support when needed.
server
Chapter 9, Frequently Asked

Questions
PAC
Chapter 6, Frequently Asked

Questions in the PAC User
Guide
Starting and Stopping Services

When the server computer is powered up, VPM services and the SQL Server automatically launch and
the server becomes active without any input from the user. Consequently, if the server computer power is
cycled off and on, the server software will automatically restart and become available for use.
After the server computer is started, you are prompted to log in to Windows. (You must log in to Windows
to access server programs.) Keep Server Administration running while you are working at the server, so
that you can be informed of status changes quickly.
VPM services and SQL Server generally run uninterrupted. Under normal conditions, do not power down
the server computer or stop either SQL Server or VPM services. The server should run continuously to
ensure timely ASE data collection and uninterrupted client access to the network performance database.
47

User Guide
Warning
For non-routine events, stop VPM services only when instructed to do so. Notify Web portal
and PAC users that the server will be temporarily unavailable before stopping VPM services.
To see if any users are logged in, use the Server Administration reporting tool. See
Identifying Active Users on page 64.
To manually stop and start VPM services:
1
Stop the Visual UpTime Select Web Application service.
Stop the Visual Performance Manager Server service.
Stop the MSSQLSERVER service.
Start the MSSQLSERVER service.
Start the Visual Performance Manager Server service.
Start the Visual UpTime Select Web Application service.

Note
Some actions may require that you stop VPM services, but leave SQL Server services running.
To stop only the VPM server or SQL Server:

1
Select Start > Settings > Control Panel > Administrative Tools.
Double-click Services to open the Services control panel.
In the list of services, select the serviceVisual UpTime Select Web Application, Visual
Performance Manager Server, or MSSQLSERVERand click Stop.
Click Yes to confirm stopping the service.
Verify that the services Status column no longer says Started.
To start just the VPM server or SQL Server:

1
Select Start > Settings > Control Panel > Administrative Tools.
Double-click Services to open the Services control panel.
In the list of services, select the serviceMSSQL Server, Visual Performance Manager Server, or
Visual UpTime Select Web Applicationand click Start.
Verify that the services Status column now says Started.
48
Monitoring Servers
Managing the Server Monitor List
3. Administering System Security
This chapter covers recommended security procedures that you should perform on the server computer.
These include assigning access privileges to user accounts and setting security options and audit policies
within the Windows server. You can leave the default security settings that were configured when you
purchased the server computer from Fluke Networks, or you can establish and configure your own
security policies in Windows.
Setting up server securityDefault user accounts, password policies, audit policy, critical files, and
registry access.
Firewall configurationRecommended firewall configuration settings for use in a service provider
network environment.
Note
You must log in to your server with Administrative privileges to verify the security settings detailed in
this chapter.
For information about adjusting optional security settings on the VPM server, see Chapter 4, Setting up
the Server, in the Software Installation Guide.
Server Security
The security design of the VPM server provides for user authentication, access control, and auditing. It
uses existing applications on the Windows operating system, SQL Server DBMS, and server software.
The security component in the server software uses the access control features of SQL Server to prevent
one customer from accessing another customers (potentially sensitive) network and application
performance data. Server application security also helps prevent unauthorized access to Windows.
Default User Accounts

This section identifies the default user accounts defined for a new server system.

In Server Administration, you can launch the application and view server status without logging in.
However, to view or edit server settings you must log in.
49

User Guide
When you run certain SQL Server applications, you may be prompted to provide your SQL Server system
administrator password. When you are finished using any of these applications, close them. For security
reasons and to conserve system resources, do not remain logged on to VPM or SQL Server
unnecessarily.
Table 4 summarizes the different logins required to access server capabilities.
Table 4 Server Logins
Login Type
Default User Name

and Password
When Requested
Windows
name: vuptime
password: Visual1
After the server computer boots, or

after logging off from the Windows
server, you can access general
system and VPM software.
VPM default
login
name: VPMadmin
password: vpm
In Server Administration, when you

want to do more than view server
status.
When you launch the Web portal or
PAC.
Internet
Information
Server
account
name: vuptime or
IUSR_[Name], depending
on the original version of
VPM installed on your
server computer
password: visual
Not explicitly requested, but used by

the server for Web services
SQL Server
name: sa*
password: VPM@dmin1
When you use some SQL Server

utilities
*For Visual Performance Manager Turnkey Server only.
To find the IUSR_<Name>:

From the Windows desktop, right-click My Computer and select Manage.
1
In the Computer Management (Local) window, expand Local Users and Groups > Users. Check
for the user IUSR_<Name>.
SQL Server and VPM services start automatically when you power up the server computer. You are not
required to log into Windows. (See Starting and Stopping Services.)
Windows Server
The Windows Server operating system on the server computer comes with two user accounts defined:
administrator and vuptime, both of which are assigned to the Administrative group. The Administrative
group has administrative privileges on the current server computer, and not the VPM network domain.
50
Monitoring Servers
Password Policy
By default, the passwords for the two default Administrator user accounts (administrator and vuptime) are
configured never to expire. Protect these accounts by changing their passwords to restrict access to the
server computer.
At server setup, Windows user account definitions are restricted to vuptime and administrator.
Authenticating and Controlling Access to the Default Web Site

Authentication and access control of the default web site must be set to enable anonymous access.
To verify anonymous login for Default Website:
1
Click Start > Programs > Administrative Tools > Internet Services Manager.
Expand local computer --> Web Sites. Right-click Default Web Site and click Properties.
Select the Directory Security tab and click Edit under Authentication and access control.
In the Authentication Methods dialog, Verify that anonymous access is set to Enabled and the
user name is set to IUSR_<Name>.
Under Authenticated access, verify that Integrated Windows Authentication is selected.
Assigning Passwords
To assign a password to any of the login names listed in Server , follow the procedures in this section.
Your Windows server may have been configured to enforce restrictions on passwords, such as limitations
on password reuse. Check the Windows Server Computer Management for the password and audit
policies on the server.
Warning
Do not change any user names assigned to these logins. Also, the password of the Windows
IUSR_<Name> user must match the password for the anonymous login of the WWW service.
To secure the Windows login:
1
Select Start > Programs > Administrative Tools > Computer Management.
Select System Tools, Local Users and Group, then select Users. Select the user name vuptime.
Select Action, then select Set Password and assign a password.
In the same dialog, select the IUSR_Name user name, then repeat the Set Password process in
step 3.
Warning
Make certain that you assign the same password to the WWW service login, as explained in
the next procedure.
51

User Guide
To secure the WWW service login:
1
Select Start > Programs > Administrative Tools > Internet Services Manager
In the left pane of the Internet Services Manager window, click the name of the server.
Right-click Default Web Site and select Properties.
Select the Directory Security tab.
Click the Edit button in the Anonymous access and authentication control section.
Check the Anonymous access box and click the Edit button.
Enter a password for the anonymous login and click OK.
To secure the SQL Server or VPM database login:

1
Select Start > Programs > Microsoft SQL Server > Management Studio.
In the left pane of the Management Studio window, click the + icon next to Microsoft SQL Servers,
then SQL Server Group, SQL Server server (where server is the hostname of the server computer),
Security, and finally Logins to expand these folders.
For SQL Server system administratorright-click the sa user name.
For VPM database administratorright-click the vupadmin user name.
Select Properties and assign a password.
Verifying Password Policy and Enforcement

Windows password policy options are exposed through the Security Settings extension to the Group
Policy Object Editor.
To verify Windows password policy settings:
1
Click Start > Run, enter Gpedit.msc. Click OK. The Group Policy Object Editor window opens.
In the left pane of the Group Policy window, expand Computer Configuration > Windows Settings
> Security Settings > Account Policies.
Click Password Policy.
View the Local Setting values for all password policies in the right pane. Apply settings based on
your companys policies. Use the settings in Windows Password Policy Settings as a guide.
Table 5 Windows Password Policy Settings
Policy
Sample Local Setting
Enforce password history
Remember 6 Passwords
Maximum password age
0 (never expire)
Minimum password age
2 days
52
Monitoring Servers
Table 5 Windows Password Policy Settings
Policy
Sample Local Setting
Minimum password length
0 characters
Maximum password length
40 characters
Passwords must meet complexity

requirements
Enabled. Requires the use of upper

and lower case characters and
numbers.
Store password using reversible

encryption
Disabled
To verify effective password enforcement:

Make sure that the value under the Local Setting column for the policy passwords must meet
complexity requirements is set to Enabled. When enabled, this setting restricts the content of
passwords. It requires a combination of upper and lower case letters and numbers, and prevents the
use of all or part of the account name.
Password Lockout Policy

In Windows Server, the password lockout policy determines how and if a user is prevented from logging in
to the system after exceeding a set number of login attempts. You need to configure Password Lockout
settings. These settings are located under the Account Policies pane of the Group Policies window
(see Verifying Password Policy and) and must match the settings in Password Lockout Policy Settings .
Table 6 Password Lockout Policy Settings
Policy
Local Setting
Account lockout threshold
Lockout after three invalid logon attempts
Account lockout duration
30 minutes
Reset account lockout counter after
30 minutes
Audit Policy
In Windows Server, the audit policy determines which security events are logged into the Security log on
your server computer. An audit records an entry whenever users perform certain actions that you specify.
For example, the modification of a file can trigger an audit entry. The audit entry shows the action
performed, the associated user account, and the date and time of the action. You can audit both
successful and failed attempts at actions.
53

User Guide
You establish an audit policy by selecting the types of security events (actions) to be audited. When such
an event occurs, an entry is added to the Security log. Your server computer is shipped with auditing
enabled on critical Windows Server, VPM, IIS Server, and Windows Registry files.
To set the audit policy:
1
Select Start > Programs > Administrative Tools > Local Security Policy.
Expand Security Settings, Local Policies and select Audit Policy.
Apply settings based on your companys policies. Use the settings shown in Audit Policy Settings as a
guide.
Table 7 Audit Policy Settings
Audit Policy
Success Failure
Audit account logon events
Audit account management
Audit directory service access
Audit logon events
Audit object access
Audit policy change
Audit privilege use
Audit process tracking
Audit system events
Security Logs
You use the Windows Event Viewer to examine security logs. Because security logs are limited in size,
change the events to be audited carefully, and consider the amount of disk space you are willing to
devote to the security log. The maximum size of the security log is defined in the Event Viewer.
The following security logs come pre-configured on your server computer:
Application logRecords events logged by applications or programs. For example, SQL Server
could record a file error in the application log.
System logRecords events logged by the Windows system components.
Security logRecords security events such as valid and invalid log on attempts, as well as events
related to resource use such as creating, opening or deleting files. (See Table 7 for recommended
settings.) For example, if you have enabled Audit logon events, attempts to log on to the system are
recorded in the security log.
54
Monitoring Servers
All three server security logs have the following default settings:
Event Log Wrapping is set to Overwrite Events as Needed.
Event Viewer log size is set to a maximum of 5056K.
To verify Event Log Wrapping:
1
Open Event Viewer by clicking Start > Settings > Control Panel. Double-click Administrative
Tools, and then double-click Event Viewer.
In the console tree, click one of the three server security logs.
On the Action menu, click Properties.
On the General tab, select the Overwrite events as needed option under Log size. If the Overwrite
events as needed option is not selected, the log may fill to capacity and newer events will not be
logged.
To check the Maximum Log Size:

On the General tab, in Maximum log size, verify the new log size in kilobytes for each log file. A
larger log size allows more history to be retained before overwriting older events.
Critical Files
Add file modification auditing for all files in the server software directory tree (c:\Program
Files\Fluke Networks\Visual Performance Manager Server) with the following extensions:
.cab, .dll, .exe, .img, .jar, and .sql.
To implement file modification auditing:
1
Right-click the appropriate directory in Windows Explorer and select Search in the context menu. The
Search Results dialog appears.
In Search for files or folder named, enter the file extension for the type of file you want to audit
preceded by a period and the * (asterisk) wildcard symbol (for example, enter *.exe to search for
executable files). Then click Search Now.
Locate all types of files listed above.
Press Ctrl+A to select all files found. Then press Alt+Enter to display the Properties dialog.
In the Properties dialog, select the Security tab and click Advanced. The Access Control Properties
dialog appears.
Note
If your computer is on a domain in which other policies override this permission or if you do not have
proper permission, your system may not display the Security tab.
55

User Guide
In the Access Control Properties dialog, select the Auditing tab. Click Add to add a new audit entry.
The Select User or Group dialog appears.
In the user list, select the group named Everyone and click OK. An Auditing Entry dialog appears,
listing file access events that are available for auditing.
Check the items as indicated in File Access Audit Settings.
56
Monitoring Servers
Table 8 File Access Audit Settings
File Access Event to Audit Successful Failed
Write attributes
Write extended attributes
Delete subfolders and files
Delete
Change permissions
Take ownership
Click OK to save the auditing entry. Click OK to close the Access Control Properties dialog. Click OK
to close the Properties dialog.
Enabling Registry Access

You must enable auditing of the Windows Registry and enforce the following restrictions for modifying the
57

User Guide
registry:
Restrict remote registry key access for all except members of the Administrators group.
Prevent unauthenticated remote user access by restricting anonymous sessions.
To verify that remote registry key access is restricted for all except members of the
Administrators group:
1
Click Start > Run, enter regedit and click OK.
In the left pane of the Registry Editor window, expand the HKEY_LOCAL_MACHINE sub-tree by
clicking the + icon.
Continue expanding through the key and sub-key registry folders (through the path shown below)
until the Winreg entry is shown:
System\CurrentControlSet\Control\SecurePipeServers\Winreg
Click the Winreg entry, and then select the Permissions from the Security menu.
Verify that the Administrators group has sole access to this key.
To prevent unauthenticated remote users from gathering system information:

1
Expand or collapse (as necessary) the HKEY_LOCAL_MACHINE sub-tree folder in the navigation
pane to the following registry path:
System\CurrentControlSet\Control\LSA
Double-click the LSA sub-key to expose the entries in the topic pane (on the right of the Registry
Editor window).
Verify that the RestrictAnonymous REG_DWORD entry (with a value of 1) appears in the LSA subkey entry listing.
Configuring Firewalls
VPM deployment in a WAN service provider environment can present security challenges not present in a
service subscriber environment. This section 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 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 providers 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.
58
Monitoring Servers
For more information about the port requirements, see Appendix A, Open Ports for Firewall
Configuration.
Setting Server Port Numbers

By default, the server uses random TCP port numbers for its side of the communication with PACs.
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.
In the left pane of the Registry Editor window, expand the HKEY_LOCAL_MACHINE sub-tree by
clicking the + icon.
Continue expanding through the key and sub-key registry folders through the following path:
HKEY_LOCAL_MACHINE\Software\Fluke Networks\UpTime\RPC Server\
Click the RPC Server folder, and select Edit > New > DWORD Value. The Registry Editor creates a
new value in the RPC Server folder.
Enter Port as the name of the new value. Double-click the value. The Edit DWORD Value dialog
appears.
In Value Data, enter the port number you want to use for the RPC server. This value must be a
decimal integer between 1024 and 65535.
In Base, select Decimal. Click OK.

59

User Guide
8
Exit from the Registry Editor.
Configure your firewall to allow incoming access to the servers RPC server on the specified port.
10 Restart the VPM services.
Firewall Port Settings

If your system includes firewalls between servers, NPAs, the ASE data collection network, Web servers,
and VPM clients, then you must configure these firewalls to match the communication port settings shown
in Appendix A, Open Ports for Firewall Configuration.
60
4. Monitoring Servers

Running Server AdministrationUse the Server Administration application to get an overview of
server status and run Remote Server Administration.
Managing the server listMonitor local and remote servers and add and remove servers from the list.
Viewing detailed server statusView detailed status on a selected server.
Polling Server StatusPoll servers to check SQL Server to determine database sizes, the number of
domains defined, and the number of ASEs defined. Set the server polling refresh rate.
Logging in to Server AdministrationLog in to view active user details and configuration settings.
Identifying active usersView details on users logged in to VPM.
Generating administrative reportsRun reports on applications, ASEs, users and groups, server
performance, system and network configuration changes, and licensing.
Monitoring APA data flowSet up e-mail alerts notifying you if APA data import to the server fails.
Running Server Administration

The Server Administration application monitors one or more servers by periodically requesting their
status. From the server status screen, you can view:
Current database storage allocation and usage.
Licensing information, for example, to determine whether licensing assignment has reached the
preset licensing limit. Find key information about a servers license or report whether a devices
licensing data is unknown.
To start Server Administration on the VPM server:
1
Select Start > Programs > Fluke Networks > Visual Performance Manager Server > Server
Administration.
If the license agreement appears, click Accept to accept the terms of the license and proceed.

User Guide
Note
Server Administration does not require you to log in to VPM to view server status. However, to
expand a server icon and configure its settings, you must log in using an account on that server.
You typically will run Server Administration with its window minimized. The applications icon on the task
bar indicates problems by changing color to reflect the most severe status of any monitored server. When
the application icon is yellow or red, restore the Server Administration window and investigate the
problem.
Server Administration shows one server icon for each monitored server (see Figure 16).
Figure 16 Monitoring Server Status
The server icons on the left side of the window are color-coded to reflect the status of the server (see
Table 9.
Table 9 Server Icon Colors
Color
Meaning
Gray
The server has not yet been contacted.
Green
Operational (no problems detected).
Yellow
Warning (may require attention).
Red
The server is unreachable.
The right side of the window shows a brief status message for each server. Table 10 describes these
status messages in increasing order of severity.
Table 10 Server Status Messages
Server Status
Icon
Cause
Recommended Action
Not contacted yet
Gray
Server Administration just started.
Wait about 30 seconds.
62
Monitoring Servers
Server Status
Icon
Cause
Recommended Action
No problems
detected
Green
None.
Insufficient DB
space
Yellow
The volume of data stored in one of the

databases is at or above 90 percent of
the current capacity of that database.
(For agent licenses, the icon in the
% Used column under the License
Information tab will also change to red
if the % Used value equals or exceeds
90 percent.)
Return to Server Administration and double-click

the servers icon for more details about space
availability and supported ASEs.
Either the duration (in weeks) of longterm archive storage is too long or the
number of ASEs in the network is too
great.
One of the databases may also have a fixed limit

and is not allowed to auto-grow. Either increase
the size of the specific database that is nearly full
or set the database to auto-grow.
Change the number of weeks for which longterm archives are maintained or to delete any
obsolete ASEs from the server in Domain
Configuration. (See Managing User Groups on
page 122.)
If these actions still do not release sufficient

database space, contact Fluke Networks s TAC
for a server computer hardware upgrade or for
assistance in optimizing the databases use of
space.
DB info not
available
Yellow
The monitored server is running a

different version of VPM software from
the server that is running Server
Administration.
If this is a known difference in software versions

(and you do not want to upgrade), remove the
server from the list of monitored servers.
Otherwise, upgrade the monitored server. Refer
to the Software Installation Guide.
License info not

available
Yellow
Server Administration cannot gain

access to the license information of
one or more of the ASEs being
monitored.
Use Server Administration to make sure the

proper license information for the ASEs has
been entered. If this action fails to clear the
message, contact your VPM vendors technical
support representative.
ASE info not

available
Yellow
One or more monitored ASEs are

running software incompatible with
Server Administration.
Update ASE software in PAC Network

Configuration. See Updating ASE Software on
the PAC in the PAC User Guide.
Unreachable
Red
The server or the network connection

to the server may be down.
First verify that the server is running, then verify

IP connectivity between your local server and the
server with the red status. If the problem
persists, contact your VPM vendors technical
support.
Server license
expires soon
Yellow
The server license is close to expiring.
Obtain a new license from Fluke Networks and

enter it into Server Administration. See
Configuring Licenses.
63

User Guide
Server Status
Icon
DB log file size may Yellow

be too small
Cause
Recommended Action
The long-term, short-term, or NetFlow

database transaction log file size is
less than 5 percent of the database file
size.
Set the log file size to be greater than 5 percent

of the database file size. To turn off this setting,
see Setting a Database Log File Size Warning.
Note: When you turn off this setting, the status
will not indicate when the log file size is less than
5 percent of the database file size.
Running Remote Server Administration

As an alternative to running Server Administration on the server computer itself, you can install and run
Remote Server Administration on any workstation. For information about installing Remote Server
Administration, see the Software Installation Guide.
Use Remote Server Administration exactly as you would Server Administration at a server computer.
However, you cannot change backup settings using Remote Administration. (In this guide, any mention of
Server Administration also refers to Remote Server Administration unless otherwise indicated.)
To start Remote Server Administration:
1
Select Start > Programs > Fluke Networks > Visual Performance Manager > Remote Server
Administration.
If the license agreement appears, click Accept to accept the terms of the license and proceed.
Note
Some Server Administration functions, such as deleting a VPM domain, require that you restart
VPM services. If you are using Remote Server Administration, make sure that your Windows user
account has permission to stop and start Windows services on the target server computer. See the
Software Installation Guide and the Windows Server online help for instructions on setting security
in Windows.
Closing Server Administration

If Server Administration is closed, servers are not monitored until the application is started again.
However, VPM services will still run, the server continues to collect data from devices, and PACs and
Web portal users can still connect to the server.
To close Server Administration:
Select Action > Exit.
64
Monitoring Servers

The Server Administration application is pre-configured to monitor the local server. If your organization
has more than one server, you can monitor them all from one location using Server Administration. To do
this, add the remote servers in Server Administration.
Note
Servers to be monitored must have IP connectivity to the computer where Server Administration is
running.
To add a remote server to Server Administration:
1
In Server Administration, select the Visual Performance Manager Servers item. All servers are
listed (see Figure 16).
Select Action > Add Server. The Name and IP Address Setup dialog appears.
In Display name, enter a descriptive name to identify the server. (The display name has no
significance outside of Server Administration.)
In Server IP address or host name, enter the host name or IP address of the server.
Click OK.
Take the following steps to remove a server from the list of monitored servers.
Note
Removing a server only causes Server Administration to stop monitoring it. The server itself is
unaffected by this action.
To remove a server from the list:
1
Right-click the server icon and select Delete Server. Server Administration shows a message asking
you to confirm the deletion.
Click OK to remove the server from the list.
Viewing Detailed Server Status

Server Administration does not require you to log in to VPM to view the status of a server. All server
status information is read-only (see Figure 17).
65

User Guide
Figure 17 Server Status Details
To view status details for a server:

In Server Administration, select the server icon. Server Administration shows the status details
listed in Table 11.
66
Monitoring Servers
Generating Administrative Reports
Table 11 Server Status Details
Category Item
Server
Information
Description
Server address The IP address or host name of the server computer.

or host name
Status
One-line status message indicating whether the server management software is in contact
with the server and the server has sufficient database resources. For messages, see
Server Status Messages .
If the server is running low on database resources, note the values for DB size and % free
for long-term, short-term, NPM, and APM databases. Then see Resolving Database
Space Issues on page 199.
Database
Information1
Server license
expiration
The date and time of expiration for the server license, if applicable. None indicates that
the server license is permanent and will not expire. Unknown indicates that the server
license key is invalid.
Domain
licensing
Licensing mode:
Short-term
DB size
Maximum amount of space allowed for the servers short-term (two-week) database. The
percentage free indicates how much of this total is still available.
Flexible(Service provider only) Feature licenses return to the pool for reuse when the
feature or ASE is removed or the entire domain is deleted.
Fixed(Service provider only) Feature licenses remain tied to the domain when a
feature or ASE is deleted or deactivated. Licenses do not return to the pool when a
domain is deleted.
NoneIn the default license mode, features are enabled server-wide, not on a domain
by domain basis.
For more information, see Configuring Licenses on page 155.
This database stores the data collected directly from ASEs. Total database size is
allocated at the factory, based on the anticipated number of ASEs in your network. To
determine the amount of space currently remaining, multiply the percentage free by the
size.
Short-term
DB log size
Maximum size of the log file for the short-term database. The percentage free indicates
how much of this total is still available.
Long-term
DB size
Maximum amount of space allowed for the servers long-term database. The percentage in
parentheses indicates how much of this total is still available.
This database supplies information used for long-term reporting and can grow quite large.
Total database size is allocated at the factory, based on the anticipated number of ASEs in
your network. To determine the amount of space currently remaining, multiply the
percentage free by the size.
Long-term
DB log size
Maximum size of the log file for the long-term database. The percentage free indicates how
much of this total is still available.
67

User Guide
Table 11 Server Status Details
Category Item
Description
Database
Information
(continued)1
Maximum amount of space allowed for the servers NPM database. The percentage
indicates how much of this total is still available.
NPM DB size
This database supplies information used for NPM long-term reporting and can grow quite
large. To determine the amount of space currently remaining, multiply the percentage free
by the size.
NPM DB log
size
Maximum size of the log file for the NPM database. The percentage free indicates how
much of this total is still available.
APM DB size
Maximum amount of space allowed for the servers Application Performance Management
database. The percentage indicates how much of this total is still available.
This database supplies information used in APM views and reports and can grow quite
large. To determine the amount of space currently remaining, multiply the percentage free
by the size.
Domain
Information
Device
Information
APM DB log
size
Maximum size of the log file for the Application Performance Management database. The
percentage free indicates how much of this total is still available.
Domain count
Number of domains currently monitored by this server.
Object count
Number of Visual UpTime Select ASEs, partner devices, defined VPI/VCIs or IP circuits,
and polled router IP SLA tests currently monitored by this server.
Number of
ASEs
supported
Maximum number of ASEs this server can support, as determined by its licenses. Polled
routers are not included in this count. This number is always 10000.
Number of
ASEs active
Number of ASEs currently monitored by this server. Polled routers are not included in this
count.
Number of
NPAs active
Number of Network Performance Appliances currently monitored by this server.
Number of
APAs active
Number of Application Performance Appliances currently monitored by this server.
Database sizes should closely match those in SQL Management Studio.
Polling Server Status

Server Administration polls all servers in its server list at the same time: either at regularly scheduled
intervals or on demand. Each polled server checks SQL Server to determine database sizes, the number
of domains defined, and the number of ASEs defined. The application does not poll any ASEs. Scheduled
68
Monitoring Servers
and on-demand polling are unrelated and do not affect each other. By default, Server Administration polls
all monitored servers every 30 minutes to update their current status information. This setting can be
changed to poll as frequently as every 5 minutes or as infrequently as once a day. Polling can also be
performed on demand.
To set the polling frequency:
1
In Server Administration, select the Visual Performance Manager Servers item. All servers are
listed (see Figure 16).
Select Action > Set Refresh Interval. A Configuration dialog appears.
Enter the polling interval in minutes. The lower the number, the more often Server Administration will
check server status. You can enter a value between 5 and 1440 (which is equal to 24 hours).
Click OK.
You can poll a server on demand to refresh its icon. If the server icon is red in the Server Administration
window, poll the server to see its current status.
To poll all servers on demand:
1
In Server Administration, select the Visual Performance Manager Servers item. The list of all
servers is shown (see Figure 16).
Select Action > Refresh Status.
Logging in to Server Administration

To view active users or any server configuration settings, you must log in to the server. The first time you
expand a server icon, Server Administration prompts you for a user name and password (see Figure 18).
69

User Guide
Figure 18 Server Administration Login
The user name and password must be valid for the server you are trying to access. For more information
about users, see Default User Accounts and Managing User Accounts.
If you cannot log in, your account may be locked. Contact your server administrator for assistance.
Identifying Active Users

Server Administration can be used to determine which user accounts are currently active on any given
server. You may want to identify active accounts if you are planning to restart the server so that you can
inform users.
To view active users on a server:
In the left side of the Server Administration window, expand the server icon and select Active
Users. Server Administration lists the user accounts currently accessing VPM (see Figure 19).
Figure 19 Active Users List
Table 12 describes the information provided by the list of active users.

Table 12 Active User Details
Item
Description
User
The login name of the user account.
Domain Name
The VPM domain that the user account is accessing.
Session Type
TraditionalThe user is using the PAC.
70
Monitoring Servers
Table 12 Active User Details
Item
Description
WebThe user is using the Web portal.
Connect Time
Elapsed time since the user began this VPM session.
IP Address
IP address of the user.

If you have installed the VPM Reporting Services, you can generate administrative reports that provide
information helpful for monitoring VPM. Reports include information on ASEs, system and network
configuration changes, licenses, server performance, users and groups, and report generation and
usage.
Topics in this section include:
Generating an on-demand report
Scheduling reports
Administrative report details
For information about applying a custom logo to administrative reports, see Changing the Logo for
Reports.
Generating an On-Demand Report

You can generate an administrative report on demand at either the server or domain level in Server
Administration.
To generate an on-demand report at the server level, in Server Administration select a server and
select Action > Reports. Select a report and from its submenu select Run Now. The report is
created as a PDF file.
To generate an on-demand report at the domain level, in Server Administration select a domain and
select Action > Reports. Select a report. The ASE Image Updates, ASE Summary, and
Configuration Changes reports can be run from domain level.
Scheduling Reports
In Server Administration, you can schedule administrative reports at the server level from the Action >
Reports menu item. When creating a schedule, you can specify the date and time, frequency, start and
end dates, and delivery options for the selected report (see Figure 20). The scheduled report is generated
as a PDF file.
When working with schedules, note:
71

User Guide
Report schedules are associated with your user name, so each user creates his or her own
schedules.
You can create one schedule for each administrative report. When you edit a reports schedule, you
overwrite the previously created schedule for that report.
When you delete a domain, report schedules associated with that domain are deleted.
Figure 20 Schedule Report Dialog
To schedule administrative reports:

1
From the Action menu, select Reports. Select a report and from its submenu, select Schedule.
Specify the report frequency:

HourlySpecify a starting hour and frequency.
OnceSpecify the date and time. The schedule remains after it has been executed.
DailySpecify the time of day. The report will run daily at the specified time from the start date
until the end date.
WeeklySpecify the day of the week and time of day. The report will run once a week starting on
the specified date and time until the end date.
MonthlySpecify the calendar day of the month and time of day. The report will run monthly on
a specified date and time from the start date until the end day.
In the Start and End Dates section, select a starting date if applicable. Click the arrow to use the
calendar. To set an end date, select the checkbox next to End this schedule on: and specify a date.
To run the report indefinitely, leave the checkbox blank.
Specify a report delivery option:

Report Server E-mailEnter an e-mail address, subject, and message. To enter multiple e-mail
addresses, separate each address by a semi-colon.
72
Monitoring Servers
Note
If you deliver a report to accounts that use anti-virus software, the recipient may not be able to open
PDF files from these accounts. See your anti-virus and e-mail software documentation to find
options for allowing PDF files.
Report Server File ShareProvide the valid filename without the extension (this may not
contain the \ / : * ? < > | characters), type the path (such as \\server\shared), enter a
username with write access to the folder, and enter the users password on the shared drive.
5
Click OK.
To delete a scheduled report:

1
From the Action menu, select Reports. Select the report type and from its submenu, select
Schedule.
In the lower left corner of the Schedule Report dialog, click Delete.
Administrative Reports
Administrative reports include:
Alarm NotificationsView information on configured alarms.
ApplicationsView information on configured standard and custom applications on a specific domain.
ASE Image UpdatesView information on successful ASE software image updates for the server or
a specific domain.
ASE Model SummaryView information about the number of ASEs deployed by model type for the
server or a specific domain.
ASE SummaryView summary information about ASEs and supported partner devices in each
domain on the server.
Configuration ChangesView information about recent administration and network configuration
changes for the server or a specific domain.
LicensesView license data for the server.
Server SummaryView domain summary information, database usage over time, and database
maintenance performance on the server.
APM Server SummaryView the status of data importing from APAs, aggregation in the VUpTimeDC
database, retrievals from the Web portal, and reports for a domain
Users and GroupsView details on all users and groups on the server.
Report Performance and UsageView breakdown of report generation by time, top users, by
appliance type, and many others.
73

User Guide
Alarm Notification Configuration

The Alarm Notification Configuration report shows all configured alarm notifications for all recipients
(including: VPM Users, VPM Groups, and the SNMP Trap and Syslog services). This report can be run
only for a specific domain.
Applications Report
The Applications report shows standard and custom applications and related details, including assigned
colors (with color image and RGB value). This report can be run only for a specific domain.
The report has the following tables:
Applications listed alphabetically, with profile information (for details, see Applications Report ).
Applications sorted by RGB color value.
Business and Rogue applications if applications have been classified.
Custom applications, which includes port range, subnet, URI prefix, and color as defined for the
custom application in the Applications or ASE Applications tool on the Web portal.
Table 13 Applications Report
Item
Description
Application
Application name.
Legacy Custom
Custom application defined for legacy v5.2 or v6.0 Visual ASE.
Custom
Custom application defined for Visual UpTime Select ASE, NPA,

or APA.
Classification
Business or Rogue classification as determined when configuring

the application.
Usage
Devices monitoring applications. ASE includes any Visual UpTime

Select ASE. VPM includes NPAs and APAs.
Color
Color as determined when configuring the application.
RGB
RGB color value.
ASE Image Updates Report

The ASE Image Updates report shows information about the most recent successful software update,
conducted from the PAC, for each ASE in the report. This report can be run server-wide or for a specific
domain.
When using the ASE Image Updates report, note:
Only the most recent update for each ASE is shown, even if the database log shows multiple
updates.
74
Monitoring Servers
ASE software updates conducted through alternate means (such as from an ASE) are not included.
Therefore, the report information may not match the ASEs actual history or state.
Deleted and inactive ASEs are not included in the report.
If the same ASE appears multiple times in a domain (for example, if the same IP address appears as
multiple access lines), the report lists each instance with its own entry because an update operation is
associated with the access line. Note that the information for the duplicate ASE (the one not chosen
when the update occurred) may be out of date because a log entry for the duplicate ASE will not
exist.
The ASE Inventory permission is required to access this report. As with the ASE Summary report, data is
organized by domain and network and sorted alphabetically. For report details, see ASE Image Updates
Report .
Table 14 ASE Image Updates Report
Item
Description
ASE
ASE name.
Site
Site name in the network.
Version
ASE software version based on the last time the ASE was identified or
data collection occurred. An entry of UNKNOWN means that the ASE is
unreachable or has not been re-identified since an upgrade.
Prior Version
Version prior to the update.
ASE Type
Current ASE type: IPT (IP Transport), MP (Multi-Protocol), or LV (LAN

Visibility).
Prior ASE Type
ASE type before software update.
IP Address
IP address of ASE.
Product ID
For Visual ASEs, the ASE product ID (serial) number. The first four digits
indicate the ASE model number.
For partner devices, the device identification number in the format:
<vendor ID>-<product ID>
User
(User ID) Name of the person doing the update
Update Time
Time of the update
ASE Models Summary Report

The ASE Models Summary report shows a count of ASEs deployed by model type for the server or a
specific domain. Because data is drawn from the VPM database and not from real-time polling of ASEs,
some discrepancy may occur between the report data and real-time data from ASE Inventory and Identify
ASE features.
75

User Guide
You can access the ASE Model Summary report at the server level to view server-wide information or
domain level to view data for a specific domain. In the server-wide report, the first section shows overall
counts for the whole server. The ASE Inventory permission is required to access this report. For report
details, see Table 15.
Table 15 ASE Models Summary Report
Item
Description
Model Number
ASE model number.
Type
Link interface type configured on the ASE: Ethernet, Frame

Relay, HDLC, and ATM.
Number of Active Number of deployed, active ASEs. Subcategories are: IPT (IP
ASEs
Transport), LV (LAN Visibility), and MP (Multi-Protocol).
VoIP Enabled
ASEs
Number of actives ASEs (counted in the preceding column) that

are VoIP-enabled.
ASE Summary Report

The ASE Summary report shows information about ASEs and supported partner devices in each domain
on the server. Because data is drawn from the VPM database and not from real-time polling of ASEs,
some discrepancy may occur between the report data and real-time data from ASE Inventory and Identify
ASE features. Summary tables in the report are listed by network for each domain.
You can access the ASE Summary report at the server level to view server-wide information or domain
level to view ASE summary data for a specific domain. The ASE Inventory permission is required to
access this report. For report details, see Table 16.
Table 16 ASE Summary Report
Item
Description
ASE
ASE name.
Site
Site name in the network.
Version
ASE software version based on the last time the ASE was
identified or data collection occurred. An entry of UNKNOWN
means that the ASE is unreachable or has not been re-identified
since an upgrade.
Speed
Line speed supported by the ASE in Kbps.
IP Address
IP address of ASE.
ASE Type
Current ASE type: IPT (IP Transport), MP (Multi-Protocol), or LV

(LAN Visibility). A partner device that is not IP Transport or LAN
Visibility, such as a Cisco MIVPP device, is considered Multi-
76
Monitoring Servers
Table 16 ASE Summary Report
Item
Description
Protocol.
Physical Interface The primary physical layer interface on the ASE. For example, T1,
DS1, HSSI, E3, Ethernet.
Link Interface
The link interface type. For example, Frame Relay, HDLC, ATM.
Partner
Indicates with a checkmark when the device is a partner device.
Product ID
For Visual ASEs, the ASE product ID (serial) number. The first four
digits indicate the ASE model number.
For partner devices, the device identification number in the format:
<vendor ID>-<product ID>
Last Data
Collection
The date and time of the last data collection from the ASE, using
the time of the last 15-minute interval. Last Data Collection
indicates how up-to-date historical data is in the database and can
reflect an inability to reach the ASE for an extended period. When
data collection has not occurred for more than two days, text is
shown in red. If the ASE has never had successful data collection it
is blank.
Note: The time reflects a successful completion of at least one set
of statistics. It does not mean all data had successfully been
collected.
Configuration Changes Report

The Configuration Changes report shows information about administration and network configuration
changes for up to the past 30 days for the VPM server or a specified domain. Report data in each table is
sorted by chronologically from the most recent changes.
The Recent Administration Changes and Recent Network Configuration Changes sections show
data for the past seven days, including the day the report was generated. Changes that have occurred in
the current or previous day are highlighted in red.
The Administration Changes and Network Configuration Changes sections show data for the entire
30 day time period. The ASE Inventory permission is required to access this report.
Table 17 Configuration Changes Report
Item
Description
Date
Date and time of the change.
User Name
The user ID of the person who made the change.
Domain Name
The shown name of the domain.
77

User Guide
Table 17 Configuration Changes Report
Item
Description
Change
Description
(Administration)
For servers, administration changes include: IP CoS settings,

users and groups settings, reports settings, domain configuration
and domain options, license key additions, and Service Summary
settings.
For domains, administration changes include: IP CoS definitions,
user-domain associations, event forwarding definitions,
Application Summary Orientation, and report settings.
Change
Description
(Network
Configuration)
Network Configuration changes (adding, deleting, or renaming a

network element) include:
Access line, network, site, ASE IP address changes.
Server filter configuration updates published to APAs.
Top 10 monitored applications configured from the PAC.
NPA and APA additions, edits, and deletions.
Network element deletions. These are shown once. For
example, when network is deleted, sites and access lines
deletions on that network are not shown.
Note: Circuit changes, custom application changes from the Web
portal, and configuration changes to the ASE (for example,
threshold event definitions) are not included.
Licenses Report
The Licenses report shows license data for the server and all domains on the server. Information in this
report matches information shown in Server Administration licensing tabs. The License Administration
permission is required to access this report. For report table contents, see Table 18.
Table 18 Licenses Report
Table
Description
Domains
Lists all domains on the server, a count of active and inactive

ASEs, and an indication of whether the domain is Service
Summary only.
Server-wide
For each feature on the server, lists the number of users and
Feature Licenses power users (total, used, and available), whether the feature
license is evaluation or not, and its expiration date if applicable.
Domain
For each feature on the domain, indicates whether the feature is
Feature Licenses enabled permanently, the number of used licenses, the number of
licenses in reserve, whether the feature license is evaluation or
not, and its expiration date if applicable.
This section is shown when the server is in domain-flexible or
fixed licensing mode.
78
Monitoring Servers
Table 18 Licenses Report
Table
Description
ASE Evaluation
Licenses
Lists the number of initial, used, and available ASE evaluation

licenses on the server and the expiration date.
ASEs Under
Evaluation
Lists evaluation ASEs by port, site, and network for each domain
on the server.
Agent Licenses
Lists the initial, used, and available counts and the expiration date
of agent licenses by agent class.
Server Summary Report

The Server Summary report shows domain summary information, short-term, long-term, APM, and NPA
database usage over time, database maintenance performance on the server, and server counts. Counts
of domains, ASEs, APAs, NPAs and interfaces, and objects managed by the server are measured daily
and reported weekly, with the maximum count per week used, for up to the past 52 weeks.
This report is useful for planning future storage needs and assessing current performance. The Server
Settings permission is required to access this report. For report details, see Table 19.
Table 19 Server Summary Report
Item
Description
Domain
Summary
Summary information for each domain is presented in two tables. The first
table lists the SNMP community string, whether the domain is enabled,
whether IP CoS SLA is enabled on the domain, whether Visual UpTime
Select, NPM, and APM features are enabled, the default data collection
time for ASEs, and the database maintenance time, The second table lists
the number of active ASEs, NPAs, and APAs, and the number of objects.
Short Term
Database Size and
Usage
Long Term
Database Size and
Usage
NPM Database Size
and Usage
APM Database Size
and Usage
Graphs show the usage and capacity of the short-term, long-term, NPM,
and APM databases and database logs over the past year. The
corresponding tables provide usage and capacity values and also include
the percentage of space free for the databases and the logs.
Database
Maintenance
Performance
For each domain, lists the average, minimum, maximum, and standard
deviation times for database maintenance based on the total number of
recent runs.
Number of Domains
Graph shows the number of domains on the server, measured at weekly
79

User Guide
Table 19 Server Summary Report
Item
Description
Over Time
intervals, for up to the past 52 weeks.
Graphs shows the maximum number of ASEs, NPAs, and APAs on the
Number of ASEs
Over Time
server, measured at weekly intervals, for up to the past 52 weeks.
Number of NPAs
Over Time
Number of APAs over
time
Number of Objects
Over Time
Graph shows the maximum number of objects on the server, measured at

weekly intervals, for up to the past 52 weeks. Objects include the number of
ASEs, partner devices, defined VPI/VCIs or IP circuits, and polled router IP
SLA tests currently monitored by this server.
Server Counts Over

Time
Table shows the number of domains, ASEs, NPAs, NPA network interfaces,
APAs, and objects on the server, measured at weekly intervals, for up to the
past 52 weeks.
APM Server Summary Report

The APM Server Summary report shows the status of data importing from APAs, aggregation in the
VUpTimeDC database, and retrievals from the Web portal and reports for a domain.
The report also shows how the VPM is being used. For example, it shows how often users see individual
Web portal pages and reports. It also logs and shows performance results for creating Web portal pages.
Status thresholds for good (green), degraded (yellow), and red (poor) are listed on the final page of the
report.
Table 20 APM Server Summary Report (continued)
Item
Description
APA Key Performance

A diagram shows an overview of the seven stages of data flow from APAs for the
Indicators - Last 15 Minutes last 15 minutes.
APA Key Performance
Indicators - Last 24 Hours
A chart shows the seven stages of data flow from APAs for the last 24 hours. Each
box in the chart represents 15 minutes.
APA Records Aggregated - Bar chart shows the number of APA records aggregated in the VPM server
Last 24 Hours
database for the last 24 hours.
Stage 1 & 2 Details - APAs Shows the latency between the current system time and the current imported data
and Data Importer
time.
A table shows error and warning messages for the last 24 hours.
A table shows the data importer processing over the last day.
80
Monitoring Servers
Table 20 APM Server Summary Report (continued)
Item
Description
Stage 3 & 4 Details - Import Shows the data importer latency, aggregator latency, and total latency.
Table and Data
Shows the number of records aggregated, processing time and aggregation rate.
Aggregation
Bar charts show the import table backlog and the aggregation rate over the last
seven days.
Tables show the last 30 entries in the aggregation log and the aggregation rate for
the last 24 hours and 30 days.
Stage 5 Details Aggregated Tables
Line chart shows the data ranges covered by each aggregated table in the database
for up to a year.
A stacked bar chart and table show the total number of records per aggregated table
by minute, hour, and day.
A stacked bar chart and table show the total disk space per aggregated table.
A table shows data deletion warnings and errors for the last 24 hours.
A bar chart shows the time it took to delete AggStat data for the last seven days.
A table shows the log of table indexes for the last 30 days.
Stage 6 Details - Retrievals Bar charts show the average retrieval time and retrieval performance distribution for
the last 60 minutes and last 24 hours.
Tables show the slowest retrievals for the last 24 hours and last seven days.
Tables show the slowest query groups, slowest aggregated table, and most popular
queries in the last seven days.
Stage 7 Details - Portal
Bar charts show the average page creation and render time and the number of Web
pages created for the last 60 minutes, last 24 hours, and last seven days. Tables
show the Web page creation and render time for the last 24 hours and last seven
days.
Bar charts show the average render time and number of reports created for the last
60 minutes, last 24 hours, and last seven days.
Tables show a log of reporting errors for the last 60 minutes, last 24 hours, and last
seven days.
A table shows the report generation time for the last 24 hours and last seven days.
Configuration Settings
A table shows the value and description of the VUpTimeDC database settings.
Status Thresholds for

Green/Yellow/Red
A table shows the stage number and name, color and value, and description of each
status threshold metric.
Users and Groups Report

The Users and Groups report shows information on all groups and user accounts on the server. The
Users and Groups permission is required to access this report. For report details, see Table 21.
81

User Guide
Table 21 Users and Groups Report
Item
Description
Groups
List of groups with user-provided description of each group.
Group Permissions User capabilities assigned to user group.

User Summary
Description of each user account. Includes user name,

description, whether the user is a power user, whether the user
is locked out, password expiration if applicable, last login date,
and default group.
User Permissions
User capabilities assigned to each user by domain.
Report Performance and Usage

The Report Performance and Usage report tracks report generation by average time (fastest and
slowest), by appliance, top users, report usage over all time, in the current week, last week, last month
and current year, by domain. There is also a six month error log.
Monitoring APA Data Flow

From the VPM server you can receive e-mail notification when the import of aggregated statistics from the
APA fails or is interrupted. The Data Importer component of the server checks the APA data import flow
every half hour and logs any errors in the Windows Application event log. E-mail alerts also include these
errors.
Alert e-mail generation uses the SMTP Server settings from the Report E-mail Delivery Settings values
in Server Administration Server Settings page, under the General Settings tab. For more information,
see Changing E-Mail Delivery Settings.
Examples of detected error conditions include:
The APA loses power or fails.
Network connectivity is disrupted between the server and APA.
The servers Data Importer service stops running.
To receive APA data import alerts via e-mail:
1 Open the DataImporter.xml file located on the VPM server at:
C:\Documents and Settings\All Users\Application Data\Fluke Networks\Visual
Performance Manager Server\config\DataImporter.xml.
2
Enter the e-mail address (or addresses separated by commas) in the AlertEmailAddress attribute of
the ApaImporter element.
Any errors encountered while sending the e-mails are logged to:
82
Monitoring Servers
C:\Documents and Settings\All Users\Application Data\Fluke Networks\Visual
Performance Manager Server\log\DataImporter.txt
83

User Guide
5. Managing Domains
Topics in this chapter include
About Domains
Creating Domains
Setting Domain Options
Conf
Error! Reference source not found.
Asso
orwarding Events and Alarms
Configu
Con
Manag
System Log Forwarding
Ena
Deleting Domains
Identifying ASEs
For more information on Web portal access permissions, see the Visual Performance Manager User
Guide.
About Domains
Each VPM server includes one or more domains. As the system administrator, you can create and
configure settings for domains, partitions of the server that contain data for unique sets of one or more
networks.
Note
Access to some domain-level tasks depends on user permissions.
84
Managing Domains
Associate an IP CoS Template with a Domain
Figure 21 Server Domain List
Double-click to view properties
Expand to view IP CoS

templates
Expand to view domains
New servers automatically include one domain called Default. You can add more domains (up to the
number supported by the server) as necessary. You cannot delete the Default domain.
Note
Do not add ASEs to the Default domain.
Server Administration lists all domains on the server and provides options for editing their properties. To
see the list of domains, expand the server and select the Domains sub-item. The domain list indicates
whether each domain is enabled or disabled and the number of users in the domain who are active at the
moment (see Figure 21).
To view or edit the properties of a specific domain, select that domain in the left pane (or double-click it in
the right pane). The domain properties are organized into tabs. The set of tabs you see depends on the
permissions associated with your user account in this domain. For example, if your account does not
have permission to configure IP CoS settings, the IP Class of Service tab will not be available.
During normal operations, all domains are enabled or fully functional, but domains can be disabled
temporarily in Server Administration. For more information, see Backing Up and Restoring Databases.
Creating Domains
Your organization may require multiple domains if it is:
A service provider offering VPM as a service to its customers.
An enterprise with separate functional groups that require separate control and data access.
85

User Guide
Figure 22 Adding a Domain
To add a domain:
1
In the left pane of Server Administration, expand the server and select the Domains sub-item. (See
Figure 21.)
Select Action > Add Domain. The Add Domain dialog appears.
In the Name field, enter a name that identifies the domain uniquely on the server. The name chosen:
Must contain 30 or fewer alphanumeric characters.
Must start with an alphabetic character, a pound symbol (#), or an underscore (_).
May contain a pound symbol or underscore only as the first character.
Is not case-sensitive.
Cannot contain blank characters (spaces or tabs).
86
Managing Domains
Cannot be the same as a user login name.
4
Select Domain May Not Be Deleted to prevent users from deleting the domain.
Select Service Summary Domain to assign the domain for Service Summary use only (available
only in default licensing mode). For more information, see Cr
For detailed information about domain configuration (including secure ASE communications, feature
module support, ASE IP address restrictions, and reports logo), see Conf
Setting Domain Options

From the domain Options tab, you can set the time for ASE data collection and database maintenance
and configure event priority settings (see Figure 23). All times are local to the server time.
Figure 23 Domain Options
Specify a priority of
1 (low) through
255 (high) for each
event type
Collecting ASE Data

Data must periodically be collected from ASEs. ASE data collection sends data from the ASEs to the
short-term database. By default, an automatic data collection occurs daily at 1:00 AM.
Setting a Default Data Collection Time

In Server Administration, you can set a default time for daily data collection in the domain. When working
87

User Guide
with data collection, note:
You can include existing ASEs that are on the 24-hour data collection schedule in the newly assigned
data collection time.
To override default data collection time for an individual ASE, change the ASEs settings in Network
Configuration on the PAC. See the PAC User Guide.
For information about coordinating data collection time with database maintenance, see Scheduling
Data Collection and Database Maintenance.
To set ASE data collection time and method:
1
In the Options tab for a domain, under ASE Configuration, enter a new time for Default Data
Collection Time. (See Figure 23.) You can use arrow keys to adjust values. The Apply default time
to existing ASEs checkbox becomes available.
Determine whether data collection will update existing ASEs:

To update the data collection time for all ASEs in the domain that have a once-per-day data
collection time, check Apply default time to existing ASEs. ASEs not on the once-per-day cycle
are not affected.
To change the default data collection time only for future ASEs added to VPM, leave the box
clear.
Click OK.
You can also collect data on demand from all ASEs in a domain by selecting Action > Collect Data from
the menu.
Performing Data Collection on Demand

On-demand data collection does not affect the daily scheduled data collection.
Note
To avoid data loss, always collect ASE data before updating ASE software or rebooting the ASE.
To perform on-demand ASE data collection:
1
In Server Administration, select the domain.
Select Action > Collect Data. A message states: Data collection was requested. It will
proceed in the background now.
Click OK.
Performing Database Maintenance for a Domain

Database maintenance helps ensure smooth operation VPM and updates the long-term database, which
supports reporting. As a domain administrator, you must perform database maintenance regularly for your
88
Managing Domains
domain. For information about performing database maintenance and data collection for all domains on a
server, see Scheduling Data Collection and Database Maintenance.
Database maintenance settings in Server Administration affect the short-term and long-term databases
differently. For more information, see Data Storage.
To schedule or perform on-demand database maintenance:
1
Collect ASE dataFirst verify that the short-term database has the most recent network performance
data available. See Error! Reference source not found.
Perform daily and on-demand database maintenanceVerify that the long-term database has the
most recent network performance data available and that obsolete data has been purged. Ongoing
maintenance also ensures that the short-term database is up-to-date. See Error! Reference source
not found.
Perform monthly database maintenance (Optional)Verify that the long-term database is trimmed to
hold the appropriate historical data. See Scheduling Monthly Database Maintenance
Back up database (Optional)From the server using SQL Server, back up databases after ASE data
collection and database maintenance to make sure the backup contains the most recent data
available. For more information, see Chapter 10, Maintaining the Databases.
Warning
If you initiate on-demand ASE data collection followed by on-demand database maintenance,
data will be queued properly. You do not have to wait for data collection to complete before
initiating database maintenance. However, do not initiate or schedule database backup
during ASE data collection or database maintenance. Likewise, do not initiate ASE data
collection or database maintenance during database backup.
About Database Maintenance

Daily and on-demand maintenance affect both the short-term and long-term databases. Both types of
maintenance accomplish the following tasks:
Roll the contents of the short-term database into the long-term database.
Verify that all data from the short-term database is accounted for in the long-term database with no
duplication.
Trim the short-term database to a maximum of 14 days of data.
Remove deleted network elements from reporting data (optional). If any network elements have been
deleted from network configuration, they no longer exist in the short-term database, but their historical
data is still available in the long-term database and accessible to reports. You can choose to remove
them from the long-term database to release storage space or keep them for historical reporting
purposes.
Delete expired Network Performance Manager (NPM) data, using the same time period (52 weeks
default) used for ASE long-term history data.
89

User Guide
Remove deleted applications, sites, and servers from Application Performance Manager (APM) data.
Aggregate data needed for and delete expired data used by Application Summary.
When applications, sites, or servers are deleted in VPM, they are actually hidden, not deleted. This allows
historical data and baselines collected for those elements to remain available for viewing, and permits
deleted servers which are rediscovered by an APA to retain most of their previous configuration
information (SNMP configuration, IP Translation configuration, etc.). On the options tab you can remove
all historical data and configuration information associated with applications, sites, and servers which
have been deleted.
The deletion of expired NPM data and the Application Summary processing will only run once per day
even if database maintenance is performed more than once.
Performing Database Maintenance on Demand

On-demand database maintenance does not affect scheduled maintenance.
To perform on-demand ASE database maintenance:
1
In Server Administration, select the domain.
Select Action > DB Maintenance. A message states: Data collection was requested. It
will proceed in the background now.
Click OK.
Scheduling Daily Database Maintenance

By default, daily maintenance automatically occurs at 2:00 AM. This action immediately follows the daily
default ASE data collection time of 1:00 AM. Coordinating these two tasks ensures that the most current
data is available for reports. If you change the daily maintenance time, you may also need to change the
ASE data collection time.
To perform on-demand maintenance, click Do Maintenance Now. Scheduled daily maintenance is not
affected by on-demand maintenance.
To configure daily database maintenance for a domain:
1
In Server Administration, select the domain. Click the Options tab.
In Daily Maintenance Time, specify the desired time for daily maintenance. (See Figure 23.) Enter
the hour, minute, second, and am/pm values or use the arrow keys to adjust these values.
To remove all data related to deleted network elements from the long-term database when database
maintenance runs, check Remove deleted network elements from reporting data. To retain this
data for historical reporting, clear the box.
To remove all data related to deleted applications, sites, or servers from the APM database, check
Remove deleted configuration items from APM data. All deleted data will be removed from the
database each day. To retain this data for historical reporting, clear the box.
90
Managing Domains
5
Click the Remove Items Now button to immediately remove all deleted applications, sites and
servers from the database. All other associated data will be removed at the designated Daily
Maintenance Time. If the Remove deleted configuration items from APM data checkbox is not
enabled, deleted data is only removed once, not each day.
Click OK to save the changes.
Scheduling Monthly Database Maintenance

Monthly maintenance trims the long-term database to the number of weeks you specify (by default, 52
weeks). It affects the long-term database only.
By default, monthly maintenance automatically occurs on the first day of every month. If you enter a value
between 29 and 31, maintenance occurs on the last day of the month in months that contain fewer than
the specified number of days. On the day scheduled, monthly maintenance begins immediately after daily
maintenance has finished.
To configure monthly database maintenance for a domain:
1
In Server Administration, select the domain. Click the Options tab.
In Monthly Maintenance Day, enter the desired day for monthly maintenance to occur.
In Keep ___ Weeks of Reporting Data, enter the maximum number of weeks of data to be stored in
the long-term database.
Click OK.
Configuring Domain-Wide Event Priorities

For each domain, you can assign priorities to system events. Priorities help determine if and how an
event is shown in the Service Summary Events tab. The priorities you assign are applied to events
reported by all ASEs in the domain.
Priorities can be specified for:
State change events for circuit, link, and physical layers.
ASE reboot events.
SNMP authentication failure events.
Data collection poll failure events.
ASEs always report ASE Reboot and Data Collection Poll Failure events.
Assigning a priority to a state-change or SNMP Authentication event has an effect only if at least one ASE
is configured to report the event. Individual ASEs are configured in Performance Monitoring (see Chapter
4, Performance Monitoring, in the PAC User Guide). To configure multiple ASEs for performance
monitoring events, use the ASE Templates tool in the PAC (see Chapter 5, Using ASE Templates, in
the PAC User Guide.).
91

User Guide
To assign priorities to events:
1
In the left pane of Server Administration, select the domain in which to assign event priorities. Click
the Options tab if it is not already selected (see Figure 23). The right pane shows the properties of
the chosen domain.
Under Global Event Priorities, enter the priority values to be assigned for each type of event. The
greater the number, the higher the priority. The valid range is 1255.
Click OK.
Configuring Domains
From the domain Configuration tab, you can configure the authentication strings used to restrict access
to Visual ASEs and partner devices, ASE secured communications settings, what feature modules to
include, and the logo used in reports for the domain.
In default licensing mode only, you can also mark the domain as Service Summary. For more
information, see Cr
Figure 24 Domain Configuration
Specify communication
settings
Create a list of excluded

subnets for the ASE
Turn off module support
Select override for reports

on the domain or leave
server-wide settings
92
Managing Domains
Setting the SNMP Community Name

SNMP communication with ASEs is restricted with a community name. The SNMP community name is
configured for SNMP agents to limit access to the SNMP agent from other network devices. For the VPM
server to communicate with ASEs, all components must have a matching community name. By default,
the PAC, server, and ASEs are configured with the SNMP community name private.
Warning
If you change the community name, you must also change it on all ASEs in the domain so
that the names match. Otherwise, communication between VPM and ASEs will fail.
SNMP community naming rules are as follows:
The name may contain a maximum of 31 characters.
The SNMP community name field is case-sensitive.
The name must match exactly between the ASE and the VPM server and PAC.
If a single ASE is configured in multiple domains, all domains must use the same community name. To
change an ASEs community name, see the ASE User Guide.
To set the SNMP community name for a domain:
1
In Server Administration, select the domain. Click the Configuration tab.
In SNMP Community String, enter the new community name. Click OK.
Configure each ASE in the domain to use the new community name.
Note
If failure notification occurs, log in to the ASE and use the EVENT command to see the IP address
attempting to contact the ASE.
Setting the TFTP Authentication String

Trivial File Transfer Protocol (TFTP) communication with partner devices is restricted with an
authentication string. VPM uses an extension to the industry standard TFTP that includes a security
feature (an encrypted public key exchange between the partner device and the server) conceptually
similar to the community string in SNMP. This mandatory TFTP authentication uses license keys to
protect communication between the server and partner devices, preventing unauthorized access to bulk
statistical information during the collection of history data from partner devices.
If your network contains partner devices, you must define a TFTP authentication string for each domain
where the partner devices are configured and enter this string into the Server Administration application.
All partner devices in a domain must have the same string: if the TFTP authentication string is changed
on the VPM system, it must also be changed for all partner devices. (Partner devices should provide their
own interface for setting the TFTP authentication string on their end.)
93

User Guide
The authentication string:
Must contain no fewer than eight characters, and no more than 16.
Cannot contain blank characters (spaces or tabs).
Must match exactly on the partner devices and the server.
Each domains Configuration tab in Server Administration contains a field named TFTP Authentication
String. By entering your TFTP string into this field, you cause the server to create an encrypted key
unique to each transfer of data from the partner device to the server.
Note
Visual ASEs do not support TFTP authentication.
TFTP string management does not require special access control permission beyond normal server
management capabilities. TFTP authentication strings must be available to PACs, to enable them to
perform authenticated transfers. Changes to these strings during system operations are propagated from
the server database to any VPM service that needs to know.
To set the TFTP authentication string for a domain:
1
In TFTP Authentication String, enter the new string. Click OK to save the change.
Configure each partner device in the domain to use the new authentication string. For more
information, see the documentation for partner devices.
Setting a Router Polling Interval

You can set the router polling interval for all routers with the IP SLA Router Polling feature on the domain.
To set the router polling interval:
1
Under Domain Configuration, for Router Polling Interval, specify a time in minutes in the range of
5 to 1440 minutes (24 hours). The default is 14 minutes.
Note
The recommended range for the polling interval is between 5 and 60 minutes.
Click OK.
Setting an Application Summary Orientation

In hub and spoke network environments, you can ensure that the VPM server correctly gathers
Application Summary data from ASEs on the domain.
94
Managing Domains
To set the Application Summary Orientation:
1
Under Domain Configuration, for Application Summary Orientation, select:

Standard when the domain has ASEs at both hub and spoke sites or when monitoring peer-topeer applications.
Spoke-only when the domain has ASEs only at spoke sites.
Hub-only when the domain has ASEs only at hub sites.
Click OK.
Domain May Not be Deleted

Enable this checkbox to prevent the domain from being deleted.
Note
The default domain cannot be deleted and the checkbox is disabled.
Creating a Service Summary Domain

In default licensing mode, you can mark a domain as Service Summary, which means that all features
beyond Service Summary are removed from all ASEs in the domain. When you create a Service
Summary domain, for each unique ASE in this and other domains, each feature license count that was
previously available in the domain is increased by one.
When creating and using Service Summary domains, note:
Service Summary domains may be created in default licensing mode only.
If you have power-user licenses on your system, you cannot create a Service Summary domain.
Because no duplicate ASEs are counted in a Service Summary domain and no features are assigned
to the domain, when the domain is deleted, no licenses are returned.
When a Service Summary domain is changed to a standard domain, all licensed server-wide features
are added to the domain. Enough licenses must be available to modify the domain.
Check Service Summary Domain. ASEs in the domain lose their features, making any licenses
assigned to those ASEs available for reuse in other domains. The ASE limit for the domain changes to
10,000. Note that the Service Summary option is available only if the system is operating in default
license mode.
To turn off Service Summary status for a domain, clear the checkbox. Service Summary status can be
turned off for a domain only if the server has enough licenses to cover all ASEs.
BGP Exclusion List

Click this button to create or edit a list of subnets to exclude from the ASE local subnet table. Each ASE
95

User Guide
auto-discovered BGP (Border Gateway Protocol) subnet will be compared to this list. If the discovered
subnet is on the exclusion list, it will not be added to the local subnet table.
Figure 25 BGP Exclusion List
To create/edit the BGP Exclusion List:

1
Click the BGP Exclusion List button.
Enter the Subnet Base IP Address in dotted decimal format. The IP address must be a valid IPV4
address.
Enter the Subnet Mask bits (between 2-32).

A maximum of 8 subnets can be added. Use the X to remove an entry.
Click OK when finished.
Download the subnet list to the ASE by using the ASE identification tool. See Error! Reference
source not found.
Configuring Secure ASE Communications

You can set the level of secured communication of network management data between ASEs and the
VPM server based on open, partial, and full security settings (for details, see ASE Secure Communication
Settings ). These settings are published to all ASEs on the domain upon next server contact with ASEs.
ASEs that support secure communication are updated. ASEs that do not support secure communication
are not affected.
When using secure ASE communications, note:
SSH version 2 and later is supported.
PuTTY can be used to access a secured ASE. Putty is installed with the server software under:
Program Files\Fluke Networks\Visual Performance Manager Server\utilities
96
Managing Domains
For more information about PuTTY, see:
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
SNMP notifications (traps) sent by ASEs are not encrypted.
To set up secure ASE communications:
1
Under Secure ASE Communications, select Enable.
For Security Level, select:

Open to use standard SNMP and TFTP communications or TLS. No additional security is
applied.
Partial to allow SNMP and TFTP read access only. This prevents unauthorized control of the
ASE, but provides access to third-party RMON polling applications.
Full to prevent all unsecured accesses. SNMP and TFTP are encrypted.
For more information, see ASE Secure Communication Settings .
Enter a passcode. Passcodes follow SNMP community name rules. For more information, see Error!
Reference source not found.
Specify the SSL TCP port used for secure communication. The default port is 2359.
Table 21 ASE Secure Communication Settings
Security Policy
Open
Partial
Full
SNMP
Read/Write
Read Only
Disabled
TFTP
Read/Write
Disabled
Disabled
Secure SNMP
Read/Write (no passcode)
Read/Write
Read/Write
Secure TFTP
Read/Write (no passcode)
Read/Write
Read/Write
Telnet
Enabled
Disabled
Disabled
SSH
Disabled
Enabled
Enabled
ICMP
Enabled
Enabled
Enabled
For information about ASE settings, see SECURITY in Chapter 5, ASE Administrative Commands, in
the ASE User Guide.
For information about applying security setting overrides for a specific ASE, see Chapter 2, Network
Communication, in the PAC User Guide.
97

User Guide
Turning Off Module Support

From the domain Configuration tab, you can turn off support for the Visual UpTime Select, Network
Performance Manager, Application Performance Manager, and Server Health modules. Users will not see
or be able to access any of the features from these modules. When you turn off support for a module, all
tabs, configuration, views, and reports are removed.
To turn off module support:
1
Under Module Support, select:

UpTime to turn off Visual UpTime Select feature support.
NPM to turn off Network Performance Manager feature support.
APM to turn off Application Performance Manager feature support.
Server Health to turn off Server Health feature support.
Restricting IP Addresses of ASEs

From the domain Configuration tab, you can restrict the IP addresses of all ASEs in the domain to a
specific network or subnet.
To restrict ASE IP addresses:
1
Under ASE IP Address Restrictions:

a
In Network Address, enter the address of the network or subnet. If you specify a network or
subnet, only ASEs within the specified address range will be accessible and configurable. To
allow any IP address, use the default value (0.0.0.0).
In Subnet Mask, enter a subnet mask to further qualify the IP address (above). To allow any
subnet mask, use the default value (0.0.0.0).
Changing the Logo for Reports on a Domain

From the domain Configuration tab, you can change the logo shown in the upper-right corner of the first
page on reports run from a domain. By default, the Fluke Networks logo is shown. The Fluke Networks
logo file is 200 pixels wide by 100 pixels high and is located in C:\inetpub\wwwroot as a sample.
To create a replacement logo, create a .jpg file with a 2:1 width to height aspect ratio.
To change the logo on reports:
1
In Server Administration, select a domain. Click the Configuration tab.
Under Default Report Logo, the currently selected logo for reports in the domain is shown.
98
Managing Domains
Click Change Logo to assign an override logo for reports in the domain only. In the Open dialog,
select a .jpg file to use as a logo and click OK.
Click Restore Default to restore the server-wide logo for reports in the domain. (This option is
available only when an override logo has been applied.)
3
In the Configuration tab, click OK.
Configuring an IP Class of Service Template

You can use a template to define IP Class of Service (IP CoS) settings for all ASEs in a domain. There is
a default template that can be modified but cannot be deleted. You can create multiple templates,
associate a domain with a template, and all IP Transport ASEs in the domain will inherit the IP CoS
settings. Within the domain, at the ASE level, you can associate a different template with each ASE.
You can set up to eight classes of service, name them, enable or disable classes, assign bitmask
settings, assign policing thresholds, and specify the class for which you will gather service-level
agreement (SLA) statistics.
Figure 26 Domain IP CoS
IP CoS names assigned here will be shown in Troubleshooting, the IP Service Level Metrics report, the
Router IP SLA Service Level Metrics report, and reports for each CoS. CoS settings for ASEs in the
domain can be viewed through the ASE Configuration dialog in Network Configuration on the PAC.
Note:
99

User Guide
It is recommended that you configure the highest priority CoS first and continue to the lowest priority
CoS. The order in which each CoS is entered will reflect its position in reports that display CoS.
If the Class of Service feature is not licensed, you can configure the first CoS (with the default name
of Best Effort) to display data for this class in the Service Advisor Troubleshooting view and IP SLA
reports. For more licensing information, see Managing Feature Licenses.
If you change the CoS for jitter, delete any configured current and average IP SLM Jitter alarms for
the previous CoS.
In Network Configuration, when you add or edit IP Transport ASEs, CoS settings are downloaded from
that ASE using TFTP. If no CoS has been defined, the default settings defined for that domain are sent to
the ASE. For more information, see Chapter 2, Network Configuration, in the PAC User Guide.
Figure 27 Defining an IP Class of Service
To create (or edit) an IP CoS template:

1
In Server Administration, expand the IP CoS Templates category. To create a new template, select
the IP CoS Templates line and select Action > Add Template. To edit an existing template, select
one from the list.
The IP Class of Service Template appears (see Figure 26).
If creating a new template (or you wish to change the name), enter a descriptive name in the
Template field.
Select a Class of Service from the list and click Edit. The Class of Service dialog appears (see
Figure 27).
To include this class in reports, check Enable Class of Service. If you do not use this class and want
to exclude it from reports, clear Enable Class of Service.
100
Managing Domains
5
To collect jitter measurements for this class (jitter is supported on one class), check Collect Jitter
Statistics on IP Circuits. (This applies only to ASEs that support jitter measurements.)
To gather SLA statistics on this class, check Use Class for SLA Measurements. To exclude this
class from SLA statistics, clear the box.
Enter a descriptive name for the class in the Description field. The name you enter can be up to 15
characters long. (Service providers typically provide this value to their customers.)
For Policing Threshold, use the radio button to select the method and then set the upper usage limit
for this class either in kilobits per second (kbps), or as a percentage of CAR (committed access rate).
For IP TOS Definitions, use the radio buttons to select DSCP (Differentiated Service Code Point) or
IPP (IP Precedence) standards or Custom. If DSCP or IPP is used, select the values to include by
enabling the checkboxes in the Value column. If Custom is selected, specify the Data/Bitmask values
in the TOS Value/Mask List field. Use hexadecimal notation; for example: 0xB8/0xFC, 0x30/0xFC.
10 Click OK to save your changes to this class. To edit another class, return to step 3.
Table 22 summarizes the CoS settings.
Table 22 IP CoS Settings
Setting
Description
Enable Class of
Service
Specify whether the class is enabled or disabled. Disabling a class

excludes it from reports, which improves the usability of reports if all
eight classes are not used.
Collect Jitter
Statistics on
IP Circuits
Specify whether to collect jitter statistics for this CoS (on ASEs that
support jitter measurements).
Use Class for

SLA
Measurements
Specify whether to monitor SLA statistics for this CoS.
Description
Apply a descriptive label for the class (up to 15 characters).
Policing
Specify either kbps or a percentage of the Committed Access Rate,
Threshold (kbps) usually set by service provider in the SLA. Service usage exceeding
this mark would not be guaranteed to the same degree as service
up to this mark.
IP TOS
Definitions
Select DSCP (Differentiated Service Code Point), IPP (IP

Precedence), or create a custom data/bitmask. These fields
(defined in hexadecimal notation) determine which CoS a particular
packet falls into. TOS Bitmask indicates what Type of Service bits
are relevant to the CoS. TOS Data indicates the values of the
relevant bits. The results of the computations are compared, and if
they are equal, then data in the packet is counted as part of the
class
101

User Guide
Delete an IP CoS Template

You can delete a template if it is not associated with any domain or ASE.
To delete an IP CoS Template:
1
In Server Administration, expand the IP CoS Templates category.
Right click on the template that you wish to delete and select Delete Template.
Note
You cannot delete the Default Template.
Associate an IP CoS Template with a

Domain
You can configure IP CoS settings for all ASEs in a domain by associating a template with the selected
domain.
Figure 28 Associate an IP CoS template with a domain
To associate an IP CoS template with a domain:

1
In Server Administration, expand the Domains category and select a domain (see Figure 21). Click
the IP Class of Service tab.
Use the Template drop-down menu to select a template.
Select a class of service from the list and click Edit (see Figure 26).
Verify that the Jitter Statistics and SLA Measurements settings are correct. You can also enter a new
name for the Class of Service. Select the checkbox to Enable Class of Service.
Click OK.
All ASEs in the domain will inherit the CoS settings.
102
Managing Domains
Forwarding Events and Alarms

Use SNMP Notification to forward all reported ASE events and performance alarms for a domain. Events
are forwarded from the server computer to designated workstations running third-party event managers,
such as HP OpenView. Events and alarms are decoded into plain text at the server and then forwarded
from the servers IP address.
Figure 29 SNMP Notification
To forward events and alarms for a domain:

1
In Server Administration, select the domain. Click the SNMP Notification tab.
To add an event forwarding destination:

a
Click Add. The Add SNMP Notification Host dialog appears.
In Host Address, enter the IP address to which events should be forwarded.
Specify whether to forward events, performance alarms, or both.
Click OK to return to Server Administration.
To delete an existing destination, select it and click Delete.

3
When you are finished configuring the list of destinations, click OK to apply the changes.
Configuring User and Group Associations

At the domain level, you can add users to the domain and define their permissions by associating them
with a group (see Figure 30).
When associating users with domains, note:
Group settings determine the permissions available to a user in the domain. See Error! Reference
source not found.
Users can be associated with specific domains from the Users Domain Group Associations tab.
See Assigning User Accounts to Domains.
103

User Guide
Figure 30 Domain Associations
Users assigned to this

domain
Select one or more users

Select a group
Click Add Association
to add to the domain
To add users to the domain:

1
In Server Administration, select the domain. Click the Associations tab. Any users already
associated with the domain are shown in the upper part of the window.
Under Add Association, select one or more available users, and then select a group. The group
defines the set of permissions available to those users.
Click Add Association to add the user or users to that domain with that groups permissions.
Configuring Report Permissions

From Web portal, users can generate reports from data stored on a particular server. As a domain
administrator, you can specify which reports are available to users in your domain (see Figure 31). By
default, all users have access to all types of reports.
Note
The report permissions apply to standard domain users only. Power users have access to all
reports, regardless of these settings. (For more information, see Designating Power Users.)
104
Managing Domains
Identifying ASEs
Figure 31 Domain Report Settings
Select a setting to
activate all its report
groups
To configure report settings for a domain:

1
In Server Administration, select the domain. Click the Report Settings tab (see Figure 31).
Select report groups to make available to users:

Select a reports settings to activate all its subgroups.
Select individual report subgroups.
See the following sections for more information on reports.
Click OK to save the report settings.
Domain and Network Reports

Table 23 lists each subgroup for domain-wide and network-wide reports and identifies the specific reports
available when a subgroup is selected.
Table 23 Domain and Network Reports
105

User Guide
Setting
Subgroup
Reports
Application
Management
None
Aggregate Application Usage Over Time

Application Usage Distribution by Hour
Application Usage Over Time
Top Application Usage
Top Clients per Application
Top Rogue Clients
Capacity
Planning
Fastest Growing Sites
Fastest Growing Sites
Most Active Circuits
Most Active Ports
Most Active Ports

Most Utilized Ports Trend
Most Active Sites
Most Active Sites
Most Overutilized and

Underutilized Circuits
Most Overutilized VCs

Most Underutilized VCs
Most Overutilized and

Underutilized Ports
Most Overutilized Ports

Most Underutilized Ports
Network Usage Profiles
Network Usage Profiles
Sites with Highest

Utilization
Sites with Highest Utilization
ATM Quality of Service
ATM Quality of Service
Most Available Ports
Most Available Ports
Most Congested VCs
Most Congested VCs
Service Level Metrics
IP Service Level Metrics

Router IP SLA Service Level Metrics
Service Level Profile
VC Service Level Verification Data
Top Problem Physical

Lines and Ports
Top Problem Physical Lines

Top Problem Ports
VoIP Assessment
VoIP Assessment
VoIP Management
VoIP Performance
Sites with Most Call Flows

Worst Performing VoIP Sites by CQ MOS
Worst Performing VoIP Sites by CQ R-Factor
Worst Performing VoIP Sites by LQ MOS
Service Level
Management
VoIP
106
Managing Domains
Identifying ASEs
Table 23 Domain and Network Reports
Setting
Subgroup
Reports
Application
Server
Management
None
Most Degraded Application Server Performance

New Application Servers
Worst Performing Application Servers
Port Reports
Table 24 lists each subgroup for port-based reports and identifies the specific reports available when a
subgroup is selected.
Table 24 Port Reports
Setting
Subgroup
Reports
Application
Management
None
Application Usage Count per IP CoS for a Port

Application Usage Counts for a Port
Application Usage Counts for a Port (Selected
Application)
End-to-End IP Circuit Application Activity
End-to-End IP Circuit Application Activity (Selected
Application)
End-to-End VC Application Activity
End-to-End VC Application Activity (Selected
Application)
Network Layer Activity
Network Layer Activity (Selected Application)
Capacity
Planning
None
Burst Analysis for a Port

End-to-End VC Burst Analysis
Port Usage Trend
Performance
Circuit Congestion
End-to-End VC Congestion Performance

Single-Ended VC Congestion Performance
Circuit Usage
End-to-End IP Circuit Usage Counts

End-to-End IP Circuit Utilization and Throughput
End-to-End Throughput Above/Below CIR
End-to-End VC Usage Counts
End-to-End VC Utilization and Throughput
Single-Ended VC Usage Counts
Most Active Circuits for a Port
Physical Line
Physical Line Performance
107

User Guide
Table 24 Port Reports
Setting
VoIP
Application
Server
Management
Subgroup
Reports
Port Usage
IP CoS Throughput Above/Below Policing

Threshold for a Port
Throughput by IP CoS for a Port
Usage Counts for a Port
Utilization and Throughput by AAL Type for a Port
Utilization and Throughput for a Port
Utilization by ATM CoS for a Port
Service Level
Management
Availability for a Port

End-to-End IP Circuit CoS Service Level
Verification
End-to-End IP Circuit CoS Service Level
Verification Graphs
End-to-End VC Service Level Verification Data
VoIP Assessment
VoIP Assessment
VoIP Management
VoIP Performance
Sites with Most Call Flows

Worst Performing VoIP Sites by CQ MOS
Worst Performing VoIP Sites by CQ R-Factor
Worst Performing VoIP Sites by LQ MOS
None
Most Degraded Application Server Performance

New Application Servers
Worst Performing Application Servers
Site Reports
Table 25 lists each subgroup for site-based reports and identifies the specific reports available when a
subgroup is selected.
Table 25 Site Reports
Setting
Subgroup
Reports
VoIP
VoIP Call Quality CQ MOS CQ MOS Distribution by Hour for a Site

CQ MOS Over Time for a Site
VoIP Call Quality LQ MOS LQ MOS Distribution by Hour for a Site
LQ MOS Over Time for a Site
VoIP Call Quality R-Factor CQ R-Factor Distribution by Hour for a Site
CQ R-Factor Over Time for a Site
108
Managing Domains
Identifying ASEs
NPM Reports
Table 26 lists domain-wide NPM reports.
Table 26 NPM Reports
Setting
Reports
NPA
Site Performance Overview

Site Performance Detail
Top Sites
APM Reports
Table 27 lists domain-wide Application Performance Management reports.
Table 27 Application Performance Management Reports
Setting
Reports
APM
This setting covers the following APA-based reports:

Applications
Application Performance Analysis
Application Transactions
Application Trend
Highest Usage or Worst Performance Chart
Highest Usage or Worst Performance Detail
Performance Overview
Performance Trend Chart
Performance Trend Detail
Servers
Sites
The setting covers the following ASE-based reports:
Application Usage for Most Utilized Ports
Top Clients Application Usage
Managing Licenses for a Domain

In domain-fixed or domain-flexible licensing mode, you can manage feature licenses and enter feature
evaluation license keys at the domain level. To view and manage licenses at the domain level, you must
have the License Administration user permission.
Note
Domain-fixed and domain-flexible licensing modes are available only for service providers.
The domain Licensing tab shows an ASE count, the count of available and reserved licenses, and the
status of feature evaluation and/or permanent feature licenses on the domain (see Figure 32).
109

User Guide
Figure 32 Domain LicensingDomain Licensing Mode with Permission
Enter feature evaluation

license key and click Add
Activate or deactivate
features for the domain
Number of licenses available per

feature server-wide
Number of licenses for this

feature held in reserve for this
domain
When working with domain-level licensing, note:

You must be in domain licensing mode with License Administration user permission to view and edit
domain licenses.
When a feature is enabled at the server, it is activated by default at all domains on the server. You
can, however, activate or deactivate a permanent feature at the domain level by selecting or
deselecting its checkbox in the Perm column.
When you activate a feature that counts ASEs, all ASEs on the domain consume the feature. To
activate a feature, the server-wide available license count must be equal to or greater than the
domain ASE count. Licenses in the domain reserve for the feature are automatically consumed first.
Then, if the reserve count is less than the number of ASEs, licenses are drawn from the server pool.
110
Managing Domains
Identifying ASEs
If the reserve count is zero when the feature is activated, licenses are drawn directly from the server
pool.
When you deactivate a feature, all consumed licenses on ASEs in the domain return to the domain
reserve for that feature. In domain-fixed mode, licenses assigned to a domain remain with that
domain. In domain-flexible mode, the server-wide administrator can reassign licenses from one
domain to another.
When managing domains with unique feature sets, you can either turn off a feature server-wide and
activate it only on specific domains or leave it available server-wide and turn it off on specific
domains. When a feature is available server-wide, by default, it is active on all new domains. When a
feature is deactivated on one domain, by default, it is not active on new domains.
To add and manage feature evaluation licenses for the domain, see Adding a Feature Evaluation
License
In default license mode, the domain Licensing tab is read-only.
Adding a Feature Evaluation License

In domain licensing mode, with License Administration permissions, you can enter feature evaluation
license keys for a domain. When you add the license key, all features included in the key will be checked
in the Eval column (see Figure 32).
To add a feature evaluation license key:
1
Contact Fluke Networks to obtain a feature evaluation license key. You will need to provide a server
ID.
In Server Administration, select a domain and select its Licensing tab.
Enter the feature evaluation license key and click Add. In the Eval column, checkboxes are shown for
the features purchased, along with the expiration date.
System Log Forwarding

The set of syslog recipients targeted by VPM for alarm notifications is configured by editing an xml file.
To edit the syslog recipients:
1
Open the DataImporterLogging.xml file in the Documents and Settings\All Users\Application

Data\Fluke Networks\Visual Performance Manager Server\config folder. You can use a text editor
like Microsoft Wordpad.
Locate the following section of code:

appender name="Syslog" type="log4net.Appender.RemoteSyslogAppender">
<Facility value="Alert" />
<Identity value="VPM" />
111

User Guide
<RemoteAddress value=172.16.20.188" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%message" />
</layout>
</appender>
3
Change the IP address value in the RemoteAddress value = ... line to the IP address of the
desired syslog recipient.
Note
If the section of code is commented out (indicated by  tags), remove the tags.
You can use a Hostname instead of an IP address.
You can create multiple syslog recipients by copying the entire section of code and inserting it after
the existing code section. You must change the name in the <appender name="Syslog" line. For
example, change it to <appender name="Syslog2". Change the RemoteAddress value to the
IP address of the additional recipient
Locate the line  and remove the comment tags. If
you have created multiple recipients, create an appender-ref line for each recipient and change
the value to match the name in the <appender name="Syslog" line. For example, if you created
two recipients, it would look like:
<appender-ref ref="Syslog" />
<appender-ref ref="Syslog2" />
Save the file. Changes take effect immediately; you do not have to restart the VPM application.
Note
During an upgrade, changes made to the DataImporterLogging.xml file are lost. A backup copy is
saved in the ...\config\backups folder. You can copy the changed sections from the backup file to
the new file.
Copying Domain Settings

If you need to set up multiple domains with similar settings, you can save time by copying the settings
from one domain to another. To copy domain settings, your user account must be associated with both
domains and configured with the Domain Management capability.
The following domain settings are copied:
Settings from the Options tab: default data collection time, default database maintenance time,
number of weeks of long-term data to preserve, and event priority settings.
112
Managing Domains
Identifying ASEs
Settings from the Configuration tab: SNMP community string, TFTP authentication string, ASE IP
address range.
ASE secured communications settings.
IP CoS settings.
Report settings.
Service Summary settings.
Protocol/Application colors.
Custom application definitions.
Business hour definitions.
Application alarm configuration settings.
Default report logo.
Note
These domain settings are always changed during copying, even if the administrator performing the
copying does not have permission to edit some of the settings. For example, if a user account has
permission to copy domain settings, but cannot edit IP CoS settings, the IP CoS settings are still
copied along with the other settings.
The following settings are not copied from the source domain to the target domain:
Module support settings.
User associationsAfter copying from the source domain, no user accounts will be associated with
the target domain. Power users can access the target domain immediately, but for other users, you
will need to associate the accounts with the target domain.
Enabled/disabled statusThe target domain will be enabled after copying.
NameThe target domain retains its name.
Event forwarding addressesAfter copying settings to the target domain, all domain forwarding
information in the target domain will be lost. If you want the target domain to forward events, you will
need to configure event forwarding after the copy.
LicensesDomain-specific licenses do not transfer to the target domain.
To copy settings from one domain to another:
1
In Server Administration, select the domain with settings to overwrite.
Select Action > Copy Settings. The Copy Domain dialog appears.
113

User Guide
3
Select a domain to copy settings from and click OK. The domains properties are copied, but the
associated users and contents (networks and configured sites, access lines, circuits, and event
configurations) are not.
Click OK. The process may take several minutes to complete. (You do not need to restart the server.)
Enabling and Disabling Domains

During normal operations, all domains are enabled or fully functional. (When a domain is created, it is
enabled by default.) You can disable domains temporarily.
A disabled domain cannot accept logons from Web portal users and PAC. Disabled domains stop
collecting data, and events generated by ASEs and partner devices in that domain are discarded. VPM
will not run scheduled reports on ASEs associated with a disabled domain.
Disabling a domain does not affect data collection on ASEs. ASEs store up to two days of data, so if you
re-enable the domain within that time, no data will be lost. NPM data is not imported into a disabled
domain.
To disable a domain, from the Server Administration tool, right-click a domain from the tree and select
Disable Domain. To enable the domain, select Enable Domain.
Note
You cannot disable the default domain or the domain in which you are currently working. Therefore,
the List of Enabled Domains dialog will show neither the default domain nor the current domain.
Deleting Domains
Deleting a domain deletes the domains association with specific users, although the users themselves
are not deleted.
In order to delete domains, your Windows user login must have Administrator or Power User privileges on
the VPM server. In addition, your VPM user account must be a member of a group with Domain
Management permission.
Warning
Deleting a domain is an irreversible operation that removes all network configuration, shortterm, and long-term data in the domain. Therefore, make sure you back up the network
performance database before deleting a domain. See Backing Up and Restoring
Databases.
Deleting a domain also stops VPM services, making the server inaccessible to all clients
regardless of the domain they are using. Notify all users before stopping these services.
Users must log out of VPM until the server is restarted. Any client users who remain logged
on will receive error messages and must exit VPM.
114
Managing Domains
Identifying ASEs
To delete a domain:
1
In Server Administration, select the domain to be deleted.
Select Action > Delete Domain. The Delete Domain dialog is shown.
If another domain needs to be deleted, clear the Restart services checkbox so that the services are
not restarted automatically.
Click OK to confirm the deletion.
If report subscriptions cannot be deleted, you may receive a message after the domain is deleted.
Click OK.
If other domains need to be deleted, repeat steps 1 through 5. When deleting the last domain, select
the Restart services checkbox.
Identifying ASEs
You can use the Identify ASE command line tool (IdentifyASE.exe) from the VPM server or PAC to
identify ASEs in a specific domain or in all domains on the server. The Identify ASE tool can be run from
the VPM server or remotely. It is installed with VPM program files.
You can schedule the Identify ASE tool to run using Windows built-in scheduling or run the tool from a
script. As with other command line programs, you can send output to a file.
The Identify ASE tool requires the Identify ASE permission for the domain. If you do not have the Identify
ASE permission for a domain, the domain is not included.
For information about the Identify ASE feature available from the PAC interface, see Identifying ASEs, in
Chapter 6, Domain Options, in the PAC User Guide.
To run the Identify ASE tool:
1
Open a command line window. From the Windows Start button, select Run. In the Run window, type
cmd and click OK.
In the command line window, go to the directory where the Identify ASE tool is located and run the
program. Default locations are:
On the PAC: <drive>:\Program Files\Fluke Networks\Visual UpTime Select
PAC\IdentifyASE
On the server: <drive>:\Program Files\Fluke Networks\Visual Performance
Manager Server\IdentifyASE
The following is shown:
At least four arguments are required. 1 passed.
Usage: IdentifyASE <Select Server> <username> <password>
[/Domain name] [/UpdateIPCoS] [/UpdatePolicing] [/Verbose]
[/Logfile name]
115

User Guide
Options:
/Domain XYZ = Specify a domain for ASE identify, where
XYZ is the domain name.
/UpdateIPCoS = Push IP CoS settings updates to ASEs during
ASE identify.
/UpdatePolicing = Push IP CoS policing thresholds updates
to ASEs during ASE identify.
/Verbose = Generate more detailed log output.
/Logfile filename = Enter a new target path and filename
for log output.
3
Enter a valid server name, user name, and password and any additional specifications (see Table
28). Options are case-insensitive and may be entered in any order. For example, to identify ASEs on
domain XYZ:
IdentifyASE servername VPMadmin vpm /Domain XYZ
During ASE identification, the current domain and network are shown as eligible ASEs are processed.
Errors, such as an unreachable ASE or an invalid login, are shown. A message at termination indicates
whether all ASEs were identified or if any failures occurred. The IdentifyASE.txt log file (located in the
same folder as the Identify ASE tool) is updated with the list of ASEs processed and errors.
Table 28 Identify ASE Commands
Command
Definition
server name
The server's DNS name or IP address.
username
Visual UpTime Select username. The username must be valid

on the server and have the Identify ASE permission in a domain
to identify ASEs in that domain.
password
The user name password, case-sensitive.
/domain XYZ
To identify ASEs in a specific domain type /domain and the

display name for the domain. For example: /domain XYZ. To
identify all ASEs in all domains to which you have permission do
not use the /domain command.
/UpdateIPCoS
Push updates to CoS settings to ASEs during ASE identify.
/UpdatePolicing
Push updates to policing thresholds to ASEs. This is relevant

only if UpdateIPCoS is specified.
/verbose
Generate more detailed output to the log file.
/logfile filename
Enter a new target path and filename for log output. You must
specify a new target if you run multiple copies of the Identify
ASE program at the same time.
116
Managing Domains
Identifying ASEs
If errors occurred during ASE identification error return codes are generated when the program
terminates (see Table 29). These can be used by a parent application or script.
Table 29 Identify ASE Assigned Values
Value
Definition
Success
Command line error
Could not connect to the server
Login failure
No domains to process (e.g., you don't have permission or domain

does not exist)
Runtime error, such as an exception
Identification failed for at least one ASE
117
6. Managing Users
As the system administrator, you can configure servers, domains, user groups, and user accounts. You
can set up user groups to control permissions for each user.
Topics in this chapter include
Typical uses of access controlVPM provides flexible ways of controlling user access.
Managing user groupsA user group is a set of access permissions shared by multiple VPM users.
You can view members of user groups, create and edit groups, and assign group capabilities.
Managing user accountsA user account is a login name and password that identifies a VPM user
and determines what features the user can access in VPM. You can create or copy user accounts,
assign or change user passwords, select domains, lock or unlock user accounts, set login
requirements for PAC users, delete user accounts, and generate a report of user accounts.
For more information on Web portal access permissions, see the Visual Performance Manager User
Guide.
Controlling Access to VPM Features

The following examples show typical reasons for controlling user access to VPM:
A service provider offers management services based on VPMThe service provider has multiple
subscribers on a single server and designates one domain per subscriber. Subscribers log in to a
Web portal or PAC and have access only to the domain that contains their own networks data.
A VPM customer site wants to divide management responsibility of the networkFor example, some
users are responsible for network configuration, performance monitoring, and system-level
operations. Others are responsible for viewing performance data. Others may be responsible for
traffic capture or reporting. To accomplish this division, the system administrator sets up user name
and password combinations (at the server) for each of these areas of responsibility. This ensures that
specific users have access only to the system capabilities for which they are responsible.
A service provider wants to limit the kinds of reports that subscribers can generateThis situation
may depend on the specific service the provider offers its customers. In this case, the system
administrator restricts certain report types on the server that those customers are permitted access
to.
A service provider has purchased partner device licenses for the servers in its network operations
center (NOC), and needs to configure licensing on each serverThe server administrator can log in
Managing Users
Controlling Access to VPM Features
to a central server and configure licensing for that server locally, then remotely configure licensing for
every other server in the service providers NOC.
A service provider needs to define custom classes of service for configuring its ATM customer
circuitsThe server administrator can log in to the central server at the NOC and configure custom
classes of service for the local and any remote servers.
Managing User Groups

A user group is a set of access permissions shared by multiple VPM users. By defining a user group in
Server Administration, you control permissions for all users in the group at once.
All permissions control is at the user group level. For this reason, every user must belong to at least one
user group and can be included in more than one group. Before setting up the first user accounts for login
access, set up the user groups that will be needed for those accounts. This is done by setting the group
capabilities (see Error! Reference source not found.).
Group membership is domain-specific. If a user account is associated with more than one domain, a
different group can apply in each of those domains. In addition, each user has a default group. The
default group applies when the user logs in to Server Administration before selecting a domain. For power
users, the default group determines access permissions in all domains.
Every new server automatically includes four user groups: Basic Users, Advanced Users, Domain
Administrators, and Administrators. Settings for these groups can be modified.
When a system is upgraded, the installation program also automatically creates any new user groups
necessary to emulate established user permissions.
Once you have established groups, you can set up user accounts (see Mana).
Setting Group Capabilities

The following tables describe each permission setting and the actions it controls (see Figure 33):
119

User Guide
Group CapabilitiesUser Group CapabilitiesNetwork Configuration Group CapabilitiesAdministration Group
CapabilitiesTroubleshooting Group Capabilities
Enter group name and

description
User Capabilities
User capabilities include event acknowledgment, Web portal password changes, feature access, and
reports-related privileges.
Table 30 User Group CapabilitiesUser
Capability
Permits User to...
Event Acknowledge
Acknowledge events shown in the Service Summary Events tab.
Change Password
Change his or her own password. This is enforced only on the Web portal
Traffic Capture
Access Traffic Capture for analyzing network traffic by application.
Portal Page Management Access option to modify and delete default Web portal pages if these pages have not
been set to read-only by an administrator. Users that do not have the Portal Page
Management permission cannot modify default pages.
Connex Performance
Allow a (non-power) user access to the VPM Connex API performance data.
120
Managing Users
Managing User Accounts
Table 30 User Group CapabilitiesUser
Capability
Permits User to...
Data
Share Reports to Other
Groups
Allow a (non-power) user to share a custom report with other groups within the
domain. The Share Report criteria is defined in each individual report.
Application Summary
Access the Visual UpTime Select Application Summary tab. Application Summary
shows application and application server performance data.
VoIP Summary
Access the Visual UpTime Select VoIP tab.
Report Scheduling
Schedule reports. This includes scheduling the date and time when all reports in a
report group are generated and the output format and destination.
E-mail Notification
Receive alarm and event notification via e-mail or text messages.
Connex Configuration
Data
Allow a (non-power) user access to the VPM Connex API configuration data.
Port Reporting
Access port and circuit performance reports. Users can also create or delete port
report subgroups and create, edit, or delete port reports.
Domain, Network and

Site Reporting
Access domain, network, and site reports.
NPM Reporting
Access domain-wide reports for data gathered by NPAs.
APM Reporting
Access domain-wide reports for data gathered by Application Performance

Appliances.
Share Reports
Allow a (non-power) user to share custom reports to other users within the same
group. Other users can run or schedule the original report but can not edit it.
Table 31 lists required licenses and group capabilities for report types.
Table 31 Required Licenses and Group Capabilities for Reports
Report Type
Report Settings
License
Group Capability
Application Performance
Management (for APA)
APM
Management
APM Reporting
Management (for NPA)
NPM
Network Performance
Management
NPM Reporting
Management (for ASE)
Application Management
Reports based on feature

license
Server Performance
Application Server
AppSummary
For domain and network

reports: Domain,
Network, and Site
Reporting
121

User Guide
Table 31 Required Licenses and Group Capabilities for Reports
Report Type
Report Settings
License
Management
Capacity Planning
Capacity Planning
Reports based on feature

license
VoIP Performance
Management
VoIP
VoIP
Group Capability
For port reports: Port
Reporting
Domain, Network, and

Site Reporting
Service Level Management Service Level Management Reports based on feature

license
Service Level Management Service Level Management Back-in-Time, Class-of(IP Service Level Metrics
Service, Reports Only, or
report)
SLA Reports
Service Level Management Service Level Management IP SLA Router Polling
(Router IP SLA Service
Level Metrics report)
Network Performance
Performance
Back-in-Time, Reports Only
Port Reporting
Network Performance
Management (for NPA)
NPM
Network Performance
Management
NPM Reporting
WAN Optimization
NPM
Network Performance
Management
NPM Reporting
Network Configuration Capabilities

Users with Network Configuration capabilities can configure networks from the PAC and perform other
domain-level tasks.
Table 32 User Group CapabilitiesNetwork Configuration
Capability
Permits User to...
Network Configuration
Access the PAC Network Configuration toolset to map the topology of WANs into the
network performance database. Access ASE trap destinations on the PAC
ASE Software Update
Download Visual ASE image files to targeted ASEs in the network.
Performance
Monitoring
Access the PAC Performance Monitoring toolset, which allows the user to configure
which network events will be reported by each ASE.
ASE Inventory
Perform an ASE Inventory.
122
Managing Users
Table 32 User Group CapabilitiesNetwork Configuration
Capability
Permits User to...
NPM Configuration
Add and configure NPAs and monitored devices and interfaces.
APM Configuration
Add and configure APAs and server filters for APAs.
Poller Configuration
Select, save, and publish Server Health information
Administration Capabilities
Users with Administration capabilities can perform administrative tasks at the server and domain levels.
Table 33 User Group CapabilitiesAdministration
Capability
Permits User to...
Server Settings
Modify global Service Summary settings, ATM CoS settings, and server-level access
control settings (such as password expiration). This permission also allows the user
to control whether Application Summary users can e-mail reports or save them on a
file server. For more information, see Chapter 7, Configuring Server Settings.
Users and Groups
Create user groups, edit the permission settings of user groups, and configure user
group membership.
Note: Because this permission enables the user to change his or her own access
permissions, grant this permission only to those users who require no other
restrictions.
IP Class of Service
Configure IP CoS settings (in the domains with which the user is associated).
License Administration
Enter license keys for ASE evaluations, partner devices (agents), feature licenses,
and a backup server license. Also permits the user to activate or deactivate feature
licenses. For more information, see Configuring Licenses and Managing Licenses
for a Domain.
Notification
Activate, deactivate, and configure alarms and events from the Alarm Notifications
administrative tool on the Web portal. Activate, deactivate, and configure the
forwarding of events from the local VPM server to other hosts running third-party
event managers (HP OpenView for example).
Domain Options
Modify the following: ASE SNMP community string name, ASE data collection
settings, database maintenance settings, and global event priorities.
Domain Management
Delete, rename, and copy domains. For power users, this capability also permits the
user to create new domains.
Note: Copying domain settings may allow a user to change settings that he or she
does not otherwise have permission to edit. For example, if a user can copy domain
settings but cannot edit IP CoS settings, the IP CoS settings are still copied along
with the other settings. For this reason, the Domain Management permission should
be granted only to users who also have IP CoS and Domain Options permissions.
123

User Guide
Table 33 User Group CapabilitiesAdministration
Capability
Permits User to...
Configure Services
Exclusion List
Edit the list of excluded services in the Visual UpTime Select Service Summary view.
By placing an item in the exclusion list, users can prevent the status of that item from
affecting the status of other items that contain it. For more information, see the Visual
UpTime Select User Guide.
Portal Administration
Access the Panel Permissions and User Group Templates administrative tools in the
Web port. For more information, see the Visual Performance Manager User Guide.
Troubleshooting Capabilities
Users with Troubleshooting capabilities can access various Troubleshooting views.
Table 34 User Group CapabilitiesTroubleshooting
Capability
Permits User to...
Basic Troubleshooting
Access the Visual UpTime Select Troubleshooting toolset for analysis of network
performance data.
Burst
Access the Burst view in the Troubleshooting toolset.
VoIP Calls
Access the VoIP Calls view in the Troubleshooting toolset.
Back-in-Time
Access historical data in the Troubleshooting toolset.
Trace File
Access the Trace File feature in the Troubleshooting toolset.
Service Advisor
Access the Service Advisor.
Application Flows
Access the Application Flows view in the Troubleshooting toolset.
IP Class of Service
Access the IP CoS view in the Troubleshooting toolset.
Viewing Members of a User Group

Selecting a group in Server Administration allows you to see which user accounts are members in a user
group (see Figure 34).
Default users can perform non-domain actions, such as creating a user or a domain. The Default User
setting specifies:
The users group membership in all domains if the user is a power user.
The users group membership in Server Administration (regardless of the power user setting).
124
Managing Users
Figure 34 User Group Members
Select a group and view

users and their associated
domains from the Users
tab
To view the members of a user group:

1
In Server Administration, select the user group.
To see which users are associated with this group when using specific domains, click the Users tab.
To see which users have this group as their default group, click the Default Users tab.
Creating User Groups

To create a user group, your user account must have Users and Groups access permission.
To create a new user group:
1
In Server Administration, expand the server where the group should be created and select the
Groups sub-item.
Select Action > Add Group. Server Administration creates a new group.
In Capabilities for, enter a name for the user group. The name must be unique among all groups on
the server. Group names are not case-sensitive.
In Description, enter a description to identify the group.
Select all permissions to be granted to members of this group. See Error! Reference source not
found. for details about permissions.
Click OK to save the new group. To add users to this group, see Assi
Editing User Groups

To edit a user group, your user account must have Users and Groups access permission.
When you edit the permissions of an existing user group, your changes apply to all current members, as
well as members added later.
125

User Guide
To edit a user group:
1
In Server Administration, select the group. Its properties are shown.
To rename the group, enter a new name in Capabilities for. The name must be unique among all
groups on the server. Group names are not case-sensitive.
Edit the Description text as needed.
Edit the permission settings as needed. To grant a permission, check the box. To deny a permission,
clear the box. See Error! Reference source not found. for details about permissions.
Click OK. To make changes to the members of the group, see Assi
Deleting User Groups

To delete a user group, your user account must have Users and Groups access permission.
A group cannot be deleted while it is associated with any users. Before you begin, verify that no users are
associated with the group and no users specify it as their default group. See Error! Reference source
not found.
To delete a user group:
1
In Server Administration, select the group.
Select Action > Delete Group.
Click OK to confirm the deletion.

Each domain must have valid user accounts associated with it. A user account is a login name and
password that identifies a VPM user and determines what features the user can access in VPM. Each
user account is associated with one or more domains, and that association determines which domains
the user can access when logging in. A user account can have different access permissions in each
domain. No users are configured by default.
Note
Multiple users can log in with the same user name and password simultaneously.
In Server Administration, you can view all user accounts on the server and edit their properties. To see
the user list, expand the server and select the Users sub-item. (If your user account does not have
permission to edit users and groups, Server Administration does not display these sub-items.)
The user list indicates each users login name, comments, default user group, whether the user is a
power user, and the time of the users most recent login (see Figure 34).
126
Managing Users
Figure 35 List of Users on a Server
To view or edit the properties of a specific user account, select that user in the left pane (or double-click
the users name in the right pane). User account properties are organized under two tabs: User Settings
(see Figure 36) and Domain Group Association.
Figure 36 User Settings - VPM Authentication
After defining domains on the server, you can configure user accounts within each domain. You can
Create or copy user accounts.
127

User Guide
Assign or change user passwords.
Select the domains to which each user has access and specify group membership to grant or deny
specific capabilities for each user in each domain.
Require specific users to log in from specific IP addresses. The Network Address field and Subnet
Mask field together restrict the IP address of the machines from which a user can gain access to
selected domains.
Lock or unlock user accounts.
Designate power users.
Specify VPM or external account login authentication.
Delete user accounts.
Generate a report of user account information. See Generating Administrative Reports on page 65.
You can also specify login and password security policies, such as password expiration and restrictions
on password text. For more information, see Configuring Login and Password Policies on page 141.
Creating User Accounts

You can create a new user account or copy an existing account to automatically associate it with the
same domains as the original. You can also specify whether the user is a power user.
Creating an Account
To create a user account:
1
Select Users in the left side of the Server Administration window.
Select Action > Add User.
In User Name, enter the login name for the new account. This name must be unique on the server.
User names are case-sensitive. The name you enter must:
Contain 50 or fewer characters.
Not be the same as a domain name.
In Password, enter an initial password. Because passwords are confidential, they display as
asterisks (*). See Table 5.
In Description, enter a description to identify the user, such as his or her full name.
To require the PAC user to log in from a specific IP address:

a
In Network Address, enter the address in dotted decimal notation.
In Subnet Mask, enter the subnet mask for that address.
The user will not be able to log in from other IP addresses. This restriction applies only in the PAC.
Web portal users are not restricted by IP address.
128
Managing Users
7
In Default Group, select the user group to be applied to this user account by default. For power
users, this setting determines their group in all domains.
To lock the account, check Account Locked. To allow the account to log in, leave the box clear.
To designate the user as a power user, granting access to all domains on the server, check Power
User. To grant access to specific domains only, leave the box clear and:
a
Click the Domain Group Association tab.
In Domains, select a domain to which access will be granted.
In Groups, select the user group with access permissions to be applied to the new user in the
context of the selected domain.
Click Add Association.
Repeat steps 9b-d for each domain to be associated with the new user account.
10 Click OK. You are requested to confirm the password.

11 Enter the password again, and click OK. (After the password is accepted, there is no correlation
between the number of characters in the password and the number of asterisks shown.)
Copying an Account
To copy a user account:
1
In Server Administration, select the user account to be copied.
Select Action > Copy User. Server Administration creates a new user account and assigns the same
description, default group, power user status, IP address settings, and domain memberships.
In User Name, enter a login name for the new user account.
In Password, enter a password for the new user account.
Make other changes to the user settings as necessary.

Note
Copying a user account does not copy the locked/unlocked status.
Click OK to save the new user account.
Editing User Account Passwords

When user passwords expire, users can still update their passwords in either the Web portal or PAC.
However, they may not have permission to change their own passwords. If necessary, the passwords for
user accounts can be edited in Server Administration.
129

User Guide
Note
If External Authentication is enabled on the Server Settings Authentication tab, the password field
will not be available for editing.
To edit the password of a user account:
1
In Server Administration, select the user account. Click the User Settings tab.
In Password, delete the existing password (if any) and enter the new password.
Click OK. The Confirm Password dialog appears.
Enter the new password and click OK.
Assigning User Accounts to Domains

Each user account is associated with one or more domains. This association determines which domains
are available to the user in VPM (see Figure 37).
To associate a user with a domain, you must first associate the user with a group. The access
permissions of the specified group apply to the user account within the specified domain. Power users,
however, are an exception to this rule. See Desifor details.
You can also associate users with a domain from the domain Associations tab. See Configuring User
and Group Associations.
130
Managing Users
Figure 37 Managing Domain Access and Group Membership
To delete an existing
association, select it from the
list and click Delete
Association
To add an association, select a

domain and a group, then
click Add Association
To manage domain access and group membership:

1
In Server Administration, select the user account. Click the Domain Group Association tab.
To add the user to a domain:
In Domains, select the domain to which access will be granted.
In Groups, select the user group to be applied to the user account when accessing the selected
domain.
Click Add Association. The domain/group association appears in the list at the top.
To remove the user from a domain:

a
In the list of domain/group associations, select the domain.
Click Delete Association.
Repeat steps 2 and 3 to adjust the list of associated domains as needed. When you are finished, click
OK.
131

User Guide
Restricting Access by IP Address

You can require PAC users to log in from a specific IP address.
Note
This restriction applies only in the PAC. Web portal users are not restricted by IP address.
To restrict a PAC users access by IP address:
1
In Server Administration, select the user account.
In Network Address, enter the address in dotted decimal notation.
In Subnet Mask, enter the subnet mask for that address.
Click OK.
To remove the IP address restriction from a user account:

1
In Server Administration, select the user account.
In Network Address, enter 0.0.0.0 to clear the address.
In Subnet Mask, enter 0.0.0.0 to clear the subnet mask.
Click OK.
Locking and Unlocking User Accounts

Locked user accounts cannot log in to VPM. If you have Users and Groups permission, you can lock a
user account to prevent access at any time. The system may also lock accounts automatically after a
number of failed login attempts or if the account goes unused for a certain period of time. For more
information about permissions, see Error! Reference source not found.
For more information about lockout policies, see Configuring User Lockout Policies.
To lock or unlock a user account:
1
To lock the account, check the Account Locked checkbox. To unlock the account, clear the box.
Click OK to save the change.
Designating Power Users

A power user is a user account that is associated with all domains on the server. Power users can access
all domains and, as a result, they do not need explicit associations, as other users do. For power users,
the Default Group determines which access permissions apply to the account in all domains.
Power users have access to all reports in each domain, regardless of the report permissions set by the
domain administrator (see Configuring Report Permissions for more information).
132
Managing Users
Power users are automatically associated with any new domains created.
To designate a user as a power user:
1
Check the Power User checkbox. A message states that the user will be automatically added to all
domains and that current associations for the user will become void.
Click OK to return to Server Administration.
In Default Group, select a user group for the account. The permissions of the selected group will
apply to the power user in all domains.
Click OK.
Specifying Authentication
When setting up a user account, if external authentication is enabled for the VPM server on the Server
Settings External Authentication tab, you can set whether the users login information will be
authenticated by the VPM server or an external LDAP or RADIUS server in the User Settings tab for a
user account.
If external authentication is enabled for the server, note:
The password field is not available for editing.
External is the default for new users.
Existing users retain VPM authentication, but this can be changed.
To specify the authentication mode:
1
For Authentication, select:

VPM Server to authenticate the user account login via the VPM Server.
External to authenticate the user account login via an external LDAP or RADIUS server.
Click OK.
Deleting User Accounts

To delete a user account:
1
Select the user account in Server Administration.
Select Action > Delete.
Click Yes when prompted to confirm the deletion.

133

User Guide
7. Configuring Server Settings
This chapter explains how to configure global settings that apply to all domains on the server. Topics
include:
Setting login and password policiesEnforce password expiration, implement password text
complexity, and lock user accounts automatically under certain conditions.
Configuring general settings for the serverThese include report publishing and delivery settings,
VoIP call quality settings, and logo customization for reports.
Defining Classes of Service for use with ATM circuits.
Enabling external authentication.
Configuring licensesSet up licenses for VPM features and feature evaluations, agents (partner
devices), ASE evaluations, and backup servers.
See also:
Configuring Service Summary Settings.
Managing Licenses for a Domain.
Configuring Login and Password Policies

In Server Administration, you can control various login security settings, including:
How often users are required to change their passwords.
How many characters are required in a password.
Whether password text can contain the user login name.
Whether users can recycle their old passwords, and how long the system tracks old passwords.
How many failed login attempts are necessary before a user account is locked.
All these options are controlled from the Access Control Settings tab in the Server Settings view of
Server Administration (see Figure 38).
134
Configuring Server Settings

Configuring ATM Class of Service Settings
Figure 38 Server SettingsAccess Control Settings
Configuring Password Expiration

You can control how many days a user can continue to use the same password. By default, passwords
do not expire.
You can also choose to expire the passwords of all new user accounts immediately when they are
created. This requires all new users to change their passwords the first time they log in and prevents
them from continuing to use the initial password that you provide when you set up the account.
Note
Password settings are global. They are enforced throughout VPM across all domains.
To configure password expiration:
1
In Server Administration, expand the server and select Server Settings. Click the Access Control
Settings tab.
To activate password expiration, check Passwords expire after. To deactivate password expiration,
clear the box.
If password expiration is activated:

135

User Guide
In the days field, enter the maximum number of days to allow users to keep a password.
To require all new users to change their passwords the first time they log in, check Change
password on first login.
Click OK. If password expiration is activated, the systems expiration clock starts counting days
beginning with the current date. After the specified number of days has passed, users will be
prompted to change their passwords the next time they log in to VPM.
Configuring Password Text Restrictions

You can require all user passwords to contain a certain number of characters. You can also forbid users
to recycle passwords that they have used before and control many old passwords VPM tracks for this
purpose. You may also enforce a set of password complexity rules that:
Require that passwords contain both numbers and upper and lower case letters.
Forbid passwords to contain the user name.
Forbid passwords to consist entirely of a portion of the user name.
By default, passwords can be any length from 0 to 40 characters, and password complexity rules are not
enforced. VPM remembers one password by default.
Note:
Password text restrictions are global. They are enforced throughout VPM across all domains.
Password restrictions apply to new or updated passwords, but they are not retroactive to existing
passwords.
To configure password text restrictions:
1
Settings tab.
To require a minimum number of characters in each new password, check Enforce minimum
password length and enter the desired number of characters. To allow passwords of any length,
clear the box.
To require passwords to contain both numbers and letters and to prevent passwords that contain the
user name or form part of the user name, check Enforce password complexity rules. To deactivate
these restrictions, clear the box.
To keep a password history for each user and prevent the recycling of passwords:
a
Check Password History Settings.
In Retain history of ___ passwords, enter the number of passwords for VPM to store and
prevent users from recycling. This setting includes the current password. To retain the current
password and 10 previous passwords in the history, enter 11. The default setting, when
activated, is 12.
136

c
In Password reuse allowed after ___ days, enter the maximum number of days you want to
keep each old password in the history list. Passwords older than this limit will be discarded from
the history, and available for use.
To stop keeping a password history, clear the Password History Settings box.
5
Click OK. Server Administration applies the settings you specified.
Configuring User Lockout Policies

You can configure VPM to automatically lock user accounts that are not used for a specific amount of
time or accounts that make a certain number of login attempts using incorrect passwords.
When a user account is locked, it can be unlocked from the Users tab of Server Administration, as
described in Locking and Unlocking User Accounts. However, user accounts that have been locked
because of repeated login failures can also be unlocked automatically after a specific time interval. You
can specify that interval or disable automatic unlocking using the following procedure.
Note
Lockout settings are global. They are enforced throughout VPM across all domains.
Figure 39 User Lockout Policy Settings
137

User Guide
To configure user lockout policies:
1
Settings tab.
To lock user accounts automatically after one or more days of inactivity, check Disable account if no
login within ___ days and enter the desired number of days. To deactivate automatic locking of idle
accounts, clear the box.
To lock user accounts automatically when they are used in failed login attempts:
a
Check Lock/Unlock Accounts.
In Lock after ___ login failures in ___ minutes, enter the maximum number of login attempts to
allow and the number of minutes for VPM to track each login failure.
To automatically unlock accounts that have been locked because of login failures, check Unlock
after __ minutes and enter the number of minutes for the account to be locked. To deactivate
automatic unlocking, clear the box.
To deactivate automatic locking based on login failures, clear the Lock/Unlock Accounts box.
4
Click OK.
Configuring General Settings

From the General Settings tab you can perform the following actions:
Configure report publishing settings.
Deactivate the feature license expiration warning.
Warn administrators if database log file sizes are too small.
Reverse the NPA interface direction.
Change the VoIP call quality metric.
Change the logo shown on reports.
Change reporting delivery settings.
138

Figure 40 Server SettingsGeneral Settings
Configuring Report Publishing Settings

You can allow users to save reports to a file server or send reports by e-mail or both. By default, these
settings are not active.
Note
Report publishing settings are server-wide. They apply to all users in all domains, for all available
reports. They do not apply to administrative reports. Clearing report settings will cause any
scheduled reports that use that option to fail.
To configure report publishing settings:
1
In Server Administration, expand the server and select Server Settings.
Click the General Settings tab.
To allow users to save reports to a file server, check Users may save reports to file server. To
forbid this, clear the box.
To allow users to send reports by e-mail, check Users may e-mail reports. To forbid this, clear the
box.
Click OK.
139

User Guide
Deactivating the Feature License Expiration Warning

By default, a warning message is issued to Web portal users on the login page when the feature licenses
will expire within 15 days. You can deactivate this warning for all non-power users.
To deactivate the feature license expiration warning:
1
Clear the Warn users if feature licenses will expire soon checkbox.
Setting a Database Log File Size Warning

By default, when the log file size is less than 5 percent of database size, the server icon turns yellow and
a warning is issued in Server Administration. You can deactivate this warning if you are not concerned
about the log file size.
Note
When you turn off this setting, the server status will not indicate when the log file size is less than 5
percent of the database file size.
To deactivate the database log file size warning:
1
Clear the Warn administrator if database logfiles are small checkbox.
Reversing the NPA Interface Orientation

You can reverse the transmit (Tx) and receive (Rx) orientation for a network interface while collecting data
from NPAs.
To reverse the NPA interface orientation:
1
Select the Reverse NPA interface orientation checkbox.
Changing the VoIP Call Quality Metric

You can change the VoIP call quality metric for all domains in the server from the General Settings tab of
Server Administration. The default metric is LQ MOS. Other options are CQ MOS and CQ R-Factor. This
setting controls the metric used in VoIP-related Performance Monitoring events, Troubleshooting views,
140

and VoIP Summary views.
You can override the server-wide setting for an individual domain from Web portal Tools. For more
information, see the Visual UpTime Select User Guide.
To change server-wide VoIP call quality metric settings:
1
Select a call quality metric from the dropdown menu. Options are:
LQ MOSListening quality mean opinion score.
CQ MOSConversational quality mean opinion score.
CQ R-FactorConversational quality R-Factor.
Changing the Logo for Reports

You can change the logo shown in the upper-right corner of the first page on all reports run from the VPM
server. By default, the Fluke Networks logo is shown. The Fluke Networks logo file is 200 pixels wide by
100 pixels high and is located in C:\inetpub\wwwroot.
To create a replacement logo, create a .jpg file with a 2:1 width to height aspect ratio.
To change the logo on reports:
1
Under Default Report Logo, click Change Default.
In the Change Default Report Logo dialog, select a .jpg file to use as a logo and click OK.
In General Settings, click OK.
See also, Changing the Logo for Reports on a Domain.
Changing E-Mail Delivery Settings

By default, the SMTP server address and the e-mail address entered during Reporting Services setup are
shown in the General Settings | E-mail Delivery tab in Server Administration. To change these settings:
In the SMTP Server address field, enter a new address or name for the SMTP server to be used by
Reporting Services.
In the From Address field, type the e-mail address from which reports will be sent. It is
recommended that you dedicate an e-mail account specifically for this purpose.
141

User Guide
Note
Make sure that virus scanning software is not blocking SMTP port 25.
If your SMTP server does not use port 25, contact Fluke Networks technical support (see Technical
Support on page xiv) for information on port settings.
You can configure Alarm Notification (see Chapter 3, Administration Tools in the VPM User Guide or
online Help) to deliver alarm notification via e-mail.

For version 6.0 and later ATM ASEs and partner devices, you can assign a Class of Service (CoS) for
each ATM virtual circuit and virtual path defined on the PAC. CoS allows you to perform the following
tasks:
Specify whether to use Sustainable Cell Rate (SCR) or Peak Cell Rate (PCR) for burst analysis on
the data VPM collects for ATM circuits.
Organize ATM virtual paths and circuits. For example, a service provider may group virtual paths with
similar characteristics and service levels into a common CoS. By viewing the CoS names and
learning what they mean to the service provider, customers will then know what service levels to
expect for their circuits.
You can select the CoS from among a standard set of five classes plus five custom, user-defined classes.
The complete set of CoS selections is retrieved from the server by the PAC, where the selections are
available during circuit configuration. ATM CoS settings apply to the server as a whole, not to any specific
domain defined on the server. (See Chapter 2, Network Configuration, in the PAC User Guide for more
information about configuring CoS for a circuit.)
Server Administration allows you to enable or disable the five standard classes and to create custom
classes. You can choose whether to use PCR or SCR for burst analysis on each custom class.
Use the following procedure to specify which ATM Classes of Service are available in the PAC for
assignment to circuits.
To configure ATM Classes of Service:
1
In Server Administration, expand the server and select Server Settings. Click the ATM Class of
Service tab.
To include a pre-defined CoS, check its box in the Pre-Defined ATM Class of Service area. To
exclude a CoS, clear the box.
To include a custom CoS:

a
Check its box in the User-Defined Class of Service area.
Enter a name for the new class in the text box.
Select either PCR or SCR from the list at the right of the text box.
142

4
Click OK.
Enabling External Authentication

You can set up authentication for login access to VPM applications to be performed against an external
LDAP (Lightweight Directory Access Protocol) or RADIUS server. This allows users to log in using their
LDAP or RADIUS credentials.
Figure 41 Server SettingsLDAP Authentication
If SSL is enabled, install

certificates on VPM serv er
143

User Guide
To configure and test LDAP authentication:

1
In Server Administration, expand the server and select Server Settings. Click the External
Authentication tab (see Figure 41).
Select Enable External Authentication.
Select the LDAP radio button.
If the directory server is a Windows Server running Active Directory, select Microsoft Active
Directory. If the directory server is a Linux/UNIX machine running OpenLDAP, select OpenLDAP.
Select the LDAP version. For most LDAP servers, select v3 (the default setting). For users of legacy
systems, which support only v2 protocol, select v2.
If the LDAP server is SSL enabled, select SSL Enabled.

Note
If SSL authentication is enabled for VPM, you must install certificates on the VPM Server. For more
information, see Chapter 4, Setting up the Server, in the VPM Software Installation Guide.
Select the BindMethod, either Simple or GSS Negotiate (if the Directory Server supports Kerberos
GSS (Generic Security Service)). GSS Negotiate is not available if OpenLDAP is selected as the
Directory Server.
Enter the LDAP server IP address or DNS name and the port number on which the server is
activated.
Enter the base DN information of the LDAP server. For OpenLDAP, if users are present under more
than one base DN, provide all possible base DNs, separated by semicolons.
10 For OpenLDAP, configure the name attribute by which users are identified on the LDAP server.
11 (Optional) Test the LDAP connection to verify settings. Enter the username and password of the test
connection and click Test. A dialog shows the status of results:
The LDAP/AD server cannot be reached.
The LDAP/AD server can be reached but authentication failed.
The LDAP/AD server can be reached and authentication passed.
The LDAP/AD server is the wrong version.
If the LDAP server cannot be reached, is the wrong version, or authentication failed, verify that the
settings are correct and retest the connection.
144

Enabling External Authentication
Figure 42 Server SettingsRADIUS Authentication
To configure and test RADIUS Server authentication:

1
In Server Administration, expand the server and select Server Settings. Click the External
Authentication tab (see Figure 42).
Select Enable External Authentication.
Select the RADIUS radio button.
Enter the RADIUS server IP address or DNS name and the port number on which the server is
activated. (Port 1812 is the typical RADIUS reserved port.)
Enter the Shared Secret for RADIUS authentication.
(Optional) Test the RADIUS connection to verify settings. Enter the user name and password of the
test server and click Test. A dialog shows the status of results:
The RADIUS server can be reached and authentication is successful.
The RADIUS server can be reached but authentication failed.
The RADIUS server cannot be reached.
If the RADIUS server cannot be reached or authentication fails, verify that the settings are correct and
retest the connection.
You can now specify External authentication in the User Settings. Refer to Specifying
Authentication.
145

User Guide
As administrator, you set up and manage the distribution of licenses in VPM. VPM provides a range of
licensing options and features. The options available to you depend on the licensing mode (default or
domain) and licensing features your organization has purchased.
Note
Domain-fixed and domain-flexible licensing modes are available for service providers only.
This section explains how licensing works and provides step-by-step instructions on each aspect of
licensing. Topics include:
Licensing modesCompare licensing features available in the default and domain-fixed and domainflexible licensing modes.
Managing feature licensesAssign permanent feature licenses or use feature evaluation licenses to
temporarily evaluate features. Service providers can also assign features only for use by power
users.
Managing ASE evaluationsUse ASE evaluation licenses to temporarily evaluate VPM ASEs.
Managing agent licensesUse agent licenses for supported partner devices in VPM.
Configuring a backup server licenseEnable a backup server for use when your primary server is
unavailable.
Using LAN Visibility licensesUnderstand how to apply and manage LAN Visibility licenses, which
are directly linked to LAN Visibility ASEs.
To view and edit server-based licensing information in Server Administration, you need License
Administration permission. For more information, see Administration Capabilities.
Licensing on both local and remote servers can be configured using Server Administration. Because the
servers database stores license key data for each server, you can administer this data remotely using
Remote Server Administration. This enables you to manage license keys for multiple servers from a
single console.
Note
From the point at which feature, feature evaluation, ASE evaluation, and agent, licenses are
created, you have 30 days to enter these into VPM.
When upgrading to the current VPM version, all licenses are returned and the new LAN Visibility license
is disabled by default.
For information about domain-level licensing options, see Managing User Groups.
146

Licensing Modes
Options for applying feature licenses depend on the licensing mode:
Default licensing modeApply feature and other licenses at the server level uniformly to all domains.
Create Service Summary domains with no features.
Domain-fixed or domain-flexible licensing modesApply feature licenses uniquely to each domain on
the server for a specified number of ASEs. Domain-fixed and domain-flexible modes provide different
options for handling licenses. Feature modules can be enabled or disabled at the server, domain, and
power-user levels.
Note
Domain-fixed and domain-flexible licensing modes are available only for service providers.
Table 35 provides a comparative analysis of licensing modes.
Table 35 Licensing Features and Options by Mode
Feature/
Option
Default
Domain-Fixed
Domain-Flexible
Feature
Licenses
Server-wide (all domains). Once assigned to a domain,

licenses can be used only by that
domain. The domain has a reserve
of licenses that may be reused
within the domain or have not yet
been used but cannot be made
available to another domain.
Once assigned to a domain, licenses

are reserved for use by that domain.
However, they can be reassigned to a
server pool by the server
administrator.
Feature
Evaluation
Licenses
Server-wide. Regular and

power users can access
features on all domains.
Single domain.
Single domain.
ASE Evaluation Server-wide.

Licenses
Server-wide.
Server-wide.
Agent Licenses Server-wide.
Server-wide.
Server-wide.
Backup
Licenses
Not applicable.
Not applicable.
Duplicate ASEs Supported across all

domains on server.
Supported within the same domain

without consuming additional
licenses. If a duplicate exists in the
domain, no licenses are
relinquished when an ASE is
deleted or inactive.
Supported within the same domain

without consuming additional
licenses. If a duplicate exists in the
domain, no licenses are relinquished
when the ASE is deleted or inactive.
Power Users
Supported.
Supported.
Server-wide.
Supported, but not

permitted on Service
147

User Guide
Table 35 Licensing Features and Options by Mode
Feature/
Option
Default
Domain-Fixed
Domain-Flexible
Not applicable. This is a domain with

no features activated.
Summary domains.
Service
Summary
Domains
Supported. No power
users are permitted.
Not applicable. This is a domain

with no features activated.
Rename
Domain
Feature licenses and

duplicate ASEs are
unaffected.
Feature licenses are lost. PowerAll licenses and duplicate ASEs are
user and feature evaluation licenses unaffected.
and duplicate ASEs are unaffected.
Disabled
Domains
Count in licensing.
Count in licensing.
Delete Domain
Active ASE evaluations

Active feature licenses, feature
are lost. ASE and
evaluations, and ASE evaluations
duplicate ASE licenses are are lost.
recovered for reuse.
Active feature evaluations and ASE

evaluations are lost. Allocated and
reserved feature licenses return to the
server pool for reuse.
New Domain
Features are enabled at

the server level unless one
or more domains is
marked Service Summary.
Inherits all server-wide features

enabled at the server level when it
is created. Feature licenses can be
modified at the domain level.
Inherits all server-wide features

enabled at the server level when it is
created. Feature licenses can be
modified at the domain level.
Add ASEs
Requires feature licenses

for regular and power
users for all enabled
features.
Requires available feature licenses

for domain. Consumes one poweruser and one regular-user license
for all features in the domain.
Requires available feature licenses on

server. Consumes one power-user
and one regular-user license for all
features in the domain.
Delete ASE
Licenses are recovered for Licenses are returned to domain

reuse.
reserve.
Inactive ASE
Inactive ASEs in any

domain do not consume
licenses.
Count in licensing.
Licenses are returned to domain

reserve.
Inactive ASEs in any domain do not Inactive ASEs in any domain do not
consume licenses.
consume licenses.
Managing Licenses in Default Mode

In default licensing mode, all domains have the same features (except for Service Summary domains),
and all feature licenses are managed server-wide. When feature licenses are applied, they are applied
across all feature-based domains. Features cannot be enabled on a per-domain basis.
For new VPM systems, default licensing mode is enabled on installation. The server has all software
feature bundles enabled for all users for a 30-day feature evaluation period for up to 10,000 ASEs.
Application flow data is collected from supported ASEs during this initial 30-day period.
148

Warning
If no permanent licenses are entered after the initial 30-day evaluation period, all domains on
the server will become Service Summary domains.
When working in default licensing mode, note:
When adding an ASE, features are enabled on all domains (except Service Summary domains) for
regular users. Power users may have additional features enabled. To add an ASE, feature licenses
for regular and power users are required for all enabled features.
Domains can be specified as Service Summary, which means that all features beyond Service
Summary are unavailable to all ASEs in the domain. For more information, see Creating a Service
Summary Domain.
If you have power-user licenses on your system, you cannot create a Service Summary domain.
When you change a Service Summary domain to a standard domain, unused and active feature
evaluation licenses are lost.
When you delete a standard domain, a license is returned for each unique ASE, both for regular-user
and power-user licenses. When you delete an ASE or domain, licenses are recovered for reuse.
When an ASE is duplicated in the same domain and in no other domain (whether once or more
times), only one license is recovered.
You can enter duplicate ASEs in any domain without consuming additional licenses.
For more information, see .
Managing Licenses in Domain Mode

Using domain licensing, service providers can purchase feature licenses and assign these to specific
domains on the VPM server as needed. This optional feature requires a domain-fixed or domain-flexible
license key and is available only to service providers. Domain-fixed and domain-flexible modes provide
different options for handling licenses.
In domain-fixed mode, feature licenses remain tied to the domain when a feature or ASE is deleted or
deactivated. Licenses do not return to the pool when a domain is deleted.
In domain-flexible mode, feature licenses return to the pool for reuse when the feature or ASE is
removed or the entire domain is deleted.
In both domain licensing modes, service providers can activate features and feature evaluation license
keys at the domain level. Features are drawn from domain reserves and the pool of available features on
the server. By contrast, in default mode, features are managed at the server-wide level only. For more
information, see Error! Reference source not found.
To use domain licensing, you must purchase a domain licensing key and a set of feature licenses to use
across domains. Then, assign features to specific domains. As ASEs are added to a domain, the server
subtracts licenses from the pool of purchased feature licenses.
To switch from domain-fixed to domain-flexible licensing, a new license key is required. In Server
149

User Guide
Administration, once you have entered the new license key, restart the VPM Server service for the
change to take effect. You cannot switch from domain-flexible mode to domain-fixed mode.
For more information about licensing options in domain mode, see .
Managing Feature Licenses

You can purchase permanent licenses and temporary evaluation licenses for features in the VPM system,
customizing the feature set to meet the needs of your organization or the organizations to which you
provide service.
When working with feature licenses, note:
Options for applying feature licenses depend on the licensing mode:
In default licensing mode, feature licenses are applied at the server level uniformly to all domains
(except Service Summary domains).
In domain licensing fixed or flexible modes, feature licenses can be applied uniquely to each
domain on the server for a specified number of ASEs. Feature modules can be enabled and
disabled at the server and domain levels.
At the server level, you can designate which features will be available for domains. You can also
create power users (such as service provider operations staff), who have access to all domains on
the server. By contrast, standard user licenses are always operable within a domain if domain
licensing is active. For more information about creating a power user, see Creating User Accounts.
In domain licensing mode, at the domain level, you can designate which features are active in a
domain. For more information, see Managing Licenses for a Domain.
User access to some features may also be restricted based on the user capabilities of the account.
For more information, see Managing User Groups.
To work with feature evaluation licenses, see Using Feature Evaluations
For more information about features, see Chapter 1, Visual Performance Manager Overview.
Adding Feature Licenses

You can activate features at any time by purchasing a feature license key from Fluke Networks and
entering the key in the Licenses > Feature License tab. The feature license key activates the set of
features that you have licensed. For each feature, the total number of licenses purchased and available is
listed, along with options for assigning andin domain-flexible modeun-assigning licenses to domains.
Service Summary does not require a feature license. Feature licenses must be specifically activated and
deactivated (see Figure 43).
150

Figure 43 Feature LicensingDomain-Flexible Licensing Mode
Number of licenses available per

feature server-wide out of the
total number
Enter feature license key

and click Add
Eval column is shown only in

default licensing mode. In
domain mode, feature
evaluations are managed at
the domain level
Enable the feature for all

users or power users, it
becomes available to all
domains
Click Save when done
Note
Each server stores its own feature license key. If your organization uses multiple servers, you must
obtain a feature license key for each server and repeat the following procedure for each server.
To add feature licenses:
1
Contact Fluke Networks to obtain a license key. You will need to provide a server ID. Be sure to
specify whether you want the license for all users or for power users only.
In Server Administration, select a server from the tree and select Licenses.
Click the Feature License tab. The total ASE count, all available features, the current feature license
count, and license status are shown (see Figure 43). Refer to the Fluke Networks website for more
information.
151

User Guide
4
To add feature evaluation or permanent licenses, enter the license key number and click Add. New
licenses are added and counts are shown in the Available and Total columns. Feature evaluation
licenses are checked and expiration dates are shown.
Note
In default licensing mode, you can enter feature or feature evaluation license keys. In domain
licensing mode, you enter only feature license keys at the server level. Feature evaluation keys are
entered at the domain level (see Managing Licenses for a Domain.).
To enable regular-user or power-user licenses at the server-wide level, select the All Users and/or
Power Users checkboxes.
Click Save. Click Cancel to cancel selections in the feature license list only. Once a license key is
entered, it cannot be canceled.
Using Feature Evaluations

Using feature evaluation licenses, you can try one or more features on a temporary basis without
affecting the permanent feature license count. When using feature evaluation licenses, note:
Feature evaluation licenses are temporary. They can be deployed on any number of ASEs.
In default licensing mode, feature evaluation licenses are server-wide, and the license key is entered
at the server level. In domain licensing, these licenses are restricted to a single domain, and the
license key is entered at the domain level (see Managing Licenses for a Domain.). A feature
evaluation license is valid for any domain but may be entered only once.
Once a feature evaluation license is entered, it remains until it expires. When it expires, the feature is
no longer available unless a permanent license or another feature evaluation license includes the
same features.
A feature evaluation license cannot be extended. However, a matching feature evaluation license can
be set up that begins when the existing feature evaluation license period ends.
Multiple feature evaluation license keys can be added without replacing the previous key. If multiple
keys are present, they are used in order of expiration.
Each feature evaluation license may include one or more feature bundles.
For information about LAN Visibility feature evaluations, see Error! Reference source not found.
Use a feature evaluation license to evaluate the routers with the IP SLA Router Polling feature.
Managing ASE Evaluation Licenses

ASE evaluation licenses let you temporarily evaluate VPM ASEs without increasing the number of ASEs
in the permanent license count. In Server Administration, you can add ASE evaluation licenses and view
total and available license counts and the number of access lines currently using ASE evaluation
licenses.
152

When using ASE evaluation licenses, note:
ASE evaluation licenses are temporary.
ASE evaluation licenses are server-wide and may be used in any domain. These licenses cannot be
assigned or restricted to a specific domain. When a domain is deleted, any active ASE evaluations
are lost.
An evaluation ASE supports features activated in the domain.
ASE evaluation licenses cannot be extended. Once the license is entered, it remains until it expires or
is converted it into a permanent ASE. Once an ASE evaluation license expires, the ASE becomes
inactive and any data is lost, even if the ASE is later re-added as a new ASE evaluation license.
An ASE evaluation license can be used to evaluate a third-party agent device.
Multiple ASE evaluation license keys can be added without replacing the previous key. Multiple ASE
evaluation license keys are used in the order in which they were entered.
For information about LAN Visibility ASE evaluations, see Error! Reference source not found.
A polled router cannot be added as an evaluation ASE. Use a feature evaluation license instead.
153

User Guide
Figure 44 ASE Evaluations Licensing
To add ASE evaluation licenses:

1
Contact Fluke Networks to obtain the ASE evaluation license key. You will need to provide the server
ID.
Click the ASE Evaluations tab. The current ASE evaluation license count is shown (see Figure 44).
To add licenses, enter a valid license key and click Add Key. The number of ASE evaluations is
shown in the Initial Count and Available columns along with the expiration date.
Managing Agent Licenses

Agent licenses are permanent licenses that allow you to use supported third-party devices (such as nonpolled routers or frame relay or ATM edge concentrators) in VPM. An agent license allows the collection
of real-time and historical performance data from the device. You can edit agent licenses and view
license counts in Server Administration.
154

When using agent licenses, note:
All agent licenses are server-wide only.
A license key must be entered for each class of agent you have licensed. Multiple keys are not
supported. A new agent license key for a class replaces the existing license key for that class.
The number of agent licenses purchased for each agent class determines the number of devices that
can be used that class. When all licenses in an agent class are in use, users cannot add more
devices of that class.
Additional licenses can be purchased at any time. A license can be released on the server by
removing one of the active devices. Another device in that class can then use that license.
For devices with multiple physical interfaces, each interface requires a separate agent license.
Figure 45 Agent Licensing
To view and edit agent licensing counts:

1
Contact Fluke Networks to obtain an agent license key. You will need to provide a server ID.
Click the Agents tab. Initial and available agent license counts, a description of each class, and the
expiration date (if applicable) are shown (see Figure 45). For permanent licenses, None is shown.
When no license is defined, Unknown is shown. When the expiration date passes, you must enter a
new agent license key for that class.
To add or modify agent licenses, select a class and click Edit.
In the Agent License dialog, enter the number of licenses you have purchased and the new license
key for that class. Click OK.
155

User Guide
6
Repeat steps 1-5 for each new license key you have obtained.
Using LAN Visibility Licenses

When working with LAN Visibility licenses, note:
LAN Visibility licenses are directly linked to LAN Visibility ASEs. The LAN Visibility feature must be
licensed in order to add LAN Visibility ASEs to VPM.
The LAN Visibility license can be activated if the number of LAN Visibility feature licenses equals or
exceeds the number of active LAN Visibility ASEs.
LAN Visibility ASEs are counted only against LAN Visibility feature license types. Standard ASEs are
not counted against LAN Visibility features. For example, if you have a license for five LAN Visibility
ASEs and a license for ten features for a system with no ASEs, five LAN Visibility ASEs and ten
standard ASEs may be added.
When a LAN Visibility license is disabled at the domain or server level, LAN Visibility features are no
longer available for that domain or server. Service Summary data is still available.
A domain may contain both LAN Visibility and Multi-Protocol or IP Transport ASEs. In this case, note:
An Application Summary feature license is required for access to the Application Summary
toolset for all ASEs.
Aggregate reports can include data from all ASEs only when the LAN Visibility license and the
licenses needed for regular ASEs for that report are active.
A report that can run on multiple ports and also on a single port may be unlicensed at the domain
or network level but licensed at the port level.
If only LAN Visibility is licensed, then the report list shows few reports at the domain or network
level. LAN Visibility ports appear on the navigation tree because these are licensed.
LAN Visibility ASEs may be added and operated under all three license modes (default, domain-fixed,
and domain-flexible).
The following feature evaluation rules apply (for more information, see Using Feature Evaluations ):
When a feature evaluation is active and no permanent LAN Visibility feature license exists, LAN
Visibility ASEs have no ASE limit.
If no feature license is already active for LAN Visibility, adding a feature evaluation will allow LAN
Visibility ASEs to be added.
LAN Visibility ASEs that have lost access to a feature due to the expiration of a previous feature
evaluation will resume access to the feature if a new feature evaluation is applied.
When a permanent LAN Visibility feature license becomes active, the LAN Visibility feature
evaluation is not needed. If a feature evaluation is active, enough permanent licenses must be
available to cover all active LAN Visibility ASEs to activate a permanent license.
156

Because feature evaluation licenses do not transfer when you switch from the default to a domain
licensing mode, permanent LAN Visibility licenses should be applied instead of LAN Visibility
feature evaluation licenses prior to changing licensing modes.
The following ASE evaluation rules apply (for more information, see Mana):
If a permanent LAN Visibility feature license is enabled, you can evaluate a LAN Visibility ASE. If
the LAN Visibility license count is full, the evaluation ASE may be added as a temporary
expansion of the limit.
To convert an evaluation ASE to a permanent ASE, a permanent LAN Visibility license must be
available.
When an ASE evaluation expires, all ASEs covered by the expiring license are automatically
marked as inactive.
Configuring a Backup Server License

Feature license keys apply to a specific VPM server and cannot be transferred to another server.
However, using a backup license, you can configure a backup server for use when the primary server is
unavailable without requiring a full set of new license keys (see Figure 46). When using a backup license,
note:
Backup licenses can be permanent or temporary.
The backup server license cannot be installed on the primary server.
Any VPM server can be designated a backup server, but only for one primary server at a time. If you
have a backup server, you must enter a license key on the backup server and indicate the server ID
of the primary server.
Warning
To use backup licensing on a new or upgrade system, first deploy permanent licenses on the
primary server. Then, on the backup server, enter the backup license key before migrating
license data from the primary server. For information about managing an upgrade with a
backup server, see the Software Installation Guide.
For information about setting up data replication for the backup server and for converting a backup
server to a primary server, contact TAC (see Technical Support). Fluke Networks does not provide
utilities for ensuring data replication. You must use SQL Server tools to replicate the data.
When creating a new backup server, you must enter the backup license key into the new backup
server before loading the databases from the primary server to the backup server. If you have loaded
the primary servers data first, contact TAC for steps to set the backup license key separately.
Network configuration operations are supported on a backup server. You can add and remove ASEs
based on your available licenses. However, on backup servers, you cannot add or edit any form of
licenses.
157

User Guide
When a backup license expires or if it has been corrupted, data collection will no longer occur on the
server.
Figure 46 Backup Licensing
Backup server ID
Get primary server ID
from the ser s
Licensing tab in Server
Administration
Enter backup license key
purchased from Visual
Network Systems
Click Edit to update an existing

backup server license
To enter a backup server license key:
1
Contact Fluke Networks to obtain the backup license key. Do this while the primary server has its own
valid license and before loading the databases from the primary server to the backup server. You will
need to provide the server ID of the primary server. See Error! Reference source not found. for
more information.
At the backup server, open Server Administration and select a server from the tree. Select
Licenses.
Note
You cannot enter a backup server license key from Remote Server Administration. You must do this
on the backup server itself.
Click the Backup License tab.
In Primary Server ID, enter the server ID for the primary server of which this server is a backup.
In Backup License Key, enter the backup license key.
To edit an existing backup server license based on purchased updates, click Edit and make the
changes. Click OK.
158

7
Click Save. The Expiration Date area updates to indicate the new expiration date of the backup
server license.
Restart Server Administration. In backup mode, licensing tabs are unavailable.
Identifying the Server ID

The server ID is an identifier unique to each VPM server and is generated from the server hardware. The
server ID is used to create license keys and to associate these license keys with a specific server.
Use the Server ID field in Server Administration to determine the server ID value. If you need to contact
Fluke Networks to obtain a new or updated license key for a local or remote server, you will need to
provide the server ID of the licensed server, along with the list of items to be licensed.
Note
In most cases, the correct local server ID value should already appear in the Server ID field of the
Licenses tab. You must update this value only in the case of a freshly upgraded server.
If you do not have administrative access or the VPM software is not yet installed, you can still retrieve the
server ID using the GetServerID.exe located in the servers executable directory.
Figure 47 Get Server ID Dialog
To view the server ID from GetServerID:

1
Run GetServerID.exe located in the server executable directory.
To view the local server ID, click Get Local ID.
To view a remote server ID, click Get Remote ID. In the Remote Server dialog, enter the name (or
IP address) of the remote server and click OK.
159
8. Managing Web Access
Web users access data over the Internet using HTTP or HTTPS connections to the web server. The web
server, which may be on the VPM server computer or installed on a separate server, sits behind a firewall
and supports concurrent access from multiple users (see Figure 48).
Figure 48 System Communication
As system administrator, your responsibilities for enabling the Visual UpTime Select web application
users capabilities are to:
Configure permissions to use the Troubleshooting toolset for the appropriate domains for all users.
Use the Server Administration application to configure user group permissions, as described in
Managing User Groups.
Configure options for the Service Summary application. You can control how often Service Summary
updates its performance information, and what priority thresholds it uses for determining performance
warnings and performance errors. See Error! Reference source not found. below.
Configure each web server to communicate with one or more VPM servers, and configure global
options on each web server. See Configuring a W
Provide users with the web servers host name or IP address to use as the URL in the form:
http://Web_Server/VisualUpTimeSelect/default.aspx
(where Web_server is the DNS hostname or IP address of a VPM web server).
Managing Web Access
Configuring Service Summary Settings

In Server Administration, you can set parameters to control how the server collects performance data and
status for the Service Summary view. You can control how often the server polls ASEs for status data,
how much recent time to consider when calculating the current error status, and the relative severity of
the error status levels. New settings will take effect after VPM services are restarted.
You can set the following parameters in Server Administration (see Figure 49):
Service Summary polling intervalNumber of minutes between polls to ASEs. If set to 0, polling is
disabled. The default value is 15.
Performance time periodNumber of hours to consider when identifying recent performance
warnings and errors. If set to 0, performance issue detection is disabled. The default value is 2.
Performance warning thresholdMinimum priority value that indicates a performance warning for
a statistical threshold event. Warnings are shown for services in Service Summary. You can specify
values from 0 to 255. The default value is 100.
Performance error thresholdMinimum priority value that indicates a performance error for a
statistical threshold event. Errors are shown for services in Service Summary. You can specify values
from 0 to 255. The default value is 200.
Figure 49 Server SettingsService Summary Settings
To configure Service Summary settings:

1
In Server Administration, expand the server and log in. For more information, see Logging in to
Server Administration.
Select Server Settings. Click the Service Summary Settings tab.
161

User Guide
3
In Service Summary polling interval, enter the number of minutes that you want the server to wait
between status polls. To disable polling, enter 0 (zero).
In Performance time period, enter the number of hours to consider when identifying recent
performance warnings and performance errors.
In Performance warning priority threshold, enter the minimum priority level that indicates a
warning. To disable performance issue warning detection, enter 0 (zero).
In Performance error priority threshold, enter the minimum priority level that indicates an error. To
disable performance issue error detection, enter 0 (zero).
Click OK to save your changes.
The web portal queries the web server based on a configurable refresh interval. Use the configuration tool
on the web server to set a minimum interval. For more information, see Configuring the Service Summary
Auto-Refresh Interval
.
Configuring a Web Server

VPM web servers enable communication between the web portal and the VPM server. They handle
requests from web browsers and generate the pages that the browsers display.
You can install a web server on a VPM server computer or on a separate computer. If you have multiple
VPM servers, each can use a separate web server, or two or more can share a web server. For more
information about planning web server locations and installing web servers, see the Software Installation
Guide.
As an administrator, you control:
Which VPM servers each web server can access. Each web server maintains a separate list of
available servers.
Which features are available to each user. You can restrict access to certain features. For more
information, see Managing User Groups.
By default, a web server responds to HTTP requests for its client communications. You can configure it to
respond to both HTTP and HTTPS, or restrict communications to HTTPS only, by editing the web server
properties in Microsoft IIS.
This section presents information you need to configure the web server for access by VPM users. Topics
include:
Logging in to the system management utility on a Web server
Controlling Web server access to Visual Performance Manager servers
Configuring global options for Visual UpTime Select users
162
Frequently Asked Questions

Licensing FAQs
Logging in to a Web Server

To configure the settings on a VPM web server, you must log in to the web servers system management
utility.
To control access to the system management utility, the web server verifies your Windows user name and
password. To log in successfully:
The user ID and password you provide must be valid for the Windows domain you specify, and
The web server must be configured to allow that user account to access the system management
utility.
When possible, the web server authenticates your user name and password automatically. It will prompt
you for a user name and password only under one of the following conditions:
You use an IP address or a fully qualified domain name (such as server.mydomain.com, rather than
simply server) when you connect to the web server. In these cases, your web browser will not
automatically send your Windows user name and password, so the web server must prompt you for
them.
The web server cannot validate the user name and password that your web browser has
automatically sent. This can occur if you are currently logged in to a different Windows domain than
the one that contains the web server.
To log in to a Web server:
1
In your web browser, go to this address:

http://server_name/WebSystemManagement/default.aspx
where server_name is the hostname or IP address of the Web server. (For secure HTTP, begin the
URL with https:// instead of http://.)
If necessary, supply your Windows login information:

a
In User Name, enter your Windows user ID.
In Password, enter the password for your Windows user ID.
Click OK.
Controlling Web Server Access to Servers

VPM web administrators can configure the list of servers that are available from a web server by using the
system management utility running on that web server. When you log in to the system management
utility, you will see a list of servers and their IP addresses.
163

User Guide
Figure 50 Configuring Servers for Web Server Access
The list of servers is sorted by name. To reverse the list, click the arrow in the Name column heading.
Each web server has one designated primary VPM server. The primary server stores user configurations
for the web server.
Adding a Server
Use the following procedure to add a server to the list. Because each web server maintains its own server
list, be sure to repeat this procedure on every web server that requires access to this server.
To add a server to the list:
1
Log in to the web server. For more information, see Log.
At the bottom of the server list, in Name, enter a name for the new server.
In IP Address, enter the IP address or DNS hostname of the server computer.

Note
If you have a firewall between the web server and the VPM server, and the firewall performs
network address translation, be sure to use the IP address that will access the target server
computer from the web servers perspective. Do not enter Localhost.
To enable access to the new server, check Enabled.
Click Add.
Setting the Primary Server

Each web server designates one server in its list as the primary server. The primary server is the server
that stores user configurations for the web server.
To set the primary server:
1
Log in to the web server. For more information, see Log
In the server list, select the server that you want to designate as primary.
164

Licensing FAQs
3
Click Edit. The servers properties appear below the server list.
Check Primary Server. Because the primary server must always be enabled, the Enabled checkbox
fills in automatically.
Click Update.
Disabling or Enabling a Server

To temporarily suspend the web servers access to a server without removing the server from the list, you
can disable the server. (This action does not affect the server itself, only the web servers communication
with it.)
To restore access to a disabled server, enable the server.
Note
You cannot disable the primary server. To disable a server that is currently serving as the primary
server, first designate a different server as primary. See Setting the Primary Server
To disable or enable a server:
1
In the server list, select the server you want to disable or enable.
Click Edit. The servers properties appear below the server list.
To disable the server, clear Enabled. To enable the server, check Enabled.
Click Update.
Removing Servers
Use the following procedure to remove one or more servers from a web servers server list. (This action
does not affect the server itself, only the web servers communication with it.)
To remove one or more servers from the list:
1
In the server list, select the servers you want to remove.
Click Delete. A dialog box asks you to confirm the deletion.
Click OK.
Editing Server Properties

You can edit the name or IP address of any entry in the server list. This action changes only the web
servers list of servers. It does not affect the server itself. You can edit only one server at a time.
You can enter up to 32 characters for a server name or IP address, but only 18 are shown in the server
list. To view the complete name of an entry in the list, move the mouse cursor over the entry.
165

User Guide
To change the name or IP address of a server:
1
Click the checkbox of the server you want to edit. You can edit only one server at a time.
Click Edit. The bottom of the page shows the properties of the server you selected.
To rename the server, enter its new name in Name.
To change the servers IP address, enter the new address in IP Address.
Click Update.
Customizing Global Web User Settings

As an administrator, you have control over settings that affect Visual UpTime Select web applications.
You can customize the link at the bottom of the Visual UpTime Select web interface navigation tree, set
the minimum interval for automatic screen refresh, and specify additional text for license-related
messages.
These settings are stored on the VPM web servers primary server. They affect all web servers that
designate that server as primary. If you are using more than one web server with different primary
servers, be sure to configure these settings for each primary server in your system.
Figure 51 Web Server Global Options
Configuring the Custom Navigation Link

The Visual UpTime Select web interface includes two customizable links at the bottom of its navigation
frame. You can configure this link to point to any web resource, such as a web-based trouble-ticketing
application.
Note
All Visual UpTime Select web application users connecting to this web server will see the same link.
The setting is stored on the web servers primary server and affects all web servers that share that
primary server. If you have multiple web servers with different primary servers, you must configure
the link separately on each.
166

Licensing FAQs
To edit the custom navigation link:
1 Log in to the web server. For more information, see Log
2
Click Configure Global Options. The Configure Global Options page appears (see Figure 51).
In URL1, enter the URL that you want to be the destination of the link.
In URL1 Name, enter the link text as you want it to appear in the Visual UpTime Select user interface.
In URL1 Description, enter a brief description of the web resource that the link will load. This
description will appear when users move the mouse pointer over the link.
Repeat for URL2 if you want a second link.
Click Apply.
Configuring the Service Summary Auto-Refresh Interval

Service Summary automatically refreshes itself to indicate the most current status of network elements
and events reported from ASEs. Visual UpTime Select users can adjust the delay of this periodic autorefresh. However, if the delay is set too low, system performance can suffer. As an administrator, you can
specify a minimum delay to prevent frequent refreshes from affecting system performance.
Note
All Visual UpTime Select users connecting to this web server will be restricted to the refresh interval
you specify. The setting is stored on the web servers primary server and affects all web servers that
share that primary server. If you have multiple web servers with different primary servers, you must
configure the refresh interval separately on each.
To set the minimum auto-refresh interval for Service Summary:
1 Log in to the web server. For more information, see Log
2
In Minimum refresh interval for Service Summary Status, enter the minimum number of seconds
to wait before Service Summary attempts to refresh. The default setting is 300 seconds (5 minutes).
The minimum is 10 seconds.
Click Apply.
Providing Additional Licensing Information

When Visual UpTime Select web application users attempt to access a feature that has not been
licensed, an error message is shown. As an administrator, you can specify additional text to include with
this message, such as contact information.
Note
All Visual UpTime Select users connecting to this web server will see the additional text you specify
in their licensing information messages. The setting is stored on the web servers primary server
and affects all web servers that share that primary server. If you have multiple web servers with
167

User Guide
different primary servers, you must configure the additional licensing information text separately on
each.
To specify additional text for licensing messages:
1
In Additional Licensing Information Text, enter the text that you want to include with licensing
messages.
Click Apply.
Accessing the Web Portal from Other

Software
Other applications can open the VPM web portal or the stand-alone Visual UpTime Select web
applications by launching its URL in a web browser. You can also create a separate web page that
launches directly to specific pages. Using this approach, you can specify:
The username and password to use when logging in.
The domain to use when logging in.
When launching stand-alone Visual UpTime Select, you can also specify:
Which application (Service Summary, Application Summary, or Troubleshooting) to display.
Which network element (network, site, circuit, or port) to select.
The web page that you create must include a Form element. The Form must:
Use the POST method.
Submit its values to either of the following URLs:
For the VPM web portal:
http://server/Portal/URLLaunch/URLLaunch.aspx
For stand-alone Visual UpTime Select web applications:
http://server/webApplicationClient/URLLaunch/URLLaunch.aspx
Note: Server is the hostname or IP address of the web server where you want to log in.
Include the parameters and values. For available parameters for the web portal, see
HTTP POST Parameters for Launching the Web Portal . For Visual UpTime Select, see Table 37.
168

Licensing FAQs
Table 36 HTTP POST Parameters for Launching the Web Portal
Parameter
Description
username
The login name of the VPM user account to use when logging in.
password
The password of the user account specified in username.
domainname
The name of the VPM domain to use.
Table 37 HTTP POST Parameters for Launching Visual UpTime Select
Parameter
Description
username
The login name of the VPM user account to use when logging in.
password
The password of the user account specified in username.
domainname
The name of the VPM domain to use.
appid
The application you want to display. Use a value of

troubleshooting to launch the Troubleshooting application. Any
other value launches Service Summary.
networkname
The name of the network you want to select. (This parameter

cannot be used with aseipaddress.)
sitename
The name of the site you want to select. You must also specify a
networkname.
portname
The name of the port you want to select. You must also specify a
networkname and sitename.
aseipaddress
The IP address of the ASE you want to select. (This parameter

cannot be used with networkname.)
ifindex
The interface index of the interface you want to select. The value
must be a positive integer. You must also specify an
aseipaddress.
eventindex
The event index of the event you want to display. The value must
be a positive integer.
pvcname
The name of the PVC you want to display. (This parameter

cannot be used with dlci or vpi.)
dlci
The DLCI number of the frame relay or HDLC circuit you want to
display. The value must be a positive integer. (This parameter
cannot be used with pvcname or vpi.)
169

User Guide
vpi
The VPI number of the ATM circuit you want to display. The
value must be a positive integer. (This parameter cannot be used
with pvcname or dlci.)
vci
The VCI number of the ATM circuit you want to display. The
value must be a positive integer. You must also specify a vpi.
layer
The layer you want to select in the Troubleshooting application.

The value must be physical, upper, or port.
You must also specify an appid of troubleshooting. (This
parameter does not apply to Service Summary.)
For example, your web page might include HTML markup like this:
<form id="LaunchForm" method="post"
action="http://host/WebApplicationClient/URLLaunch/URLLaunch.aspx">
<input type="hidden" name="username" value="webuser">
<input type="hidden" name="password" value="p455w012d">
<input type="hidden" name="domainname" value="MyDomain">
</form>
And JavaScript to submit the form instantly:
<script language="JavaScript"><!-document.forms[0].submit();
// --></script>
170

Licensing FAQs
9. Frequently Asked Questions
This chapter covers Frequently Asked Questions (FAQs) that may come up when administering a Visual
Performance Manager server. Please consult this appendix before calling your Visual Performance
Manager vendors technical support.
System Configuration and Operation

Q: What must I do so that my Visual Performance Manager vendors technical support personnel can
access my server to troubleshoot problems?
A: For users who can provide Internet access or are running Windows Terminal Server, contact TAC for
information on how to set up access.
If you have a server with pcAnywhere on it, (1) connect a phone line to the servers modem port; (2)
provide the technical support personnel with the phone number; and (3) launch pcAnywhere. To set
pcAnywhere to wait for a call, click Be a host, then double-click the modem icon. When the technical
support personnel are finished with the troubleshooting task, close pcAnywhere and disconnect the
phone line.
Q: If I have an enhancement to the Visual Performance Manager application that I believe would be
beneficial, where do I send the requests?
A: Customers are encouraged to submit enhancements. Please send all feature requests to your Fluke
Networks Sales Representative or Systems Engineer. The Product Management Team will review
your request and consult the parties necessary to determine whether to include your feature request
in an upcoming release.
Q: If my Visual Performance Manager system elements (ASEs, servers, and clients) are located in
different time zones, which time zone should I set each ASE to?
A: ASEs, servers, and clients work together to assure that the statistics collected are stored with the
proper time reference. There is no need to set clocks on the ASEs. However, each server and client
should be set to its own local time zone so that data you display on the server or client is relative to
your viewing location.
The clients local time determines the time shown for all events, conversations, traffic captures,
troubleshooting data, and Web-based report data.
171

User Guide
Some tasks scheduled from a client (such as data collection, database maintenance, and scheduled
report group generation) actually occur on the server and their results are shown in log files on the
server. Consequently, enter the servers time in the clients corresponding dialog when scheduling
these tasks.
Q: We are a service provider upgrading to Visual Performance Manager with AppFlows and VoIP. Will
this affect our existing PVC sizing and database performance?
A: The Select AppFlows feature adds a significant amount of management data on ports where the
feature is active.
Application Flows also increases the amount of data stored in the database and can increase the
length of time to complete nightly data collection up to 25 percent. If you are upgrading Visual
Performance Manager server software on an older server machine, verify that the computer meets
the server hardware requirements (listed in the Software Installation Guide). Because Application
Flows increases the amount of data collected and stored by the server, it is recommended that you
meet the dual-processor server requirements.
After upgrading, if nightly data collection is an issue for application flows data, contact TAC for
information about modifications you can make on the Visual Performance Manager server to improve
performance.
Q: I have a system that has been running for some time. I recently reset the default ASE data collection
time, but data collection is continuing at the same time. Why?
A: You can include existing ASEs in the newly assigned data collection time. In the Domain Options tab
in Server Administration, select the Apply default time to existing ASEs to apply the new default time
to all new and existing ASEs on the 24-hour data collection schedule.
Q: How can I make sure that my scheduled database maintenance is properly coordinated with ASE
data collection?
A: For the most efficient processing of data, database maintenance should start as soon as data
collection completes. To accomplish that, simply schedule database maintenance to occur at least
one minute after data collection is scheduled to start. Data collection will delay database maintenance
until all scheduled collection for the domain has completed.
Server Administration FAQs

Q: What should I do if Server Administration indicates that the short-term or long-term database is
approaching the size of allocated database space?
A: First, follow the database maintenance procedures as explained in Chapter 10, Maintaining the
Databases. If a database cannot be expanded any more due to lack of available hard drive space,
contact your Visual Performance Manager vendors technical support.
172

Licensing FAQs
Q: In Server Administrator, I renamed Domain1 to Domain2. I then tried to create another domain with
the name Domain1. Why did this cause an error message?
A: You first have to create the new domain with a unique name before renaming it. Create a new domain
with the name Domain3 and then rename it to Domain1.
Q: From Remote Server Administration, when I select Help I get a message saying the help files are not
in the folder location. Why?
A: Remote Server Administration was installed using the Compact option, which does not include Help.
To include Help, use the Complete option.
ASE on Multiple Servers

Q: Can I add an ASE on more than one Visual Performance Manager server?
A: You can. However, you will need to take the following actions to the following conditions apply:
Make sure the ASE has appropriate separate feature licenses on each server.
Use the same version of Visual Performance Manager on the servers. If they are not, the ASEs
image must not be for a newer version that the older server's version.
Each server performs data collection. Therefore, set up the communications bandwidth to the
ASE to allow for double collection.
Set the same community strings for each domain with the ASE in both Visual Performance
Manager systems.
Each server must be able to access the IP address of the ASE.
ASE subnets must match.
Define the same IP Class of Service settings in the relevant domain on each server.
Define the same custom applications in the relevant domain on each server. The most recent
update in either domain will be pushed to the ASE automatically, so if the servers do not match,
unexpected results may occur.
Define the same ten applications monitored by the ASE in both systems. Changes from one
server affect the statistics tracked for both servers.
ASEs that are paired with the duplicated ASE to define circuits must also be duplicated or those
circuits will not be available in both ASEs.
The ASE will process threshold alarms set from either server and traps will be sent to both
servers. Therefore, traps can be received by a server for threshold alarms not set by that server.
If an ASE image is to be uploaded, perform data collection on both servers prior to the update
and reboot to minimize loss of data.
173

User Guide
Licensing FAQs
Q: How can I view licensing information for the Visual Performance Manager server?
A: The License Summary report shows license data for the server and all domains on the server. For
more information, see Licenses Report.
Q: How do I know what licensing mode is active?
A: In Server Administration, select a server. On the Server Status page, in Server Information, for
Domain Licensing, you will see the term: Flexible, Fixed, or None. Domain-fixed and domainflexible licensing modes are for service providers only. For more information on these licensing
modes, see Configuring Licenses.
Server ID
Q: Where does the server ID come from?
A: The server ID is the MAC address of the LAN adapter. The server picks the first one of the eligible
MAC addresses. If you re-configure the server so that one Ethernet adapter is disabled, the server
may begin using a new ID, which would invalidate its license keys.
Q: What happens with laptops and docking stations?
A: If a laptop uses one Ethernet adapter when operating as a disconnected laptop, and another adapter
when connected to a docking station, the server ID will be different depending on whether the laptop
is docked or not. Thus, licenses may be valid only in one mode or the other.
Q: How do I move my licenses to another server?
A: A backup license is available for temporary moves. For permanent moves to a new server, contact
Fluke Networks sales.
Upgrade and New System Questions

Q: What licenses do I get on a new Visual Performance Manager system, and for how long are these
active?
A: All features are available on your system for 30 days for up to 10,000 ASEs. This allows you ample
time to set up permanent licenses and to try out features you did not purchase.
174

Licensing FAQs
Q: What licenses do I get on an upgrade Visual Performance Manager system?
A: All licensed features available on your previous version of Visual Performance Manager are available
on the upgrade.
Q: What kinds of warnings are given during this initial grace period?
A: A user adding an ASE within five days of expiration of the license will get an expiration warning when
the ASE has been successfully added. The Server Administration application shows expiration dates
for licenses. Icons turn yellow within three days of expiration and include Server license expires
soon and the expiration date in summary information. There is no warning when logging on to the
PAC or Web portal.
Q: What happens if my default license expires before I add a permanent license key?
A: All domains become Service Summary-only.
ASE Limits
Q: What is the ASE limit if I have a power-user license and a per-server license?
A: Whichever ASE limit is smaller. For example, if you have a per-server license for 1000 and a power
user license for 1500 ASEs, the servers limit is 1000, and that is shown in Server Administration.
Q: Can I enter a license key for fewer ASEs than I already have?
A: Only if features are disabled. To enable features you will need at least as many feature licenses as
ASEs.
Q: Do inactive ASEs count against the ASE limit?
A: No. If you make an inactive ASE active again, the server checks that the server has not reached its
ASE limit.
Q: How can I restrict the number of ASEs in a specific domain?
A: In domain-fixed or flexible licensing modes you can control the feature sets of individual domains. For
more information, see Managing Licenses for a Domain. In default licensing mode, all domains have
all features available on the server.
175

User Guide
Evaluation and Temporary Licenses

Q: How do you change an ASE evaluation license to a permanent ASE that uses feature licenses
without losing data on ASE?
A: In Network Configuration on the PAC, edit the ASE, clear Evaluation ASE and click OK. For more
information, see Chapter 2, Network Configuration, in the PAC User Guide.
Q: If I want to evaluate a third-party device, what type of licenses do I need?
A: To evaluate the device, you need only an ASE evaluation license. To permanently use the device,
you need an agent license and any feature licenses active in the domain.
Q: How do I check my expiration dates on temporary licenses?
A: Expiration dates are shown in their respective tabs in server licensing.
License Key Backup and Recovery

Q: Are license keys stored in the database?
A: Yes, feature licenses and agent licenses are all in the database. The registry is not used to hold
license keys.
Q: How do I restore license keys?
A: If you restore a backed up database, it includes the license keys. Therefore, you do not need to keep
them separately, as long as you actually have current backups.
Power Users
Q: What defines a power user?
A: A power user is a user account that is associated with all domains on the server. Power users can
access all domains and, as a result, they do not need explicit associations as other users do. For
more information, see Designating Power Users.
Q: Must I have a power user license?
A: No. If all users should see the same features in whatever domains they can access, then you only
need a per-server license for the features. You only need a power user license if some users should
have access to additional features beyond what the standard user gets.
176

Licensing FAQs
Sharing Licenses
Q: I want to manage an ASE from multiple servers. Do I need a license for each server?
A: Yes, you need a feature license for each server with capacity for an additional ASE. Visual ASEs do
not require an agent license. A partner device would require an agent license of the proper license
class on each server.
Domain-Fixed and Flexible Licensing

Q: How can I deactivate a feature in one domain and keep it active in all other domains on the server?
A: In domain licensing mode, when managing domains with unique feature sets, you can either turn off a
feature server-wide and activate it only on specific domains, or you can leave it available server-wide
and turn it off on specific domains. When a feature is available server-wide, all new domains have the
feature active by default. When you deactivate a feature on one domain, new domains will not have
the feature active by default.
Q: Can I rename a domain and keep the licenses?
A: It depends on your licensing mode. For more information, see Table 35.
Q: In domain licensing mode, can I add feature evaluation license keys server-wide instead of only at
individual domains?
A: No. The key is domain independent when it is generated, but it may be used only once, in any
domain. See Adding a Feature Evaluation License.
Backup Server Licensing

Q: Can a server be the backup for multiple primary servers?
A: Yes, as long as it is the backup for only one at a time, and you have the backup license key for each
pair. For example, if you have three active servers and one backup, you need three backup license
keys, one for each active server and the backup server. To activate the backup server, load the data
for the proper active server and enter the backup license for that combination.
Q: Why are backup servers restricted from adding ASEs?
A: To prevent the primary and backup servers from both operating as full systems with only one set of
licenses.
177

User Guide
Restoring Databases
Q: Can I restore my databases to a server other than the original server?
178
A: For information about performing this operation, see TAC. Because license keys are issued for a
specific server, you will need to obtain a new set of license keys for the new server. If this restoration
is performed improperly, licenses will be invalid and features will not work.

User Guide
10. Maintaining the Databases
VPM stores data about your network performance in short-term and long-term databases. (See Data
Storage for a description of both databases.) This chapter describes how to maintain these databases,
making the data available for reports and ensuring the smooth operation of the VPM system. Topics
include:
Scheduling data collections and database maintenanceCollect network performance data from
ASEs and set database maintenance times on the server.
Moving domains to a new serverDisable domains before migrating and reset destination addresses
and enable domains after migration.
Backing up and restoring databasesBack up the VPM databases to archive media such as a
backup tape drive and restore them from a backup using SQL Server utilities (outside of VPM).
Note
Make sure that your SQL Server license is accurate and valid. Each VPM user requires a user CAL
(Client Access License). Depending on your VPM usage, you may need to purchase additional user
CALs or a per-processor license. For more information about SQL Server licensing, see:
http://www.microsoft.com/sql/howtobuy/default.mspx
Domain administrators can perform database maintenance for a specific domain. If you are an
administrator for the entire server, you should also familiarize yourself with that information. See
Performing Database Maintenance for a Domain. See Chapter 2, Server Overview for a description of
the component databases in the network performance database.
Scheduling Data Collection and Database

Maintenance
The ASE data collection, database maintenance, database backup administrative tasks affect each other.
Perform data maintenance actions in the following sequence:
1
Collect ASE dataDo this first to make sure the short-term database contains the most recent
network performance data available. (See Chapter 5, Domain Functions, in the PAC User Guide.)
180
Maintaining the Databases

Scheduling Data Collection and Database Maintenance
2
Perform database maintenanceDo this second to make sure the long-term database contains the
most recent network performance data available and the short-term database is in the best possible
condition. (See Error! Reference source not found.)
Note
To make sure that scheduled database maintenance is properly coordinated with ASE data
collection, schedule database maintenance to occur at least one minute after data collection is
scheduled to start. Data collection will delay database maintenance until all scheduled collection for
the domain has completed.
Back up the databasesDo this last to make sure the backup contains the most recent data available
and that the databases are in good condition. (See Error! Reference source not found.)
Warning
If you initiate on-demand ASE data collection and then initiate on-demand database
maintenance, VPM will queue these actions properlyyou do not have to wait for data
collection to complete before initiating database maintenance. Do not initiate or schedule
database backup during ASE data collection or database maintenance. Do not initiate ASE
data collection or database maintenance during database backup. Otherwise, the backup
may contain inconsistent data.
About the Databases

VPM stores data about your network performance in a short-term database (VUpTime), along-term
database (VUpTimeLT), and an NPM database (VUpTimeNF). (See Data Storage for a description of
both databases.)
At any time, you can perform database maintenance that:
Rolls the content of the short-term database into the long-term database.
Verifies that all data from the short-term database is accounted for in the long-term database, with no
duplication.
Trims the short-term database to a maximum of 14 days of data.
You can schedule daily database maintenance from Server Administration or the PAC. The daily
scheduled database maintenance performs the same tasks listed above and lets you delete obsolete data
from the long-term database. You also can schedule monthly database maintenance, which trims the
long-term database to a specified number of weeks. See Scheduling Monthly Database Maintenance for
more information.
Warning
Do not perform database maintenance if database backup is in progress.
181

User Guide
Collecting ASE Data in All Domains

You can perform on-demand data collection for all domains on the server at once. On-demand data
collection does not affect the daily scheduled data collection.
Note
Always collect ASE data before updating ASE software.
To perform on-demand ASE data collection for all domains:
1
In Server Administration, select the server.
Select Action > Collect Data. A message states: Data collection was requested. It will
proceed in the background now.
Click OK.
Performing Database Maintenance in All Domains

You can perform on-demand database maintenance for all domains on the server at once. On-demand
database maintenance does not affect scheduled maintenance.
To perform on-demand ASE data collection:
1
In Server Administration, select the server.
Select Action > DB Maintenance. A message states: Data collection was requested. It
will proceed in the background now.
Click OK.
Checking the Database Maintenance Log

You can use Server Administration to view entries from the database maintenance log. The log indicates
the domain, start time, and total running time of each database maintenance run for all domains on the
server. Sort the list by the Start Time column to see the entries in chronological order, or sort by Domain
Name to group the entries by domain.
182

Scheduling Data Collection and Database Maintenance
Figure 52 Server AdministrationDatabase Maintenance Log
To view database maintenance log entries:

1
In the left pane of Server Administration, expand the server and log in. For more information, see
Logging in to Server Administration.
Select DB Maintenance Log. Server Administration shows a list of log entries.
Resolving Database Space Issues

Short-term and long-term database space allocation is set at the factory based on the anticipated number
of ASEs in your network. Once VPM hardware and software is installed and configured, the server begins
collecting data from ASEs and accumulating that data in the short-term and long-term databases.
Server Administration indicates when the short-term or long-term database sizes approach the total
allocated space. See Viewing Detailed Server Status.
The short-term database accumulates network data continually with each daily or on-demand ASE data
collection. It can become too large if daily maintenance does not occurfor instance, if the server is down
when daily maintenance is scheduled. To correct this, perform on-demand database maintenance. See
Performing Database Maintenance in All Domains
The long-term database accumulates network data continually with each daily or on-demand
maintenance operation. It can become too large when:
Monthly maintenance does not occurThis can happen if, for instance, the server is down when
monthly maintenance is scheduled. To correct this, set the Monthly Maintenance Day to the current
day and set Daily Maintenance Time to the soonest, most convenient hour. (Performing on-demand
maintenance will not trigger monthly maintenance.) See Performing Database Maintenance for a
Domain.
The number of weeks of data retained in the database is too large for the servers capacityTo
correct this, decrease the number in the Keep ___ Weeks of Reporting option and repeat the daily
and monthly maintenance as described in the previous item.
183

User Guide
The database is retaining a large volume of obsolete data that should be trimmedTo correct this,
select Remove deleted network elements... and perform on-demand database maintenance. If
either database is still too large, contact your vendors technical support.
If your resources are still inadequate for your needs, consider migrating the domain to another server
computer. In some cases, the database size can be expanded (either manually or automatically) if your
server has additional storage capacity. Contact your VPM vendors technical support for assistance.
Moving a Domain to a Different Server

You can transfer one or more domains from one server to another. This flexibility is important if server
database storage space reaches capacity in one server computer or if efficiency requires domain
relocation from an over-utilized server to an under-utilized server.
To properly migrate domains, complete the following tasks:
Disable and enable domainsFrom the Server Administration tool, disable domains before moving
them to another server computer. First take the domain out of service prior to migrating it (copying it
to a new server), and then delete the domain on the originating server. See Enabling and Disabling
Domains.
Reset event destination addressesFrom the PAC, after you have physically relocated and enabled
the domain databases on the new server, reset the event destination addresses for ASEs in the
migrated domain from the IP address of the old server to the IP address of the new server. This
prevents the ASEs from sending events to their old server instead of their new one. See Chapter 5,
Domain Function, in the PAC User Guide.
To physically move SQL Server data from one server to another, use SQL Server tools (for example, the
Data Transformation Services, accessed from the SQL Server Management Studio). For complete
instructions and advice on migrating domains between servers, contact TAC (See Technical Support).
Note
Scheduled reports are not migrated with the domain settings. All users who had created scheduled
reports must recreate them after domain migration.
Backing Up and Restoring Databases

You can schedule a frequent backup of server databases (daily backup is recommended). Include the
following databases in the backup (the first two constitute the network performance database):
VUpTimeVPM short term database
VUpTimeLTVPM long term database
VUpTimeNF NPM database
VUpTimeDCApplication Performance Management database
184

VAdminVPM server configuration database
fnet_portalWeb portal database
ReportServerReporting Services database
ReportServerTempDBReporting Services temporary database
masterSQL Server master category of users
msdbjobs and alerts scheduled in SQL Server
SQL Server automatically performs database consistency checks before launching the backup procedure.
Note
When you schedule a database backup, the SQL Server Agent (MSSQLSERVER) service must be
started and set to automatic.
Warning
Make sure that a scheduled backup does not begin until the server has completed scheduled
ASE data collection and database maintenance. (See Sche)
Warning
When backing up and restoring databases, notify all Web portal and PAC users that the
server will be shut down.
To back up SQL databases on the VPM server:
1
From the server, open SQL Server Management Studio and select a database to back up:
fnet_portal, master, msdb, ReportServer, ReportServerTempDB, VAdmin, VUpTime,
VUpTimeLT, VUpTimeNF, or VUpTimeDC. Right-click the database name and select Tasks >
Backup. Determine the name and location and perform the database backup.
Repeat step 1 for each database.
To restore SQL databases on the VPM server:

1
Shut down the following services:

Visual Performance Manager Server
Visual UpTime Select Web Application
All SQL Server services except the SQL Server (MSSQL Server) service.
IIS Admin
World Wide Web Publishing
For more information, see Starting and Stopping Services.
185

User Guide
2
In SQL Server Management Studio, select any database except the master database. Right-click and
select Tasks > Restore > Database.
To restore from backup select From Device and, under General, select the database file from
the backup location.
To overwrite the existing database file, under Options, select Overwrite.
Under Select the backup sets to restore, check the database.
Click OK to begin the restore. A message indicates that the restore has successfully completed.
Repeat step 2 for each database except the master database.
Place SQL Server into single-user mode and restore the master database. For more information
about setting SQL Server into single-user mode, see the TAC Knowledge Base.
Warning
SQL Server must be placed in single-user mode when restoring the master database.
a
From the Services window, stop the SQL Server (MS SQL Server) service and close SQL
Server Management Studio.
From the Windows task bar, select Start > Run and type services.msc. Click OK.
Open a DOS window and go to the directory on the drive where SQL Server is installed:
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn
Run the command sqlservr.exe -m to start a server instance in single-user mode that is
required. The following message is shown:
SQL Server started in single-user mode ...
Open a second DOS window and go to the directory on the drive where SQL Server is installed:
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn
Type the command sqlcmd -S <server name> to start the sqlcmd utility.
For line 1>, type RESTORE DATABASE master FROM DISK = '<location of
master>\master.bak'
For line 2>, type GO. A successful restore message is shown.

After the master database is restored, SQL Server shows the message Connection broken.
This informational message requires no corrective action.
From the Services window, restart the SQL Server (MSSQL Server) service so that SQL Server
restarts in multi-user mode and uses the newly restored master database.
Restart all services that were previously stopped.
For detailed procedures on backing up and restoring SQL Server databases, see:
http://msdn.microsoft.com/en-us/library/ms177429.aspx
186

Using Backup Tapes

For backup to tape, a 14-day rotation of daily backup tapes is recommended, with one set of tapes stored
off site. Discard old tapes once a year and begin using new tapes.
Windows Emergency Repair Disks

As part of routine maintenance, make sure that you have Windows emergency repair disks available.
To create Windows emergency repair disks:
1
Click Start > Programs > Accessories > System Tools, and then click Backup.
On the Welcome tab, click Emergency Repair Disk.
Follow the instructions that appear on your screen.
Label the disks and store them in a safe location for emergency use.
187
A. Open Ports for Firewall

Configuration
When using VPM with firewalls in place between VPM components, you must configure the firewall
software to allow communication on the ports indicated in Firewall Port Settings.
Note:
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 VPM server and APAs. By default
these ports are 80, 443, and 22 but they can be reconfigured on the APA.
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.
Table 38 Firewall Port Settings
Settings Between...
Application
Layer 4
Port
Source
Destination
Web Client and Server
HTTP
TCP
80
Web
server
Web Client and standalone Web Server
HTTP
TCP
80
Web
Web server
PAC and Server
Portmapper
TCP
111
PAC
server
RPC
TCP
<selected port> PAC
server
1024-65535
server
Proxied SNMP and UDP

TFTP1
PAC
Open Ports for Firewall Configuration
Settings Between...
ASE and Server
ASE and Client
APA and Server or standalone Web Server
APA and Client
Application
Layer 4
Port
Source
Destination
PAC Notifications2
UDP
1024-65535
server
PAC
SNMP
UDP
161
server
ASE
SNMP Traps
UDP
162
ASE
server
TFTP3
UDP
69
server
ASE
SSL
TCP
2359
server
ASE
Telnet4
TCP
23
client
ASE
SSH4
TCP
22
Web
ASE
Non-secure TCP
TCP
80
server
APA
Secure TCP
TCP
443
server
APA
SSH
TCP
22
client
APA
Web Administration TCP
80
client
APA
TCP
NPA port
configured for
Web access
server
NPA
NTP Time
Synchronization
UDP
123
Internet time
server
server
SQL Server
TCP
1433
Remote Server server

Administration
PC
Microsoft RPC
endpoint mapper
TCP
135
NPA and Server or standalone Web Server5
Remote Server
Administration and Server
Server and stand-alone

Web Server
Microsoft RPC over TCP

port numbers
returned by
endpoint mapper6
<selected
ports>
Proxied SNMP and UDP

TFTP1
1024-65535
Microsoft RPC
endpoint mapper
135
TCP
Web server
server
189

User Guide
Settings Between...
Application
Layer 4
Port
Microsoft RPC over TCP

port numbers
returned by
endpoint mapper5
<selected
ports>
SQL Server
TCP
1433
.NET Remoting
TCP
8086
WCF Services
TCP
8005
Source
Destination
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.
4
ASEs support SSH or Telnet connectivity, but not both at the same time.
To use HTTPS for all VPM server to NPA communication, use port 443 or 8443.
You can configure port numbers for RPC via registry settings. For more information, see the TAC Knowledge Base.
190
Reestablish Reporting on a Renamed Server
B. Reestablish Reporting on a
Renamed Server
Renaming a VPM server affects the communication between SQL Reporting Services and the server.
Therefore, before renaming a server, first verify that scheduled and unscheduled reports are successfully
running on the server. Once you have renamed a VPM server, take the following steps to make sure that
reports will run on the server.
Note:
You must know the sa user password for SQL Server (default is VPM@dmin1) and the password for
the Windows vuptime user (default is visual). If a user other than vuptime will be used for Reporting
Services configuration, you must know that user password.
Other computers that refer to this computer by name may need to be refreshed.
To re-establish reporting on a renamed server:
1
Rename the VPM server and restart the machine.
Stop the Visual Performance Manager Server and Visual UpTime Select Web Application services.
Open SQL Server Management Studio. Connect using the new server name and the sa account.
Use the master database.
Execute the following query:

Select @@servername
The former name of the server is shown.
Execute the following query to update @@servername:

sp_dropserver '<old_name>'
GO
sp_addserver '<new_name>', local
GO
Close SQL Server Management Studio and restart the SQL Server (MSSQLSERVER) service.
Open SQL Server Management Studio and execute the following query
Select @@servername
191

User Guide
The new name of the server is shown.
To reconfigure the report server:
1
Start the Reporting Services Configuration tool and connect to the report server that uses the
ReportServer database on the renamed server.
Open the Database Setup page in the left panel.
In Server Name, type or select the new SQL Server name and click Connect. (Use SQL Server
Account credentials and enter the user name sa and its password in the SQL Server Connection
dialog.)
Click Apply. (Use SQL Server Account credentials and enter the user name sa and its password in
the dialog.) Exit the panel.
Run the VPM server prerequisite installation tool located on the VPM CD. From Windows Explorer,
navigate to the CD drive ServicePacks folder and open VisualPerformanceManagerPrerequisite.exe. This will reconfigure SQL Server Reporting Services for the server.
or
To manually reconfigure SQL Server Reporting Services for the VPM server, select Start > Run to
open a command prompt and execute the following two commands:
cmd> rsconfig -e -m localhost -s localhost -d ReportServer -a Windows u <NewMachineName>\vuptime -p <password>
cmd> rsconfig -e -m localhost -s localhost -d ReportServerTempDB -a
Windows -u <NewMachineName>\vuptime -p <password>
Substitute the proper login, if the default vuptime is not correct.
When the process is complete, reboot the server or restart the two services stopped earlier. Check
that reports, including scheduled reports, execute properly.
192
Supported Standards
C. Supported Standards
Visual Performance Manager complies with the following standard Simple Network Management Protocol
(SNMP) platforms or methods:
Standard MIB SupportVisual Performance Manager complies with RFCs 1213 (MIB II), 1406 (DS1),
1315 (frame relay DTE), and 1757 (RMON), which provide configuration and statistical information.
Data from these Management Information Bases (MIBs) can be gathered directly from Visual ASEs
through any SNMP management system.
SNMP Trap ExportAll events generated by Visual ASEs may be sent to other managers that add
details such as source network, access line, PVC name, and event descriptions. This export
capability avoids the need to compile the Fluke Networks MIB onto other systems and simplifies
integration with existing event and alarm management systems.
Table 39 shows supported RFCs and MIBs.
Table 39 Supported RFCs and MIBs (continued)
RFC or MIB
Supported Group
MIB II (RFC 1213)
System group
Interfaces group
Transmission group
(see DS1 MIB support and Frame Relay DTE MIB support below)
TCP group
IP group
ICMP group
UDP group
SNMP group
Frame Relay DTE MIB

(RFC 1315)
DLCMI group
Circuit group
Error group
193

User Guide
Table 39 Supported RFCs and MIBs (continued)
RFC or MIB
Supported Group
DS1 MIB
Configuration group
Fractional group for configuration
NearEnd Stat group
DDS MIB
Fluke Networks has implemented a DDS statistics group as a public
MIB.
RMON (RFC 1757)
(RMON is a LAN
monitoring standard.
However, these groups,
which are relevant to
WAN monitoring, have
been implemented. The
remaining groups deal
specifically with LAN
statistics and are not
relevant to WAN
analysis.)
3 - Alarmsallows the setting of thresholds on various LAN traffic

parameters to generate events which a probe will count or use to
generate SNMP events.
7 - Filtersused in conjunction with packet capture, this group
provides a generic filter capability. It allows logical combinations of
filters and maintains counts of each match while filtering packets
matching the criteria into the packet capture buffer.
8 - Packet Captureallows the creation of capture buffers and
controls how the buffers are filled and how much of each packet is
stored.
9 - Eventsallows the creation of log entries or the generation of
SNMP events based on thresholds, counter values, or trigger
conditions.
A Visual UpTime Select event has an enterprise address of visual (1.3.6.1.4.1.1246) and an event type of
7. The event will contain ten variables that hold the forwarded event information. Table 40 lists these
variables and their associated OIDs.
Table 40 Fluke Networks SNMP Event Variables and OIDs
OID
SNMP Event Variable
1.3.6.1.4.1.1246.4.6.1
vnForwardTrapEventIndex
1.3.6.1.4.1.1246.4.6.2
vnForwardTrapElementName
1.3.6.1.4.1.1246.4.6.3
vnForwardTrapEventDesc
1.3.6.1.4.1.1246.4.6.4
vnForwardTrapDataTime
1.3.6.1.4.1.1246.4.6.5
vnForwardTrapTime
1.3.6.1.4.1.1246.4.6.6
vnForwardTrapPriority
.1.3.6.1.4.1.1246.4.6.7
vnForwardOriginalEnterprise
194
Supported Standards
Table 40 Fluke Networks SNMP Event Variables and OIDs
OID
SNMP Event Variable
.1.3.6.1.4.1.1246.4.6.8
vnForwardOriginatingAgent
.1.3.6.1.4.1.1246.4.6.9
vnForwardOriginalGenericTrap
.1.3.6.1.4.1.1246.4.6.10
vnForwardOriginalSpecificTrap
195

User Guide
Glossary
Click the letter in the table of contents to find terms beginning with that letter.
A
APA (Application Performance Appliance)
Device installed at the data center or other hub sites in an enterprise network that monitors data passing
through core switches. APAs monitor application traffic and measure application performance and usage.
Application
A software program that receives and responds to requests. One application can have multiple
application servers (for example, an organization may deploy e-mail servers on multiple computers). Also,
a single computer can host multiple applications (for example, a Web server and database server can
both be installed on the same computer).
Application flow
A collection of traffic across a network that is exchanged between two hosts for a single application. By
monitoring application flows it is possible to measure application performance and to detect the
application hosts - including clients and servers.
The Visual UpTime AppFlows and AppSummary feature modules monitor IP application flows for
both client/server and peer-to-peer applications running over either TCP or UDP.
Application Response Time

The time required for the application server to begin responding to a clients request. Application
response time can be used to monitor application performance, detect over-utilized servers, and indicate
client experience when used as part of the EURT (end-user response time) measurement.
Application server
A software program that receives and responds to requests for a single client/server application. One
application can have multiple application servers (for example, an organization may deploy e-mail servers
on multiple computers). Also, a single computer can host multiple application servers (for example, a Web
server and database server can both be installed on the same computer).
196
The Visual UpTime AppFlows and AppSummary feature modules automatically discover the servers
for IP applications.
ASE (Analysis Service Element)

Hardware devices connected to a WAN network whose embedded agent software collects application
and network performance data for detailed analysis by the Visual Performance Manager server and
display by clients. ASEs monitor traffic to and from the WAN simultaneously. At least one ASE is located
on each managed network circuit. ASEs can be Visual ASEs produced by Fluke Networks or partner
devices equipped with agent software. See also Visual Performance Ma
B
Burstiness
In the context of a packet network, data that uses bandwidth only sporadically. During pauses, channels
are idle, and no traffic flows across them in either direction. Visual UpTime Troubleshooting examines
burstiness in 1-second granularity.
C
CAR (committed access rate)
Indicates the amount of bandwidth allocated to IP traffic on a port from the customer edge router to the
provider edge router. If CAR is set to 0 in the Network Configuration toolset, then calculations will be
based on line speed.
CIFS
The Common Internet File System is a protocol that lets programs make requests for files and services on
remote computers on the internet.
Client
A host computer that sends out requests for an application.
Client Data Transfer Time

The time required to send the transaction request
Connections
The number of new socket connections established between the client and server.
197

User Guide
CoS (class of service)

On IP networks, different types of traffic can be consolidated and prioritized assigning classes to each
type based on a Error! Reference source not found.. In Visual Performance Manager you can monitor
application usage, top talkers, and SLA data for up to eight IP classes of service.
D
Data Rate
Data Transfer Time

The length of time it takes to transmit a complete response for a unit of data, measured from the initial to
final packet in a response. In Visual Performance Manager, DTT is measured as the average combined
data transfer time of the client request and the server response data.
Data Volume
Device
A network element of some kind.
Data Transfer Time

The length of time it takes to transmit a complete response for a unit of data, measured from the initial to
final packet in a response. In Visual Performance Manager, DTT is measured as the average combined
data transfer time of the client request and the server response data.
DRE
Data Redundancy Elimination is an advanced form of network compression that allows Cisco WAAS to
maintain a database that has been seen previously traversing the network. This information is used to
remove redundant transmission patterns from having to utilize network bandwidth.
E
EPM
EndPoint Mapper is a Cisco WAAS accelerator that allows WAAS to classify MS-RPC traffic flows that
use dynamic ports assigned by a port mapper.
Event
A significant network occurrence that can be reported by the ASE to Visual UpTime or forwarded to
another event management system. You configure ASEs to monitor the network for statistical threshold
and state-change events in the Performance Monitoring toolset on the Visual UpTime PAC.
198
End-user Response Time

The amount of time it takes for a client to receive a response from the server for a transaction request. In
Visual Performance Manager, EURT includes the application response time, data transfer time, and
network round trip time. See Error! Reference source not found. Error! Reference source not found.
and Network Round Trip
H
HTTP
HyperText Transfer Protocol is an application protocol used for transferring files on the World-Wide Web.
Hysteresis
In the Visual UpTime Performance Monitoring tool, indicates how far from a threshold a statistic must
move before the same event can be generated again.
I
IP Connection
The number of new socket connections established between the client and the server. See also Error!
Reference source not found.
IP Piggyback
A setting where an ASE has the same IP address as the router to which it is connected. (The ASE is said
to piggyback on the routers IP address.) The ASE must be assigned special port numbers so that it is
possible to distinguish between messages intended for the router as opposed to messages intended for
the ASE.
Initial Network Round Trip

For TCP/IP networks, initial network round trip is the elapsed time between a TCP SYN/ACK response
packet sent from the server to the client and the resulting TCP ACK packet from the client. It measures
the network transit time plus the time required to establish a TCP session. See also Network Round Trip
L
LinkSafe
Protective bypass relay that causes an inline ASE to maintain the flow of network traffic in the event of an
ASE operational or power failure. All inline probe ASEs feature the Linksafe relay and protective
bypass mechanisms.
199

User Guide
LMIsolate (link management isolate)

An ASE feature that provides emulation of link management messages in the absence of a router or
when the end-user router is down.
LZ
Persistent Lempel-Ziv compression is a standards-based compression with a long-lived, connectionoriented compression history that can be used to further minimize the amount of bandwidth consumed by
a TCP flow.
M
MAPI
Messaging Application Program Interface is an email protocol used extensively by Microsoft Exchange
Server and Outlook clients.
MOS (mean opinion score)

The subjective measurement of the quality of a voice line, scored on a scale of above 0 to 5, with a 5
indicating that speech quality is perfect. The MOS is an average of the numbers for a particular VoIP
codec. Call quality metric algorithms supported in Visual Performance Manager are Listening Quality
MOS (LQ MOS), Conversation Quality MOS (CQ MOS), and Conversation Quality R-Factor.
N
N-tier application
Application program distributed among three or more separate computers in a distributed network. Visual
Performance Manager supports n-tier application monitoring using APAs.
NetFlow
A network protocol for collecting IP traffic information.
NetFlow Tracker
See Network Performance Appliance.
NFS
Network File System is a client/server application that allows a user to access a file on a remote
computer.
NPA
See Network Performance Appliance
200
NPM
See Network Performance Management
Network Performance Appliance (NPA)

Formerly Netflow Tracker. Device with NetFlow Tracker software installed that collects and reports on
NetFlow/IPFIX traffic information from Cisco routers and managed switches, and flow standards from
other vendors.
Network Performance Management (NPM)

VPM feature that provides network-wide views of Netflow data.
Network Round Trip

The time required for an application data packet to travel across the network from a specific source to a
specific destination and for the response to return. This encompasses network transit time with network
element processing as well as TCP delay.
P
PAC (Platform Applicable Client)
Windows-based client software in the Visual Performance Manager client-server architecture. From the
PAC, users configure networks and perform ASE management tasks in a domain.
Panel
A panel is discrete component of a Web portal that has its own content source and behavior and operates
within the portal framework. Each portal view is a combination of one or more panels.
Portal
Also known as Web portal. A Web site or service that offers a broad array of resources and services. The
Visual Performance Manager Web portal allows the user to view data and use data and resources from a
variety of sources and applications.
Promiscuous mode
Refers to the circuit auto-discovery or circuit detection feature of an ASE. This setting is configured in the
Network Configuration toolset on the PAC.
Multi-Protocol frame relay ASEs in promiscuous mode will auto-discover circuits without employing the
LMI polling protocol.
201

User Guide
R
RTD (round trip delay)
The SLA measurement that indicates how long (in milliseconds) it takes for a packet to travel from the
near-end ASE to the far-end ASE on a circuit and back. The measurement calculates only the time the
packet is on the circuit. The turnaround time at the far-end ASE is removed from the measurement.
S
Server
A host computer which receives requests for an application and sends back responses. See also Visual
Performance Manager
Server Connect Time

For TCP/IP networks, server connect time is the elapsed time between a TCP SYN request packet and
the responding TCP SYN/ACK packet. It measures the time required to establish a TCP session.
Because TCP layer requests are usually handled by the operating system kernel, the server connect time
is an indicator of both LAN health and server health.
Server Data Transfer Time

The time required to send the transaction response.
Site
A location on the network. A site can be characterized by one or more IP subnets.
SLA (service level

agreement)
An agreement reached between a WAN service provider and customer that specifies WAN performance
regarding RTD, FDR or DDR, and availability. Visual Performance Manager helps users verify these
service level measurements through reports and Troubleshooting graphs and statistics.
SPAN (switched port analyzer)

Also called port mirroring. A LAN switch feature that enables the switch to select network traffic for
analysis by a network analyzer, such as the Ethernet ASE in SPAN mode.
SSL
Secure Sockets Layer is a protocol for establishing authenticated and encrypted sessions between web
servers and clients.
State-change event
Any of the following network events that ASEs can be configured to report back to the PAC:
202
Link Layer ChangePort (access channel) up or down; circuit endpoint active, inactive, or invalid.
Access Line Signal LossPhysical line up or down.
SNMP Authentication FailureIncorrect SNMP community name is used in attempts to contact the
ASE.
ASE Reboot and Data Collection Poll Failure events are always reported and are not configurable.
T
TCP Connection Reuse
A WAAS acceleration technique. Connection reuse decreases the load time for complex pages or pages
with numerous embedded objects.
TCP Out of Orders

TCP segments have a sequence number that identifies the segment and where it belongs in a data
stream. The sequence number can be used to reorder segments that are received in the wrong order.
TCP Resets
The Reset (RST) bit in the TCP header is designed to allow a device to abort the TCP connection.
TCP Retransmissions
The sending device transmits packets and waits for acknowledgement of receipt. It acknowledgement is
not received in a certain timeframe, the sender resends that packets.
TCP Zero Windows

TCP window size is the amount of information that a machine can receive during a TCP session and still
be able to process the data. As the TCP session is initiated and the server begins sending data, the client
decrements its window size as the buffer fills. At the same time, the client is processing the data and
emptying the buffer. Through TCP ACK frames, the client informs the server of how much memory is
available in the buffer. If the TCP window size reaches zero, the client will not be able to receive any
more data until memory in the buffer becomes available.
TFO
Transport Flow Optimization. Cisco Wide Area Application Services (WAAS) uses a variety of TFO
features to optimize TCP traffic intercepted by WAAS devices. TFO protects communicating clients and
servers from negative WAN conditions, such as bandwidth constraints, packet loss, congestion, and
retransmission.
Total Bytes
Number of bytes sent by the client and server (includes packet header and payload).
203

User Guide
Transaction
An individual request and response exchange for a single application between a specific client and a
specific server. A single application flow can contain multiple transactions.
Transaction type
A classification used to differentiate different transactions. Transaction types include values such as
SELECT, UPDATE, INSERT and DELETE for relational databases and GET and POST for Web
applications.
U
URI
Uniform Resource Identifier is a string of characters used to identify a resource on the internet.
V
A comprehensive system for enabling and monitoring enterprise applications deployed over a network.
Visual Performance Manager (Visual Performance Manager) is comprised of a server that stores and
processes data, Web and Windows-based clients that display data, and ASEshardware devices
deployed on a wide area network to gather application and network performance data.
Visual Performance Manager server

The server software in the Visual Performance Manager client-server architecture. The server stores the
application and network performance database and manages client access to network configuration and
database resources.
W
WAE
Cisco Wide Area Application Engine (WAE) platforms are a portfolio of powerful, scalable network
appliances that host Cisco WAN optimization and application acceleration solutions that enable branchoffice server consolidation and performance improvements for centralized applications and provide
remote users with LAN-like access to applications, storage, and content across the WAN.
Web portal
Browser-based, single access point through which users interact with data in Visual Performance
Manager. 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.
204
Index
***NOTE: Did not change page numbers
A
access
controlling 32
database 37
group permissions 123
reporting capabilities 105
storage of settings 34
user accounts required for server 40
Web server 175
access lines 11, 69, 73
configuring 35
report permissions 105
adding
agent licenses 165
ASE evaluation licenses 163
domains 116
feature licenses
for all domains 160
for single domain 111
LAN Visibility licenses 166
users 133
administrative tasks 35, 86
for web access 171
scheduling data collection 196
Administrators group 122
Adobe Acrobat Reader, Web access to xi
Advanced Users group 122
agent licenses 165
classes 166
Alarm Notifications report 68
alarms
permission to notify 127

User Guide
APA 11, 12
as data source for APM feature 6
configuration permission 126
data gathered by 26
monitoring data flow from 77
on enterprised hosted system 21
viewing number active 62
APAs
data aggregation 24
ports 205
APM Configuration group permission 126
APM Reporting group permission 124
APM Server Summary report 75
Application Flows 10
group permission 127
upgrading to 186
Application Management reports
domain and network 107
port 108
Application Performance Appliance. See APA
Application Performance Management 5
database 201
database and log size 61
reporting permission 124
reports 110
server report 75
Application Performance Manager
turning off feature 97
Application Server Management reports
port 109
Application Summary 9
report publishing options 147
applications 34
server 34
Server Administration 53
Visual UpTime Select
Traffic Capture 10
Troubleshooting 9
VoIP 9
Applications report 68
architecture, Visual UpTime Select 11
ASE Image Updates report 69
ASE Inventory group permission 126
206
ASE Models Summary report 70

ASE Summary report 71
ASEs 11
adding 157
ATM
class of service 151
collecting data 84
communication 90
configuring
on backup server 168
data collection 25, 28
and server 37
and storage 34
default time 34
timing of 196
deleting 157
duplicate 94, 157
evaluation licenses 163
event configuration on the PAC 36
events reported 89
identifying 118
inactive 157
inventory of 36
IP class of service settings 99
LAN Visibility 10, 166
maximum supported 62
MIB support 211
not available message 56
number of active 62
restricting IP addresses in domain 97
secured communications 95
software update permission 126
updating software 35, 56
user access to 126
using on multiple servers 187
associations, domains and users 104
ATM
configuring class of service 151
auditing 45
critical files 46
file access settings 48
registry 49
authentication
enabling LDAP 152
enabling RADIUS 152
207

User Guide
specifying for user account 138
auto-refresh, Service Summary
setting minimum interval 180
B
backing up databases 36, 86, 117, 200
scheduling 201
tapes and tape drive 203
timing of 196
Back-in-Time Troubleshooting
backup
licenses 167
server, converting to primary 168
Basic Users group 122
BGP Exclusion list 94
Burst, group permission 127
C
capabilities, user 124, 126, 127
Capacity Planning reports
port 108
circuits 22
service level metrics for 29
Cisco
NetFlow data 1
router polling 10
class of service
ATM 151
IP 98
collecting ASE data 28, 31, 34
colors
applications shown in report 68
server status 54
community string, SNMP 90, 98
user access to modify 127
complexity rules, password 143
components, Visual UpTime Select 11
Configuration Changes report 72
Configure Services Exclusion List group permission 127
configuring
authentication for ASE communication 90
BGP Exclusion list 94
class of service
208
ATM 151
IP 98
event priorities 89
events 32
firewalls 50
networks 35
report permissions 105
server ports 51
Service Summary settings 172
user and group associations 104
Web Server 174
Connex Configuration Data group permission 124
Connex Performance Data group permission 124
consistency checks, database 201
contacting Fluke Networks xiii
copying
domains 116
users 134
creating
domains 81, 93
user groups 129
users 133
customizing
logo for reports 98
module support 97
Web navigation link 179
D
data
analysis 19
application performance 24, 26
collection 31, 34, 36, 84
and storage 19, 25, 26, 28, 31
by ASEs 28
on-demand 85
permissions 127
scheduled 84
scheduling 196
long-term 32
management in Visual UpTime Select 11
network performance 28
storage 26, 31, 34
database 28, 34
access to 37
209

User Guide
administration, timing 86
available space 61
backing up 36, 86, 200
and restoring 200
before deleting domain 117
timing 196
consistency checks 201
deleting obsolete records 87
log file size 57, 61
setting warning 148
maintenance 25, 36, 85, 86, 197
default time 34
on demand 87
permissions 127
scheduling 87
timing 196
management 32
not available message 56
password 40
restoring 36
securing login 43
size of 35, 61
space issues 56, 199
tape backups 203
default
ASE data collection time 25, 34
data collection time 36
database maintenance time 25, 34, 36
groups 122
licensing mode 156, 158
creating Service Summary domains 94
feature evaluations 162
features 159
long-term database storage 26, 34
server status polling interval 62, 63
user name and password for logons 40
users 128
deleting
domains 117
network elements from the database 87
scheduled reports 67
user groups 130
users 139
Device Overview 7
documentation ix
Domain Administrators group 122
210
domain license mode 156, 158

adding feature evaluations 113
feature evaluation 162
features 159
Domain Management group permission 115, 127
domains 79
adding 116
assigning users to 135
changing logo on reports for 98
configuring IP class of service 98
copying 115, 116
creating 81, 157
Service Summary-only 93
deleting 117, 157, 158
disabling and enabling 116, 200
editing properties 83
entering community string 90
event priorities 89
forwarding events 103
licenses 111
managing 79
users in 130
naming 82
renaming 157
restricting ASE IP addresses 97
Service Summary 158
setting
data collection 84
database maintenance 85
viewing properties 80
duplicate ASEs
and Service Summary domains 94
default licensing 158
E
editing
domain properties 83
server properties on Web server 178
user account passwords 134
user groups 129
emergency repair disk, creating 203
Ethernet ix
LAN Visibility 10
211

User Guide
events
assigning priorities 89
configuring 36
forwarding 103
permission 127
to acknowledge 124
to configure 126
to forward 127
priority levels of 36
server security 45, 46
timing 86
expiration of passwords 142
F
FAQs 36
feature evaluation licenses 162
adding to domain 111, 113
managing on domain 111
feature licenses 159
adding 160
managing on domain 111
firewall
configuring 50
configuring for Web server 176
port settings 52
fnet_portal 201
G
GetServerID.exe 170
H
hardware
APAs 12
NPAs 13
server 19
help xii
HP OpenView 103
HTTP 174
POST parameters for launching Web applications 182
HTTPS
restricting Web server communication to 174
Web server type 19, 171
212
I
IdentifyASE.exe 118
installing
upgrade system 156
Visual UpTime Select 35
IP class of service 98, 99
configuring 98
delete 102
group permission 126, 128
policing threshold 101
setting jitter 100
IP connectivity, server-to-server 56, 58
IP SLA Router Polling 10
polling interval 92
IPFIX 7
IUSR_Name, finding 41
J
jitter
setting for class of service 100
L
LAN Visibility 10, 166
ASEs 10
launching
Remote Server Administration 57
Web applications remotely 181
LDAP authentication
enabling 152
specifying for user account 138
License Administration group permission 126
License Summary report 73
licenses 155, 155170
adding text to Web interface 180
agent 165
ASE evaluation 163
backup 167
deactivating feature expiration warning 148
default mode 158
domain licensing 158
feature 159, 160
key storage 191
LAN Visibility 166
213

User Guide
permission to add 126
licensing modes 60, 156
default 158
domain license options 111
link
configuring custom navigation for Web users 179
link layer
data analysis 28
LinkSafe 219
lockout settings, configuring 144
log files
database maintenance 186, 198
security 45
login
configuring 141
system accounts on server 40
logo on reports
domain 98
server 150
M
master database 201
maximum
password ages and lengths 44
MIBs 211
Microsoft
IIS documentation 174
Product Security Notification Service 33
Windows versions supported xiii
minimum password length, setting 143
monitoring
APA data flow 77
servers 53
msdb database 201
N
names
domain 82
SNMP community 90
NetFlow 7
NetFlow data 1, 13
Network Configuration group permission 126
Network Configuration toolset 20, 36
network performance database. See database.
Network Performance Manager
214

Network Troubleshooting
networks
configuring 35
in domains 79
management and performance 35
stored configuration data 34
NPA 2, 13
communication with server 27
features 7
group permissions 126
reversing interface orientation 149
viewing number active 62
NPA Configuration group permission 126
NPM 7
reports 110
NPM Reporting group permission 124
P
PAC 19
administrative tasks on 35
communication with server 51
configuring
ATM class of service 151
IP class of service 99
data collection from 34
IP address login restrictions 133
restricting user access by IP address 137
Panel Page Management group permission 124
partner devices
and interface differences 32
definition of 32
licenses 165
TFTP authentication 91, 92
passwords 40
assigning 42
configuring
expiration 142
settings 141
text restrictions 143
editing users 134
expiration 142
215

User Guide
for client users 130
history settings 144
lockout policy 44
maximum ages and lengths 44
permission 124
policy 41
verifying 43
restricting text of 143
Web server 174
payload analysis 28
PCAnywhere 33
Performance Monitoring
user access to 126
Performance reports 109
permissions
group 123, 126, 127
user 126
physical layer 4, 71
access circuit data 28
policing threshold 101
Poller Configuration 126
polling
routers 10
server status 62, 63
Service Summary 172
polling interval, routers 92
Port Reporting group permission 124
Portal Administration group permission 127
power users 138, 191
and Service Summary domains 94
creating 133, 160
default licensing 158
designating 138
domain management permission 127
enabling licenses 162
per licensing mode 157
priority
for CoS 99
for events 84, 89, 172
PuTTY 96
PVC
Application Flows impact on 186
216
R
RADIUS authentication, enabling 152
recycled passwords 143
registry 49
specifying port numbers 51
remote management software 33
Remote Server Administration 34, 35, 57, 155
and backup server 169
starting 57
repair disk, creating 203
Report Scheduling group permission 124
reporting
and long-term database 85
APM reports 110
domain and network reports 106
NPM reports 110
permissions 105
port reports 108
site reports 109
reports 10
administrative 6776
deleting 67
scheduling 65
Alarm Notifications 68
APM server summary 75
Applications 68
ASE image updates 69
ASE models 70
ASE summary 71
changing delivery settings 150
changing logo for
domain 98
server 150
configuration changes 72
configuring access to 35, 105
domain and network report categories 106
license summary 73
permissions 105
publishing options 147
server summary 74
users and groups 65, 76
VoIP 9
ReportServer database 201
ReportServerTempDB database 201
217

User Guide
restoring databases 36
RFCs 211
router polling 10
RPC server
setting port number for 51
S
security
ASE communications 95
audit policy 45
log 45
default settings 46
passwords
expiration 142
text restrictions 143
provided by Visual Performance Manager services 32
server 40
software updates on server 33
verifying effective password enforcement 44
server ix, 32
adding 58
adding to Web server list 176
administrative tasks 35
applications 34
backup license for 167
changing logo on reports for 150
communicating with
PAC 51
Web server 174
communication with NPAs 27
configuring
ports 51
data collection and storage 19, 28, 31, 34
defined 19
disabling on Web server list 177
downloading documentation from xii
editing properties for Web server 178
firewall 50
ID 170
identifying active users 64
license expiration 60
licensing 155
list of (on Web Server), sorting 176
logging in 63
218
managing
domains 79
feature licenses 160
monitoring APA data flow to 77
monitoring status 54, 55, 58
details 59
polling status 62, 63
removing 59
removing from Web server list 178
restricting access to 49
security 39
server settings permission 126
setting primary for Web server 177
setting up ASE communication 90
software 17
status color 54
Unreachable message 56
uses of 32
verifying IP connectivity 56
Visual Performance Manager services 31
launching at startup 37
restarting 38
stopped on domain deletion 117
stopping 201
Web server access to 175
Server Administration 34, 35, 36
adding server 58
closing 58
configuring
IP class of service 98
domains
adding feature evaluations 113
assigning event priorities 89
configuring IP class of service 98
copying 116
creating 81
data collection 84
database maintenance 85
deleting 117
forwarding events 103
managing licensing 111
Service Summary 93
viewing 80
219

User Guide
licenses 155
adding feature 160
ASE evaluations 163
backup server 167
LAN Visibility 166
managing agents 165
using evaluations 162
logging in 63
monitoring server status 53, 59
removing server 59
running remotely 57
user groups
creating 129
deleting 130
editing 129
setting permissions 123
viewing members 128
users
assigning to domains 135
copying accounts 134
creating 133
deleting 139
editing passwords 134
Server Health
Poller Configuration 126
Server Settings group permission 126
Server Summary report 74
Service Advisor group permission 127
service level
verification 29
Service Level Management reports 107
Service Summary
configuring auto-refresh interval 180
configuring settings for 172
domains 93, 157, 158
exclusion list permission 127
minimum auto-refresh interval 180
services 31
MSSQLSERVER 37
starting and stopping 37
Visual Performance Manager 57
stopped on domain deletion 117
WWW 43
Share Reports group permission 124
220
Share Reports to Other Groups group permission 124

SNMP 17, 211
community string
on domain 90
on server 90
user access to modify 127
software
on PAC 19
on server 17, 32
updating in ASEs 35, 56
upgrading on server 35
sorting the server list (on Web Server) 176
space, database 56
SQL Server
access control 40
securing login 43
service 37
user knowledge of ix
username and password 40
utilities 195
starting and stopping services 37
state-change events 20
priority levels of 36
storing ASE data 31
system architecture 11
system management tools 33
T
TCP 51
technical support xiv
third party software 32
templates
ASE configuration 35, 36
for ASEs 32
TFTP 17
authentication 91
timing, administrative events 86
TOS bitmask and data, IP class of service 101
Trace File group permission 127
Traffic Capture 10
training xiv
221

User Guide
U
unreachable server 56
updating ASE software 35, 56
upgrading
managing licenses 156
server 35
user groups created 123
URL for server 172
user groups 121, 122
creating 129
deleting 130
editing 129
generating report 65
permission to create 126, 129
setting capabilities 123
viewing members 128
users 21, 121, 130
assigning to domains 135
capabilities for 124, 126, 127
configuring
associations for domain 104
lockout settings 144
passwords 142, 143
copying 134
creating 133
groups 129
default 40, 41
deleting 139
groups 130
editing groups 129
editing passwords 134
generating report 65
groups 122
identifying active 64
locking accounts 137
PAC login restrictions 133
passwords 142, 143
permissions 123
power users 138
restricting access to PAC by IP address 137
viewing in group 128
viewing properties of 131
Users and Groups report 76
222
V
VAdmin 201
Fluke Networks, contacting xiii
Visual Performance Manager 1, 2
access control 121
administrative tasks 35
architecture 11, 19
databases 200
default users 40
documentation ix
features 3
help xii
licenses 155
agent 165
ASE evaluation 163
backup server 167
feature 159, 160
LAN Visibility 166
licensing options 10
passwords 40
server applications 34
services 31, 37, 57
software supported xiii
system communication 171
upgrading 156
Application Flows 10
feature modules 810
reports 105
Service Summary 3
events 89
Traffic Capture 10
Troubleshooting 9
VoIP 9
VoIP 9
changing call quality metric 149
report publishing options 147
reports
port 109
site 110
223

User Guide
VoIP Calls Troubleshooting
VoIP Summary
VUpTime 34, 197, 200
VUpTimeDC 201
VUpTimeLT 34, 197, 200
VUpTimeNF 28, 201
W
Web access
administrative tasks related to 171
to Adobe Acrobat Reader xi
to documentation xii
Web browsers xiii
Web portal 2, 19
custom navigation link, configuring 179
global settings for 178
launching from URL 181
password change permission 124
Web server 19
adding server to list 176
configuring 174
controlling access to server 175
disabling server on list 177
editing server properties 178
global settings for Web users 178
logging in 174
managing system from 19
removing server from list 178
setting primary server 177
Windows
auditing 45, 46
firewall 205
passwords
assigning 42
lockout policy 44
registry 49, 51
repair disk, creating 203
securing login 42
security options 39
Server 2003, default users 41
services 31, 57
username and password 40
versions supported xiii
224
WWW service 43
225

VPM v8.0 - Admin Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

VPM v8.0 - Admin Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Visual Performance Manager

System Administration Guide

Visual Performance Manager

Visual Performance Manager

Visual Performance Manager

Visual Performance Manager

Visual Performance Manager

Software License Agreement

Visual Performance Manager

U.S. Government Restricted Rights

Visual Performance Manager Overview ......................................................................... 15

Visual Performance Manager

Application Performance Appliances ................................................................................. 25

Server Overview .............................................................................................................. 42

Administering System Security ...................................................................................... 49

Critical Files ....................................................................................................................... 55

Monitoring Servers .......................................................................................................... 61

Visual Performance Manager

Setting the TFTP Authentication String .............................................................................. 93

Managing Users ............................................................................................................. 118

Configuring Server Settings ......................................................................................... 134

Visual Performance Manager

Changing the Logo for Reports ........................................................................................ 141

Managing Web Access .................................................................................................. 160

Frequently Asked Questions ........................................................................................ 171

License Key Backup and Recovery ..................................................................................... 176

Open Ports for Firewall Configuration ......................................................................... 188

B. Reestablish Reporting on a Renamed Server ............................................................. 191

Visual Performance Manager

About this Guide

Guides and Other Documents

Visual Performance Manager

Visual Performance Manager

Click Download Documentation.

To access documentation from your local drive:

Launching Online Help

Launching Help from the Web Portal

Launching Help from the Server or PAC

Supported Web Browsers and Operating Systems

VPM server/ Web server

Windows Server 2008 R2 Standard Edition with

Visual UpTime Select PAC

Windows Server 2008 R2 with SP1

Select Resources > Downloads and Updates.

Select the update that you want.

Do one of the following:

If you already have an account, sign in.

Visual Performance Manager

Visual Performance Manager Overview

1. Visual Performance Manager

Topics in this chapter include:

What is Visual Performance Manager?

Visual Performance Manager software features

System architecture components

How the Visual Performance Manager system is deployed

How data is managed in the Visual Performance Manager system

What is Visual Performance Manager?

Visual Performance Manager

Visual Performance Manager Overview

Visual Performance Manager Features

Visual Performance Manager

Application Performance Management

Visual Performance Manager Overview

Visual Performance Manager