tech ref guidemasuninetinet.uninet.net.mx/docs/vitalsuite/adv10.pdf · 2006-04-11 · change the...

Lucent Technologies - ProprietaryThis document contains proprietary information of Lucent Technologies and

is not to be disclosed or used except in accordance with applicable agreements.

Copyright © 2006 Lucent TechnologiesAll rights reserved.

VitalSuite®

Performance Management Software 10.0Advanced Administration and Reference Guide

190-409-006R10.0April, 2006

Copyright © 2006 Lucent Technologies. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Lucent Technologies and the business management owner of the material.

This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Lucent Technologies and the business management owner of the material.

Trademarks

AppWorks, MIBWorks, ModemExpert, NavisCore, NavisXtend, Net.Medic, Transact Toolkit, VitalAgent, VitalAgent Automon, VitalAgentIT, VitalApps, VitalAnalysis, VitalHelp, VitalHelp Remote, VitalNet, VitalSigns, and VitalART are trademarks of Lucent Technologies. Brick, iMerge, Navis, VitalSuite, and VitalEvent are registered trademarks of Lucent Technologies. This product includes code licensed from RSA Data Security. This product includes software developed by Ralf S. Engleschall <[email protected]> for use in the mod_ssl project (http://www.modssl.org/). All other brand and product names are registered trademarks or trademarks of their respective holders.

Acknowledgements

VitalSuite Performance Management software includes open-source software from Apache Software Foundation (http://www.apache.org/), Apache Jakarta Project, Apache XML Project, Advanced Network Technologies Division Software Distribution, Blat, Counterpane Labs, Eclipse, The ExoLab Group - Castor Project, Info-Zip, Jean Loup Gailly and Mark Adler, Matt Brunk, The JTDS Project - software developed by CDS Networks Inc., Matt Welsh and The Regent of the University of California, Mod_SSL Project, Limburgs Universitair Centrum implementation, Open_SSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/), SourceForge.net, Sun Microsystems, TCL/TK, Thomas Boutell, Westhawk LTD.

To view the terms of the license agreement for these open-source applications, see the <productname>_license.txt files on your VitalSuite server.

http://www.modssl.org

http://www.apache.org

http://www.openssl.org

.....................................................................iii

Contents

About this document xiii

Purpose............................................................................................................................................................. xiii

Reason for reissue ........................................................................................................................................ xiii

Intended audience ........................................................................................................................................ xiii

Conventions used ..........................................................................................................................................xiv

Additional information, training, or documentation .........................................................................xv

Documentation set .........................................................................................................................................xv

Technical support ..........................................................................................................................................xix

How to order ...................................................................................................................................................xix

How to comment ...........................................................................................................................................xix

1 Ports and protocols 1

VitalSuite Performance Management ports, protocols and transactions ..........................2

Overview............................................................................................................................. 2

Ports and protocols used between VitalSuite Performance Management servers...................3

VitalSuite Performance Management transactions .............................................................................5

Change the VitalSuite APPS Analysis functionality posting port .........................................9

Overview............................................................................................................................. 9

Minimize the orphaning of VitalAgents................................................................................................10

Change the port number in the Web Console .....................................................................................11

Edit the VitalSuite APPS Configuration server’s registry .............................................................13

Update HTML files and verify changes ................................................................................................14

2 Server and account security options 17

Secure Socket Layer implementation ................................................................................................19

Overview........................................................................................................................... 19

Introduction to SSL .......................................................................................................................................20

SSL software and directory structure on Windows...........................................................................21

Enable SSL on Windows.............................................................................................................................22

Disable Secure Socket Layer on Windows...........................................................................................25

SSL software and directory structure on UNIX .................................................................................26

Contents

.....................................................................iv

Enable SSL on UNIX ...................................................................................................................................27

Disable Secure Socket Layer on UNIX.................................................................................................30

Secure Shell implementation ..................................................................................................................32

Overview ........................................................................................................................... 32

Introduction to SSH.......................................................................................................................................33

Configure public key authentication for SSH......................................................................................34

Remote authentication server ................................................................................................................36

Overview ........................................................................................................................... 36

Introduction ......................................................................................................................................................37

Authentication server requirements ........................................................................................................38

Create an import file of your VitalSuite Performance Management accounts .......................40

Enable a remote authentication server....................................................................................................42

3 VitalSuite Performance Management IP address changes 47

Change VitalSuite NET IP addresses on Windows.....................................................................50

Overview ........................................................................................................................... 50

Change the IP address of a single VitalSuite NET server on Windows....................................51

Change the IP addresses of distributed VitalSuite NET servers on Windows........................54

Change VitalSuite NET IP addresses on UNIX............................................................................60

Overview ........................................................................................................................... 60

Change the IP address of a single VitalSuite NET server on UNIX...........................................61

Change the IP addresses of distributed VitalSuite NET servers on UNIX...............................64

Update the Master Server databases........................................................................................................66

Update the Aggregation Server databases ............................................................................................68

Update the Polling Server databases.......................................................................................................71

Update the Reporting Server databases .................................................................................................74

Change the IP addresses of VitalSuite APPS servers.................................................................77

Overview ........................................................................................................................... 77

Process overview............................................................................................................................................78

Direct existing VitalAgents to post to a new IP address .................................................................79

Update the Configuration server IP address.........................................................................................81

Delete obsolete source addresses in VSSyncTimeTable.................................................................83

Update the VitalSuite APPS databases with the new IP address .................................................85

Scenario 1: VitalSuite APPS Analysis and Help on the same machine ....................................86

.....................................................................v

Scenario 2: VitalSuite APPS Analysis and Help on two separate machines...........................89

Scenario 3: Distributed VitalSuite APPS Analysis environment.................................................92

Change the VitalSuite APPS Analysis server IP address and edit the registry.......................94

Change the VitalSuite APPS Help IP address by re-installing the product .............................96

Update VitalAgentIT clients to target a new address.......................................................................98

Correct DSN connections on Windows .......................................................................................... 100

Overview......................................................................................................................... 100

Update and test VitalSuite Performance Management DSNs.................................................... 101

VitalSuite Performance Management DSNs .................................................................................... 106

4 Allowing open access to VitalSuite Performance Management pages using vsopenURL107

Configure the vsopenURL utility.......................................................................................................... 108

Use cases ........................................................................................................................................................ 111

5 Log files 115

Log file locations......................................................................................................................................... 116

VitalSuite NET log files ........................................................................................................................... 117

Example VitalSuite NET log files ........................................................................................................ 123

VitalSuite APPS Analysis log files ...................................................................................................... 128

VitalSuite APPS Analysis example log files .................................................................................... 132

VitalSuite APPS Help functionality log files ................................................................................... 135

Windows Find utility ................................................................................................................................. 138

Performance enhancements..................................................................................................................... 139

6 Technical tips and notes 141

Overview......................................................................................................................... 141

Recommended Web browser settings ............................................................................................. 143

Overview......................................................................................................................... 143

Windows 2003 recommended settings ............................................................................................... 144

Internet Explorer recommended settings............................................................................................ 145

Configure proxy bypass for IP addresses in Internet Explorer .................................................. 146

Configure Internet Explorer to allow session cookies................................................................... 148

Add VitalSuite Performance Management servers as trusted sites in Internet Explorer . 150

Firefox recommended settings ............................................................................................................... 152

Contents

.....................................................................vi

Technical notes........................................................................................................................................... 153

Overview ......................................................................................................................... 153

Commonly used URLs.............................................................................................................................. 154

List of VitalSuite Performance Management services.................................................................. 155

Guidelines for printing VitalSuite Performance Management pages ..................................... 156

Web server disk checking interval........................................................................................................ 157

VitalAgent accelerator keys .................................................................................................................... 158

VitalAgent recording upload activity in a daily log....................................................................... 159

Resolve VitalSuite APPS Analysis functionality DNS issues with the VAServerMap utility160

Tips for resolving common problems.............................................................................................. 164

Overview ......................................................................................................................... 164

Resolve Page Not Found errors in the Web Console..................................................................... 165

Web Console not displaying correctly ................................................................................................ 167

7 Branding the Web Console and VitalAgent icons 169

Overview ......................................................................................................................... 169

Web Console branding guidelines ........................................................................................................ 170

Brand the Web Console ............................................................................................................................ 172

Web Console branding examples.......................................................................................................... 173

Add a message to the login page ........................................................................................................... 177

VitalAgent branding................................................................................................................................... 179

Restore the default VitalAgent icons................................................................................................... 182

8 Back up and restore 183

Backup guidelines for VitalSuite NET UNIX ............................................................................. 185

Overview ......................................................................................................................... 185

Backup considerations............................................................................................................................... 186

Tablespaces and file systems to back up............................................................................................ 187

Introduction to the VitalSuite NET UNIX backup and restore scripts ................................... 189

Back up VitalSuite NET UNIX data.................................................................................................... 190

Backup guidelines for VitalSuite NET (Windows) and VitalSuite APPS..................... 192

Overview ......................................................................................................................... 192

Backup considerations............................................................................................................................... 193

Databases to include in your backup ................................................................................................... 194

.....................................................................vii

File systems to include in your backup............................................................................................... 196

Back up VitalSuite APPS and VitalSuite NET data with MS-SQL Server .......................... 197

Enable MS-SQL Server to back up to a network drive................................................................. 203

Other backup considerations .............................................................................................................. 204

Overview......................................................................................................................... 204

Other data to include with your backup.............................................................................................. 205

Backup schedule guidelines .................................................................................................................... 206

Restore guidelines ..................................................................................................................................... 207

Overview......................................................................................................................... 207

Before you restore....................................................................................................................................... 208

Restore VitalSuite NET UNIX data..................................................................................................... 210

Restore VitalSuite APPS and VitalSuite NET data with MS-SQL Server............................ 212

Attach databases .......................................................................................................................................... 215

Restore file systems from a backup...................................................................................................... 217

9 Move VitalSuite NET databases 219

Important information ........................................................................................................................... 221

Database files................................................................................................................................................ 222

Recommended location and directory names for the moved database files ......................... 224

Windows short names................................................................................................................................ 225

Move VitalSuite NET databases........................................................................................................ 226

Process to move the VitalSuite NET databases............................................................................... 227

Query and save the sysfiles ..................................................................................................................... 228

Stop the VitalSuite NET services.......................................................................................................... 230

Detach the database.................................................................................................................................... 232

Edit the SQL attach scripts ...................................................................................................................... 234

Edit the registry............................................................................................................................................ 236

Attach the database..................................................................................................................................... 238

Test and verification................................................................................................................................ 240

Process to verify a successful database move .................................................................................. 241

Check the database configuration ......................................................................................................... 242

Check the poller DSN configuration.................................................................................................... 244

Verify product operation .......................................................................................................................... 246

Contents

.....................................................................viii

10 Move Analysis databases 247


Database files................................................................................................................................................ 249



Move Analysis databases....................................................................................................................... 253

Process to move the Analysis databases............................................................................................. 254

Query and save the sysfiles...................................................................................................................... 255

Stop the Analysis services........................................................................................................................ 257







Verify product operation........................................................................................................................... 268

11 Move Help databases 269


Database files................................................................................................................................................ 271



Move Help databases............................................................................................................................... 274

Process to move the Help databases .................................................................................................... 275

Query and save the sysfiles...................................................................................................................... 276

Stop the Help services ............................................................................................................................... 278







Verify product operation........................................................................................................................... 289

.....................................................................ix

12 Move ART databases 291


Database files................................................................................................................................................ 293



Move ART databases .............................................................................................................................. 297

Process to move the ART databases .................................................................................................... 298

Query and save the sysfiles ..................................................................................................................... 299

Stop the ART services............................................................................................................................... 301







Verify product operation .......................................................................................................................... 312

13 VitalSuite NET technical notes 313

Overview......................................................................................................................... 313

Protocols and interface type codes ................................................................................................... 315

Overview......................................................................................................................... 315

Protocols and protocol groups................................................................................................................ 316

Interface type codes.................................................................................................................................... 327

Adding VitalSuite NET resources manually ............................................................................... 337

Overview......................................................................................................................... 337

Add resources manually to VitalSuite NET...................................................................................... 338

Resource configuration file ..................................................................................................................... 340

Resolve missing resource data in VitalSuite NET..................................................................... 343

Overview......................................................................................................................... 343

Verify the collector is enabled................................................................................................................ 344

Verify the collector is running................................................................................................................ 346

Access the UTM status codes................................................................................................................. 348

Modify the default SNMP timeout value........................................................................................... 352

Contents

.....................................................................x

Threshold parameters............................................................................................................................. 354

Overview ......................................................................................................................... 354

Default quality index parameters for resource types ..................................................................... 355

Network alarm threshold measurements ............................................................................................ 368

Using the System Application MIB to monitor applications............................................... 393

Overview ......................................................................................................................... 393

Introduction ................................................................................................................................................... 394

Install the CIAgent on Windows........................................................................................................... 395

Install the CIAgent on UNIX.................................................................................................................. 397

Determine the applications to monitor on Windows ..................................................................... 399

Determine the applications to monitor on UNIX............................................................................ 402

Configure the SAPPApplicationsTable .............................................................................................. 404

RMON2 flow limits .................................................................................................................................. 406

Overview ......................................................................................................................... 406

Introduction to RMON2 flow limits .................................................................................................... 407

Change the RMON2 flow limits used by VitalSuite NET........................................................... 408

Example commands for changing RMON2 flow limits............................................................... 410

Tivoli integration....................................................................................................................................... 411

Overview ......................................................................................................................... 411

Introduction ................................................................................................................................................... 412

Configure Tivoli to launch VitalSuite NET from a pre-defined server.................................. 413

Configure Tivoli to launch VitalSuite NET from a selected server......................................... 415

Miscellaneous notes.................................................................................................................................. 417

Overview ......................................................................................................................... 417

Common issues and resolutions with NavisXtend ......................................................................... 418

Shutdown commands for VitalSuite NET UNIX servers ............................................................ 420

Aggregation Editor utility ........................................................................................................................ 421

Change the resource limit in My Reports for VitalSuite NET on Windows ........................ 423

Change the resource limit in My Reports for VitalSuite NET on UNIX............................... 425

A VitalSuite APPS Help functionality Mail, SNMP, and Remedy Gateways 427

How the VitalSuite APPS Help functionality gateways work............................................. 430

Overview ......................................................................................................................... 430

How the Mail Gateway works................................................................................................................ 431

How the SNMP gateway works............................................................................................................. 433

.....................................................................xi

How the VitalSuite APPS Help functionality integrates with Remedy.................................. 435

Mail and SNMP Gateway installation and upgrade................................................................ 437

Overview......................................................................................................................... 437

General considerations .............................................................................................................................. 438

Upgrade scenarios....................................................................................................................................... 439

Move a mail or SNMP gateway from a Master to Posting server ............................................ 440

Pre-installation tasks for the mail and SNMP gateways .............................................................. 442

Install the mail and SNMP gateways................................................................................................... 443

Customize your mail and SNMP gateway......................................................................................... 445

Test the configuration................................................................................................................................ 447

Overview of the MailGateway.ini and snmptrap.ini files.......................................................... 448

Overview......................................................................................................................... 448

Introduction ................................................................................................................................................... 449

Gateway settings validation tool ........................................................................................................... 450

Ticket filters .................................................................................................................................................. 452

Mail and SNMP gateway filter examples .......................................................................................... 454

Health record data fields........................................................................................................................... 456

MailGateway.ini and snmptrap.ini examples ................................................................................... 459

Overview of the mail and SNMP gateway template files ...................................................... 461

Overview......................................................................................................................... 461

About the mail gateway template.......................................................................................................... 462

Example of a mail template file............................................................................................................. 464

About the SNMP gateway template..................................................................................................... 466

Example of an SNMP trap template file............................................................................................. 468

Remedy gateway installation............................................................................................................... 470

Overview......................................................................................................................... 470

Pre-installation tasks for the Remedy gateway................................................................................ 471

Install the Remedy gateway..................................................................................................................... 472

Set up the Remedy demonstration schema........................................................................................ 474

Customize your Remedy environment................................................................................................ 476

Remedy gateway files .............................................................................................................................. 478

Overview......................................................................................................................... 478

Overview of the remedy.ini file............................................................................................................. 479

Data maps....................................................................................................................................................... 480

Data map examples..................................................................................................................................... 481

Contents

.....................................................................xii

Data fields used in the remedy.ini file................................................................................................. 484

Filters ............................................................................................................................................................... 486

Filter examples ............................................................................................................................................. 487

Example of a remedy.ini file................................................................................................................... 489

Index 495

....................................................................xiii

About this document

Purpose

This manual describes advanced administration tasks that are performed outside the Web Console. This manual also includes technical reference information that administrator’s may find useful when performing advanced tasks.

Reason for reissue

This manual has been reissued for release 10.0.

Intended audience

This manual is intended for Information Technology (IT) professionals who are responsible for configuring, deploying, and administering the VitalSuite Performance Management software products. This manual assumes the reader understands the basics of their web browser as well as the Windows and/or UNIX operating systems on which the products run.

The following groups of individuals use the VitalSuite Performance Management software products:

Types of users Description

Administrators IT professionals who install, configure, and maintain the VitalSuite Performance Management software products. This manual and the installation guides are intended for these users. The VitalSuite Performance Management Software Advanced Administration and Reference Guide describes advanced administration procedures not supported in the Web console and also provides technical reference information. The VitalSuite Performance Management Software Installation Guide describes how to install VitalSuite NET, and VitalSuite APPS. The VitalAgent Administrator’s Guide describes configuration, deployment, and maintenance of VitalAgent clients, as well as VitalAgent Automon configuration for synthetic transactions.

VitalSuite NET and Real-time users

IT professionals who use VitalSuite NET and the Real-time option to monitor the performance of network devices. The VitalSuite Network Performance Management Software User’s Guide is intended for these users.

....................................................................xiv

Conventions used

The following table shows the typographical conventions used throughout this manual:

Analysis users IT professionals who use the Analysis functionality of VitalSuite Application Performance Management software as a service-level monitoring and capacity planning tool. The VitalSuite Application Performance Management Software User’s Guide is intended for these users.

Help users IT professionals who use the Help functionality of VitalSuite Application Performance Management software to identify and resolve network- and application-related problems on their TCP/IP networks. The VitalSuite Application Performance Management Software User’s Guide is intended for these users.

VitalAgent and VitalAgentIT users Users within an organization who run these agents on their desktop computers to collect information for Analysis and Help. The online help system provides all relevant information.

Types of users Description

Convention Meaning Example

Bold Helvetica font Names of items on screens, such as buttons and menu items.

Select the Client check box.

bold A keyboard key you should press.

Press Enter.

Uniform resource locators (URLs).

The address of the page that customers can use to order additional copies of the documentation is: http://www.lucentdocs.com.

italics Names of manuals, directories, files, or the first occurrence of a glossary term.

Fo more information, refer to the VitalSuite Network Performance Management Software User’s Guide.

<Angle brackets>

Variables for which you must substitute another value.

http://<server’s IP address or name> where <server’s IP address or name> is the IP address or name of the VitalSuite NET server.

Letter Gothic font

Text to type into a field or dialog box.

In the RESOURCE NAME text box, enter *Dallas.

Click Click the left button on your mouse once.

To select a link in the Web Console, click it.

....................................................................xv

Additional information, training, or documentation

For a complete list of new features for your product, refer to the Release Notes posted on the Lucent Support web site.

The following table provides URLs for product information, training, and additional user documentation:

Documentation set

You can access all documents with the exception of the database schemas at: http://www.lucent.com/support.

Right-click Click the right button on your mouse.

Right-click on an event in the Windows Console to display its pop-up menu.

Double-click Double-click the left button on your mouse.

Double-click on the icon to start the VitalAgent Installer.

Convention Meaning Example

Description Location

Education ServicesThis group offers cost-effective educational programs that teach administrators and users how to install, administer, and use the products.

https://training.lucent.com

email: [email protected]

Online HelpAll VitalSuite Network Performance Managment software and Application Performance Management software products have online help in addition to the manuals online.

Click in the Web Console navigation bar.

Accessing Documentation OnlineAfter logging into this site, click the name of your product. You can access documents such as Release Notes and User Guides in the Release Information and Manuals and Guides links. If you do not have a user ID and password, click the Access & Registration link on the Support site to obtain your login information.

http://www.lucent.com/support

or

Click in the Web Console navigation bar to access the local documentation page on your product server.

https://training.lucent.com



....................................................................xvi

VitalSuite Performance Management software documents

The following table lists the documents that support VitalSuite Network Performance Management and VitalSuite Application Performance Management software (VitalSuite NET and VitalSuite APPS):

VitalSuite Application Performance Management software documentation

The following table lists the documents that support VitalSuite APPS:

Document name Describes Document type

VitalSuite® Performance Management Software Administrator’s Guide

How to manage the VitalSuite NET and VitalSuite APPS servers and Real-time features.

• Printed book• PDF

VitalSuite® Performance Management Software Installation Guide

How to install the VitalSuite NET and VitalSuite APPS servers.


VitalSuite® Performance Management Software Advanced Administration and Reference Guide

Advanced administration procedures that are not supported in the Web Console and provides technical reference information.

PDF

VitalSuite® VSOpen API User’s Guide

How to manage user accounts, domains, groups, and devices through a C++ program or command-line interface.

PDF


VitalSuite® APPS Quick Start Card

System requirements, and installation and configuration procedures.

• Printed card• PDF

VitalSuite® Application Performance Management Software User’s Guide

How to use the product. • Printed book• PDF

VitalAgent Administrator’s Guide

How to manage VitalAgent and VitalAgentIT client software that collects and uploads information to VitalSuite APPS.


Transact Toolkit User’s Guide How to install and use Transact Toolkit. PDF

VitalSuite® Application Performance Management Software Help Functionality List of Events

List of Help events. Use this event information when creating creating ticket filters for the Help Mail Gateway, SNMP Gateway, or the Remedy Action Request system.

PDF

VitalSuite® Application Performance Management Software Database Schema

Tables and field descriptions in the VitalSuite APPS database. To obtain a copy, contact Lucent technical support.

PDF

....................................................................xvii

VitalSuite Network Performance Management software documents

The following table lists the documents that support VitalSuite NET and Real-time:

VitalSuite® Application Performance Management Software Release Notes

New features and the related known problems. This document is only available on the Support Web site.

HTML


VitalSuite® NET Quick Start Card (UNIX)

System requirements, and installation and configuration procedures for VitalSuite NET UNIX.


VitalSuite® NET Quick Start Card (Windows)

System requirements, and installation and configuration procedures for VitalSuite NET Windows.


VitalSuite® Network Performance Management Software User’s Guide

How to use the product. • Printed book• PDF

VitalSuite® Network Performance Management Software Administrator’s Checklist

List of tasks to help administrators maintain VitalSuite NET.

PDF

VitalSuite® Wireless Performance Management Software Administrator’s Guide

VitalSuite wireless functionality and administration.


VitalSuite® Wireless Performance Management Software KPI Reference Guide

CDMA performance measurements. PDF

VitalSuite® Wireless Performance Management Software Database Schema

Tables and field descriptions in the wireless database. To obtain a copy, contact Lucent technical support.

PDF

MIBWorks User’s Guide How to add support for new resource types that reside on SNMP to VitalSuite NET using the MIBWorks GUI.

PDF

MIBWorks SDK User’s Guide How to add support for new resource types that reside on SNMP to VitalSuite NET using the MIBWorks SDK.

PDF


....................................................................xviii

VitalSuite Advanced Reporting Tool

The following table lists the documents that support VitalSuite ART:

DataWorks SDK User’s Guide How to collect performance data from statistics files created by other network monitoring systems and incorporate the data into Web Console pages and reports.

PDF

VitalSuite® Network Performance Management Software List of Supported Devices

List of network standards and devices supported by VitalSuite NET and the VitalSuite NET resource types available for each device.

PDF

VitalSuite® Network Performance Management Software Database Schema

Tables and field descriptions in the VitalSuite NET database. To obtain a copy, contact Lucent technical support.

PDF

VitalSuite® Network Performance Management Software Release Notes

New features and the related known problems in VitalSuite NET. This document is only available on the support Web site.

HTML


VitalSuite® ART Quick Start Card (UNIX)

The system requirements, and installation and configuration procedures for VitalSuite ART UNIX.


VitalSuite® ART Quick Start Card (Windows)

The system requirements, and installation and configuration procedures for VitalSuite ART Windows.


VitalSuite® Advanced Reporting Tool Administrator’s Guide

How to install, use and manage the VitalSuite ART product.


VitalSuite® Advanced Reporting Tool Database Schema

The tables and field descriptions in the VitalSuite ART database. To obtain a copy, contact Lucent technical support

PDF

VitalSuite® Advanced Reporting Tool Release Notes

The new features and the related known problems in VitalSuite ART. This document is only available on the support Web site.

HTML


....................................................................xix

Technical support

This section contains the contact information for Lucent technical support.

Web

To open or update an assistance request over the Web, log into the Lucent Technical Support site at http://www.lucent.com/support and select the CARES link.

Phone

Customers in the United States can call 1-866-LUCENT8 (582-3688) or send fax to 1-650-318-1104.

For customers in international locations, visit the Lucent Customer Support Home Page at http://www.lucent.com/support. Select your country from the Technical Support Phone Numbers drop-down menu, click Go, and call the support number that is displayed.

How to order

You can order additional printed guides from http://www.lucentdocs.com.

How to comment

To comment on this information product, go to the Online Comment Form or email your comments to the Comments Hotline ([email protected]).




http://www.lucentdocs.com

mailto:[email protected]

....................................................................xx

....................................................................1

1 Ports and protocols

Purpose

This chapter provides a visual guide and table to help administrators ensure that communication is enabled between VitalSuite Performance Management servers. It also contains a listing of VitalSuite Performance Management transactions, ports, and protocols.

Contents

This chapter contains the following topics:

VitalSuite Performance Management ports, protocols and transactions 2

Ports and protocols used between VitalSuite Performance Management servers

3

VitalSuite Performance Management transactions 5

Change the VitalSuite APPS Analysis functionality posting port 9

Minimize the orphaning of VitalAgents 10

Change the port number in the Web Console 11

Edit the VitalSuite APPS Configuration server’s registry 13

Update HTML files and verify changes 14

....................................................................2

VitalSuite Performance Management ports, protocols and transactions

..........................................................................................................................................................................................Overview

Purpose

This section describes the transactions performed by VitalSuite Performance Management servers and the ports and protocols VitalSuite Performance Management servers use for these transactions.

Contents

This section contains the following topics:


3

VitalSuite Performance Management transactions 5

....................................................................3


Ports and protocols used between VitalSuite Performance

..........................................................................................................................................................................................Management servers

Overview

When you deploy VitalSuite Performance Management servers, you need to make sure the necessary ports are open on your network so the distributed servers can transfer data and synchronize configuration information.

If a network security device, such as a firewall, stands between any of your VitalSuite Performance Management servers, network devices, or VitalAgents, you might need to work with your company’s firewall administrator to enable communication over these ports.

VitalSuite Performance Management network diagram

The following figure displays the ports used by VitalSuite Performance Management servers for communication. Note the following:

• There is one Reporting server for VitalSuite APPS and one Reporting server for VitalSuite NET, but you can use a single Reporting server for all three products.

• In most environments, the VitalSuite APPS Configuration server is integrated with either the Analysis functionality or Help functionality Master server. However, you can separate the Configuration server function from your Master server. If you choose to deploy a dedicated VitalSuite APPS Configuration server, the port 2474 needs to be open.

....................................................................4

VA Posting server

VH Posting server

VA Aggregation server

VA/VH Reporting

server

VN Reportingserver

VitalAgents

VSWEB VHPORT

VA Master server VH Master server

ODBC

HTTP/HTTPS,VSWEB

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

VN Polling server

VN Aggregation server

VN/VitalSuite Master server

Monitored devices

FTP

HTTP/HTTPS,ODBC

HTTP/HTTPS

HTTP/HTTPS

VSWEB

VSWEB

RMTEST

VitalAnalysis Environment VitalHelp Environment VitalNet Environment

ProtocolHTTP.............HTTPS..........VSWEB.........VHPORT.......RMTEST....... 3375

Port8044324743280

HTTP/HTTPS,

VHPORT

SNMP,ICMP

SNMPquery

Bulk statistic collection device

Port

161, 16220, 21

ProtocolODBC - Oracle........ 1521 - MS-SQL..... 1433SNMP............FTP...............

Bidirectional communication

Unidirectionalcommunication

....................................................................5

VitalSuite Performance Management transactions

..........................................................................................................................................................................................VitalSuite Performance Management transactions

Purpose

This topic describes the transactions that occur between VitalSuite Performance Management servers and the ports and protocols used for each transaction.

VitalAgent transactions

The following table describes the VitalAgent transactions.

* Identifies proprietary ports.

Transaction name

Destination port/protocol

Source anddestinationserver Description

Historical data upload

2474/HTTP

VitalAgent --> VA Posting Server

VitalAgent sends modem session and transaction data to VitalSuite APPS on an hourly basis. This port can be configured (see “Change the VitalSuite APPS Analysis functionality posting port”, on page 9).

Real time alarm

3280/VHPort*

VitalAgent --> VH Posting Server

VitalAgent immediately sends alarm information to VitalSuite APPS.This port is not configurable.

Config check 2474 and 80/HTTP

VitalAgent -->VitalSuite APPS Configuration server

VitalAgent checks hourly, daily, or weekly with the VitalSuite APPS Configuration server to obtain updated configuration information.This port can be configured (see “Change the VitalSuite APPS Analysis functionality posting port”, on page 9).

Remote test 3375/RMTEST*

VH Posting Server -->VitalAgent

VitalSuite APPS administrators can initiate remote tests to help resolve problems. For information on running remote tests refer to the VitalSuite Application Performance Management Software User’s Guide.This port is not configurable

....................................................................6

VitalSuite APPS Analysis functionality transactions

The following table describes the VitalSuite APPS Analysis functionality transactions. Note that VA = VitalSuite APPS Analysis functionality.

Transaction name



Config sync 80/HTTP VA Master server --> VA Aggregation and Posting servers

The Master server performs a full configuration synchronization with the Aggregation and Posting servers on a nightly basis. Configuration information includes server, domain, user, and group lists as well as report purging intervals and report generation schedules.This port is not configurable.

Data transfer 1433/ODBC VA Posting server --> VA Aggregation server

The Posting server transfers data to the Aggregation server every hour.

Report generation

80/HTTP, XML VA Master server --> VA Aggregation server

The Master server generates reports from the appropriate Aggregation server on an as needed basis. Current reports are cached on the VA Master server to minimize overhead.This port is not configurable.

....................................................................7

VitalSuite Performance Management transactions

VitalSuite APPS Help functionality transactions

The following table describes the VitalSuite APPS Help functionality transactions. Note that VH = VitalSuite APPS Help functionality.

VitalSuite NET transactions

The following table describes the VitalSuite NET transactions. Note that VN = VitalSuite NET.

Transaction name



Config sync 80/HTTP VH Master server --> VH Posting server

The Master server performs a full configuration synchronization with the Posting server on a nightly basis. Configuration information includes server, domain, user, and group lists.This port cannot be configured.

Data transfer 3280 VitalAgent --> VH Posting --> VH Master server

Alarms are sent in real time as they occur from agent to Posting server.

Report generation

80/HTTP, XML VH Master server --> VH Posting server

The Master server generates reports from the appropriate Posting server on an as-needed basis. Current reports are cached on the VH Master server to minimize overhead.This port is not configurable.

Transaction name



Config sync 80/HTTP VN Master server --> VN Aggregation and Polling servers

The VitalSuite NET Master server performs configuration synchronization with the Aggregation and Polling servers nightly. Configuration information includes server, domain, user, and group lists, report purging intervals, and report generation schedules.This port is not configurable.

SNMP 161, 162 VN Polling servers --> Devices

The VN Polling server uses this port to access devices.

FTP 20, 21 Stat collection device --> VN Polling server

VitalSuite NET Polling servers collect bulk data (such as from iMerge and some Navis devices) through FTP.

....................................................................8

Data transfer 1433/ODBC/ (MSSQL)1521/ODBC (Oracle)

VN Polling server --> VN Aggregation server

The VitalSuite NET Polling server transfers data to the Aggregation server on an hourly basis.

Report generation

80/HTTP, XML VN Master server --> VN Aggregation server

The VitalSuite NET Master server generates reports from the appropriate Aggregation server on an as needed basis. Current reports are cached on the VN Master server to minimize overhead.This port is not configurable.

Common-sign-on1

1645 VitalSuite Performance Management servers --> Remote authentication server

When administrators and users log onto VitalSuite Performance Management servers that are in common sign-on through remote authentication server (RAS) mode, the communication with the remote server goes through port 1645.

1 Remote authentication login (Navis Id or RADIUS)

Transaction name



....................................................................9

Overview

Change the VitalSuite APPS Analysis functionality posting port

..........................................................................................................................................................................................Overview

Purpose

The chapter describes how to allow VitalAgents to report through a different port number than the default port 2474. The configurable port applies to Analysis data posting only, and might be useful for firewall issues in some environments. There is no way to modify the agent port for reporting to VitalSuite APPS. These procedures apply to both single server and distributed environments.

Process

To change the port for Analysis data posting, follow this process:

1. “Minimize the orphaning of VitalAgents”, on page 10.

2. “Change the port number in the Web Console”, on page 11.

3. “Edit the VitalSuite APPS Configuration server’s registry”, on page 13.

4. “Update HTML files and verify changes”, on page 14.

Contents


Minimize the orphaning of VitalAgents 10

Change the port number in the Web Console 11

Edit the VitalSuite APPS Configuration server’s registry 13

Update HTML files and verify changes 14

....................................................................10

..........................................................................................................................................................................................Minimize the orphaning of VitalAgents

When to use

Use this procedure to minimize the number of VitalAgents that become orphaned after changing the port number used to post data to VitalSuite APPS.

Changing the port number will “orphan” any agents currently installed and posting using the 2474 port number. After the port change, any previously-installed agents must be manually changed to post via the new port number. A good way to minimize the orphaning of agents is to keep both the default port number and the new port number on separate servers for a few overlapping days so that late reporting clients are not excluded.

Before you begin

Ensure that no security devices prevent VitalAgents from communicating with VitalSuite APPS over the new port number you select.

Related information

For more information about the ports used by VitalSuite Performance Management, refer to “Ports and protocols used between VitalSuite Performance Management servers”, on page 3.

Procedure

To minimize the orphaning of VitalAgents:

...........................................................................................................................................................................

1 Keep the older server operational with the configuration target changed to the new server and new port number.

...........................................................................................................................................................................

2 Set up a new server with the new port.

...........................................................................................................................................................................

3 After a reasonable amount of time (when all VitalAgents are migrated to the new server) the old port can be closed and the old server taken down.

Important! Old and new server terms are interchangeable. Administrators can clone the existing configuration to a new temporary machine and keep the new server up while they change the old one to the new port setting.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................11

Change the port number in the Web Console

..........................................................................................................................................................................................Change the port number in the Web Console

When to use

Use this procedure to ensure that VitalAgents doing their configuration checks pick up their new posting assignments

Before you begin

Make sure you know the new port number VitalAgents will use to post data to VitalSuite APPS. This is the same port number that was used in “Minimize the orphaning of VitalAgents”, on page 10.

Related information

For detailed information about the VitalAgent configuration pages on the Web Console, refer to the VitalAgent Administrator’s Guide.

Procedure

To enter the new port number in the Web Console:

...........................................................................................................................................................................

1 Log in as administrator and select: ADMIN | Agents | Software Update target.

...........................................................................................................................................................................

2 Change port 2474 to the available port of your choice.

...........................................................................................................................................................................

3 Click Submit.

...........................................................................................................................................................................

4 Select ADMIN | Agents | Configuration | Configuration update.

...........................................................................................................................................................................

5 Change the Port number from 2474 to the new port number.

...........................................................................................................................................................................

6 Click Submit.

...........................................................................................................................................................................

7 Select Configuration Update by Domain, then change and submit each domain (one by one) from port 2474 to new port.

...........................................................................................................................................................................

8 Select ADMIN | Agents | VitalAnalysis | Upload target.

...........................................................................................................................................................................

9 Change the port form 2474 to the new port in the Upload to target field.

....................................................................12

...........................................................................................................................................................................

10 Click Submit.

...........................................................................................................................................................................

11 Select Advanced.

...........................................................................................................................................................................

12 Change the upload target from port 2474 to the new port number for each Domain (one by one).

...........................................................................................................................................................................

13 Click Submit for each domain before moving on to the next.

...........................................................................................................................................................................

14 Select All Groups from the Groups drop-down list.

...........................................................................................................................................................................

15 Verify or edit the port number to be the new port number.

...........................................................................................................................................................................

16 Click Submit.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................13

Edit the VitalSuite APPS Configuration server’s registry

..........................................................................................................................................................................................Edit the VitalSuite APPS Configuration server’s registry

When to use

After changing the VitalAgent posting port in the Web Console, follow these procedures to make the necessary changes to the VitalSuite APPS server’s registry.

Before you begin

Make sure you have appropriate account permissions to stop services and edit registry settings on the VitalSuite APPS Configuration server. In most environments, the VitalSuite APPS Configuration server is the Master server.

Related information

Refer to your Windows documentation for information about the Windows registry settings.

Purpose

To edit the registry settings on the VitalSuite APPS Configuration server:

...........................................................................................................................................................................

1 On the VitalSuite APPS Configuration server, stop the following Windows services:

• Apache

• VAAggr

• VitalSuiteWeb

...........................................................................................................................................................................

2 Change the registry settings from 2474 to an available port of your choice, as follows:

a. From a command prompt, enter regedit.

b. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VitalSuiteWeb\Parameters

c. Set the following parameters (in this example from port 2474 to port xx):

\LISTEN_PORT = “xx”\VC_UPLOAD_TARGET = “IPAddress:xx”\VC_CONFIG_TARGET = “IPAddress:xx”\VC_VERSION_TARGET = “IPAddress:xx”\VS_CONFIG_TARGET = “IPAddress:xx” (required if VitalSuite APPS Help functionality is installed)

...........................................................................................................................................................................

3 From the Windows Services screen, restart the Apache, VAAggr, and VitalSuiteWeb services.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................14

..........................................................................................................................................................................................Update HTML files and verify changes

When to use

Use this procedure to update the HTML configuration files and to verify that port 2474 has been changed to the new port you specified.

Before you begin

After changing the VitalAgent posting port, wait until after the next scheduled configuration check to complete the procedures in this topic.

Related information

Refer to the VitalSuite Performance Management Software Administrator’s Guide for information about configuration checks and when they occur.

Procedure

To update the HTML files and verify the port change:

...........................................................................................................................................................................

1 Check the config.htm file located in the Program Files\VSCommon\Webroot\Grouplist\Default folder to verify that port 2474has been changed to the new port number.

...........................................................................................................................................................................

2 In the Grouplist folder, check all the domains defined and verify that all the config.htm files have instances of 2474 changed to the new port number.

...........................................................................................................................................................................

3 In the Webroot folder verify that config.htm (if it exists) and vhconfig.htm are updated to the new port number. These two files might not have any IP addresses, but you still need to check.

...........................................................................................................................................................................

4 Manually change the default file names in the folder Webroot to:

• VitalAgent-A-<IPAddress>-<NewPortNumber>.exe

• VitalAgentIT-A-<IPAddress>-<NewPortNumber>.exe

...........................................................................................................................................................................

5 Edit default.htm and vagentit.htm by replacing all instances of 2474 with the new port number.

...........................................................................................................................................................................

6 Download and install VitalAgent on a test system.

....................................................................15

Update HTML files and verify changes

...........................................................................................................................................................................

7 After approximately three hours verify the new VitalAgent is posting data.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................16

....................................................................17

2 Server and account security options

..........................................................................................................................................................................................Overview

Purpose

This chapter discusses how to enable SSL on your VitalSuite Performance Management servers, implement Secure Shell for FTP transactions, and use a remote authentication server in your VitalSuite Performance Management environment.

Contents


Secure Socket Layer implementation 19

Introduction to SSL 20

SSL software and directory structure on Windows 21

Enable SSL on Windows 22

Disable Secure Socket Layer on Windows 25

SSL software and directory structure on UNIX 26

Enable SSL on UNIX 27

Disable Secure Socket Layer on UNIX 30

Secure Shell implementation 32

Introduction to SSH 33

Configure public key authentication for SSH 34

Remote authentication server 36

Introduction 37

Authentication server requirements 38

....................................................................18

Create an import file of your VitalSuite Performance Management accounts

40

Enable a remote authentication server 42

....................................................................19

Overview

Secure Socket Layer implementation

..........................................................................................................................................................................................Overview

Purpose

This section describes how to enable and disable Secure Socket Layer (SSL) on Windows and UNIX-based VitalSuite Performance Management servers.

Contents


Introduction to SSL 20

SSL software and directory structure on Windows 21

Enable SSL on Windows 22

Disable Secure Socket Layer on Windows 25

SSL software and directory structure on UNIX 26

Enable SSL on UNIX 27

Disable Secure Socket Layer on UNIX 30

....................................................................20

..........................................................................................................................................................................................Introduction to SSL

Background

VitalSuite Performance Management supports the SSL (Secure Socket Layer) security protocol, which was developed by Netscape and is widely used for authenticating and encrypting data passed over the Web.

Distributed VitalSuite Performance Management environments

When you enable SSL for a distributed VitalSuite Performance Management environment, enable SSL first on the Master server, followed by the Aggregation, Polling/Posting, and Reporting servers.

Certifying authorities (CA)

The following table lists the certifying authorities you can use to authenticate your CSR.

CA Web site

VeriSign http://digitalid.verisign.com/server/apacheNotice.htm

Thawte Consulting http://www.thawte.com/certs/server/request.html

CertiSign Certificadora Digital Ltda http://www.certisign.com.br

IKS GmbH http://www.iks-jena.de/produkte/ca

GlobalSign http://globalsign.net/

....................................................................21

SSL software and directory structure on Windows

..........................................................................................................................................................................................SSL software and directory structure on Windows

Purpose

This topic lists the SSL software packaged with your Windows-based VitalSuite Performance Management product and describes the SSL directory structure.

SSL software

The following table describes the SSL software packaged with your VitalSuite Performance Management product.

Directory structure

The following table shows a segment of the VitalSuite Performance Management file structure as it looks after the SSL-related software is loaded.

Software Description Product Web sites

Apache 1.3.31 Web server software http://www.apache.org

mod_ssl-2.8.17 for Apache 1.3.27

Cryptographic software http://www.modssl.org

Openssl-0.9.7d Toolkit to implement SSL; library of cryptographic functions

http://www.openssl.org

Directory SSL-related files SSL-related directories

\vscommon\program\ ssleay32.dlllibeay32.dll

\vscommon\Apache\ openssl.exeVSEnableSSL.batVSDisableSSL.batVSSSLOn.regVSSSLOff.reg

\vscommon\Apache\modules ApacheModuleSSL.dll

\vscommon\Apache\conf openssl.cnfhttpd-ssl.conf

\vscommon\Apache\conf ssl.keyssl.crt

\vscommon\Apache\logs ssl

....................................................................22

..........................................................................................................................................................................................Enable SSL on Windows

When to use

Use this procedure to enable SSL on a Windows-based VitalSuite Performance Management server.

Before you begin

Ensure that all of your VitalSuite Performance Management servers are DNS-registered and are using their fully-qualified domain names as their internally configured address. You can verify whether your servers are using their fully-qualified domain names through the Web Console, on the ADMIN tab, Servers page.

Related information

For more information about SSL, refer to:

• “Introduction to SSL”, on page 20.

• “SSL software and directory structure on Windows”, on page 21.

Procedure

To enable SSL on your Windows-based VitalSuite Performance Management server:

...........................................................................................................................................................................

1 Create an RSA private key for the Apache server with the Triple-DES option in the PEM format.

Example: <VitalSuite_home>\vscommon\Apache\openssl genrsa -des3 -out server.dat 1024

where server.dat is the default name given to the private key.

...........................................................................................................................................................................

2 Back up the new server key file for safekeeping and secure the password or phrase.

...........................................................................................................................................................................

3 Create a certificate-signing request (CSR) using the server RSA private key created in Step 1by entering the following command:

<VitalSuite_home>\vscommon\Apache\openssl req -config conf\openssl.cnf -new -key server.dat -out server.csr

where server.dat is the default name given to the key and server.csr is the default name of the CSR.

Result: The command prompts you for several pieces of information.

...........................................................................................................................................................................

4 When you are asked to enter the “CommonName,” use the fully qualified domain name (FQDN).

....................................................................23

Enable SSL on Windows

...........................................................................................................................................................................

5 Send the CSR to a Certifying Authority (CA) for authentication.

Additional information: For a list of CAs, refer to “Certifying authorities (CA)”, on page 20.

Result: The CA sends back the authenticated CSR.

...........................................................................................................................................................................

6 Save the certificate to a file called server.crt.

...........................................................................................................................................................................

7 Run the following command to save the key to an Apache-readable format:

<VS_home>\vscommon\Apache\openssl rsa -in server.dat -out server.key

Additional information: For more information about this process, refer to the following URL: http://www.modssl.org/docs/2.8/ssl_faq.html.

...........................................................................................................................................................................

8 Copy the server.key file to the following directory:

<VitalSuite_home>\vscommon\apache\conf\ssl.key\

...........................................................................................................................................................................

9 Copy the server.crt file to the following directory:

<VitalSuite_home>\vscommon\apache\conf\ssl.crt\

...........................................................................................................................................................................

10 Edit the following entries in the Apache configuration file (httpd-ssl.conf) if the new certificate files are not server.crt and server.key.

• SSL Certificate File—<VitalSuite_home>\vscommon\Apache\conf\ssl.crt\server.crt • SSL Certificate Key File—<VitalSuite_home>\vscommon\Apache\conf\ssl.key\server.key

....................................................................24

...........................................................................................................................................................................

11 Do one of the following:

Result: The batch file performs the following actions:

• Makes backup files of the existing configuration file

• Switches the configuration files for SSL and NoSSL

• Changes the VitalSuite Performance Management registry to enable SSL

• Restarts the Apache service

...........................................................................................................................................................................E N D O F S T E P S

If you want to... Run the following script

Utilize port 80, which is the default behavior for VitalSuite Performance Management

\vscommon\Apache\VSEnableSSL.bat

Disable port 80 \vscommon\Apache\VSEnableSSL_secure.bat

....................................................................25

Disable Secure Socket Layer on Windows

..........................................................................................................................................................................................Disable Secure Socket Layer on Windows

When to use

Use this procedure to disable SSL on a Windows-based VitalSuite Performance Management server.

Before you begin

You should plan to disable SSL during non-business hours when your VitalSuite Performance Management servers are not being used.

Related information



• “SSL software and directory structure on Windows”, on page 21.

Procedure

To disable SSL on a Windows-based VitalSuite Performance Management server:

...........................................................................................................................................................................


Result: The following actions are performed:

• Makes a back up file of the existing configuration file

• Switches the configuration files for SSL and NoSSL

• Changes the VitalSuite registry to disable SSL

• Restarts the Apache service

Important! Some links on the My Vital page might remain insecure and direct you to cached data until the nightly synchronization takes place.

...........................................................................................................................................................................

2 Run the file on any other VitalSuite Performance Management servers in your environment.

...........................................................................................................................................................................E N D O F S T E P S

If you use Run the following script

Port 80 (the default port) for VitalSuite Performance Management communication

\vscommon\Apache\VSDisableSSL.bat

A port other than 80 for VitalSuite Performance Management communication

\vscommon\Apache\VSDisableSSL_secure.bat

....................................................................26

..........................................................................................................................................................................................SSL software and directory structure on UNIX

Purpose

This topic lists the SSL software packaged with your UNIX-based VitalSuite Performance Management product and describes the SSL directory structure.

SSL software

The following table describes the SSL software that comes packaged with your VitalSuite Performance Management product.

Directory structure

The following table shows a segment of the VitalSuite Performance Management file structure as it looks after the SSL-related software is loaded.

Software Description Product Web sites

Apache 1.3.27 Web server software www.apache.org

mod_ssl-2.8.4 for Apache 1.3.20 Cryptographic software www.modssl.org

Openssl-0.9.6e Toolkit to implement SSL; library of cryptographic functions

www.openssl.org

Directory SSL-related filesSSL-related directories

$VSHOME/vscommon/apache/libexec libssl.so

$VSHOME/vscommon/apache/bin vssslctl

$VSHOME/vscommon/openssl opensslrandopenssl.cnf

$VSHOME/vscommon/apache/logs ssl_engine_logssl_request_log

$VSHOME/vscommon/Apache/conf ssl.keyssl.crt

....................................................................27

Enable SSL on UNIX

..........................................................................................................................................................................................Enable SSL on UNIX

When to use

Use this procedure to enable SSL on a UNIX-based VitalSuite Performance Management server.

Before you begin

Ensure that all of your VitalSuite Performance Management servers are DNS-registered and are using their fully-qualified domain names as their internally configured address. You can verify whether your servers are using their fully-qualified domain names through the Web Console, on the ADMIN tab, Servers page.

Related information



• “SSL software and directory structure on UNIX”, on page 26.

For more information about openssl, refer to $VSHOME/vscommon/apache/openssl/README.

Procedure

To enable SSL on your UNIX-based VitalSuite Performance Management server:

...........................................................................................................................................................................

1 In a terminal window, log in to your UNIX system as vsadm.

...........................................................................................................................................................................

2 Navigate to the $VSHOME/vscommon/apache/openssl directory.

...........................................................................................................................................................................

3 Create a Triple-DES encrypted RSA private key for the Apache server by entering the following commands:

export RANDFILE=$VSHOME/vscommon/apache/openssl/rand./openssl genrsa -des3 -out server.dat 1024

Important! You can replace the contents of the rand file, provided the file contains at least 26 characters. If the rand file contains less than 26 characters you will receive a “PRNG not seeded” error.

...........................................................................................................................................................................

4 Back up the new server key file for safekeeping and secure the password or phrase.

...........................................................................................................................................................................

5 Provide a PEM pass-phrase when prompted.

....................................................................28

Additional information: This pass-phrase can be any text you prefer. Other steps in this procedure prompt you for the pass-phrase you provide in this step.

...........................................................................................................................................................................

6 Create a certificate signing request (CSR) using the server RSA private key created above by entering the following command:

./openssl req -config openssl.cnf -new -key server.dat -out server.csr

Result: This command prompts you for several pieces of information.

...........................................................................................................................................................................

7 When you are asked to enter the “CommonName,” use the fully qualified domain name (FQDN). When you are asked to enter a PEM pass-phrase, use the same PEM pass-phrase as in Step 5.

...........................................................................................................................................................................

8 Send the CSR to a Certifying Authority (CA) for authentication.

Additional information: For a list of CAs, refer to “Certifying authorities (CA)”, on page 20.

Result: The CA sends back the authenticated CSR.

...........................................................................................................................................................................

9 Save the certificate to a file called server.crt.

...........................................................................................................................................................................

10 Run the following command to save the key to an Apache-readable format:

./openssl rsa -in server.dat -out server.key

Additional information: For more information about this process, refer tohttp://www.modssl.org/docs/2.8/ssl_faq.html.

...........................................................................................................................................................................

11 When prompted, enter your PEM pass-phrase.

...........................................................................................................................................................................

12 Copy the server.key file to the following directory:

$VSHOME/vscommon/apache/conf/ssl.key/

...........................................................................................................................................................................

13 Copy the server.crt file to the following directory:

$VSHOME/vscommon/apache/conf/ssl.crt/

...........................................................................................................................................................................

14 Change to the $VSHOME/vscommon/apache/conf directory.

....................................................................29

Enable SSL on UNIX

...........................................................................................................................................................................

15 Open the httpd.conf file and verify the SSLCertificateFile and SSLCertificateKeyFile lines include the correct server.crt and server.key paths, where <install_dir> is your VitalSuite Performance Management installation directory:

Example: SSLCertificateFile /<install_dir>/vscommon/apache/conf/ssl.crt/server.crt

Example: SSLCertificateKeyFile /<install_dir>/vscommon/apache/conf/ssl.key/server.key

...........................................................................................................................................................................

16 In the httpd.conf file, do the following:

a. Locate the following entry:<Directory "/usr/local/vscommon/apache/cgi-bin">SSLOptions +StdEnvVars </Directory>

b. Change the path to the following:

<Directory "/usr/local/vscommon/webroot/cgi-bin">

c. Save your changes.

...........................................................................................................................................................................

17 Navigate to the $VSHOME/vscommon/apache/bin directory.

...........................................................................................................................................................................

18 At the command line enter su, then provide the server’s root password when prompted.

...........................................................................................................................................................................


Result: The batch file:

• Changes the VitalSuite Performance Management registry to enable SSL

• Restarts the Apache server with SSL by using the apachectl script

...........................................................................................................................................................................

20 Open your Web Console and click Regenerate on each page of the Console to update pages that were previously cached.

Important! Some links on the My Vital page might remain insecure and direct you to cached data until the nightly synchronization takes place.

...........................................................................................................................................................................E N D O F S T E P S

If you want to... Run the following script

Utilize port 80, which is the default behavior for VitalSuite Performance Management

./vssslctl enable

Disable port 80 ./vssslctl_secure enable

....................................................................30

..........................................................................................................................................................................................Disable Secure Socket Layer on UNIX

When to use

Use this procedure to disable SSL on a UNIX-based VitalSuite Performance Management server.

Before you begin

You should plan to disable SSL during non-business hours when your VitalSuite Performance Management servers are not being used.

Related information



• “SSL software and directory structure on UNIX”, on page 26.

Procedure

To disable SSL on a Windows-based VitalSuite Performance Management server:

...........................................................................................................................................................................

1 In a terminal window, log into your UNIX system as vsadm.

...........................................................................................................................................................................

2 Go to the $VSHOME/vscommon/apache/bin directory.

...........................................................................................................................................................................

3 At the command line enter su, then provide the server’s root password when prompted.

...........................................................................................................................................................................


Result: The following actions are performed:

• Changes the VitalSuite Performance Management registry to disable SSL

• Restarts the Apache server without SSL by using the apachectl script

If you use Run the following script

Port 80 (the default port) for VitalSuite Performance Management communication

./vssslctl disable

A port other than 80 for VitalSuite Performance Management communication

./vssslctl_secure disable

....................................................................31

Disable Secure Socket Layer on UNIX

...........................................................................................................................................................................

5 Open your Web Console and click Regenerate on each page of the Console to update pages that were previously cached.

Important! Some links on the My Vital page might remain secure and direct you to cached data until the nightly synchronization occurs.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................32

Secure Shell implementation

..........................................................................................................................................................................................Overview

Purpose

This section describes how to enable Secure Shell (SSH) for UNIX-based VitalSuite NET servers, enabling you to use Secure Shell FTP for your CSV and wireless data sources in VitalSuite NET.

Contents


Introduction to SSH 33

Configure public key authentication for SSH 34

....................................................................33

Introduction to SSH

..........................................................................................................................................................................................Introduction to SSH

Purpose

VitalSuite NET supports the SSH protocol, which enables you to use Secure FTP transfers of CSV and Wireless data to VitalSuite NET data sources.

Refer to the VitalSuite Performance Management Software Administrator’s Guide for information about configuring VitalSuite NET to obtain CSV and wireless data via FTP.

Supported Sun SSH versions

VitalSuite NET supports the use of Sun SSH version 1.0 with SSH protocol version 2.0.

Required SSH installations

To enable SSH for VitalSuite NET, you must install:

• SSH Server on the source FTP server that will transfer data to VitalSuite NET

• SSH client on the VitalSuite NET Polling server receiving data from the source FTP server

SSH packages

You must install the following packages, available on your Solaris installation media:

• SUNWgss—Generic Security Service software

• SUNWtcpd—TCP wrappers

• SUNWzlib—zip compression libraries

• SUNWsshr—client files and utilities for the root (/) directory

• SUNWsshdr—server files and utilities for the root (/) directory

• SUNWsshcu—common source files for the /usr directory

• SUNWsshdu—server files for the /usr directory

• SUNWsshu—client files and utilities for the /usr directory

For instructions to install the SSH packages, refer to your Sun documentation.

Public key authentication

After you have installed the SSH client on the VitalSuite NET Polling server, you must configure the public key authentication for that server. Refer to “Configure public key authentication for SSH”, on page 34 for more information.

Ensure that sshd is running

After you have installed the required SSH clients and files, and you have configured the public key authentication, ensure that the SSH server (/usr/lib/ssh/sshd by default) is running.

....................................................................34

..........................................................................................................................................................................................Configure public key authentication for SSH

When to use

Use this procedure to configure the public key authentication for the servers you plan to use for secure FTP transfers of data to VitalSuite NET.

Before you begin

Ensure that you have installed the Solaris server, client, and packages listed in “Introduction to SSH”, on page 33.

Related information

For more information about SSH refer to:

• Your Sun documentation

• “Introduction to SSH”, on page 33

Procedure

To configure public key authentication for SSH:

...........................................................................................................................................................................

1 Log in to your VitalSuite NET Polling server as vsadm.

...........................................................................................................................................................................

2 Do one of the following, based on the type of public key authentication you want to use:

...........................................................................................................................................................................

3 When prompted, accept the default file location and use a null passphrase.

Result: For RSA version 2, the public key is written to ~vsadm/.ssh/id_rsa.pub and the private key is written to ~vsadm/.ssh/id_rsa. For DSA, the public key is written to ~vsadm/.ssh/id_dsa.pub and the private key is written to ~vsadm/.ssh/id_dsa.

...........................................................................................................................................................................

4 Change the permissions of the .ssh directory with the following command:chmod 775 ~/.ssh

If you want to use... Enter this command

Rivest, Shamir, and Aldeman (RSA) authentication version 2

ssh-keygen -t rsa

Directory System Authentication (DSA) ssh-keygen -t dsa

....................................................................35

Configure public key authentication for SSH

...........................................................................................................................................................................

5 Append the contents of the ~vsadm/.ssh/id_rsa.pub or ~vsadm/.ssh/id_dsa.pub file on the VitalSuite NET Polling server. to the ~<username>/.ssh/authorized_keys file on the FTP server.

Important! For Secure Shell FTP, the <username> value must match the “FTP User Name” value on the corresponding VitalSuite NET Data Sources page.

...........................................................................................................................................................................

6 Change the permissions of the authorized_keys file on the FTP server with the following command:

chmod 600 ~/.ssh/authorized_keys

...........................................................................................................................................................................E N D O F S T E P S

....................................................................36

Remote authentication server

..........................................................................................................................................................................................Overview

Purpose

This section provides information to help you set up a remote authentication server for your VitalSuite Performance Management environment.

Contents


Introduction 37

Authentication server requirements 38


40

Enable a remote authentication server 42

....................................................................37

Introduction

..........................................................................................................................................................................................Introduction

Overview

You can configure VitalSuite Performance Management to use a remote authentication server to provide access to VitalSuite Performance Management. User names and passwords are stored on the authentication server, enabling you to centralize account information for your applications. The login process appears the same to the user, whether a remote server or local VitalSuite Performance Management authentication is used.

When enabled, the remote authentication server determines whether an account has access to VitalSuite Performance Management. If the remote server determines that access should be allowed, the VitalSuite Performance Management login server provides the appropriate access within VitalSuite Performance Management.

Supported authentication servers

In addition to the default VitalSuite Performance Management authentication mode, VitalSuite Performance Management supports authentication modes for two remote authentication servers: Navis Identity Software and RADIUS.

Important! A special license option is required to use Navis Identity Software with VitalSuite Performance Management. Contact your sales representative if you have not activated this option and would like to use Navis Identity Software to authenticate VitalSuite Performance Management accounts.

Primary and secondary authentication servers

You can define primary and secondary remote authentication servers. The secondary server can authenticate accounts if the primary server is inaccessible. VitalSuite Performance Management allows only one primary server and one secondary server to be defined at any given time. Primary servers cannot be deleted while VitalSuite Performance Management is using an external authentication mode.

If you are using a primary server and want to define a different server as primary, you must first change the current primary server to secondary or standby. During the time between the demotion of the current server and the promotion of the new primary server, attempted user logins will return an error unless VitalSuite NET is using the default local authentication mode.

....................................................................38

..........................................................................................................................................................................................Authentication server requirements

Purpose

This topic discusses the requirements for using a remote authentication server with your VitalSuite Performance Management environment.

Account requirements

For each user, there must be a remote authentication server account and a corresponding local VitalSuite Performance Management account. The Login ID of the account on the remote authentication server must match the User ID of the VitalSuite Performance Management account. If these IDs do not match, the remote server cannot authenticate the account for VitalSuite Performance Management access.

If you do not have administrator access to the remote authentication server, work with the administrator of the remote server to create the appropriate accounts. Refer to your authentication server documentation for information about creating accounts.

In an environment where new accounts must be created for both the remote server and VitalSuite Performance Management, create them first on the remote server, then create the matching account in VitalSuite Performance Management.

If you have an existing remote authentication server, and you have added a new VitalSuite Performance Management installation, you must create the local VitalSuite Performance Management accounts individually. Refer to the VitalSuite Performance Management Software Administrator’s Guide chapter on Account Administration for more information.

If you are using Microsoft IAS as your RADIUS server, ensure that the “Unencrypted Authentication” parameter is selected. Work with your authentication server administrator to ensure the proper configuration.

Administrator requirements

Two types of administrators are required to configure VitalSuite Performance Management to function with remote authentication:

• The administrator of the remote authentication server is responsible for maintaining the user’s login information, and for providing access to VitalSuite Performance Management.

• The VitalSuite Performance Management administrator is responsible for the user’s domain, VitalSuite Performance Management access level (user or administrator), and all other account-specific access within VitalSuite Performance Management.

Password requirements

This topic contains information about the password requirements.

....................................................................39

Authentication server requirements

General information

When remote authentication is enabled, the account passwords on the remote authentication server are used. Local VitalSuite Performance Management passwords are used when the authentication mode is set to Default.

When remote authentication is enabled, only VitalSuite Performance Management administrators can change local passwords. When a non-administrator user attempts to change his or her local password, VitalSuite Performance Management presents a message instructing the user to contact the administrator.

The administrator of the remote authentication server maintains passwords on the remote server. Work with the remote authentication server administrator to update and maintain passwords when using remote authentication.

Password verification process

Passwords are not shared between VitalSuite Performance Management and the remote server. When remote authentication is enabled in VitalSuite Performance Management, the user name and password entered at the login screen are verified by the remote server. The remote server does not verify permissions within VitalSuite Performance Management. The remote server merely verifies that the user’s account has permission to access VitalSuite Performance Management software. Once the remote server has authenticated the account, the VitalSuite Performance Management login server uses the matching local account information to determine what VitalSuite access is granted to that account (such as administrator access, domain association, and UI profiles).

The local VitalSuite Performance Management passwords are used at the login screen only when the local authentication mode is enabled.

Password changes with Navis Identity Software

Navis Identity Software administrators can configure passwords to expire. When a user attempts to log in to VitalSuite Performance Management with an expired password, a new window prompts the user to enter the login ID and expired password. The user is then redirected to a Change Password page on the remote authentication server. After changing the password, the user must open a new browser to log in to VitalSuite Performance Management.

Important! There is no guarantee that the Navis Identity Software server is using Secure Socket Layer (SSL). Be aware that if you are using SSL with VitalSuite Performance Management, the change-password process can occur in a non-secure environment. If this is a concern, work with the administrator of the remote authentication server to configure passwords that do not expire.

....................................................................40

Create an import file of your VitalSuite Performance Management

..........................................................................................................................................................................................accounts

When to use

If you have existing VitalSuite Performance Management accounts and have added a new Navis Identity Software authentication server, use this procedure to run the vslistuser command-line utility to create a text file of VitalSuite Performance Management accounts that the Navis administrator can import to the remote server. The utility is located in the <install_dir>/vscommon/program directory

The vslistuser utility produces output only for Navis Identity Software authentication servers.

Before you begin

You must have your Navis server configured before using the vslistuser utility. The utility cannot create the import file of accounts until the Navis Identity authentication server has been set up and configured.

Related information

Refer to your Navis documentation for information about the Navis Identity authentication server.

Procedure

To create an import file of your VitalSuite Performance Management accounts:

...........................................................................................................................................................................

1 Open a command prompt on the System Master server.

...........................................................................................................................................................................

2 Run the following command depending on your operating system:

Windows: vslistuser <product> <password> <domain_admin-user> <output>

UNIX: vslistuser <password> <domain_admin-user> <output>

Additional information: Refer to “Command description”, on page 41 for a description of the command operands.

...........................................................................................................................................................................

3 Provide the output file (default name is vsusers.csv) to your Navis administrator so they import the accounts to the Navis Identity authentication server.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................41


Command description

The following table describes the operands of the vslistuser command.

Operand Description

<product> The <product> can be vn (for VitalSuite NET), va (for VitalSuite APPS Analysis functionality), or vh (for VitalSuite APPS Help functionality). Specify the product that serves as your System Master server. On UNIX this option is not used, because only VitalSuite NET is supported on UNIX.

<password> The <password> becomes the default password for all accounts on the Navis server. Before running vslistuser, contact the Navis administrator to learn the password requirements of the remote server. For example, the Navis server might impose a minimum character-length for all passwords.

<domain_admin-user> The <domain_admin-user> specifies the type of account VitalSuite Performance Management domain administrators will have on the Navis server. If you specify admin, domain administrators will gain the permissions of Navis administrators once the text file is Imported to the Navis server. If you specify user, domain administrators will have the same permissions on the Navis server as non-administrator users.

<output> The <output> specifies the name of the output file. This option is not required, and defaults to vsusers.csv.

....................................................................42

..........................................................................................................................................................................................Enable a remote authentication server

When to use

Use this procedure to enable a remote authentication server for your VitalSuite Performance Management environment.

Before you begin

Make sure that the primary remote authentication server is configured and that all accounts exist on both the remote server and VitalSuite Performance Management.

If you are using Navis Identity Software, make sure that your VitalSuite Performance Management license grants use of Navis Identity Software. You can check your license options by clicking the ADMIN tab, clicking the Servers link, and opening the License Key page.

If you are using RADIUS instead of Navis Identity Software, when configuring your authentication server ensure that the NAS Identifier and Secret string are the same for each VitalSuite Performance Management server. An Application ID field is required on the form that enables you to define a remote authentication server in VitalSuite Performance Management. Use the NAS Identifier value for the Application ID field. Refer to your RADIUS documentation for more information about the NAS Identifier and Secret string.

Related information

Refer to your remote authentication server documentation for information about configuring the remote server.

Procedure

To enable remote authentication in VitalSuite Performance Management:

...........................................................................................................................................................................

1 Ensure that you are logged into the System Master server as a global administrator. Use your local VitalSuite Performance Management account password for this login.

Important! You need only enable remote authentication on the System Master server. VitalSuite Performance Management propagates the update to the other servers.

...........................................................................................................................................................................

2 Enter the following URL in your browser, where <server_name> is the System Master server: http://<server_name>/cgi-bin/vscsocfgmgr.cgi

Result: The Authentication Mode page displays:

....................................................................43

Enable a remote authentication server

...........................................................................................................................................................................

3 Use the Authentication Mode page to specify the appropriate mode of account authentication.

Additional information

When the Default mode is used, accounts are authenticated using the local information available in the Accounts page of the ADMIN tab. You can use the Authentication Mode page to switch the login mode to local in the event your remote servers are not available.

Before selecting an authentication mode, however, you must configure a remote authentication server.

...........................................................................................................................................................................

4 Click Remote Authentication Server in the menu pane.

...........................................................................................................................................................................

5 Use the Remote Authentication Server page to edit, delete, and add remote authentication servers from your VitalSuite Performance Management environment.

Additional information

You can define only one primary authentication server and one secondary authentication server. You cannot delete a server that is designated as the primary authentication server.

To edit the definitions of a remote authentication server, select the server name from the list and click Edit.

To delete a remote authentication server from your VitalSuite Performance Management environment, select the server name from the list and click Delete.

...........................................................................................................................................................................

6 Click New.

Result: The Remote Authentication Server: New page displays:

....................................................................44

...........................................................................................................................................................................

7 Fill in the fields on the page.

Additional information: For a description of each field on this page, refer to “Remote Authentication Server: New field descriptions.”, on page 45.

...........................................................................................................................................................................

8 Click Submit to add the remote authentication server.

...........................................................................................................................................................................

9 Click Authentication Mode in the menu pane.

...........................................................................................................................................................................

10 Select the authentication mode you want to use, then click Submit.

Important! If the primary and secondary remote authentication servers are inaccessible, users will not have access to VitalSuite Performance Management. If this happens, open the Authentication Mode page and set the mode to VitalSuite Default to enable users to log into VitalSuite Performance Management using their local account information.

...........................................................................................................................................................................

11 To begin using the new remote authentication server account information immediately, close the browser to log out, then open a new browser and log into VitalSuite Performance Management using the remote authentication server account information.

Important! The vscsocfgmgr page does not include a logout function.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................45

Enable a remote authentication server

Remote Authentication Server: New field descriptions.

The following table describes the fields on the Remote Authentication Server: New page.

Field Description

Server Name The remote authentication server’s host name or IP address.

Port The port number through which VitalSuite Performance Management can communicate with the remote authentication server. The default is 1645.

Secret The verification string used by the remote authentication server. Refer to your authentication server documentation for more information about the Secret string.

Application ID The identification string of the remote authentication server. This is used to validate the authentication request made by VitalSuite Performance Management.This is known as the NAS Identifier for RADIUS servers.Refer to your authentication server documentation for more information about the Application ID and NAS Identifier.

Mode The function of the remote authentication server.• Primary—indicates the server is the first to be accessed for account

authentication.• Secondary—indicates the server is to be used in the event the primary server

cannot authenticate the account.• Standby—indicates the server is not active, but remains configured for future

use as a primary or secondary server.You can define one primary server, one secondary server, and multiple standby servers.

Retry The number of authentication attempts the primary server makes before the secondary server is used.

Timeout The time between failed authentication attempts. The default time is three seconds.

....................................................................46

....................................................................47

3 VitalSuite Performance Management IP address changes

..........................................................................................................................................................................................Overview

Purpose

This chapter describes how to change the IP address of a VitalSuite Performance Management server.

Impact of an IP address change

It is recommended that IT administrators not change the addresses of their VitalSuite Performance Management servers due to the complexity of the process. Changing the address of a server can result in the following issues:

• Causes the VitalSuite Performance Management license keys to be invalid

• Disrupts clients’ configured targets of where to post their data

• Makes database access inoperable as IP addresses can be hard-coded in the database in cases where self-identity is not configured with DNS

If such changes are unavoidable, strictly follow the guidelines in this section.

Before you begin

Before you change the IP address of any VitalSuite Performance Management server, do the following:

• Back up all VitalSuite Performance Management data as described in Chapter 8, “Back up and restore”.

• Obtain a new VitalSuite Performance Management license key if you change the address of the System Master server.

Each VitalSuite Performance Management license key is associated with your Master server’s static IP address so your existing license key will be invalid if you change the Master server to a new address. If you change the address of an Aggregation or Polling server in a distributed environment, a new license key is not needed.

....................................................................48

Required knowledge

Changing the address of a VitalSuite Performance Management server requires you to modify your system’s registry and update the SQL Server databases that contain your system’s IP address and VitalSuite Performance Management license key. You need to be familiar with database concepts and SQL scripts to complete these tasks.

Contents

This chapter discusses the following topics:

Change VitalSuite NET IP addresses on Windows 50

Change the IP address of a single VitalSuite NET server on Windows 51

Change the IP addresses of distributed VitalSuite NET servers on Windows

51

Change VitalSuite NET IP addresses on UNIX 60

Change the IP address of a single VitalSuite NET server on UNIX 61

Change the IP addresses of distributed VitalSuite NET servers on UNIX 64

Update the Master Server databases 66

Update the Aggregation Server databases 68

Update the Polling Server databases 71

Update the Reporting Server databases 74

Change the IP addresses of VitalSuite APPS servers 77

Process overview 78

Direct existing VitalAgents to post to a new IP address 79

Update the Configuration server IP address 81

Delete obsolete source addresses in VSSyncTimeTable 83

Update the VitalSuite APPS databases with the new IP address 85

Scenario 1: VitalSuite APPS Analysis and Help on the same machine 86

Scenario 2: VitalSuite APPS Analysis and Help on two separate machines 89

Scenario 3: Distributed VitalSuite APPS Analysis environment 92

Change the VitalSuite APPS Analysis server IP address and edit the registry

94

....................................................................49

Overview

Change the VitalSuite APPS Help IP address by re-installing the product 96

Update VitalAgentIT clients to target a new address 98

Correct DSN connections on Windows 100

Update and test VitalSuite Performance Management DSNs 101

VitalSuite Performance Management DSNs 106

....................................................................50

Change VitalSuite NET IP addresses on Windows

..........................................................................................................................................................................................Overview

Purpose

This section describes how to change the IP address of a VitalSuite NET system in a single-server and distributed environment on Windows and UNIX platforms.

Contents


Change the IP address of a single VitalSuite NET server on Windows 51


54

....................................................................51

Change the IP address of a single VitalSuite NET server on Windows

..........................................................................................................................................................................................Change the IP address of a single VitalSuite NET server on Windows

When to use

Use this procedure to change the IP address of a single VitalSuite NET Windows server (VitalSuite NET Master, Polling, and Aggregation servers all on the same system).

Before you begin

Make sure that you have obtained a new license key for your VitalSuite NET server based on the new IP address. For more information on how to obtain a new key, refer to the VitalSuite Performance Management Software Administrator’s Guide.

Make sure that you can connect to the MS-SQL Server databases using SQL Query Analyzer. In most cases you can use the dba account with the password sql.

Related information

For information about changing the IP address of distributed VitalSuite NET servers, refer to “Change the IP addresses of distributed VitalSuite NET servers on Windows”, on page 54.

Procedure

To change the address of a VitalSuite NET server on Windows:

...........................................................................................................................................................................

1 Change the IP address of the VitalSuite NET server.

Important! VitalSuite NET servers require static IP addresses.

...........................................................................................................................................................................

2 Update the VitalSuite NET server’s registry key as follows:

a. Enter regedit at a command prompt to display the Registry Editor.

b. Go to the HKEY_LOCAL_MACHINE\Software\VitalSuiteCommon directory.

c. Right-click on the VSInstallIP field, and select Modify.

Result: The Edit Sharing window opens.

d. Enter the new IP address of your VitalSuite NET server, and click OK.

...........................................................................................................................................................................

3 Update the VNMaster, VNAggr and VNPoller databases with the new address and license key. To run this script, follow these steps:

a. Log in to the SQL database on the VitalSuite NET server.

b. Using Query Analyzer, enter the SQL commands for each VitalSuite NET database, as listed in “Update scripts for a single VitalSuite NET Windows server”, on page 52. Before you run each command, replace items in angle brackets with the specified information.

....................................................................52

...........................................................................................................................................................................

4 Run the following commands to stop the sync processes:<install>\VSCommon\program\VSSyncCtl stop<install>\VitalNet\Program\RTSyncStop

Result: The sync processes stop, and will be automatically restarted within 5 minutes.

...........................................................................................................................................................................

5 Stop the Tomcat service on Windows.

...........................................................................................................................................................................

6 Restart the Tomcat service, then wait 2 minutes.

...........................................................................................................................................................................

7 Update the DSN connections as described in “Correct DSN connections on Windows”, on page 100.

...........................................................................................................................................................................

8 Verify that your existing firewall policies for VitalSuite NET still apply to the new address.

...........................................................................................................................................................................E N D O F S T E P S

Update scripts for a single VitalSuite NET Windows server

The following table provides the scripts to run on each VitalSuite NET database to update the server’s IP address.

VNMaster Database

use VNMASTER update dba.vsMasterTable set serverAddress = ‘<new_address>' where serverRole = 'VNMASTER' go update dba.vnAggrTable set aggrAddress = '<new_address>' where aggrAddress = '<old_address>' go update dba.vnLicenseKeyTable set serverkey = ‘<new_key>’, ServerAddr = '<new_address>’ go

VNAggr Database

use VNAGGR update dba.vsMasterTable set serverAddress = ‘<new_address>' where serverRole = 'VNMASTER' go update dba.vnAggrTable set aggrAddress = '<new_address>' where aggrAddress = '<old_address>' go update dba.vnPollerDSNTable set PollerAddress = '<new_address>' where PollerAddress = '<old_address>' go update dba.vnPollerDSNTable set PollerDSN = 'ToPollerDSN_<new_address>' where PollerAddress = '<new_address>' go update dba.vnLicenseKeyTable set serverkey = ‘<new_key>’, ServerAddr = '<new_address>’ go

....................................................................53

Change the IP address of a single VitalSuite NET server on Windows

VNPoller Database

use VNPOLLER update dba.vnPollerDSNTable set PollerAddress = '<new_address>' where PollerAddress = '<old_address>' go update dba.vnPollerDSNTable set PollerDSN = 'ToPollerDSN_<new_address>' where PollerAddress = '<new_address>’ go update dba.vnLicenseKeyTable set serverkey = ‘<new_key>’, ServerAddr = '<new_address>’ go

....................................................................54

Change the IP addresses of distributed VitalSuite NET servers on

..........................................................................................................................................................................................Windows

When to use

Use this procedure to change the IP address of each server in your distributed VitalSuite NET environment (Master, Aggregation, and Polling servers on separate systems).

The procedure in this topic assumes you are changing every address in your distributed VitalSuite NET environment. If you are not changing the address of a particular machine, you do not need to run the commands that ask you for the new address when updating the VitalSuite NET databases on that machine. For example, if you have a machine that runs only an Aggregation server, and you are not changing the address of that machine, when you run the procedures in the following sections you do not need to run the commands that prompt you for a <new_aggr_address>.

Before you begin

Note the following before changing the address of your VitalSuite NET servers:

• Obtain a new VitalSuite NET license key based on the new IP address of the VitalSuite NET Master server. For more information on how to obtain a new key, refer to the VitalSuite Performance Management Software Administrator’s Guide.

• Write down each server’s old and new address so you can refer to this information when updating the VitalSuite NET databases.

• Your VitalSuite NET server(s) must have static addresses.

• Change the addresses of your servers in as short a time span as possible.

• Change the address of each system in the following order:

a. Master server

b. Reporting servers (if installed)

c. Aggregation servers

d. Polling servers

For example, complete all steps for changing the address on the Master server before you proceed to changing the address of the Reporting or Aggregation server.

Make sure you can connect to the MS-SQL Server databases using SQL Query Analyzer. In most cases you can use the dba account with the password sql.

Related information

For information about changing the IP address of a single VitalSuite NET server, refer to “Change the IP address of a single VitalSuite NET server on Windows”, on page 51.

....................................................................55


Procedure

To change the address of each server in a distributed VitalSuite NET environment on Windows:

...........................................................................................................................................................................

1 Change the address of the VitalSuite NET server. On Windows you can change your system’s address from the Control Panel.

...........................................................................................................................................................................

2 Update the VitalSuite NET server’s registry key as follows:

a. Enter regedit at a command prompt to display the Registry Editor.

b. Go to HKEY_LOCAL_MACHINE\Software\VitalSuiteCommon.

c. Right-click on the VSInstallIP field, and select Modify to display the Edit Sharing window.

d. Enter the server’s new IP address, and select OK.

...........................................................................................................................................................................

3 Use the appropriate script to update the databases on your VitalSuite NET server. To run a script, follow these steps:

a. Log in to the SQL database on the VitalSuite NET server you are updating with the new address.

b. From Query Analyzer, open the appropriate script.

The Master_update.sql script updates the necessary databases on the VitalSuite NET Master server, the Reporting_update.sql script updates the databases on the Reporting server (if installed), the Aggr_update.sql script updates the databases on the Aggregation servers, and the Poller_update.sql script updates the databases on the Polling servers.

c. Manually replace the values in brackets with the specified information.

Refer to “Update scripts for a distributed VitalSuite NET environment”, on page 57 for the contents of each script.

...........................................................................................................................................................................

4 Run the script.

...........................................................................................................................................................................

5 Run the following commands to stop the sync processes:<install>\VSCommon\program\VSSyncCtl stop<install>\VitalNet\Program\RTSyncStop


...........................................................................................................................................................................

6 Stop the Tomcat service on Windows.

...........................................................................................................................................................................

7 Restart the Tomcat service, then wait 2 minutes.

....................................................................56

...........................................................................................................................................................................

8 Repeat the steps in this section on each Master, Reporting (if installed), Aggregation, and Polling server affected by the address change.

...........................................................................................................................................................................

9 Update the DSNs as described in “Correct DSN connections on Windows”, on page 100.

...........................................................................................................................................................................

10 Verify that your existing firewall policies for VitalSuite NET still apply to the new IP addresses.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................57


Update scripts for a distributed VitalSuite NET environment

The following table provides the scripts for updating each server in your distributed VitalSuite NET Windows environment.

Script Contents Description

Master Server (Master_update.sql)

use VNMASTERupdate dba.vsMasterTable set serverAddress = '<new_master_address>' where serverRole = 'VNMASTER' go

Updates the vsMasterTable with the Master server’s new address.

use VNMASTER update dba.vnlicenseKeyTable set serverkey = '<new_key>', ServerAddr = '<new_master_address>' go

Updates the vnLicenseKeyTable with the Master server’s new IP address and license key.

Important! This must be the IP address and not the fully-qualified domain name.

use VNMASTERupdate dba.vnAggrTable set aggrAddress = '<new_aggr1_address>' where aggrAddress = '<old_aggr1_address>' go

Updates the vnAggrTable with the new address of the first Aggregation server.

use VNMASTER update dba.vnAggrTable set aggrAddress = '<new_aggr2_address>' where aggrAddress = '<old_aggr2_address>' go

Updates the vnAggrTable with the new address of the second Aggregation server. If only one Aggregation server is installed, delete this section of the script. If more than two Aggregation servers are installed, duplicate this section of the script for each additional Aggregation server.

use VNMASTERupdate vsReportingServerTable set serverAddress = ‘<new_reporting_address>’ where serverAddress = '<old_reporting_address>' go

Updates the vsReportingServerTable with the new address of the Reporting server.

Important! Do not run this script if you do not have a Reporting server installed.

Aggregation Server (Aggr_update.sql)

use VNAGGR update dba.vsMasterTable set serverAddress = '<new_master_address>' where serverRole = 'VNMASTER' go

Updates the vsMasterTable with the new address of the Master server.

....................................................................58

use VNAGGR update dba.vnAggrTable set aggrAddress = '<new_aggr_address>' where aggrAddress = '<old_aggr_address>' go

Updates the vnAggrTable with the new address of the Aggregation server.

use VNAGGRupdate dba.vnLicenseKeyTable set serverkey = '<new_key>', ServerAddr = '<new_master_address>' go

Updates the vnLicenseKeyTable with the new license key and the IP address of the Master server.

use VNAGGR update dba.vnPollerDSNTable set PollerAddress = '<new_poller1_address>' where PollerAddress = '<old_poller1_address>' go

Updates the vnPollerDSNTable with the new IP address of Polling server #1.

use VNAGGR update dba.vnPollerDSNTable set PollerDSN = 'ToPollerDSN_<new_poller1_address>' where PollerAddress = '<new_poller1_address>' go

Updates the vnPollerDSNTable with the new DSN name of Polling server #1.

use VNAGGR update dba.vnPollerDSNTable set PollerAddress ='<new_poller2_address>' where PollerAddress = '<old_poller2_address>' go

Updates the vnPollerDSNTable with the new IP address of Polling server #2.If this Aggregation server has only one Polling server, delete this section of the script. If this Aggregation server has more than two Polling servers, duplicate this section of the script for each additional Polling server.

use VNAGGR update dba.vnPollerDSNTable set PollerDSN = 'ToPollerDSN_<new_poller2_address>' where PollerAddress = '<new_poller2_address>' go

Updates the vnPollerDSNTable with the new DSN name of Polling server #2.If this Aggregation server has only one Polling server, delete this section of the script. If this Aggregation server has more than two Polling servers, duplicate this section of the script for each additional Polling server.

use VNAGGRupdate vsReportingServerTable set serverAddress = ‘<new_reporting_address>’ where serverAddress = '<old_reporting_address>' go


Important! Do not run this script if you do not have a Reporting server installed.


....................................................................59


Polling Server (Poller_update.sql)

use VNPOLLER update dba.vnPollerDSNTable set PollerAddress = ' <new_poller_address>' where PollerAddress = '<old_poller_address>' go

Updates the vnPollerDSNTable with the Polling server’s new address.

use VNPOLLER update dba.vnPollerDSNTable set PollerDSN = 'ToPollerDSN_<new_poller_address>’ where PollerAddress = '<new_poller_address>' go

Updates the vnPollerDSNTable with the Polling server’s new DSN.

use VNPOLLERupdate dba.vnLicenseKeyTable set serverkey = '<new_key>', ServerAddr = '<new_master_address>' go

Updates the vnLicenseKeyTable with the new license key and IP address of the Master server.

Reporting Server (Reporting_update.sql)

use VNMASTER update dba.vsMasterTable set serverAddress = '<new_master_address>' where serverRole = 'VNMASTER' go

Updates the vsMasterTable with the Master server’s new address.

use VNMASTER update dba.vnLicenseKeyTable set serverkey = '<new_key>', ServerAddr = '<new_master_address>' go

Updates the vnLicenseKeyTable with the Master server’s new license key and IP address

use VNMASTER update dba.vnAggrTable set aggrAddress = '<new_aggr1_address>' where aggrAddress = '<old_aggr1_address>' go

Updates the vnAggrTable with the new address of the Aggregation server.

use VNMASTERupdate dba.vsReportingServerTable set serverAddress = '<new_reporting_address>' where serverAddress = '<old_reporting_address>'



....................................................................60

Change VitalSuite NET IP addresses on UNIX

..........................................................................................................................................................................................Overview

Purpose

This section describes how to change the IP addresses on all the VitalSuite NET servers in a distributed UNIX environment.

Contents

This section covers the following topics:

Change the IP address of a single VitalSuite NET server on UNIX 61

Change the IP addresses of distributed VitalSuite NET servers on UNIX 64

Update the Master Server databases 66

Update the Aggregation Server databases 68

Update the Polling Server databases 71

Update the Reporting Server databases 74

....................................................................61

Change the IP address of a single VitalSuite NET server on UNIX

..........................................................................................................................................................................................Change the IP address of a single VitalSuite NET server on UNIX

When to use

Use this procedure to change the IP address of a single VitalSuite NET UNIX server (VitalSuite NET Master, Polling, and Aggregation servers all on the same system).

Before you begin

Obtain a new VitalSuite NET license key based on the new IP address. For more information on how to obtain a new key, refer to the VitalSuite Performance Management Software Administrator’s Guide.

Important! Although this procedure uses sqlplus as the SQL editor, you can use any SQL editor to run the listed commands.

Related information

For information about changing the IP address of distributed VitalSuite NET servers, refer to “Change the IP addresses of distributed VitalSuite NET servers on UNIX”, on page 64.

Procedure

To change the address of a VitalSuite NET server on UNIX:

...........................................................................................................................................................................

1 Change the IP address of the VitalSuite NET server. (Consult your UNIX documentation and vendor for details about changing your IP address.)

Important! VitalSuite NET servers require static IP addresses.

...........................................................................................................................................................................

2 Open a terminal to your VitalSuite NET system and log in as vsadm.

...........................................................................................................................................................................

3 Update the VitalSuite NET server registry key as follows:

a. In a text editor, open $REGISTRY_DIR/HKEY_LOCAL_MACHINE/SOFTWARE/VitalSuiteCommon/param.dat.

b. Edit the VSInstallIP line to include the new IP address.

Example: “VSInstallIP” “10.10.10.2” “1”

c. Save the param.dat file and close your text editor.

...........................................................................................................................................................................

4 Update VNMaster, VNAggr, VNPoller databases:

a. Run sqlplus and connect as vnmdba with a password of sql.

b. Run the series of queries on each of the database tables as provided in “Scripts to update the VitalSuite NET databases”, on page 63.

....................................................................62

...........................................................................................................................................................................

5 Update the Poller and Aggr DSNs by running the following commands, where <new_address> is the new address:

$VSHOME/vscommon/webroot/cgi-bin/vsadddsn.cgi ToPollerDSN_<new_address> <new_address> VNPOLLER$VSHOME/vscommon/webroot/cgi-bin/vsadddsn.cgi VNAGGR <new_address> VNAGGR

...........................................................................................................................................................................

6 Enter the new VitalSuite NET license key based on the new IP address. For information on how to obtain a new license key, refer to the VitalSuite Performance Management Software Administrator’s Guide.

...........................................................................................................................................................................

7 Reboot your system.

...........................................................................................................................................................................

8 Run the following commands to stop the sync processes:$VSHOME/vscommon/program/VSSyncCtl.sh stop$VSHOME/vitalnet/program/RTSyncStop.sh


...........................................................................................................................................................................

9 Run the following command to stop the Tomcat process:$VSHOME/vscommon/jakarta-tomcat/bin/shutdown.sh

...........................................................................................................................................................................

10 Run the following command to restart the Tomcat process:$VSHOME/vscommon/jakarta-tomcat/bin/startup.sh

...........................................................................................................................................................................

11 Verify that your existing firewall policies for VitalSuite NET still apply to the new addresses.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................63

Change the IP address of a single VitalSuite NET server on UNIX

Scripts to update the VitalSuite NET databases

The following table provides the scripts to run to update your VitalSuite NET databases with the new IP address.

Update vsMasterTable on the VNMaster and VNAggr Databases

update vsMasterTable set serverAddress = ‘<new_address>' where serverRole = 'VNMASTER'

Update VNAggrTable on the VNMaster and VNAggr Databases

update vnAggrTable set aggrAddress = ‘<new_address>’ where aggrAddress = ‘<old_address>’;

Update the VNPollerDSNTable on the VNAggr and VNPoller Databases

update vnPollerDSNTable set PollerAddress = ‘<new_address>’, PollerDSN = ‘ToPollerDSN_<new_address>’ where PollerDSN = ‘ToPollerDSN_<old_address>’;

Update VNLicenseKeyTable on VNMASTER, VNAggr, VNPoller Databases

update vnlicenseKeyTable set serverkey = ‘<new_key>’, ServerAddr = ‘<new_address>’;

....................................................................64

Change the IP addresses of distributed VitalSuite NET servers on

..........................................................................................................................................................................................UNIX

When to use

Use this procedure to update your VitalSuite NET databases with the new IP address of each UNIX system in your distributed environment.

The procedure in this topic assumes you are changing every address in your distributed VitalSuite NET environment. If you are not changing the address of a particular machine, you do not need to run the commands that ask you for the new address when updating the VitalSuite NET databases on that machine. For example, if you have a machine that runs only an Aggregation server, and you are not changing the address of that machine, when you run the procedures in the following sections you do not need to run the commands that prompt you for a <new_aggr_address>.

Before you begin

Follow these guidelines when changing the address of your VitalSuite NET systems:

• Obtain a new VitalSuite NET license key based on the new IP address of the Master server. For information on how to obtain a new license key, refer to the VitalSuite Performance Management Software Administrator’s Guide.

• Write down each server’s old and new address so you can refer to this information when updating the VitalSuite NET databases.

• Your VitalSuite NET server(s) must have static addresses.

• Change the addresses of your servers in as short a time span as possible.

Related information

For information about changing the IP address of a single (non-distributed) VitalSuite NET system, refer to “Change the IP address of a single VitalSuite NET server on UNIX”, on page 61.

Procedure

To change the IP address of each server in your distributed VitalSuite NET UNIX environment:

...........................................................................................................................................................................

1 Change the IP address of your VitalSuite NET Master server and then update the Master server databases as described in “Update the Master Server databases”, on page 66.

...........................................................................................................................................................................

2 Change the IP address of each Aggregation server and then update the Aggregation server databases as described in “Update the Aggregation Server databases”, on page 68.

...........................................................................................................................................................................

3 Change the IP address of each Polling server and then update the Polling server databases as described in “Update the Polling Server databases”, on page 71.

....................................................................65

Change the IP addresses of distributed VitalSuite NET servers on UNIX

...........................................................................................................................................................................

4 Change the IP address of your Reporting server (if installed) and then update the Reporting server databases as described in “Update the Reporting Server databases”, on page 74.

...........................................................................................................................................................................

5 Enter the new VitalSuite NET license key based on the new IP address of the Master server. Refer to the VitalSuite Performance Management Software Administrator’s Guide for more information.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................66

..........................................................................................................................................................................................Update the Master Server databases

When to use

Use this procedure to update the VitalSuite NET Master server database with the new IP addresses of the VitalSuite NET servers.

Before you begin

Make sure you have already changed the IP address of each VitalSuite NET system. The procedure in this topic is for updating the VitalSuite NET master database after an IP address change has occurred.

Related information

For more information on changing the IP address of your VitalSuite NET UNIX server, refer to “Change the IP addresses of distributed VitalSuite NET servers on UNIX”, on page 64.

Procedure

To update the Master server with the new IP address in your distributed VitalSuite NET environment on UNIX:

...........................................................................................................................................................................

1 Open a terminal to your VitalSuite NET Master server, and log in as vsadm.

...........................................................................................................................................................................






...........................................................................................................................................................................

3 Run sqlplus, and connect as vnmdba with a password of sql.

...........................................................................................................................................................................

4 Update the tables on the Master server as follows:

a. Enter the following command, where <new_master_address> is the new address of the Master server:update vsMasterTable set serverAddress = ‘<new_master_address>’ where serverRole = ‘VNMASTER’;

....................................................................67

Update the Master Server databases

b. Perform this step only if you changed the IP Address of an Aggregation server.

For each Aggregation server connecting to this Master server, enter the following command, where <new_aggr_address> is the new address of the Aggregation server and <old_aggr_address> is the original address of the Aggregation server:update vnAggrTable set aggrAddress = ‘<new_aggr_address>’ where aggrAddress = ‘<old_aggr_address>’;

c. Enter the following command, where <new_key> is the new license key and <new_master_address> is the new IP address of the Master server:update vnlicenseKeyTable set serverkey = ‘<new_key>’,ServerAddr = ‘<new_master_address>’;

d. Perform this step only if you changed the IP Address of a Reporting server.

If you have a Reporting server in your environment, enter the following command, where <new_reporting_address> is the new address of the Reporting server and <old_reporting_address> is the original address of the Reporting server:update vsReportingServerTable set serverAddress = ‘<new_reporting_address>’ where serverAddress = ‘<old_reporting_address>’;

...........................................................................................................................................................................

5 Exit sqlplus.

...........................................................................................................................................................................

6 Reboot your system.

...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................

10 Proceed to “Update the Aggregation Server databases”, on page 68.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................68

..........................................................................................................................................................................................Update the Aggregation Server databases

When to use

Use this procedure to update the VitalSuite NET Aggregation server databases in your UNIX environment.

Before you begin

Make sure you have completed the following tasks:

• Changed the IP address of the VitalSuite NET Aggregation server(s).

• Updated the Master Server database as described in “Update the Master Server databases”, on page 66.

Related information

For more information about changing the IP address of a VitalSuite NET UNIX server, refer to “Change the IP addresses of distributed VitalSuite NET servers on UNIX”, on page 64.

Procedure

To update each Aggregation server with the new address in your distributed VitalSuite NET environment on UNIX:

...........................................................................................................................................................................

1 Open a terminal on a machine containing a VitalSuite NET Aggregation server, and log in as vsadm.

...........................................................................................................................................................................






...........................................................................................................................................................................

3 Run sqlplus, and connect as vnadba with a password of sql.

...........................................................................................................................................................................

4 Update the database tables on the Aggregation server as follows;

a. Perform this step only if you changed the IP Address of the Master server.

Enter the following command, where <new_master_address> is the new address of the Master server:update vsMasterTable set serverAddress = ‘<new_master_address>’ where serverRole = ‘VNMASTER’;

....................................................................69

Update the Aggregation Server databases

b. Enter the following command, where <new_aggr_address> is the new address of the Aggregation server and <old_aggr_address> is the original address:update vnAggrTable set aggrAddress = ‘<new_aggr_address>’ where aggrAddress = ‘<old_aggr_address>’;

c. Perform this step only if you changed the IP Address of a Polling server.

For each Polling server connecting to this Aggregation server, enter the following command, where <new_poller_address> is the new address of the Polling server and <old_poller_address> is the original address. update vnPollerDSNTable set PollerAddress = ‘<new_poller_address>’, PollerDSN = ‘ToPollerDSN_<new_poller_address>’ where PollerDSN = ‘ToPollerDSN_<old_poller_address>’;

d. Perform this step only if you changed the IP Address of the Master server.

Enter the following command, where <new_key> is the new license key and <new_master_address> is the new IP address of the Master server:update vnlicenseKeyTable set serverkey = ‘<new_key>’, ServerAddr = ‘<new_master_address>’;

e. Perform this step only if you changed the IP Address of a Reporting server.

If you have a Reporting server in your environment, enter the following command, where <new_reporting_address> is the new address of the Reporting server and <old_reporting_address> is the original address.update vsReportingServerTable set serverAddress = ‘<new_reporting_address>’ where serverAddress = ‘<old_reporting_address>’;

...........................................................................................................................................................................

5 Exit sqlplus.

...........................................................................................................................................................................

6 Update the Aggregation server’s DSN in the odbc.ini file by typing the following command, where <new_aggr_address> is the new IP address:

$VSHOME/vscommon/webroot/cgi-bin/vsadddsn.cgi VNAGGR <new_aggr_address> VNAGGR

...........................................................................................................................................................................

7 Perform this step only if you changed the IP Address of a Polling server.

For each Polling server connecting to this Aggregation server, update the Polling server’s DSN in the odbc.ini file by typing the following command, where <new_poller_address> is the new address of the Polling server:

$VSHOME/vscommon/webroot/cgi-bin/vsadddsn.cgi ToPollerDSN_<new_poller_address> <new_poller_address> VNPOLLER

Important! You can safely remove the ToPollerDSN_<old_poller_address> DSN value from the odbc.ini file. While it causes no harm, it no longer serves a purpose.

...........................................................................................................................................................................

8 Reboot the system.

....................................................................70

...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................

12 Repeat this procedure for each machine with an Aggregation server, then proceed to “Update the Polling Server databases”, on page 71.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................71

Update the Polling Server databases

..........................................................................................................................................................................................Update the Polling Server databases

When to use

Use this procedure to update the VitalSuite NET Polling Server databases on UNIX.

Before you begin


• Changed the IP address of the VitalSuite NET Polling server(s).

• Updated the databases of the Master and Aggregation Servers as described in the previous topics of this section.

Related information

For more information about changing the IP address of your VitalSuite NET UNIX servers, refer to “Change the IP addresses of distributed VitalSuite NET servers on UNIX”, on page 64.

Procedure

To update each Polling server with the new address in your distributed VitalSuite NET environment on UNIX:

...........................................................................................................................................................................

1 Open a terminal on a machine containing a VitalSuite NET Polling server, and log in as vsadm.

...........................................................................................................................................................................






...........................................................................................................................................................................

3 Run sqlplus, and connect as vnpdba with a password of sql.

...........................................................................................................................................................................

4 Update the database tables on the Polling server as follows;

a. Enter the following command, where <new_poller_address> is the new address of the Polling server and <old_poller_address> is the original address of the Polling server:update vnPollerDSNTable set PollerAddress = ‘<new_poller_address>’, PollerDSN = ‘ToPollerDSN_<new_poller_address>’ where PollerDSN = ‘ToPollerDSN_<old_poller_address>’;

....................................................................72

b. Perform this step only if you changed the IP Address of the Master server.


...........................................................................................................................................................................

5 Exit sqlplus.

...........................................................................................................................................................................

6 Perform this step only if you changed the IP Address of an Aggregation server.

Update the Aggregation server’s DSN in the odbc.ini file by typing the following command, where <new_aggr_address> is the new IP address:

$VSHOME/vscommon/webroot/cgi-bin/vsadddsn.cgi VNAGGR <new_aggr_address> VNAGGR

...........................................................................................................................................................................

7 Update the Polling server’s DSN in the odbc.ini file by typing the following command, where <new_poller_address> is the new address of the Polling server:

$VSHOME/vscommon/webroot/cgi-bin/vsadddsn.cgi ToPollerDSN_<new_poller_address> <new_poller_address> VNPOLLER

Important! You can safely remove the ToPollerDSN_<old_poller_address> DSN value from the odbc.ini file. While it causes no harm, it no longer serves a purpose.

...........................................................................................................................................................................


...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................

12 Repeat this procedure for each machine with a Polling server.

....................................................................73

Update the Polling Server databases

...........................................................................................................................................................................

13 If you have Reporting servers in your environment, proceed to “Update the Reporting Server databases”, on page 74.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................74

..........................................................................................................................................................................................Update the Reporting Server databases

When to use

Use this procedure to update the VitalSuite NET Reporting Server database on UNIX. Many VitalSuite NET environments do not have a Reporting Server installed. If this is the case, you can skip this procedure.

Before you begin


• Changed the IP address of each VitalSuite NET system.

• Updated the databases of the Master, Aggregation and Polling Servers as described in the previous topics of this section.

Related information

For more information about changing the address of your VitalSuite NET UNIX servers, refer to “Change the IP addresses of distributed VitalSuite NET servers on UNIX”, on page 64.

Procedure

To update each Reporting server with the new address in your distributed VitalSuite NET environment on UNIX:

...........................................................................................................................................................................

1 Open a terminal on a machine containing a VitalSuite NET Reporting server, and log in as vsadm.

...........................................................................................................................................................................



b. Edit the VSInstallIP line to include the new IP address. For example:



...........................................................................................................................................................................

3 Run sqlplus, and connect as vnmdba with a password of sql.

....................................................................75

Update the Reporting Server databases

...........................................................................................................................................................................

4 Update the database tables on the Reporting server as follows:

a. Perform this step only if you changed the IP Address of the Master server.

Enter the following command, where <new_master_address> is the new address of the Master server:update vsMasterTable set serverAddress = ‘<new_master_address>’ where serverRole = ‘VNMASTER’;

b. Perform this step only if you changed the IP Address of an Aggregation server.

For each Aggregation server connecting to this Reporting server, enter the following command, where <new_aggr_address> is the new IP address of the Aggregation server and <old_aggr_address> is the original IP address of the Aggregation server:update vnAggrTable set aggrAddress = ‘<new_aggr_address>’ where aggrAddress = ‘<old_aggr_address>’;

c. Enter the following command, where <new_reporting_address> is the new address of the Reporting server and <old_reporting_address> is the original address of the Reporting server:update vsReportingServerTable set serverAddress = ‘<new_reporting_address>’ where serverAddress = ‘<old_reporting_address>’;

d. Perform this step only if you changed the IP Address of the Master server.


...........................................................................................................................................................................

5 Exit sqlplus.

...........................................................................................................................................................................


...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


....................................................................76

...........................................................................................................................................................................

10 Repeat this procedure for each machine with a Reporting server, then reboot.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................77

Overview

Change the IP addresses of VitalSuite APPS servers

..........................................................................................................................................................................................Overview

Purpose

This section defines the procedures for changing the IP address of VitalSuite APPS servers.

Contents


Process overview 78

Direct existing VitalAgents to post to a new IP address 79

Update the Configuration server IP address 81

Delete obsolete source addresses in VSSyncTimeTable 83

Update the VitalSuite APPS databases with the new IP address 85

Scenario 1: VitalSuite APPS Analysis and Help on the same machine 86

Scenario 2: VitalSuite APPS Analysis and Help on two separate machines 89

Scenario 3: Distributed VitalSuite APPS Analysis environment 92


94

Change the VitalSuite APPS Help IP address by re-installing the product 96

Update VitalAgentIT clients to target a new address 98

....................................................................78

..........................................................................................................................................................................................Process overview

Purpose

This topic provides the general process to follow for changing the IP address of your VitalSuite APPS servers.

Process

To change the IP address of a VitalSuite APPS server, follow this process:

5. “Direct existing VitalAgents to post to a new IP address”, on page 79.

6. “Update the Configuration server IP address”, on page 81.

7. “Delete obsolete source addresses in VSSyncTimeTable”, on page 83.

8. “Update the VitalSuite APPS databases with the new IP address”, on page 85.

9. “Change the VitalSuite APPS Analysis server IP address and edit the registry”, on page 94.

10. “Change the VitalSuite APPS Help IP address by re-installing the product”, on page 96.

11. (If applicable) “Update VitalAgentIT clients to target a new address”, on page 98.

12. “Update and test VitalSuite Performance Management DSNs”, on page 101.

....................................................................79

Direct existing VitalAgents to post to a new IP address

..........................................................................................................................................................................................Direct existing VitalAgents to post to a new IP address

When to use

Use this procedure to direct your existing VitalAgents to post data to a new IP address.

Before you begin

Complete this task before you change the IP address of any VitalSuite APPS system.

If you change the IP address of a server before VitalAgents are updated with the new IP address target, you run the risk of orphaning your VitalAgents.

Related information

For more information about changing the IP address of a VitalSuite APPS server, refer to “Process overview”, on page 78.

Purpose

To update your VitalAgents to post data to the new IP address of the VitalSuite APPS server:

...........................................................................................................................................................................

1 Log in to the System Master server as an administrator.

...........................................................................................................................................................................

2 Click the ADMIN tab and select the Agents link.

...........................................................................................................................................................................

3 Update the upload target as follows:

a. Select Upload target in the VitalAnalysis agents menu frame.

Result: The Upload Target page opens.

b. Enter the new IP address in the text field, and click Submit.

...........................................................................................................................................................................

4 If your VitalAgents are targeting VitalSuite APPS servers from different domains or groups do the following:

a. Click Advanced.

Result: The Upload target: Advanced page opens.

....................................................................80

b. Replace the old IP address with the new address for each domain and group by selecting the Domain drop-down menu and the Groups drop-down menu.

c. Click Submit after changing the IP address for each domain and group.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................81

Update the Configuration server IP address

..........................................................................................................................................................................................Update the Configuration server IP address

When to use

Use this procedure to update the IP address of your VitalSuite APPS Configuration server.

The Configuration server is responsible for downloading software updates to client desktops and to distribute policies to VitalAgent clients. In most cases, the Configuration server is located on your VitalSuite APPS Master server. The same Configuration server can be used for both VitalSuite APPS Analysis functionality and VitalSuite APPS Help functionality. For large networks with many VitalAgent clients, multiple Configuration servers can be installed throughout your network.

Before you begin

Consider the strategy of designating a temporary VitalSuite APPS Configuration server for VitalAgents to check into to find the new IP address of their posting servers.

Related information


Procedure

To update an IP address of the Configuration server:

...........................................................................................................................................................................

1 In the ADMIN tab, select Servers to create a new IP address using these steps:

a. Select Agent configuration in the Setup menu frame.

Result: The Agent Configuration page opens displaying the old IP address(es).

b. Select the appropriate Configuration server from the list and click Delete.

c. After confirmation of the deletion(s), return to the Agent Configuration page.

d. Click in the Configuration servers text box.

e. Click New.

Result: The Agent Configuration Server: New page opens.

....................................................................82

f. Enter the Server name and new Server address.

g. Click Submit.

...........................................................................................................................................................................

2 Repeat steps e through g for other Configuration servers with new IP addresses.

...........................................................................................................................................................................

3 Wait until all your existing agents do their next configuration check.

Result: Your VitalAgents are updated with the new IP address of the Configuration server. (VitalAgents do configuration checks every hour, day, or week as previously established on the Agent configuration update page accessed on the Agents link of the ADMIN tab.)

Important! If you change the address of your Configuration server before your agents perform their next configuration update, you will lose (or orphan) your agents. All data from these agents will be lost unless you go to each VitalAgent client and manually change its upload target.

Important! In between the time that you change the targets on the Agents page and you change the IP address of the VitalSuite APPS server(s), your VitalAgents cannot upload data. Instead, they store data on their client machines until you assign the new IP address to the VitalSuite APPS servers.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................83

Delete obsolete source addresses in VSSyncTimeTable

..........................................................................................................................................................................................Delete obsolete source addresses in VSSyncTimeTable

When to use

Use this procedure to delete old source IP addresses is various databases. This action is required because MS-SQL databases might not reliably sync to the latest source IP address, which can cause aggregation failures and in extreme cases some data loss.

Every night your Aggregation and Posting/Polling servers synchronize with the Master servers to ensure all data is consistent. The nightly sync updates the VSSyncTimeTable on the database for each server.

After changing IP addresses for VitalSuite APPS Analysis functionality and reinstalling VitalSuite APPS Help functionality, verify the new source address on every VSSyncTimeTable using SQL Enterprise Manager and delete old source addresses in the following databases: VAMaster, VAAggr, VAPost, VAHConfig, VHMaster, VHPost, and VitalHelp.

If VitalSuite NET is part of your VitalSuite Performance Management environment, the VitalSuite APPS Analysis functionality and VitalSuite APPS Help functionality Master servers must source the VitalSuite NET Master server IP address.

Before you begin

Make sure you can use SQL Enterprise Manager to connect to the VitalSuite APPS databases.

Related information


....................................................................84

Procedure

To delete old source addresses in the VSSyncTimeTable:

...........................................................................................................................................................................

1 Using SQL Enterprise Manager, check the VSSyncTimeTable in each VitalSuite APPS database on each server and make sure the new IP address is listed in the table.

...........................................................................................................................................................................

2 Using Query Analyzer, connect to each VitalSuite APPS database on each server and remove legacy rows by entering the following delete statement:

delete VSSyncTimeTable where sourceAddress = '<obsolete IP address>'

Example: delete VSSyncTimeTable where sourceAddress = '100.10.10.10'

Important! Use single quotes around the obsolete IP address(es).

...........................................................................................................................................................................E N D O F S T E P S

....................................................................85

Update the VitalSuite APPS databases with the new IP address

..........................................................................................................................................................................................Update the VitalSuite APPS databases with the new IP address

When to use

Use this procedure to update the VitalSuite APPS databases with the new IP address.

The MS-SQL Server databases must be modified to reflect the new IP addresses of your VitalSuite APPS servers. Sample scripts for updating these databases are provided in the following topics.

Before you begin

Make sure you can use SQL Query Analyzer to connect to the databases on your VitalSuite APPS servers.

Related information


Procedure

To update the VitalSuite APPS databases:

...........................................................................................................................................................................

1 Using SQL Query Analyzer, log into the appropriate database using the dba account and the sql password.

...........................................................................................................................................................................

2 Run the scripts provided in the following scenarios, replacing generic text in brackets (< >) with the requested IP address:

• “Scenario 1: VitalSuite APPS Analysis and Help on the same machine”, on page 86.

• “Scenario 2: VitalSuite APPS Analysis and Help on two separate machines”, on page 89.

• “Scenario 3: Distributed VitalSuite APPS Analysis environment”, on page 92.

...........................................................................................................................................................................

3 Repeat the previous steps on the other databases as required.

Alternatively, you can use the MS-SQL Server Enterprise Manager to manually make the database changes instead of using Query Analyzer.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................86

..........................................................................................................................................................................................Scenario 1: VitalSuite APPS Analysis and Help on the same machine

Purpose

Use the scripts in this topic to update the databases when VitalSuite APPS Analysis and Help functionality are installed on the same machine.

Databases modified

The databases modified in this scenario include: VAMaster, VAAggr, VAPost, VAHConfig, VHMaster, and VitalHelp. If you choose to re-install VitalSuite APPS Help functionality from CD (see “Change the VitalSuite APPS Help IP address by re-installing the product”, on page 96), there is no need to modify the VHMaster and VitalHelp databases for VitalSuite APPS Help functionality because of the product re-install.

Scripts

The following table provides the scripts you need to run to update your VitalSuite APPS system with the new IP address.

Updating the VSMasterTable, VAHServerTable, VAHPostServerTable, and VSReportingServerTable, on the VAMaster database

Use VAMASTER Update VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress =‘<Old VAMaster Address>’ go Update VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMaster Address>’ go Update VAHServerTable set ServerAddress = ‘<New VAAggr Address>’ where ServerAddress =‘<Old VAAggr Address>’go Update VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress =‘<Old VAHConfig Address>’ go Update VAHPostServerTable set PostServerAddress = ‘<New VAPost Server Address>’ where PostServerAddress = ‘<Old VAPost Server Address>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

....................................................................87

Scenario 1: VitalSuite APPS Analysis and Help on the same machine

Updating the VSMasterTable, VAHServerTable, VAHPost ServerTable, and VSReportingServerTable on the VAAggr database

Use VAAGGRUpdate VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress = ‘<Old VAMaster Address>’ go Update VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMaster Address>’ goUpdate VAHServerTable set ServerAddress = ‘<New VAAggr Address>’ where ServerAddress = ‘<Old VAAggr Address>’go Update VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’ go Update VAHPostServerTable set PostServerAddress = ‘<New VAPost Server Address>’ where PostServerAddress = ‘<Old VAPost Server Address>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

Updating the VSMasterTable on the VAHConfig database

Use VAHCONFIGUpdate VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress = ‘<Old VAMaster Address>’ go Update VSSyncTimeTable set sourceAddress = ‘<New sourceAddress>’ where sourceAddress =‘<Old sourceAddress>’go

Updating VSMasterTable, VAHServerTable, and VAHPostServerTable on VitalHelp database

Use VITALHELPUpdate VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where server address = ‘<Old VHMaster address>’goUpdate VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’goUpdate VAHPostServerTable set ServerAddress = ‘<New VHPostServer Address>’ where ServerAddress = ‘<Old VHPostServer Address>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New sourceAddress>’ where sourceAddress =‘<Old sourceAddress>’go

....................................................................88

Updating VSMasterTable on VAHConfig database

Use VAHCONFIGUpdate VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMasterAddress>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New sourceAddress>’ where sourceAddress =‘<Old sourceAddress>’go

....................................................................89

Scenario 2: VitalSuite APPS Analysis and Help on two separate machines

Scenario 2: VitalSuite APPS Analysis and Help on two separate

..........................................................................................................................................................................................machines

Purpose

This topic provides the scripts to update the MS-SQL Server databases for a VitalSuite APPS Analysis functionality single-server environment in which the Master, Aggregation, Posting, and Configuration servers are installed on one machine.

Scripts to update the VitalSuite APPS Analysis functionality databases

The following table provides the scripts to run to update the VitalSuite APPS Analysis functionality server with the updated IP address:

Updating the VAMaster database

Use VAMASTER Update VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress =‘<Old VAMaster Address>’go Update VAHServerTable set ServerAddress = ‘<New VAAggr Address>’ where ServerAddress =‘<Old VAAggr Address>’go Update VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress =‘<Old VAHConfig Address>’go Update VAHPostServerTable set PostServerAddress = ‘<New VAPost Server Address>’ where PostServerAddress = ‘<Old VAPost Server Address>’ goUpdate VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

....................................................................90

Updating the VAAggr database

Use VAAGGRUpdate VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress= ‘<Old VAMaster Address>’goUpdate VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMaster Address>’goUpdate VAHServerTable set ServerAddress = ‘<New VAAggr Address>’ where ServerAddress = ‘<Old VAAggr Address>’go Update VAHServerTable set Server Address = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’goUpdate VAHPostServerTable set PostServerAddress = ‘<New VAPost Server Address>’ where =PostServerAddress = ‘<Old VAPost Server Address>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

Updating the VAHConfig database

Use VAHCONFIGUpdate VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress =‘<Old VAMaster Address>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

....................................................................91

Scenario 2: VitalSuite APPS Analysis and Help on two separate machines

Scripts to update the VitalSuite APPS Help functionality databases

You do not need to modify the VitalSuite APPS Help functionality databases if you re-install the product. The following scripts are provided if you prefer not to re-install VitalSuite APPS Help functionality.

Update VSMasterTable, VAHServerTable, VAHPostServerTable, and VSReportingServerTable on VHMaster database

Use VHMASTER Update VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMaster Address>’ go Update VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’goUpdate VAHPostServerTable set PostServerAddress = ‘New VHPost Server Address’ where PostServerAddress = ‘<Old VHPost Server Address>’go Update VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

Update VSMasterTable, VAHServerTable, and VAHPostServerTable on VitalHelp database

Use VITALHELPUpdate VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMaster Address>’go Update VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’ go Update VAHPostServerTable set PostServerAddress = ‘<New VHPost Server Address>’ where PostServerName = ‘<Old VHPost Server Address>’go Update VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

Update VSMasterTable on VAHConfig database

Use VAHCONFIGUpdate VSMasterTable set ServerAddress = ‘<New VHMaster Address>’ where ServerAddress = ‘<Old VHMaster Address>’ goUpdate VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old IP Address>’go

....................................................................92

..........................................................................................................................................................................................Scenario 3: Distributed VitalSuite APPS Analysis environment

Purpose

This topic provides the scripts to update the MS-SQL databases in a distributed environment when the VitalSuite APPS Analysis functionality Master, Aggregation, Posting, and Reporting servers are installed on different machines. Replace the bracketed (< >) text (including brackets) with new IP address information on each line of scrip before running the script on the database.

Scripts to update VitalSuite APPS Analysis functionality in a distributed environment

The following table provides the scripts for updating each VitalSuite APPS Analysis functionality server in your distributed environment.

Updating the VSMasterTable, VAHServerTable, VAHPostServerTable and VSReportingServerTable on the VAMaster database

Use VAMASTER Update VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress = ‘<Old VAMaster Address>’go Update VAHServerTable set ServerAddress = ‘<New VAAggr Address>’ where ServerAddress = ‘<Old VAAggr Address>’goUpdate VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’go Update VAHPostServerTable set PostServerAddress = ‘<New VAPost Server Address>’ where PostServerAddress= ‘<Old VAPost Server Address>’ go Update VSReportingServerTable set ServerAddress = ‘<New IP Address>’ where ServerAddress = ‘<Old IP Address>’goUpdate VSSyncTimeTable set sourceAddress = ‘<New sourceAddress>’ where sourceAddress =‘<Old sourceAddress>’go

....................................................................93

Scenario 3: Distributed VitalSuite APPS Analysis environment

Updating the VSMasterTable, VAHServerTable, VAHPostServerTable, and VSReportingServerTable on the VAAggr database

Use VAAGGRUpdate VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress = ‘<Old VAMaster Address>’go Update VAHServerTable set ServerAddress = ‘<New VAAggr Address>’ where ServerAddress = ‘<Old VAAggr Address>’go Update VAHServerTable set ServerAddress = ‘<New VAHConfig Address>’ where ServerAddress = ‘<Old VAHConfig Address>’go Update VAHPostServerTable set PostServerAddress = ‘<New VAPost Server Address>’ where PostServerAddress = ‘<Old VAPost Server Address>’ goUpdate VSReportingServerTable set ServerAddress = ‘<New IP Address>’ where ServerAddress = ‘<Old IP Address>’Update VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress =‘<Old sourceAddress>’go

Updating the VAHConfig database

Use VAHCONFIGUpdate VSMasterTable set ServerAddress = ‘<New VAMaster Address>’ where ServerAddress = ‘<Old VAMaster Address>’go Update VSSyncTimeTable set sourceAddress = ‘<New IP Address>’ where sourceAddress = ‘<Old sourceAddress>‘go

....................................................................94

Change the VitalSuite APPS Analysis server IP address and edit the

..........................................................................................................................................................................................registry

When to use

After updating the VitalSuite APPS Analysis functionality databases, use these procedures to change the IP address on each VitalSuite APPS Analysis functionality machine and update the registry key to reflect the new IP address.

Important! Failure to update the registry key results in the Web Console tabs bar only displaying the ADMIN tab.

Before you begin

Obtain a new VitalSuite APPS ANalysis functionality license key based on the new IP address of the system. For information on how to obtain a new key, refer to the VitalSuite Performance Management Software Administrator’s Guide.

Related information


Procedure

To update the IP address of the VitalSuite APPS Analysis functionality system and edit the registry key:

...........................................................................................................................................................................

1 Change the IP address of the server through its TCP/IP properties.

...........................................................................................................................................................................

2 Update the VitalSuite APPS Analysis functionality server’s registry key as follows:

a. Enter regedit at a command prompt.

Result: The Registry Editor opens.

b. Go to HKEY_LOCAL_MACHINE\Software\VitalSuiteCommon.

c. Right-click the VSInstallIP field, and select Modify to display the Edit Sharing window.

d. Enter the new IP address of your server, and select OK.

....................................................................95


...........................................................................................................................................................................

3 Replace the license key associated with the old IP address:

a. Log in as administrator to the System Master and in the ADMIN tab, click Servers.

b. In the VitalAnalysis menu frame select License key.

c. Enter the new license key and click Submit.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................96

Change the VitalSuite APPS Help IP address by re-installing the

..........................................................................................................................................................................................product

When to use

Use this procedure to re-install the VitalSuite APPS Help functionality instead of running scripts to update the VitalSuite APPS Help functionality databases with the new IP address. Re-installing the product is the recommended method for changing the server IP address.

This method minimizes the process of changing IP addresses for VitalSuite APPS Help functionality servers and there is usually no loss of alarm data. With each VitalAgent able to hold 1,024 alarm transactions and store data until it has a posting target, the probability of data loss is minimal. There might be some historical data loss, however.

Before you begin

Make sure you have the VitalSuite APPS Help functionality installation CD so you can re-install the product.

Related information


Procedure

To re-install the VitalSuite APPS Help functionality:

...........................................................................................................................................................................

1 To preserve VitalSuite APPS Help functionality data, back up database, log, and web report files that you want to save from the \Program Files\VSCommon directory. However, do not restore the databases because they contain incorrect (obsolete) IP addresses.

...........................................................................................................................................................................

2 Uninstall and reinstall the VitalSuite APPS Help functionality from the CD.

Additional information: For information on how to uninstall and reinstall VitalSuite APPS Help functionality, refer to the VitalSuite Performance Management Software Installation Guide.

...........................................................................................................................................................................

3 Specify the new VitalSuite APPS Help functionality IP address on the Master servers page of the Web Console.

...........................................................................................................................................................................

4 Designate the Posting servers and their new IP addresses.

...........................................................................................................................................................................

5 Enter the new license key.

....................................................................97

Change the VitalSuite APPS Help IP address by re-installing the product

...........................................................................................................................................................................

6 After re-installing VitalSuite APPS Help functionality, make sure all the VitalSuite APPS Help functionality services have been started on your servers. If required, manually restart the following services: Apache, VitalHelp, VitalHelpMaster, VitalSuite AtBoot Scheduler, and VitalSuiteWeb. (The VAAggr service must be started on VitalSuite APPS Analysis functionality servers, as well.)

Result: The MS-SQL databases automatically update with a new installation on the updated VitalSuite APPS Help functionality server addresses.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................98

..........................................................................................................................................................................................Update VitalAgentIT clients to target a new address

When to use

Use this procedure to update a VitalAgentIT client with the new IP address to use for posting data.

When the change of the IP address is complete for the VitalSuite APPS servers, you might need to inform the users of VitalAgentIT who are not automatically notified to update their server policies. If VitalAgentIT clients are currently posting to obsolete servers, users must manually update their posting targets to avoid orphaning their data.

Before you begin

Identify the VitalAgentIT clients that need to be manually updated with the new target IP address.

Related information


Procedure

To update a VitalAgentIT client to post to a new IP address:

...........................................................................................................................................................................

1 From the VitalAgentIT dashboard, select View | Preferences.

Result: The Preferences window displays.

...........................................................................................................................................................................

2 In the Server Policy tab, enter <new IP address>:2474 in the text field.

....................................................................99

Update VitalAgentIT clients to target a new address

...........................................................................................................................................................................

3 Click OK.

Result: You are prompted whether you want to purge all the data currently in the datafiles.

...........................................................................................................................................................................

4 Click OK to purge the existing data files and confirm new policy.

Important! Agents other than VitalAgentIT will have to be updated manually via SMS, or by hand (using forced configuration checks to correct server). Refer to the VitalAgent Administrator’s Guide for more information.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................100

Correct DSN connections on Windows

..........................................................................................................................................................................................Overview

Purpose

This section describes how to correct DSN connections on a Windows VitalSuite Performance Management server.

Contents


Update and test VitalSuite Performance Management DSNs 101

VitalSuite Performance Management DSNs 106

....................................................................101

Update and test VitalSuite Performance Management DSNs

..........................................................................................................................................................................................Update and test VitalSuite Performance Management DSNs

When to use

Once you update the VitalSuite Performance Management databases with the new license key and IP addresses, use this procedure to update the DSNs on each VitalSuite Performance Management system on Windows and test their connections.

Before you begin

Make sure you have completed the process of changing the IP address of each VitalSuite Performance Management server before you update and test the DSNs.

Related information

For information on which VitalSuite Performance Management DSNs to update and test, refer to “VitalSuite Performance Management DSNs”, on page 106.

Purpose

To update and test the VitalSuite Performance Management DSNs:

...........................................................................................................................................................................

1 Open the ODBC Data Source Administrator on the VitalSuite Performance Management server you want to update and test.

The ODBC Data Source Administrator is located under Windows Administrative Tools.

...........................................................................................................................................................................

2 Select the System DSN tab.

...........................................................................................................................................................................

3 Select a data source, and click Configure.

Result: The Microsoft SQL Server DSN Configuration window displays.

....................................................................102

...........................................................................................................................................................................

4 Make sure the Server field contains the correct name or IP address of the appropriate VitalSuite Performance Management server, then click Next.

Result: The next Microsoft SQL Server DSN Configuration window displays.

...........................................................................................................................................................................

5 Click Client Configuration and verify the following:

• The configuration is using TCP/IP

• Dynamic Ports is unchecked

....................................................................103


...........................................................................................................................................................................

6 Return to the SQL Server DSN Configuration window and verify the following:

• The With SQL Server authentication using a login ID and password entered by the user option is selected.

• The Connect to SQL Server to obtain default settings for the additional configuration options box is checked.

...........................................................................................................................................................................

7 Enter the login information for the sa account.

...........................................................................................................................................................................

8 Click the Client Configuration button and make sure the Network Libraries is set to TCP/IP. Click OK to return to the Microsoft SQL Server DSN Configuration window.

...........................................................................................................................................................................

9 Click Next.

Result: The next Microsoft SQL Server DSN Configuration window displays.

...........................................................................................................................................................................

10 Click Next.

Result: The final Microsoft SQL Server DSN Configuration window displays.

....................................................................104

...........................................................................................................................................................................

11 Click Finish.

Result: The ODBC Microsoft SQL Server Setup window opens.

...........................................................................................................................................................................

12 Click Test Data Source.

Result: The Data Source Administrator tests the ODBC connection to the data source and displays the test results. If a test did not complete successfully, verify that you entered the correct IP addresses in the databases.

....................................................................105


...........................................................................................................................................................................

13 Repeat the previous steps to update the remaining DSNs on the other VitalSuite Performance Management servers.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................106

..........................................................................................................................................................................................VitalSuite Performance Management DSNs

VitalSuite NET DSNs

The following table shows the DSNs you need to update on each server in a distributed VitalSuite NET environment. In a single-server VitalSuite NET environment, all DSNs are located on the same system.

VitalSuite APPS Analysis functionality DSNs

The following table shows the DSNs you need to verify on each server in a distributed VitalSuite APPS Analysis functionality environment. In a single-server environment, all DSNs are located on the same system.

VitalSuite APPS Help functionality DSNs

The following table shows the DSNs you need to update on each server in a distributed VitalSuite APPS Help functionality environment. In a single-server environment, all DSNs are located on the same system.

Server DSN

Master server VNMaster, ToAggrDSN_

Reporting server (if installed) VNMaster

Aggregation server ToPollerDSN_ (one per Polling server), VNAggr

Polling server VNAggr, VNPoller

Server DSN

Master server VAMaster

Reporting server (if installed) VAMaster

Aggregation server VAAggr

Posting server(s) VAPost1, etc.

Server DSN

Master server VHMaster

Reporting server (if installed) VHMaster

Posting server(s) VHPost1, etc.

....................................................................107

4 Allowing open access to VitalSuite Performance Management pages using vsopenURL

..........................................................................................................................................................................................Overview

Purpose

This chapter discusses the vsopenURL utility, which lets global administrators create designated user accounts and provide users with access to VitalSuite Performance Management without requiring them to log in.

Contents


Configure the vsopenURL utility 108

Use cases 111

....................................................................108

..........................................................................................................................................................................................Configure the vsopenURL utility

When to use

Use this procedure to provide users with direct, open access to a VitalSuite Performance Management page so they do not have to login to view a specific report or heat chart.

Before you begin

Make sure you have:

• A global administrator account on the System Master server.

• Changed the mode to executable (chmod +x) when running the utility on a UNIX system.

Related information

For more information about setting up open access to VitalSuite Performance Management pages, refer to “Use cases”, on page 111.

Procedure

To configure the vsopenURL utility:

...........................................................................................................................................................................

1 Log in to the System Master server as global administrator.

...........................................................................................................................................................................

2 Open the configuration interface by typing the following URL into your Web browser:

http://<SystemMaster>/cgi-bin/vsopenurl.cgi?action=4

Result: The first time the OpenURL Configuration page is displayed the Require userID option is pre-checked and the User List is blank. Global administrators have two options for users (ID required or ID not required) when configuring the vsopenURL utility. The first provides more control and flexibility. In each case, access is granted through specific accounts.

....................................................................109

Configure the vsopenURL utility

...........................................................................................................................................................................

3 When Require userID is checked, do the following (otherwise proceed to the next step):

a. Enter user names in the User List box as a series of user IDs separated by commas (no spaces).

b. Click Update to submit the user list.

c. Advise the OpenURL users to configure the following URL pattern when using OpenURL:

http://<servername>/cgi-bin/vsopenurl.cgi?action=1&acc=<userID>&vsLink=http://AVitalSuiteLink

where <servername> is the IP address or DNS name of the server and <userID> is the account name for the privileged user

d. Add or delete user IDs by repeating Step 2 on page 108.

...........................................................................................................................................................................

4 Uncheck the Require userID check box on the OpenURL Configuration page to provide access through a specialized user account described in the following steps.

Result: The Open URL Configuration page refreshes with the User List text box hidden.

...........................................................................................................................................................................

5 Create a fixed userID called openurl using the Accounts link.

....................................................................110

...........................................................................................................................................................................

6 Advise the OpenURL users to configure the following URL pattern when using OpenURL:

http://<servername>/cgi-bin/vsopenurl.cgi?action=1&vsLink=http://AVitalSuiteLink

(Notice that in this case, the URL parameter acc is not needed.)

...........................................................................................................................................................................

7 Click Update to save the configuration to the VSCommon/webroot/myvital/schedule/openURL.ini file.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................111

Use cases

..........................................................................................................................................................................................Use cases

Purpose

This topic provides examples that illustrate URLs that could be included in an email or on a custom Web page to provide direct access to VitalSuite Performance Management pages of special interest to specified accounts.

Important! In environments where Secure-Socket Layer (SSL) is enabled, users must enter the fully qualified domain names for servers in the URL address, otherwise they will not gain access.

Example 1—Default Operations Page

Example 1 illustrates a URL that loads the default NETWORK Operations page, where xxx.xxx.xxx.xxx equals the IP address of the System Master server and yyy.yyy.yyy.y represents the appropriate IP address of the VitalSuite Performance Management server containing the intended page.

http://xxx.xxx.xxx.xxx/cgi-bin/vsopenurl.cgi?action=1&acc=<user14>&vsLink= http://yyy.yyy.yyy.y/cgi-bin/vnresource.cgi?show=All

....................................................................112

Example 2—Filtered Pages

This example illustrates how the NETWORK Operations page filters could be included in the URL to provide access to a report of only the resources that meet specific criteria (such as all Cisco routers whose average CPU utilization is greater than 30 percent for the last month). The example link of vsopenurl, generates a report based on power search on the NETWORK Operations page.

http://<servername>/cgi-bin/vsopenurl.cgi?action=1&acc=<userID>&vsLink=http://<servername>/cgi-bin/vnresource.cgi?dmn=0&grp=g-1&sp=3&rel=1&f_csc_s0=%3E30&s_csc=r0&so_csc=1&respg=200&show=csc=200&show=csc&vsuser=<userID>

NETWORK Operations page example

The following example NETWORK Operations page shows the listing for Cisco routers with over 30% CPU utilization.

Example 3—Restricted Navigation Pages

This example illustrates the ability to load only portions of the full frameset. In this example the NETWORK Summary page is loaded but without the navigation tabs at the top of the page.

http://xxx.xxx.xxx.xxx/cgi-bin/vsopenurl.cgi?action=1&acc=<userID>&vsLink=http://100.10.101.11/VNConsole/html/VN-20040111-20040111/0/netsummaryl1-0/RightChart.htm

Tabless Network Summary Page example

The following example shows a tabless NETWORK Summary page.

....................................................................113

Use cases

Example 4—Single Detail Graph

This example illustrates how the NETWORK Operations page filters could also be included in the URL to provide access to a view of a detail graph.

http://xxx.xxx.xxx.xxx/cgi-bin/vsopenurl.cgi?action=1&acc=<userID>&vsLink=http://100.100.101.1/cgi-bin/vngrapher.cgi/9020001000000130070000000100000002010002010600000008010?role=7&dmn=12&alarmtype=<userID>

Single detail graph

The following example shows a single detail graph that is normally accessed through the NETWORK Operations page.

....................................................................114

Example 5—My Vital Page

This illustrates how the My Vital page could also be added to the URL to provide access for a specified time period.

http://xxx.xxx.xxx.xxx/cgi-bin/vsopenurl.cgi?action=1&acc=<userID>&vsLink=http://yyy.yyy.yyy.yyy/cgi-bin/myvital.exe?FrameType=ContentFrame&Operation=Show&TimeSpan=Yesterday

My Vital page example

The following example shows a My Vital page directly accessed using an Open URL.

....................................................................115

5 Log files

..........................................................................................................................................................................................Overview

Purpose

This chapter provides a brief description of the contents of VitalSuite Performance Management log files and their locations on the VitalSuite Performance Management servers. The tables provided show the most commonly used log files for troubleshooting, and then a more extensive alphabetical listing of product logs.

Contents


Log file locations 116

VitalSuite NET log files 117

Example VitalSuite NET log files 123

VitalSuite APPS Analysis log files 128

VitalSuite APPS Analysis example log files 132

VitalSuite APPS Help functionality log files 135

Windows Find utility 138

Performance enhancements 139

....................................................................116

..........................................................................................................................................................................................Log file locations

Purpose

This topic lists the major log types and their location on the VitalSuite Performance Management servers.

Locations

The following table provides the location of most VitalSuite Performance Management log files.

Log type Location

VitalSuite NET VitalSuite NET Master, Aggregation, and Polling servers in <install_dir>/Program Files/VSCommon/webroot/logs.

VitalSuite APPS VitalSuite APPS Configuration server, VitalSuite APPS Analysis functionality Master, Aggregation, Posting servers, and on the VitalSuite APPS Help functionality Master and Posting servers:<install_dir>/Program Files/VSCommon/webroot/logs

Install logs Windows: Installation log files for Windows are located in the <VN_Install_Dir>/Program Files/VSCommon directoryUNIX: Installation log files for UNIX are located in <VN_Install_Dir>/VSCommon/vsinstall.log.<date>

Apache <VN_Install_Dir>/VSCommon/apache/logs directory:access_log.yyyy_mm_dd.logerror_log.yyyy_mm_dd.log

....................................................................117

VitalSuite NET log files

..........................................................................................................................................................................................VitalSuite NET log files

Purpose

This topic lists the VitalSuite NET logs and provides information about how they can help troubleshoot problems.

Common VitalSuite NET log files

An extensive listing of VitalSuite NET log files is presented in alphabetical order in “Complete list of VitalSuite NET log files”, on page 118. The following important log files are listed here as a commonly useful resource in tracking the source of VitalSuite NET issues:

Log File Server Deleted Purpose/Troubleshooting use

cron.log.(day-number) M,A,P 7 days Lists which programs were started.On UNIX, the cron.log file is in the \var\cron directory. Only the root user has access.On Windows, the cron.log file is in the /VSCommon/webroot/logs folder. (See “Cron log”, on page 123)

VN_Discovery_mmddyyyy_hhmmss.txt

P 14 days Tracks device and resource discovery, and identifies exact time of each discovery. (See “Discovery log”, on page 124)

VNDDyyyymmdd.log M 8 days Lists duplicate devices when unexpected or suspended devices are discovered by VitalSuite NET Aggregation servers.(See “VNDD log”, on page 124)

VNEyyyymmdd.log M,A,P 9 days Lists errors from Polling servers and other programs. (See “VNE log file”, on page 125)

VNSyyyymmdd.log M,A,P 9 days Includes the following information:• System messages indicating the starting,

stopping, and/or restarting of collectors on VitalSuite NET Polling servers

• Domain and group updates, scheduled reports on VitalSuite NET Aggregation servers

• Batch email, scheduled reports on the VitalSuite NET Master server

(See “VSC log file”, on page 126)

VNTyyyymmdd.log A,P 8 days Logs data about trend aggregation. (See “VNT log file”, on page 127)

....................................................................118

Collector log files

VitalSuite NET collector logs are listed in the following tables.

Complete list of VitalSuite NET log files

The following table lists alphabetically all of the logs found in the VitalSuite NET logs directory. In the Server column, M=Master, A=Aggregation, P=Poller. If Reporting servers are configured, log files appearing on the Master server also appear on the Reporting server.

VSCyyyymmdd.log M,A,P 8 days Is created during the nightly synchronization of common database tables and files by vssync.exe. Check this log when one or more database tables are not synchronized across servers. (See “VSC log file”, on page 126)

VSPyyyymmdd.log A,P 9 days Logs information about data aggregation process. (See “VSP log file”, on page 126)

Log File Server Deleted Purpose/Troubleshooting use

Log (Collector) Contents

AC-<<xxxx><date>.log asynchronous collector (where xxxx is the dataset identifier)

BC-<xxxx><date>.log bCollector (where xxxx is the dataset identifier)

saa<date>.log Cisco SAA/IP SLA Collector

sysapp<date>.log System Application Collector

VNNavis<date>.log Navis Collector

UC-<xxxx><date>.log uCollector (where xxxx is the dataset identifier)

Log Name Server Contents/Purpose

Atboot.log M,A,P Logs atboot service output

BC-xxxx<date>.log P bCollector logs where xxxx is the dataset identifier

Cron.log M,A,P Logs runs of scheduled executables

CWMConnect<date>.log P Logs Cisco WAN Manager activity

DSSched-<date>.log P Logs activity of the dssched program such as failed attempts to contact the VNPollerTable in the database

GroupRetag<date>.log A,P GroupRetag.exe output log; daemon ensures resources are assigned to their proper reporting groups

msinfo.log M,A,P Logs system information reports for workstation

....................................................................119


mvschd<date>.log M,A,P Logs scheduler output for start and finish times of scheduled generation of My Vital page

myreportsToDB<date>.log M,A,P Logs transfers of reports to the database and removal of files from the web-user directory subdirectories

MYV<date>.log M,A,P Overall My Vital log for graph generation

NMV<date>.log M,A,P My Vital log for VitalSuite NET only

ODA.log andODA<date>.log

M, A Logs status and errors for on-demand aggregation processes.

ResMod<date>.log P Logs information from the Resource modification tool (if used)

Retag<date>.log A,P Retag.exe output log; daemon ensures resources are assigned to their proper domains

saa<date>.log P Logs Cisco SAA/IP SLA collector resource scheduling for polling

sysapp<date>.log P System application collector

UC-xxxx<date>.log P uCollector logs where xxxx is the dataset identifier

VN80CFIX_log_<date>_<time>.txt

M,A,P Conversion fix start and end timechecks for upgrades from VS 8.0

VNA<date>.log M Logs vnvhEventManager activity for VitalSuite NET alarms; records alarm threshold failures, ODBC SQL alarm failures

VNAdminGro<date>.log M Logs Primetime/Default Primetime settings, and Host (traffic) groups settings

VNAGGR<date>.log M vnsetupaggrsrvr.cgi output file; logs information about updated Aggregation server information (including added/deleted/modified Polling servers and information set on the setup and failover page)

VNALARM<date>.log P Alarm log of threshold.cgi activity (setting of VitalSuite NET alarm thresholds)

VNBusyHour.log M, A, P Logs errors related to Busy Hour functionality.

VNDD<date>.log M,P detectDup.exe output log; refers to detection of duplicate devices

vndebug.log M,A,P Logs debug activity.


....................................................................120

VNDevQry<date>.log M, A Logs errors associated with the Device Query page of the Web Console.

VN-Discovery_ <date>_<time>.txt

P Lists which devices and resources were discovered

VNDiscovertHistory.txt P Records instances of the running of VN-Discovery

VNDownloatStats-DSID-<date>.log

P Log file for the Bulk Data download program: VNDownloadStats.exe, which is launched by DSSched.exe

VNE<date>.log M,A,P VitalSuite NET collector log; indicates stopping, starting and restarting of collectors on the Polling server, failed connections, device migration errors, and several other reported data (not directly relevant to troubleshooting)

VNJspError.log M,A Logs errors made for group rules and domain rules.

VNKPI.log M Logs errors made when trying to create or edit KPIs for VitalSuite NET collectors.

VNLICN<date>.log M Logs vnlicensekey.cgi activity

VNLicUpg<date>.log M,P Logs upgrade license activity

VNNavis<date>.log P VN Navis collector log; all Navis information is listed here

VNP <date>.log A,P VitalSuite NET traffic monitoring (generic) collector log; ODBC failures recorded here if the system cannot connect to the Polling server during aggregation; also any log with a debug flag uses this log

VNPP<date>.log M Admin property log; registers vnproperty.cgi activity including listing of numbers of resources, devices, etc.

VNQI<date>.log M Logs activity of vnqualityindex.cgi (ADMIN | Thresholds | Quality index pages)

VNQIHC<date>.log M Logs activity of vnqualityheatchart.cgi (ADMIN | Thresholds | Network thresholds and Network sensitivity pages)

VNR<date>.log M,A,P Logs VN standard reports generation

VNS<date>.log M,A,P VN system log; most processes write to this log: Retag, startcollectors, runBEmail, crschedrun, etc.

VNSetInt<date>.log M Logs activity the VNSetinterval.cgi (ADMIN | Network | Polling Interval)


....................................................................121


VNT<date>.log A,P Trend aggregation log

VNVWP<date>.log M Logs resource preferences view activity of the vnresviewpref.cgi

VSA<date>.log M Logs the output of vsadmingroup.cgi, i.e., domain rules, group policy configuration definitions entered on the Groups UI

VSAdmin<date>.log M Logs domain and reporting groups UI settings

VSC<date>.log M,A,P Database/File nightly synchronization log

VSClXML<date>.log M,A Logs nightly cleanup of temporary xml files such as browser cookies

VsCommonJavaError.log M,A Logs errors during the creation of groups and domains.

VSDefVi<date>.log M,A Logs changes made to the default view

VSEUIP<date>.log M Logs entries on the ADMIN | Accounts | User Interface Profiles | Rename link

VSFP<date>.log M,A,P Logs file propagation (VSFilePropagate.cgi)

VSGLOG<date>.log M Logs output from the vsgetlog.exe; This executable is a user tool that can be used to zip all zip log files within VitalSuite Performance Management. If Vital Net is the Suite master, then this tool should be run on the Master server

VSLOG<date>.log M Logs vnetuserlog.cgi activity (administrative activity)

VSLogin<date>.log M,A,P Tracks server logins; records VSLoginAdmin.exe activity

VSMSVR<date>.log M Logs vssetupmastersvr.cgi output; captures settings entered on the ADMIN | Master Servers page

VSN<date>.log M,A,P Logs heat chart generations

VSNUIP<date>.log M Logs activity on new user interface profile page and propagation of new UI profiles

VSO<date>.log M,A Logs information about execution of vscommon.cgi; VS Portal log, common to VN/VA/VH

VSP<date>.log A,P Aggregation log; shows aggregation start, run, and completion


....................................................................122

VSQ<date>.log M Logs the debugging information for the vswebsql.exe program (online query tool to access the database directly). After logging onto VitalSuite NET as an administrator, you can run this program/cgi-bin/vswebsql.exe.The log file is only generated if you set the registry key VSWEBSQL_LOG_MASK (set value = 1) under HKEY_LOCAL_MACHINE/SOFTWARE/VitalSuiteCommon

VSRptSv<date>.log M Logs setup of a Reporting server on the Servers | Master Servers page

VSS<date>.log M,A Logs instances of generated pdf system status reports

VSsrvpr<date>.log M Logs VSServiceProfile.cgi output (ADMIN | Groups | Service level | Profile page)

VSG<date>.log M,A Records vasgetlog.exe activity (Get log files)

VSStatus<date>.log M,A,P Logs VitalSuite Performance Management system status information (ADMIN❇System link); log file of vsHealth.exe (run as a cron job on VitalSuite NET Master to check the status of the Aggregation servers)

vssystemerror.log M,A,P Logs memory errors, memory leaks, and other VitalSuite Performance Management system errors

VSUIP<date>.log M Logs changes to settings on the ADMIN | Accounts | User Interface Profiles page (UI tabs and links)

VSUN<date>.log M Logs activity on ADMIN | Accounts | New Account page

VSUser<date>.log M Records instances of administrative activity on the ADMIN | Accounts page such as display and delete

VSUserEdit<date>.log M Logs vsaccountedit activity (ADMIN | Accounts | Edit Account)

VSUserp<date>.log M Logs user account password activity (ADMIN | Accounts | Edit Account | Change Password)

VSX<date>.log M,A,P Logs vxmlgen.exe output; information on inter-server communications using XML

VSYSE<date>.log M,A Logs failures to find the VNDiscoveryHistory.txt file


....................................................................123

Example VitalSuite NET log files

..........................................................................................................................................................................................Example VitalSuite NET log files

Purpose

This topic displays examples of the main VitalSuite NET log files.

Cron log

The following example shows the cron log of running jobs.

....................................................................124

Discovery log

The following example shows the discovery log for devices and resources.

VNDD log

The following example shows the VNDD log file used to locate duplicate devices.

....................................................................125


VNE log file

The following example shows the VNE log file that lists errors from Polling servers.

VNS log file

The following example shows the VNS log file that lists start/stop Polling server messages.

....................................................................126

VSC log file

The following example shows the VSC log file shows synchronization of common database tables.

VSP log file

The following example shows the VSP log file that shows data aggregation.

....................................................................127


VNT log file

The following example shows the VNT log file that shows trend aggregation.

....................................................................128

..........................................................................................................................................................................................VitalSuite APPS Analysis log files

Purpose

This topic lists the VitalSuite APPS Analysis functionality logs and provides information about how they can help troubleshoot problems.

Location

The following table lists common log files and their location.

VitalSuite APPS Analysis functionality common log files

The following VitalSuite APPS Analysis functionality logs are among the commonly used logs for troubleshooting. A more extensive list in alphabetical order is provided in “Complete list of VitalSuite APPS Analysis functionality log files”, on page 129.

Log file Location

Installation log files (installed.log, upgraded.log, deleted.log)

Program Files\VSCommon

Apache log files (access.log, error.log) Program Files\VSCommon\Apache\logs

General VitalSuite APPS Analysis functionality log files

Program Files\VSCommon\Webroot\logs(on the VitalSuite APPS Analysis functionality Master, Aggregation, and Posting servers)

Log Server Deleted Purpose/Content

cron.log.(day- number)

M,A,P 7 days Lists which programs were started.The cron.log file is in the VSCommon/webroot/logs folder. (See “Cron log”, on page 123)

VAAyyyymmdd.log A 5 days Logs VAAggr service activity, providing information about the aggregation process.Notes aggregation and re-aggregation occurrences, when the next aggregation is scheduled, purges of aggregate data, cache size, synchronization times, etc. (See “VAA log file”, on page 132)

VACyyyymmdd.log M,A 5 days Logs information about the generation of heat chartsLists requests for heat chart generation, when and whether the chart is generated/regenerated, etc. (See “VAC log file”, on page 133.)

VAGyyyymmdd.log M 5 days Lists administrative commands issued. (See “VAG log file”, on page 134)

....................................................................129

VitalSuite APPS Analysis log files

Complete list of VitalSuite APPS Analysis functionality log files

The following table lists alphabetically many of the logs found in the VitalSuite APPS Analysis functionality logs directory. In the Server column, M=Master, A=Aggregation, P=Posting, C=VitalSuite APPS Configuration. If Reporting servers are configured, log files appearing on the Master server also appears on the Reporting server.

VAQyyyymmdd.log A 5 days Lists database query information.

VARyyyymmdd.log M,A 5 days Lists information about report generation, including requests for report generation, when and whether the report is generated/regenerated, etc. (See “VAR log files”, on page 134)

VSWyyyymmdd.log P,C 5 days Logs activity of the VitalSuite Performance Management Web service, listening on port 2474View information about VitalAgent configuration checks, VitalAgent data posting to VitalSuite APPS Analysis functionality, purging database table operations, disk space on the install drive on the server. (See “VSW log file”, on page 133.)

Log Server Deleted Purpose/Content

Log Server Contents/Purpose

AMV<date>.log M,A Logs information about the VitalSuite APPS Analysis functionality portion of My Vital

atboot.log M,A,P Logs atboot service output

APCGI<date>.log M,C Logs adminPostCGI activity, agent machine IDs, status checks

cron.log M,A,P Logs runs of scheduled executables

mvschd<date>.log M,A Logs output for start and finish times of scheduled generation of My Vital page

MYV<date>.log M,A Overall My Vital log for graph generation

VAA<date>.log A Log file for the VAAggr service; provides information about aggregation process; aggregation and re-aggregation schedules, purges of stale aggregate data, and server cache information.

VABEC<date>.log M VA batch email log for published reports

VABES<date>.log M VA batch email log for standard reports

....................................................................130

VAC<date>.log M,A Logs all information about the generation of heat charts; lists requests for heat chart generation, when and whether the chart is generated/regenerated, etc.

VAG<date>.log M Logs administrative commands issued

VAHPP<date>.log M,A,P Log information on VH server properties checks (VAHProperty.cgi) ADMIN | Servers | VitalAnalysis | Properties

VAMR<date>.log M,A Logs all information related to VitalSuite APPS Analysis functionality data for My Reports

VAQ<date>.log A Logs database query information related to aggregation tables

VAR<date>.log M,A Logs information about VitalSuite APPS Analysis functionality report generation; lists requests for report generation, when and whether the report is generated/regenerated, etc.

vasetupstd<date>.log M Logs information on customizations of the layout of standard reports (ADMIN | Preferences)

VRP<date>.log M Information on generation of reports.(There is also a log named VRPyyyymmddS.log that contains only information on removing expired reports.) (VCRPT_LOG_MASK)

VSA<date>.log M,A Logs the addition of new Aggregation server(s)

VSC<date>.log M,A,P Database/File nightly synchronization log

VSClXML<date>.log M,A Logs the nightly cleanup of temporary XML files.

VsCommonJavaError.log M,A Logs errors during the creation of groups and domains.

VSFP<date>.log M,A,C Logs file propagation (VSFilePropagate.cgi)

VSG<date>.log M,A,C Information on execution of the vacgi.exe and vscgi.exe programs of VitalSuite APPS Analysis functionality, reflects activity of the following pages:• ADMIN | Agents• ADMIN | Applications (New Edit, Enable/Disable)• License set under cron job and on execution of the vscgi

and vhcgi programs of VitalSuite APPS Help functionality. (VSCGI_LOG_MASK)

VSGLOG<date>.log M Logs output from the vsgetlog.exe. This executable is a user tool that can be used to zip all zip log files within VitalSuite Performance Management. If VitalSuite APPS Analysis functionality is the suite master, then this tool should be run on the Master server


....................................................................131

VitalSuite APPS Analysis log files

VSLogin<date>.log M Tracks server logins; records VSLoginAdmin.exe activity

VSMMVR<date>.log M Logs vssetupmastersvr.cgi output; captures settings submitted on the ADMIN | Master Servers page

VSO<date>.log M Common to all three servers (VA,VH and VN) contains information on execution of the vcommcgi program. (VSCGI_LOG_MASK)

VSQ<date>.log M Common to all three servers; contains information associated with the use of the web-based remote database query (vssql.htm).

VSS<date>.log M,A,P, C

Logs instances of generated pdf system status reports

Vssrvpr<date>.log M,C Only present on the Suite Master; if VitalSuite APPS Help functionality Master is the System Master; this log records vsserviceprofile.cgi activities and reflects all service level profile operation

VSStatus<date>.log M,A,P Logs VitalSuite Performance Management system status information (ADMIN | System link); log file of vsHealth.exe (run as cron job on VitalSuite APPS Analysis functionality Master server to check the status of the Aggregation servers)

VSV<date>.log M,A Common to VA and VH; contains server information that is equivalent to the VCC log data on the Agent machine; called the VSC process for the servers; consists of information on communication between servers. Unless the debugging flag is set in the registry, only errors are written to this log. (VSCGI_LOG_MASK)

VSW<date>.log M,P,C Log file for the VitalSuite Performance Management Web service, listening on port 2474 View information about VitalAgent configuration checks, VitalAgent data posting to VitalSuite APPS Analysis functionality, purging base table operations, disk space on the install drive on the server; duplicate MIDs; (one of the most useful logs for VA since it contains information on agents posting data). (VSW_LOG_MASK)

VSX<date>.log M,A,P Logs vxmlgen.exe output; information on inter-server communications using XML


....................................................................132

..........................................................................................................................................................................................VitalSuite APPS Analysis example log files

Purpose

This topic provides examples of the most common VitalSuite APPS Analysis functionality log files. For a description of each log file, refer to “VitalSuite APPS Analysis functionality common log files”, on page 128.

VAA log file

The following example shows the VAA log file for the aggregation process.

....................................................................133

VitalSuite APPS Analysis example log files

VSW log file

The following example shows the VSW log file of VitalSuite Performance Management Web service activity.

VAC log file

The following example shows the VAC log file for heat chart generation.

....................................................................134

VAG log file

The following example shows the VAG log file for administrative commands.

VAC log file

The following example shows the VAC log file for database queries.

VAR log files

The following example shows the VAR log files for report generation.

....................................................................135

VitalSuite APPS Help functionality log files

..........................................................................................................................................................................................VitalSuite APPS Help functionality log files

Purpose

This topic lists the VitalSuite APPS Help functionality logs and provides information about how they can help troubleshoot problems.

Common VitalSuite APPS Help functionality log files

The following files are commonly used to troubleshoot VitalSuite APPS Help functionality issues.

Complete list of VitalSuite APPS Help functionality log files

The following table alphabetically lists the logs found in the VitalSuite APPS Help functionality logs directory. In the Server column, M=Master, P=Posting, C=VitalSuite APPS Configuration. If Reporting servers are configured, log files appearing on the Master server also appears on the Reporting server.

Log Server Deleted Contents/Purpose

cron.log.(day number)

M,A,P 7 days Lists which programs were started.The cron.log file is in the VSCommon/webroot/logs folder. (See “Cron log”, on page 123.)

VHS<date>.log P 4 days Contains server information, such as: server statistics, when VitalSuite APPS Help functionality service is first started, event postings, activity of the VHTraceRtManager.

VSW<date>.log M,P,C 4 days Logs activity of the VitalSuite Performance Management Web service that listens on port 2474.View information about VitalAgent configuration checks and remaining disk space on the VitalSuite Performance Management installation drive on the server.

Log Server Content/Purpose

APCGI<date>.log M,C Logs adminPostCGI activity, agent machine IDs, status checks.

Cron.log M,P,C Logs cron jobs (scheduled executables).

HMV<date>.log M,P Logs executable activity that renders the event status on My Vital pages (vhmyvital.exe).

mvschd<date>.log M,P Log of scheduled starts and stops of the My Vital executable.

....................................................................136

MYV<date>.log M,P Logs the MyVital.exe activity which renders the overall My Vital pages.

VAHPP<date>.log M,P Log information on VH server properties checks (VAHProperty.cgi) ADMIN | Servers | VitalHelp | Properties

VHCGI<date>.log M,P Logs activity of the vhcgi.exe used to render the ALARMS | Applications page, some frames of the ALARM | Summary page, and viewing preference related to VitalSuite APPS Help functionality.

VSGLOG<date>.log M Logs output from the vsgetlog.exe. This executable is a user tool that can be used to zip all log files within VitalSuite Performance Management. If VitalSuite APPS Help functionality is the System master, then this tool should be run on the VitalSuite APPS Help functionality Master server.

VHGWY<date>.log M,P Logs activity of the Mail Gateway for VitalSuite APPS.

VHH<date>.log M,P Logs vhchart.exe which renders VitalSuite APPS Help functionality heat charts on the ALARMS | Summary page and generates client lists on the Applications | Clients screen.

VHMS<date>.log M Logs the activity of the Master serve service.

VHR<date>.log M,P Logs vsremote.exe data; this executable is used to run remote tests and display data.

VHS<date>.log P Logs the activity of the Posting server service; contains server information, such as server statistics, when VitalSuite APPS Help functionality service is first started, and event postings.

VSA<date>.log M,P,C Log file reporting various executable and dll files which render ADMIN tab pages; executables using this log file include: vsggi.exe, custdxrx.exe, dxrxdll, and vhremote.exe.

VSC<date>.log M,P,C Database/File nightly synchronization and configuration log.

VSFP<date>.log M File propagation log.

VSG<date>.log M,C Vscgi log/sync between VA/VH; includes license checks and propagation of license information; logs activity to do with the ADMIN | Thresholds link.

Vslogin<date>.log M,P,C Logs tracking logins.

VSNIP<date>.log M Logs UI profile additions.

VSO<date>.log M,P vcommcgi log of database calls.


....................................................................137

VitalSuite APPS Help functionality log files

Vssrvpr<date>.log M,C Only present on the Suite Master; if VitalSuite APPS Help functionality Master is the System Master; this log records vsserviceprofile.cgi activities and reflects all service level profile operation.

VSV<date>.log M Common to VA and VH; contains server information that is equivalent to the VCC log data on the Agent machine. It is called the VSC process for the servers. It consists of information on communication between servers. Unless the debugging flag is set in the registry, only errors are written to this log (VSCGI_LOG_MASK).

VSW<date>.log M,P,C Log file for the VitalSuite Performance Management Web service, listening on port 2474 View information about VitalAgent configuration checks, VitalAgent data posting to VitalSuite APPS Analysis functionality, purging base table operations, disk space on the install drive on the server; duplicate MIDs; one of the most useful logs for VitalSuite APPS Help functionality because it contains information on agents posting data (VSW_LOG_MASK).

VSX<date>.log M,P Logs vxmlgen.exe output; information on inter-server communications using XML.


....................................................................138

..........................................................................................................................................................................................Windows Find utility

Purpose

In the Windows environment you can take advantage of the find utility and registry flags to help focus your troubleshooting.

If you are debugging a problem using very large log files (which might be too large to open in Notepad), and you know the specific information you are looking for, you can use the Windows find utility. For details and description of the flags you can use, open a DOS window and type find/?

Example

For example, if you want to see all error messages in a log:

1. Open a DOS window.

2. Change to the directory (for example, <install_dir>/Program Files/VSCommon/Webroot/logs).

3. Enter the following:

find “ER:” vsw20040913.log

This displays all the errors in the VSW log file for October 13, 2004.

4. To write the information to a file, enter:find “ER:” vsw20030913.log > error.log

...........................................................................................................................................................................E N D O F S T E P S

....................................................................139

Performance enhancements

..........................................................................................................................................................................................Performance enhancements

Purpose

This topic explains the performance enhancements in VitalSuite NET.

Overview

For service provider customers, VitalSuite NET’s strategy for handling a large set of resources is to increase the distribution of machines. As a result, the service provider customers face the following issues:

• A deployment that is more expansive than the other VitalSuite NET customers.

• Fewer number of higher end Solaris servers. Benchmark results have shown that the current release of VitalSuite NET does not scale well with the size of the machine.

• Need for multiple Oracle licenses since an Oracle database is installed on each server.

In order to scale VitalSuite NET in a realistic and cost effective manner, it is required to increase the capacity of VitalSuite NET so that the same or fewer number of machines in a distribution can handle more resources.

Performance enhancements

The following enhancements are applied to VitalSuite NET to improve the performance:

• Weekly and monthly data aggregations are performed daily instead of hourly.

• Multiple aggregators are launched in parallel.

• Database access and other database changes are utilized.

• Multiple threads process each dataset aggregation.

• Aggregate only to groups corresponding to the global domain and the domain a resource belongs to.

• For machines that host both the aggregator and poller database, aggregate directly to the aggregator database which eliminates the intermediate step of writing to the poller database.

....................................................................140

....................................................................141

6 Technical tips and notes

..........................................................................................................................................................................................Overview

Purpose

This chapter provides technical tips and notes on about the VitalSuite Performance Management products.

Contents


Recommended Web browser settings 143

Windows 2003 recommended settings 144

Internet Explorer recommended settings 145

Configure proxy bypass for IP addresses in Internet Explorer 146

Configure Internet Explorer to allow session cookies 148

Add VitalSuite Performance Management servers as trusted sites in Internet Explorer

150

Firefox recommended settings 152

Technical notes 153

Commonly used URLs 154

List of VitalSuite Performance Management services 155

Guidelines for printing VitalSuite Performance Management pages 156

Web server disk checking interval 157

VitalAgent accelerator keys 158

VitalAgent recording upload activity in a daily log 159

....................................................................142

Resolve VitalSuite APPS Analysis functionality DNS issues with the VAServerMap utility

160

Tips for resolving common problems 164

Resolve Page Not Found errors in the Web Console 160

Web Console not displaying correctly 167

....................................................................143

Overview

Recommended Web browser settings

..........................................................................................................................................................................................Overview

Purpose

This section describes the recommended Web browser settings for Internet Explorer and Firefox.

Contents


Windows 2003 recommended settings 144

Internet Explorer recommended settings 145

Configure proxy bypass for IP addresses in Internet Explorer 146

Configure Internet Explorer to allow session cookies 148

Add VitalSuite Performance Management servers as trusted sites in Internet Explorer

150

Firefox recommended settings 152

....................................................................144

..........................................................................................................................................................................................Windows 2003 recommended settings

Purpose

This topic describes the recommended Web browser settings for users on the Windows 2003 operating system.

Animated GIF settings

If you have a Windows 2003 system, set the following values in Internet Explorer to display animated GIFs:

Tools | Internet Options | Advanced | Multimedia | select Play animations in web page

Settings for local intranet sites

Each VitalSuite Performance Management server’s hostname and IP address must be added to your browser’s local intranet site to avoid an “invalid user” error message. The cookie from VitalSuite Performance Management will not be accepted if the required URL address is not added to the local intranet sites.

To add a server to the local intranet sites, go to Tools | Internet Options | Security | Local intranet | Sites | Advanced and in the Add to this web site to the zone box, enter the VitalSuite Performance Management server IP address.

....................................................................145

Internet Explorer recommended settings

..........................................................................................................................................................................................Internet Explorer recommended settings

Purpose

This topic describes the recommended Web browser settings for Internet Explorer (IE) 6.0.

Standard settings

Open the Internet Explorer and configure the following settings before logging into the Web Console:

• Tools | Internet Options | Security tab | select Local Intranet as the Web content zone | Custom Level button | select “Enable” for Scripting of Java applets

• Tools | Internet Options | General tab | Temporary Internet files | Settings button | select Every visit to the page

• Tools | Internet Options | Advanced tab | Microsoft VM | select JIT compiler for virtual machine enabled (requires a restart)

Accept cookies from VitalSuite Performance Management

In addition to the standard settings, you must configure Internet Explorer to accept cookies from your VitalSuite Performance Management servers. Select one of the following methods to set up Internet Explorer to accept cookies from VitalSuite Performance Management:

To... Then...

Add each VitalSuite Performance Management server as a local intranet site

Refer to the procedure in “Add VitalSuite Performance Management servers as trusted sites in Internet Explorer”, on page 150.

Use a proxy server, if a proxy server is used in your environment

Configure Internet Explorer to bypass the proxy server for VitalSuite Performance Management servers, as described in “Configure proxy bypass for IP addresses in Internet Explorer”, on page 146.

To always allow session cookies Refer to the procedure in “Configure Internet Explorer to allow session cookies”, on page 148.

....................................................................146

..........................................................................................................................................................................................Configure proxy bypass for IP addresses in Internet Explorer

When to use

If you use a proxy server in your VitalSuite Performance Management environment, you might want to enable a computer to bypass the proxy server for certain VitalSuite Performance Management servers. This is useful for enabling VitalSuite Performance Management to set cookies on Internet Explorer. Use this procedure to specify the IP addresses of VitalSuite Performance Management servers for which Internet Explorer will bypass the proxy server.

Before you begin

Make sure you know the IP addresses of your proxy and VitalSuite Performance Management servers.

Related information

For more information about recommended settings for Internet Explorer, refer to “Internet Explorer recommended settings”, on page 145.

Procedure

To configure IP addresses that bypass a proxy server in Internet Explorer:

...........................................................................................................................................................................

1 From the Tools menu in Internet Explorer, select Internet Options.

Result: The Internet Options window opens.

...........................................................................................................................................................................

2 Click the Connections tab.

...........................................................................................................................................................................

3 Click LAN Settings.

Result: The Local Area Network (LAN) Settings window opens.

...........................................................................................................................................................................

4 Ensure that the following boxes are checked:

• Use a proxy server for your LAN

• Bypass proxy server for local addresses

...........................................................................................................................................................................

5 In the Address field enter the IP address of the proxy server.

...........................................................................................................................................................................

6 In the Port field enter the port number used to access the proxy server.

....................................................................147

Configure proxy bypass for IP addresses in Internet Explorer

...........................................................................................................................................................................

7 Click Advanced.

Result: The Proxy Settings window opens.

...........................................................................................................................................................................

8 In the Exceptions field enter the IP addresses or a range of IP addresses for your VitalSuite Performance Management servers.

Example: 100.100.*.*

...........................................................................................................................................................................

9 Click OK in the Proxy Settings window.

...........................................................................................................................................................................

10 Click OK in the Local Area Network (LAN) Settings window.

...........................................................................................................................................................................

11 Click OK in the Internet Options window.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................148

..........................................................................................................................................................................................Configure Internet Explorer to allow session cookies

When to use

Use this procedure to allow session cookies to be set in Internet Explorer. Configuring Internet Explorer to accept cookies from VitalSuite Performance Management servers is required for VitalSuite Performance Management to function properly.

Before you begin

Ensure that you have configured the standard settings in Internet Explorer, as described in “Internet Explorer recommended settings”, on page 145.

Related information


Procedure

To configure Internet Explorer to allow session cookies:

...........................................................................................................................................................................


Result: The Internet Options window opens.

...........................................................................................................................................................................

2 Click the Privacy tab.

...........................................................................................................................................................................

3 In the Settings section click Advanced.

Result: The Advanced Privacy Settings window opens.

...........................................................................................................................................................................

4 Select Override automatic cookie handling.

...........................................................................................................................................................................

5 Ensue that the Accept option is selected for the First-party Cookies and Third-party Cookies fields.

...........................................................................................................................................................................

6 Select Always allow session cookies.

...........................................................................................................................................................................

7 Click OK in the Advanced Privacy Settings window.

....................................................................149

Configure Internet Explorer to allow session cookies

...........................................................................................................................................................................

8 Click OK in the Internet Options window.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................150

Add VitalSuite Performance Management servers as trusted sites in

..........................................................................................................................................................................................Internet Explorer

When to use

Use this procedure to add VitalSuite Performance Management servers as trusted sites in Internet Explorer.

Adding VitalSuite Performance Management servers as trusted sites allows Internet Explorer to accept cookies from VitalSuite Performance Management servers. For alternative methods that provide the same result, refer to “Accept cookies from VitalSuite Performance Management”, on page 145.

Before you begin

Make sure you know the IP addresses of your VitalSuite Performance Management servers.

Related information


Procedure

To add your VitalSuite Performance Management servers as trusted sites in Internet Explorer:

...........................................................................................................................................................................


...........................................................................................................................................................................

2 Click the Security tab.

...........................................................................................................................................................................

3 Select Local Intranet as the Web content zone.

...........................................................................................................................................................................

4 Click Sites...

...........................................................................................................................................................................

5 In the Local intranet window, click Advanced...

....................................................................151

Add VitalSuite Performance Management servers as trusted sites in Internet Ex-

...........................................................................................................................................................................

6 Enter the IP addresses or the fully qualified domain name of your VitalSuite Performance Management servers and click Add after each one.

Important! Instead of entering one address for each VitalSuite Performance Management server, use a wildcard to add a single address that covers all VitalSuite Performance Management servers, for example http://10.10.10.*.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................152

..........................................................................................................................................................................................Firefox recommended settings

Purpose

This topic describes the recommended settings for Firefox 1.0.1.

Standard settings

If you did not import the settings from Internet Explorer, you can use the standard settings that is pre-configured on Firefox 1.0.1.

Using machines names

To use machine names to reach the VitalSuite NET servers instead of the server’s IP address, do one of the following:

Important! Because the browser does not correctly process special characters such as 10.10.* when connecting with the VitalSuite NET servers by their machine names, using a wildcard in the setup causes a machine name access to fail. In a multi-server configuration, this restriction applies to Master, Aggregation, and Polling servers.

Exclude the VitalSuite Performance Management servers from the proxy server

To exclude the VitalSuite Performance Management servers from the proxy server when using Firefox 1.0.1:

Tools | Options | Connection Setting | under General category, in the No Proxy For: listbox, enter .sv.lucent.com and each server’s IP address.

If you... Then...

Did not import the settings from Internet Explorer

Choose one of the following:• Use the proxy server and leave the No Proxy for

box blank.• Specify No Proxy for both the hostname and

server IP address and use the server’s complete IP address.

Imported the settings from Internet Explorer Specify No Proxy for both the hostname and server IP address and use the server’s complete IP address.

....................................................................153

Overview

Technical notes

..........................................................................................................................................................................................Overview

Purpose

This section provides technical notes about the VitalSuite Performance Management product.

Contents


Commonly used URLs 154

List of VitalSuite Performance Management services 155

Guidelines for printing VitalSuite Performance Management pages 156

Web server disk checking interval 157

VitalAgent accelerator keys 158

VitalAgent recording upload activity in a daily log 159

Resolve VitalSuite APPS Analysis functionality DNS issues with the VAServerMap utility

160

....................................................................154

..........................................................................................................................................................................................Commonly used URLs

Purpose

This topic lists commonly used VitalSuite Performance Management URLs.

Commonly used URLs

The following table lists the commonly used VitalSuite Performance Management URLs.

URL Description

http://<System_Master or Reporting server’s IP address or name>Include the port number if the server is not using port 80. For example, http://vitalsuite:81.

Login page. Use to access VitalSuite NET and VitalSuite APPS.

http://<vitalapps Configuration server’s IP address or name>:2474orhttp://<vitalsuite_apps>:2474/default.htm

VitalAgent download page. Download the VitalAgent software onto a client desktop.

http://<vitalsuite apps server’s IP address or name>:2474/vagentit.htm

VitalAgentIT download page. Download the VitalAgentIT software onto a client.

http://<vitalsuite apps server’s IP address or name>:2474/transact.htm

Transact Toolkit download page. Download the Transact Toolkit software onto a VitalAgent client.

http://<vitalsuite apps server’s IP address or name>:2474/automon/automon.htm

VitalAgent Automon download page. Download the VitalAgent Automon software onto a VitalAgent or VitalAgentIT client.Refer to the VitalAgent Administrator’s Guide for all information relating to VitalAgent Automon.

http://www.lucent.com/support Remote VitalSuite Performance Management Online Documentation page. Access the VitalSuite Performance Management Release Notes and online versions of all VitalSuite Performance Management manuals. To access the local VitalSuite Performance Management Online Documentation page that resides on your VitalSuite Performance Management server, click in the navigation bar.

http://www.lucentdocs.com Page that VitalSuite Performance Management customers can use to order additional copies of the documentation.

....................................................................155

List of VitalSuite Performance Management services

..........................................................................................................................................................................................List of VitalSuite Performance Management services

Purpose

This topic lists the VitalSuite Performance Management services installed with your VitalSuite Performance Management products. You can view the status of each service by viewing the System Status report described in the Server and System Administration chapter of the VitalSuite Performance Management Software Administrator’s Guide.

Windows services

The following table lists all the VitalSuite Performance Management services for Windows environments.

Service name Installed with...

Apache Web Server All VitalSuite APPS servers, except the Configuration server

VitalSuiteWeb All VitalSuite APPS servers including the Configuration server

VAAggr VitalSuite APPS Analysis functionality Aggregation server

VitalHelp VitalSuite APPS Help functionality Posting server

VitalHelpMaster VitalSuite APPS Help functionality Master server

VitalSuite AtBoot Scheduler All VitalSuite APPS, VitalSuite NET, and VitalSuite ART servers

Tomcat All VitalSuite NET servers, VitalSuite ART

Apache All VitalSuite NET servers, VitalSuite ART

NobleNet PortMapper for TCP VitalSuite ART

Actuate Process Management Daemon 7

VitalSuite ART

Vital IPC Server VitalSuite NET, on Aggregation and Polling servers. This is the Navis Event Bus, which is used to process communication between the collectors, the Trap Admin UI, and the Trap Engine. When the VoIP license is enabled, the Navis Event Bus is used to process communication between VoIP components.

VitalSuite NET collection VitalSuite NET Polling server with VoIP option enabled

Mediation VitalSuite NET Polling server with VoIP option enabled

CORBA server VitalSuite NET Polling server with VoIP option enabled

Resource Engine VitalSuite NET Polling server with VoIP option enabled

....................................................................156

..........................................................................................................................................................................................Guidelines for printing VitalSuite Performance Management pages

Purpose

This topic provides guidelines for printing various VitalSuite Performance Management pages.

VitalSuite APPS reports

You can use your browser to print any displayed VitalSuite Performance Management page. For VitalSuite APPS reports, you can also use the PRINT icon shown in the menu frame.

The browser sends the output to the default printer on the local system. The PRINT icon sends the output to the default printer assigned to the system account on the server.

VitalSuite Performance Management pages

To print a page using Microsoft Internet Explorer, do one of the following:

• Print the entire current web page by clicking Print in the browser.

• Print only the selected frame by making a selection in the Print window that displays when you right-click and choose Print on the pop-up menu.

• Print all frames individually by making a selection in the Print dialog that displays when you click Print on the right-mouse button menu.

PDFs

To print a PDF generated with the PDF FILE icon on VitalSuite NET reports, click the printer icon in the Acrobat toolbar. Always select the Shrink to Fit option on the Print window to be sure that the entire report fits on the printed page.

....................................................................157

Web server disk checking interval

..........................................................................................................................................................................................Web server disk checking interval

Default setting

By default, the VitalSuite Performance Management Web server checks disk space every 60 minutes (3600 seconds). It is recommended that you change this interval to 5 minutes (300 seconds).

Registry field

To change the disk check interval on VitalSuite APPS servers, change the web_disk_space_check_interval registry variable from 3600 to 300. This registry variable is located in the following path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VitalSuiteWeb\Parameters\.

....................................................................158

..........................................................................................................................................................................................VitalAgent accelerator keys

Purpose

This topic describes the VitalAgent accelerator keys that can be useful when troubleshooting issues.

List of accelerator keys

The following table describes the accelerator keys supported by VitalAgent.

Usage

Note the following when using accelerator keys:

• The agent’s dashboard must be the active window for the accelerator keys to work.

• Hold down the Alt key and press the other specified key. For example, hold down Alt and press A to force the client to check the VitalSuite APPS server for a configuration update.

• If you configured the agent user interface to exclude the dashboard, you must use the VCC commands instead of these accelerator keys as a troubleshooting tool. For a list of VCC command line options, refer to “Command line options for the VCC program”, on page 159.

Key Description

Alt+A Forces VitalAgent to check the VitalSuite APPS Configuration server for a configuration update.

Alt+F8 Opens a window that displays such server parameters as the configuration update target.

Alt+F5 Opens the About box, which displays such information as the version number of the VitalAgent.

Alt+F6 Opens the agent Network Info window.

....................................................................159

VitalAgent recording upload activity in a daily log

..........................................................................................................................................................................................VitalAgent recording upload activity in a daily log

VCC log file

If you enable the Maintain Upload Log option (refer to the VitalAgent Administrator’s Guide), all VitalAgent and VitalAgentIT clients record upload activity in a daily log. The log is named VCC<yyyymmdd> and is stored in the Log folder of the client installation directory.

To create the log on one client, enable the following registry entry on the VitalAgent client:

HKEY_LOCAL_MACHINE\SOFTWARE\VitalSigns\VitalAgent\Config\VCC_LOG

The log indicates the type of data uploaded to the VitalSuite APPS server. You can also check the log to see the results of a VCC command entered from the command line.

Command line options for the VCC program

The following table describes the command line options for the VitalAgent client’s VCC program. All VCC command line options are case-sensitive.

Option Description

Common options

-V <version #> Performs a software version update check by polling the Configuration server. You must also specify the existing VitalAgent version number (for example, vcc -V 9.1.0.11).

-F Uploads data to a VitalSuite APPS server. By default, VCC uploads data to the target specified by the VC_UPLOAD_TARGET registry variable.

-C Performs a configuration check to its VitalSuite APPS server. By default, VCC checks the configuration target specified by the VC_CONFIG_TARGET variable.

-VHFltCheck Downloads the VitalSuite APPS event filters from the Configuration server.

-DomandGrp Downloads the domain and group ID from the Configuration server.

Other options (used in conjunction with the common options)

-u Overrides the default target with a specified URL or IP address. If the appropriate target is defined in the registry, then this parameter is optional.

-p Specifies the name of the proxy web server. This parameter is optional.

-n Specifies the port of the identified proxy web server. This parameter is optional.

-t Displays the contents of the agent configuration file (config.htm). This option does not update the client’s agent policy parameters. To update the policy parameters, run VCC with the -C option.

....................................................................160

Resolve VitalSuite APPS Analysis functionality DNS issues with the

..........................................................................................................................................................................................VAServerMap utility

Purpose

Due to the MS-SQL Server architecture, updates to server names and IP addresses might leave conflicting information in the database ServerMapTables. Use the information in this section to run the VAServerMapUtil.exe utility, which resolves possible ServerMapTable database issues listed below.

DNS issue with VitalSuite APPS Analysis functionality

A server has a DNS name (such as Server-A) and IP address. After some time another server can be set up that has a different DNS name (such as Server-B) but re-uses the same IP address:

In many cases the function performed by the new server is also the same as that of the former.

DNS solution using the VAServerMap utility

The VAServerMapUtil.exe utility makes VitalSuite APPS Analysis functionality view the new server entry the same as the old server instead of as a different server.

The utility provides VitalSuite APPS administrators a tool to:

• Generate a report from ServerMapTable detailing duplicate entries and conflicts. For example, reports contain all entries that have different DNS names for the same IP address and different Application IDs.

• Resolve differences of DNS names for the same server. For example, if the DNS name has changed for the same IP address, the administrator can decide which DNS name to retain.

Usage

The executable is part of the installation package on the VitalSuite APPS Aggregation and Posting servers. The administrator must run them individually, one at a time, on the server of interest to view and resolve ServerMapTable entries. In a distributed environment the executable should be run on each server.

The executable for VAServerMapUtil.exe and options are described below:

0007 [-S dataSource][-D database user ID][-P database Password][-Q Query]

DNS Name IP Address

Server-A 10.10.10.50

Server-B 10.10.200.200 (temp address)

Server-A (Disabled)

Server-B 10.10.10.50 (IP address reused)

....................................................................161

Resolve VitalSuite APPS Analysis functionality DNS issues with the VAServerMap

[-U Update] [-I Ip address][-A Application id][-N server Name][-O Output file name][-H Help]

Command options

The table below further defines the command options and their usage.

Use Case 1

To generate a conflict report on the Vital Analysis Aggregation server, run this command:

VAServerMapUtil.exe

The display returns records of instances of same IP address with more than one server name. In addition to the screen output, the information is logged in a file named (by default) VAS.txt in the Program Files directory.

CommandOptions Definition Usage

-S dataSource Specifies database DNS name. By default it will connect to the VAAggr database.

-D Database user ID User ID for database login.

-P database Password Password for database login.

-Q Query Specifies a query to the database ServerMapTable.

-U Update Specifies an update to the servermaptable. When this option is set, the admin must provide the IP address and server name.

-I IP address Specifies the IP address.

-A Application ID Specifies the application ID number.

-N server Name Specifies the server name.

-O Output file name Specifies that the program writes the output to VAS.txt; also allows admin to specify a directory path to the file.

-H Help file Prints out the option usage file.

....................................................................162

Example

From this VAS.txt report, the administrator can see that:

• IP address 100.10.10.9 has been assigned to two different server names and two different applications.

• IP address 100.11.22.32 has been assigned to two different applications.

• IP address 100.200.100.11 has been assigned to two different server names and two different applications.

To specify a file name other than VAS.txt and/or location, use the -O option. For example:

VAServerMapUtil.exe -O <installdir>\Program Files\VSCommon\Webroot\logs\VAmaptablelog.txt

Use Case 2

To generate a conflict report on the VAPost server:

1. Log in as <database user ID> with <database login password>.

2. Run this command:VAServerMapUtil.exe –S VAPost –D <userid> –P <password>

Records are returned with same IP address with more than one server name on VAPost database.

Use Case 3

To retrieve all the records in the ServerMapTable and output the result to a file named myoutput.txt, run this command (Asterisks (*) can be used as a wildcards):

VAServerMapUtil.exe –Q –I * -A * -N * -O myoutput.txt

Records are displayed showing the results of the query for the range of IP addresses, the range of server names, the range of application IDs, in a file called myoutput.txt in xyz directory.

Use Case 4

To update the server name to “myserver” for IP address 1.2.3.4, run the command below:

VAServerMapUtil.exe –U –I 1.2.3.4 -N myserver

The server name is changed to “myserver” for all the records when the IP Address equals 1.2.3.4; in addition, a Program Files\VAU.txt log file is generated to maintain a history of server name changes.

IP ADDRESS SERVER NAME APP ID(APP NAME) ---------- ----------- ----------------100.10.10.9 machine1 139(File/Print)100.10.10.9 us7155fps01.abc.wxyz.com 1433(MS-SQL)100.11.22.32 139(File/Print)100.11.22.32 1433(MS-SQL)100.200.100.11 vaga6701.abc.wxyz.com 139(File/Print)100.200.100.11 datastoreu.ih.wxyz.com 1498(Sybase)

....................................................................163

Resolve VitalSuite APPS Analysis functionality DNS issues with the VAServerMap

Important! Applying the DNS name change implies removing duplicate entries so that there are unique entries for the server IP address and App ID in the table.

To update the server name to “my server” for IP address 1.2.3.4 and assign to it a single application (App ID 80, for example), run the command below:

VAServerMapUtil.exe –U –I 1.2.3.4 -N myserver -A 80

The server name is changed to “myserver” for all the records when the IP address equals 1.2.3.4 the App Id equals “80.”

Example04/01/04 17:32:11 Data in ServerMapTable before executing the query:100.10.100.110 80 drproxy.proxy.abc.com04/01/04 17:32:23 Data after exec:100.10.100.110 80 drproxy.proxy.abc.com_test

Important! The administrator cannot change the file name and output location for the VAU.txt file. The file contains a time stamp for each database transaction.

....................................................................164

Tips for resolving common problems

..........................................................................................................................................................................................Overview

Purpose

This section provides solutions and techniques that can help resolve common VitalSuite Performance Management issues.

Contents


Resolve Page Not Found errors in the Web Console 165

Web Console not displaying correctly 167

....................................................................165

Resolve Page Not Found errors in the Web Console

..........................................................................................................................................................................................Resolve Page Not Found errors in the Web Console

When to use

Use this procedure to resolve errors in accessing the pages in the Web Console. For example, if you click on a page in the Web Console and receive a Page Not Found error, follow the instructions in this topic to resolve the problem.

Before you begin

Make sure you have administrator access to the Web Console.

Related information

For more information about troubleshooting issues with the Web Console, refer to “Web Console not displaying correctly”, on page 167.

Procedure

If you cannot access the VitalSuite NET or VitalSuite APPS server, verify that the server addresses are defined correctly as follows:

...........................................................................................................................................................................

1 Verify the correct server addresses have been entered in the Web Console:

a. In the ADMIN tab, click Servers.

b. Click Master servers under Setup in the menu frame.

Result: The Master Servers form opens.

c. In the text fields, make sure the server name or IP address for each installed VitalSuite Performance Management server product is correct.

If the server information is not correct, make the necessary corrections. You must include the port number for a server (for example, http://server:81) if the server is not using the default port (port 80).

d. Make sure the correct product is selected as the System Master server by selecting the option button next to that product. If VitalSuite NET is installed, select it as the VS Master server. If VitalSuite NET is not installed, select VitalSuite APPS as the System Master server.

e. Click Submit to save your changes, or click Reset to cancel.

....................................................................166

...........................................................................................................................................................................

2 Verify the VitalSuite Performance Management services are running:

a. Use the System Status Report to determine if any VitalSuite Performance Management services are down. This report shows the status of the VitalSuite Performance Management services for each server component (Master, Aggregation, Polling, and so on).

b. If a service is down, go to the Windows Services screen and manually start the service.

Refer to the VitalSuite Performance Management Software Administrator’s Guide for information about the System Status Report.

...........................................................................................................................................................................

3 Check for event errors related to the VitalSuite Performance Management server or database.

a. From the Windows taskbar, choose Start | Programs | Administrative Tools (Common) | Event Viewer.

b. Select Log | System.

Result: The system error log opens with a list of errors encountered on the server.

c. Check the log to ensure that there are no errors related to the VitalSuite Performance Management server or database.

d. Close the system error log.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................167

Web Console not displaying correctly

..........................................................................................................................................................................................Web Console not displaying correctly

Purpose

This topic provides tips on troubleshooting problems related to the Web Console.

Unable to access heat charts and reports

If you cannot access the VitalSuite Performance Management heat charts and reports from a particular machine, check that the machine from which you accessing the heat charts and reports has a supported web browser installed. For a list of the supported web browsers, refer to the product Release Notes or Quick Start Cards.

Pages not being refreshed

If you are experiencing HTML pages that are not being refreshed or browser problems, then change your browser settings. For recommended browser settings, refer to sections, “Recommended Web browser settings”, on page 143 in this book.

Heat charts and reports not displayed correctly

If the heat charts and reports are not displaying properly, check that your monitor supports and runs a minimum of 1024 x 768 pixels.

Missing GIF files on heat charts

If you reinstall VitalSuite APPS, the icon for a missing GIF will appear in all of your previously generated heat charts. You can restore the heat charts by regenerating them. The missing GIFs are shared between heat charts, so regenerating a few heat charts will restore all of them.

Navigation

Due to the way in which the heat charts and administrative forms use frames, it is not recommended that you use the browser’s BACK and FORWARD buttons with these pages.

....................................................................168

....................................................................169

7 Branding the Web Console and VitalAgent icons

..........................................................................................................................................................................................Overview

Purpose

This chapter describes how to brand the pages in the Web Console and the VitalAgent icons.

Contents

This chapter covers the following topics:

Web Console branding guidelines 170

Brand the Web Console 172

Web Console branding examples 173

Add a message to the login page 177

VitalAgent branding 179

Restore the default VitalAgent icons 182

....................................................................170

..........................................................................................................................................................................................Web Console branding guidelines

Pages you can brand

You can brand the following pages on the Web Console with your company name or logo:

• Login page

• Standard report pages

• My Reports pages

• My Vital page

Important! It is recommended you brand the Web Console during non-business hours. This way you can test how the custom image appears on the interface and make changes without distracting users that are currently logged into the system.

Recommended logo sizes

The following table provides the recommended size for your logo images depending on its location.

Image Size (pixels) Size (inches)

Login image width: 106height: 15

width: 1.10height: 0.16

Standard Reports image width: 85height: 11


My Reports image width: 152height: 43


My Vital image width: 80height: 30


....................................................................171

Web Console branding guidelines

Logo names and locations

The following table lists the required name and location for your logo:

File name and location Description

.../vscommon/webroot/images/customer_login_logo.gif

Appears on the Web Console login page, as shown in “Login page example”, on page 173.Place this file on the System Master server and any Aggregation servers from which you login.Make sure to overwrite the existing blank GIF image in the directory.

.../vscommon/webroot/images/customer_report_logo.gif

Appears at the bottom of the standard reports, as shown in “Standard reports example”, on page 174. Place this file on your VitalSuite NET and VitalSuite APS Master and Aggregation servers.Make sure to overwrite the existing blank GIF image in the directory.

.../vscommon/webroot/MyReports/logos/myreportslogo.gif

Appears at the bottom of the My Reports pages, as shown in “My Reports Branding Example”, on page 175. Place this file on your VitalSuite NET and VitalSuite APPS Master and Aggregation servers.This file automatically replaces the existing Lucent logo as the default graphic.

.../vscommon/webroot/myvital/logos/<filename>

Placing an image in this directory on the System Master server lets users select the image when they personalize their My Vital page. This file can have any name and must be in GIF or JPEG format.

....................................................................172

..........................................................................................................................................................................................Brand the Web Console

When to use

Use this procedure to customize pages in the Web Console with your own images, such as your organization’s logo.

Before you begin

Obtain the GIF images you want to appear on the branded Web Console pages.

Related information

For more information about branding, refer to “Web Console branding guidelines”, on page 170.

Procedure

To brand the Web Console:

...........................................................................................................................................................................

1 Make sure each GIF image is sized to be appropriately displayed on the Web Console page.

Additional information: Refer to “Web Console branding guidelines”, on page 170 for the recommended size for each image.

...........................................................................................................................................................................

2 Rename each image and place in the appropriate directory on your VitalSuite Performance Management servers.

Additional information: Refer to “Web Console branding guidelines”, on page 170 for the correct name and location for these images.

...........................................................................................................................................................................

3 View the branded pages in the Web Console to make sure the custom images are appropriately displayed.

To view the new custom image on an existing My Report or standard report, you might need to regenerate the report.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................173

Web Console branding examples

..........................................................................................................................................................................................Web Console branding examples

Purpose

This topic provides branding examples of the Web Console.

Login page example

The following figure shows where customized branding appears on the Web Console login page. The same customized branding appears on the initialization page that displays once you have entered your account information and are waiting to be logged into the system.

The Login page contains Lucent branding that cannot be removed. The custom image you add to this page appears below the Lucent branding.

Legend1. Custom branding (optional)

2. Lucent branding (permanent)

b c

....................................................................174

Standard reports example

The following figure shows where the customized branding appears on the standard reports. The customized branding on the standard reports also appears in the PDF and batch email versions of the reports.

The standard report pages contain Lucent branding that cannot be removed. The custom image you add to this page appears along side the Lucent branding.

Legend1. Lucent branding (permanent)

2. Custom branding (optional)

b c

....................................................................175

Web Console branding examples

My Reports Branding Example

The following figure shows where customized branding appears on the MyReports pages. The customized branding on My Reports also appears in the PDF and batch email versions of the reports.

Legend1. Replaceable Lucent logo

b

....................................................................176

My Vital Branding Example

Users can brand their My Vital page with any GIF or JPEG image you place in the <install_dir>/vscommon/webroot/myvital/logos directory. After an image is placed in this directory, users can select the logo from a drop-down list that appears when they personalize their My Vital page.

For information on personalizing the My Vital page, refer to the VitalSuite Application Performance Management Software User’s Guide or the VitalSuite Network Performance Management Software User’s Guide.

Legend1. Replaceable Lucent logo

2. Users can personalize their My Vital page and select a new logo

b c

....................................................................177

Add a message to the login page

..........................................................................................................................................................................................Add a message to the login page

When to use

Use this procedure to add a message to the VitalSuite Performance Management login page. Adding a message is a good way to notify your VitalSuite Performance Management users about scheduled downtimes, recent upgrades, and who to contact for problems.

Before you begin

Make sure you have directory access to your VitalSuite Performance Management server.

Related information

For information about logging into a VitalSuite Performance Management server, refer to your VitalSuite Network Performance Management User’s Guide or VitalSuite Application Performance Management Software User’s Guide.

Procedure

To add a message to the VitalSuite Performance Management login page:

...........................................................................................................................................................................

1 Compose your message in a text file named customer_message.txt. The message cannot be longer than 256 characters.

...........................................................................................................................................................................

2 Copy the text file to the following directory on the VitalSuite Performance Management server that you want to display the message (usually the System Master server): <VS_install_dir>\vscommon\webroot\config.

...........................................................................................................................................................................

3 Go to your login page and verify the message is displayed.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................178

Example

The following example shows the login page with a custom message about the VitalSuite Performance Management version running on the system.

Legend1. Custom text message on the login page

b

....................................................................179

VitalAgent branding

..........................................................................................................................................................................................VitalAgent branding

Overview

You can replace the default VitalAgent icons that appear in the Windows system tray for VitalAgent and VitalAgentIT with your own customized graphic, such as your organization’s logo. Animated images can also be used globally or for specified domains for users with VitalAgent or VitalAgentIT installed on their systems.

Customized images must be an animated bitmap file (.bmp), and can replace system tray, Startup program list, and animated icons seen in the VitalAgent dashboard. No other icons displayed by the VitalAgent dashboard can be customized.

You can design your own .bmp files that contain the icons in a strip (multiple-image) format for animation such as the one that appears in the following figure.

The .bmp files are described in “Branding options”, on page 180. If a particular .bmp is not provided, then the icons packaged in the VitalAgent or VitalAgentIT executable are used.

Example

The following example shows an animated .bmp file with required and optional icons.

Legend1. Mandatory icons

2. Optional animation icons

3. Initial state

4. Green state

5. Error state

Requirements

Each custom bitmap file must adhere to the following requirements:

• 24 x 24 pixels for each image in the sequence

• Exact named files as shown in “Branding options”, on page 180 (code searches for specified filenames)

• Mandatory first three images:

• initial state image—displayed when the operation starts

• green state image—displayed when the operation is in progress

• error state image—displayed when the operation encounters an error

b c

d e f

....................................................................180

• Optional animation images: the number of these images varies based on type of strip and is different for each animation. If the animation icons are provided, then they are displayed in a round-robin sequence, the first icon displayed first, then the second and so on, until all the animation icons are displayed. After the last animation icon is displayed, the first animation icon is displayed again and the cycle continues until the monitored operation has completed.

Branding options

The following table lists the eight different animated files you can brand.

The eight VitalAgent default .bmp files are downloaded from the server by the VCC program when VitalAgent is installed on a client machine.

Global and domain-specific implementations

To use your customized .bmp icons globally, install the files in the Default directory on the VitalSuite APPS Help functionality Master server:

<installdir>\Program Files\VSCommon\Webroot\Grouplist\Default

Bitmap name-default icons Description

ToneAnim.bmp During a modem dial-up, after the line goes off-hook and dial tone is detected.

HandAnim.bmp Progress during a modem dial-up, when a hand-shake between the two modems is ongoing.

ScanAnim.bmp Successful logon to dial-up modem.

IpNegAnim.bmp When a logon is successful and the user’s computer is being registered on the network.

ConAnim.bmp Successful logon and the user’s computer is being connected to the Server computer.

NormalAnim.bmp Normal operation of VitalAgent. Bitmaps show cross icon in green background. The second image (green state icon) on strip is the default product icon and is displayed in the Startup menu.

AlarmAnim.bmp (standard VitalAgent cross alarm icon, but shown all in red)

Used whenever a VitalAgent posts an alarm. These bitmaps display the cross icon on red a background.

....................................................................181

VitalAgent branding

To use your customized .bmp icons in specific domains, install the files in the domain directory on the VitalSuite APPS Help functionality Master server:

<installdir>Program Files\VSCommon\Webroot\Grouplist\<DomainID>

Where <DomainID> is the name of a specific domain (i.e., DID2, DID3).

Important! You can use customized icons for any or all of the VitalAgent default icons. VitalAgent searches first in the domain directories and then the default directory for new icons. If bitmaps are not found in either of these directories, the default bitmaps are used.

....................................................................182

..........................................................................................................................................................................................Restore the default VitalAgent icons

When to use

This topic describes the database setting to use to restore the default VitalAgent icons.

Database setting

The database setting to use to restore the default VitalAgent icons is VS_USE_DEFAULT_TRAY_ICONS (STRING VALUE = 1).

The VCC program reads this flag every time a configuration check is performed.

Where to enter the database setting

Enter the database setting on the Web Console’s ADMIN | Agents | Database values form. For more information, refer to the VitalAgent Administrator’s Guide.

....................................................................183

8 Back up and restore

..........................................................................................................................................................................................Overview

Purpose

This chapter provides detailed guidelines you should refer to when developing backup and restore procedures for your VitalSuite Performance Management environment.

Contents

This chapter covers the following topics:

Backup guidelines for VitalSuite NET UNIX 185

Backup considerations 186

Tablespaces and file systems to back up 187

Introduction to the VitalSuite NET UNIX backup and restore scripts 189

Back up VitalSuite NET UNIX data 190

Backup guidelines for VitalSuite NET (Windows) and VitalSuite APPS 192


Databases to include in your backup 194

File systems to include in your backup 196

Back up VitalSuite APPS and VitalSuite NET data with MS-SQL Server 197

Enable MS-SQL Server to back up to a network drive 203

Other backup considerations 204

Other data to include with your backup 205

Backup schedule guidelines 206

....................................................................184

Restore guidelines 207

Before you restore 208

Restore VitalSuite NET UNIX data 192

Restore VitalSuite APPS and VitalSuite NET data with MS-SQL Server 204

Attach databases 215

Restore file systems from a backup 217

....................................................................185

Overview

Backup guidelines for VitalSuite NET UNIX

..........................................................................................................................................................................................Overview

Purpose

This topic provides guidelines for backing up and restoring VitalSuite NET data on UNIX systems. If you are running VitalSuite NET on Windows, refer to “Backup guidelines for VitalSuite NET (Windows) and VitalSuite APPS”, on page 192.

If VitalSuite ART is also installed on your VitalSuite NET UNIX system, refer to the VitalSuite Advanced Reporting Tool Administrator’s Guide for information on backing up VitalSuite ART data.

Contents



Tablespaces and file systems to back up 187

Introduction to the VitalSuite NET UNIX backup and restore scripts 189

Back up VitalSuite NET UNIX data 190

....................................................................186

..........................................................................................................................................................................................Backup considerations

Role of the Oracle DBA

Only an experienced Oracle database administrator should develop backup procedures for VitalSuite NET data. For more detailed information on backing up data, refer to the Oracle9i User-Managed Backup and Recovery Guide from Oracle.

Packaged scripts versus third-party applications

VitalSuite NET UNIX comes with scripts you can use to back up and restore data. Running these scripts temporarily stop data collection and aggregation. For this reason, you may want to use a third-party application to back up and restore data based on the guidelines in this chapter.

How to avoid data loss during back ups

This topic describes the data loss problem that can occur when performing backups and provides a solution to this issue.

Data loss problem

By default, the VitalSuite NET database runs in NOARCHIVELOG mode. When in this mode, consistent backups of the database can be performed but only if the database is closed. In general, you should avoid closing the database on any server that functions as a VitalSuite NET Polling server. Closing the database on a Polling server disrupts data collection and will likely result in data loss.

Solution

One solution to avoid data loss is to install your VitalSuite NET Polling servers on separate, stand-alone systems, and perform consistent backups of only the VitalSuite NET Aggregation and Master database. Closing the database on the Aggregation and Master servers during backup does not result in a loss of active data collection.

When your Polling servers are on separate, stand-alone systems, you can choose to not back up these servers. Even in the event that a Polling server’s database becomes corrupted, data loss is typically limited to not more than two hours of aggregated statistics plus all the up-to-the-minute data.

Another option is to perform inconsistent backups, which allow you to continue active data collection and aggregation during the backup process. However, you must switch the database to ARCHIVELOG mode for this type of backup.

....................................................................187

Tablespaces and file systems to back up

..........................................................................................................................................................................................Tablespaces and file systems to back up

Purpose

This topic describes the VitalSuite NET tablespaces and file systems that are important to include in your backup. If you are using a third-party application to back up VitalSuite NET data, make sure to include these tablespaces and file systems in the backup file.

Important tablespaces

You can perform selective physical backups of the VitalSuite NET tablespaces listed in the following table. However, to perform consistent backups of a VitalSuite NET tablespace running in NOARCHIVELOG mode, you must first take the tablespace offline.

If a server has more than one role (such as functioning as an Aggregation and Polling server), back up all of the relevant tablespaces on that server.

Common

VSDBA

VitalSuite NET Master server

VNMCOMMON VNMCOMMON_INDEX

VNMSYSTEM VNMSYSTEM_INDEX

VNMDOMAIN VNMDOMAIN_INDEX

VNMINIT VNMINIT_INDEX

VitalSuite NET Aggregation server

VNACOMMON VNACOMMON_INDEX

VNASYSTEM VNASYSTEM_INDEX

VNAINIT VNAINIT_INDEX

VNADOMAIN VNADOMAIN_INDEX

VNACONFIG VNACONFIG_INDEX

VNAPOLLER VNAPOLLER_INDEX

VNASTATS VNASTATS_INDEX

VitalSuite NET Polling server

VNPSYSTEM VNPSYSTEM_INDEX

VNPINIT VNPINIT_INDEX

....................................................................188

Important VitalSuite NET file systems

This topic describes important VitalSuite NET file systems to back up.

Web-users directory tree

The web-users directory tree contains data about the user accounts you create. This data is stored in the following directory:

/<Installation Directory>/vscommon/webroot/web-users

Important! If a failure occurs and you need to reinstall a VitalSuite Performance Management product and you cannot restore the web-users directory, all your user configurations (such as My Vital specifications) will be lost.

Configuration files for batch emails, heat charts, and reports

If you have configured batch emails in VitalSuite NET, all, some, or none of the files listed in the following table may exist.

If you have configured Schedule Heat Chart or Reports in VitalSuite NET, you can protect this configuration data by backing up the following configuration files:

Configuration files created using MIBWorks

If you built collectors with MIBWorks, the configuration files (with .cfg extensions) for these collectors are located in either the /config/local directory or the /config/default directory of your VitalSuite NET installation.

VNPPOLLER VNPPOLLER_INDEX

VNPUTM VNPUTM_INDEX

File Name Location

email.lst /<Installation Directory>/vscommon/webroot/config

emailst.lst /<Installation Directory>/vscommon/webroot/config

mailAliases /<Installation Directory>/vscommon/webroot/config

mailHost /<Installation Directory>/vscommon/webroot/config

File Location

crsched.cfg and hcsched.cfg

/<Installation Directory>/vscommon/webroot/config/vitalnet

mvsched.cfg /<Installation Directory>/vscommon/webroot/My Vital/schedule

....................................................................189

Introduction to the VitalSuite NET UNIX backup and restore scripts

..........................................................................................................................................................................................Introduction to the VitalSuite NET UNIX backup and restore scripts

Overview

VitalSuite NET (UNIX version only) comes bundled with backup and restore scripts that take a logical backup of the VitalSuite NET database and important file systems and restore the data if needed. You can either use these scripts, or follow the guidelines provided in “Backup guidelines for VitalSuite NET UNIX”, on page 185 to create your own backup process.

The backup process can take hours to complete on large VitalSuite NET databases.

Script location

The backup and restore scripts are located in the /<Installation Directory>/vitalnet/program directory on your VitalSuite NET server. The file names are vsbackup.sh and vsrestore.sh.

Backup tasks performed

The backup script performs the following tasks:

• Stops the VitalSuite NET collectors, Apache web server and the Cron job and restarts these processes once the backup is complete.

Important! Data collection, data aggregation, report generation, and the Web Console are disabled while these processes are down.

• Backs up the /<Installation Directory>/vscommon/webroot/web-users directory that contains information about your user accounts.

• Backs up the following batch email configuration files located in the <Installation directory>/vscommon/webroot/config directory:

• email.lst and emailst.lst files

• mailAliases and mailhost files

These files only exist if you have configured batch emails in VitalSuite NET.

• Backs up all the configuration files located in the /<Installation directory>/vscommon/webroot/config/vitalnet directory.

• Performs a logical backup of all the VitalSuite NET schemas on the system.

If a server has multiple VitalSuite NET schemas (such as when it is acting as a Master, Aggregation, and Polling server), the script automatically backs up the schemas in a single file.

Restore tasks performed

The restore script performs the following tasks:

• Removes all database objects and users created as part of the VitalSuite NET installation.

• Restores all database objects and users from the backup file.

• Restores important file systems with information about user accounts and batch emails.

....................................................................190

..........................................................................................................................................................................................Back up VitalSuite NET UNIX data

When to use

Use this procedure to backup VitalSuite NET UNIX data using the packaged back up script.

Important! Data collection, data aggregation, report generation, and the Web Console are disabled while VitalSuite NET data is backed up using the script.

Before you begin

Make sure you know the password of the system user account for the Oracle database.

Related information

For more information about using the VitalSuite NET scripts, refer to “Introduction to the VitalSuite NET UNIX backup and restore scripts”, on page 189.

Procedure

To use the backup script:

...........................................................................................................................................................................

1 Open a terminal to the VitalSuite NET system and log in as root.

...........................................................................................................................................................................

2 Make sure the oracle account has write access to the directory that will store the backup files.

Result: The backup script uses the oracle account to backup the database and must have write access to the directory you specify when running the script.

...........................................................................................................................................................................

3 Change to the following directory:

cd /<Installation Directory>/vitalnet/program

...........................................................................................................................................................................

4 Run the backup script as follows:

./vsbackup.sh <Backup Directory>

where <Backup Directory> is the base location where you want the backup files to be stored. The oracle user account must have write access to this directory.

....................................................................191

Back up VitalSuite NET UNIX data

...........................................................................................................................................................................

5 Enter the password of the system user account for the Oracle database.

Result: The backup script does the following:

• Creates a subdirectory called vitalbackup under the location you specified.

• Compresses the file system data into a single backup file called vnfiles_<dayofweek>.tar.gz. For example, if you use the backup script on a Wednesday and back up to the /tmp directory, the following file would be created: /tmp/vitalbackup/vnfiles_Wed.tar.gz.

• Creates a /<base directory>/vitalbackup/Vitanet.<dayofweek> directory and stores the logical database backup files in this directory.

• Removes old backup files from the corresponding weekday in the previous week. So if you backup to the same directory on the same day, the previous week’s backup is always overwritten.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................192

Backup guidelines for VitalSuite NET (Windows) and VitalSuite APPS

..........................................................................................................................................................................................Overview

Purpose

This section provides guidelines for backing up and restoring VitalSuite NET and VitalSuite APPS data in a Windows environment.

Contents



Databases to include in your backup 194

File systems to include in your backup 196

Back up VitalSuite APPS and VitalSuite NET data with MS-SQL Server 197

Enable MS-SQL Server to back up to a network drive 203

....................................................................193

Backup considerations

..........................................................................................................................................................................................Backup considerations

Overview

VitalSuite APPS and VitalSuite NET (Windows version) do not come with backup and restore applications. Therefore, the VitalSuite Performance Management administrator is responsible for using the backup capabilities in MS-SQL Server or a third-party application to backup and restore data based on the guidelines in this chapter.

If VitalSuite ART is installed on your VitalSuite NET system, refer to the VitalSuite Advanced Reporting Tool Administrator’s Guide for information on backing up VitalSuite ART data.

MS-SQL Server considerations

If you are using MS-SQL Server to perform backups, note that Transaction Log backups cannot be used with VitalSuite Performance Management product databases. The VitalSuite Performance Management products use Non-Logged Bulk Inserts and Select Into statements, which are incompatible with Transaction Log backups.

Third-party application considerations

If you use a third-party backup application other than MS-SQL Server to perform a backup of live data, your backup application must be able to use the live database backup facilities built into MS-SQL Server. This facility is provided by the Backup Statement of MS-SQL Server and may also be supported by some third-party backup products.

The MS-SQL Server databases are kept in files in the Windows file system and cannot be backed up as ordinary files while MS-SQL Server is running or paused.

....................................................................194

..........................................................................................................................................................................................Databases to include in your backup

Purpose

This topic lists the various VitalSuite APPS and VitalSuite NET databases to include in your backup. Use these database names for live backups of your products’ SQL databases.

File formats

VitalSuite Performance Management product SQL database files always have a file name ending in one of the following extensions: *.MDF, *.NDF, or *.LDF.

Database names and locations

Important! If needed, you can restore your VitalSuite Performance Management product software from the appropriate installation CD. Therefore, there is no need to back up the VitalSuite Performance Management product directory trees.

If a server has more than one role (for example, if it functions as an Aggregation and Polling server), back up all of the relevant databases on that server.

RoleDatabase name Database location

VitalSuite APPS Analysis functionality

Master VAMaster <InstallDir>\VitalAnalysis\Data\VAMaster

Aggregation VAAggr <InstallDir>\VitalAnalysis\Data\VAAggr

Posting VAPost <InstallDir>\VitalAnalysis\Data\VAPost

VitalSuite APPS Analysis functionality/Help functionality

Config VAHConfig <InstallDir>\VitalSolution\Data\VAHConfig

VitalSuite APPS Help functionality

Master VHMaster <InstallDir>\VitalHelp\Data\VHMaster

Posting VitalHelp <InstallDir>\VitalHelp\Data\VHPost

VitalSuite NET

Master VNMaster <InstallDir>\VitalNet\Data\VNMaster

....................................................................195

Databases to include in your backup

Other MS-SQL Server databases

Other MS-SQL Server databases (such as the MSDB, Northwind, Pubs, and Model databases) are not used by the VitalSuite Performance Management products. Therefore, you do not need to back them up. If your MS-SQL Server Master database is damaged, you should re-install MS-SQL Server. It is easier to restore the Master database by reinstalling MS-SQL Server than to restore the database from a backup.

Aggregation VNAggr <InstallDir >\VitalNet\Data\VNAggr<InstallDir>\VitalNet\Data\Microsoft

Important! Normally, the VNAggr database resides in the VitalNet\Data\VNAggr directory only. However, if VitalSuite NET was upgraded from version 7.x to 8.x, the database files for the VNAggr database may be distributed across the VitalNet\Data\VNAggr and VitalNet\Data\Microsoft directories.

Poller VNPoller <Install Dir>\VitalNet\Data\VNPoller

RoleDatabase name Database location

....................................................................196

..........................................................................................................................................................................................File systems to include in your backup

Purpose

This topic describes the file systems that should be included in your backup.

Web-users directory tree

The web-users directory tree contains data necessary for all the user accounts you create. The following directory needs to be backed up for all VitalSuite Performance Management products:

<Installation Directory>\VSCommon\webroot\web-users

Important! If a failure occurs and you need to reinstall a VitalSuite Performance Management product and you cannot restore the web-users directory, all your user accounts will be lost and you will need to recreate them manually.

Customized transaction types (VitalSuite APPS only)

If you have created customized transaction types using Transact Toolkit, or you have modified any of the predefined transaction definitions, your additions and modifications are stored in the following directory tree:

<Installation Directory>\VSCommon\webroot\Grouplist

You should back up this entire directory tree.

Configuration files created through MIBWorks (VitalSuite NET only)

If you have built collectors with MIBWorks, the configuration files (with .cfg extensions) for these collectors are in <Install_Dir>\VitalNet \Config\local or <Install_Dir>\VitalNet \Config\Default.

Batch email configuration files (VitalSuite NET and VitalSuite APPS Analysis functionality)

If you have configured batch emails in VitalSuite NET or VitalSuite APPS, you must back up the following files from <Install_Directory>\VSCommon\webroot\Config. Depending on your use of batch email, all, some, or none of these files may exist:

VitalSuite NET VitalSuite APPS

Email.lst vaEmail.lst

EmailSt.lst vaEmailSt.lst

mailAliases mailAliases

mailHost mailHost

....................................................................197

Back up VitalSuite APPS and VitalSuite NET data with MS-SQL Server

Back up VitalSuite APPS and VitalSuite NET data with MS-SQL

..........................................................................................................................................................................................Server

When to use

Use this procedure to back up the VitalSuite APPS and VitalSuite NET databases using the MS-SQL server.

The backup method in this section does not use some of MS-SQL Server’s advanced backup options. To use options that are not specified in the following procedures, consult your database administrator.

Before you begin

Make sure you can connect to your VitalSuite APPS and VitalSuite NET databases using Enterprise Manager.

Related information

For more information about backing up VitalSuite APPS and VitalSuite NET data with MS-SQL Server, refer to “Backup considerations”, on page 193.

Procedure

To back up your VitalSuite NET and VitalSuite APPS databases using MS-SQL Server:

...........................................................................................................................................................................

1 Make sure the SQLServerAgent service is running on the VitalSuite Performance Management server you are backing up.

Additional information: The Windows Services screen (Start | Programs | Administrative Tools | Services) displays the status of SQLServerAgent. You need to manually start this service if it is not running.

...........................................................................................................................................................................

2 Click Start | Programs | Microsoft SQL Server | Enterprise Manager to launch Enterprise Manager.

....................................................................198

...........................................................................................................................................................................

3 Click within the Enterprise Manager to expand the server on which you have installed VitalSuite APPS or VitalSuite NET.

Example

...........................................................................................................................................................................

4 Expand the Management folder.

Example

...........................................................................................................................................................................

5 Right-click DataBase Maintenance Plans, and click New Maintenance Plan.

Example

Result: The Database Maintenance Plan Wizard opens.

....................................................................199


...........................................................................................................................................................................

6 Click Next.

Result: The Select Databases window displays.

...........................................................................................................................................................................

7 Select the option for These Databases, and select the appropriate VitalSuite APPS or VitalSuite NET databases depending on the components installed on your system.

Additional information: Refer to “Databases to include in your backup”, on page 194 for more information.

...........................................................................................................................................................................

8 Click Next.

Result: The Update Data Optimization Information window displays.

...........................................................................................................................................................................

9 Accept the default settings on the Updated Data Optimization Information window by clicking Next.

Database optimization should only be performed with all VitalSuite APPS processes stopped.

Result: The Database Integrity Check window displays.

....................................................................200

...........................................................................................................................................................................

10 Accept the default settings on the Database Integrity Check window by clicking Next.

Database integrity checking should only be performed with all VitalSuite APPS processes stopped.

Result: The Specify the Database Backup Plan window displays.

...........................................................................................................................................................................

11 In the Specify the Database Backup Plan window, do the following:

• Unselect the Verify the integrity of the backup when complete check box.

• Choose a tape or disk location for the backup file.

• Click Change to change the backup schedule.

Result: The Edit Recurring Job Schedule window displays.

...........................................................................................................................................................................

12 Specify the recurring backup schedule as follows:

• Select Daily from the Occurs section.

• Specify 4:15 AM in the Occurs once at option box. This is the recommended time to schedule backups because no other VitalSuite Performance Management processes are running at this time.

• Select the No end date option and click OK.

Result: You are returned to the Specify the Database Backup Plan window.

...........................................................................................................................................................................

13 Click Next on the Specify the Database Backup Plan window.

Result: The Specify the Backup Disk Directory window displays.

....................................................................201


...........................................................................................................................................................................

14 Do the following:

• Specify the backup disk directory (required only if saving the backup to disk).

• Select the Remove files older than option box and specify a time frame. This enables the MS-SQL Server to remove old backups so your disk does not run out of space in the future.

Example

...........................................................................................................................................................................

15 Click Next.

Result: The Specify the Transaction Log Backup Plan window displays.

...........................................................................................................................................................................

16 Accept the default settings on the Specify the Transaction Log Backup Plan window by clicking Next.

Transaction log backups cannot be performed on VitalSuite Performance Management databases.

Result: The Reports to Generate window displays.

...........................................................................................................................................................................

17 Accept the default settings on the Reports to Generate window by clicking Next.

Result: The Maintenance Plan History window displays.

...........................................................................................................................................................................

18 Accept the default settings on the Maintenance Plan History window by clicking Next.

Result: The Completing the Database Maintenance Plan Wizard window displays.

...........................................................................................................................................................................

19 Enter the plan name and review the plan settings.

....................................................................202

...........................................................................................................................................................................

20 Click Finish to accept the settings or Back to change the settings.

Result: Once the database maintenance plan is created, the following window appears:

...........................................................................................................................................................................

21 Click OK to complete the creation process.

...........................................................................................................................................................................

22 Verify your maintenance plan was successfully created by selecting the Database Maintenance Plan icon under the Management folder.

...........................................................................................................................................................................

23 If you selected to back up files to a network drive, verify MS-SQL Server has permission to write to the network drive.

Additional information: Refer to “Enable MS-SQL Server to back up to a network drive”, on page 203.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................203

Enable MS-SQL Server to back up to a network drive

..........................................................................................................................................................................................Enable MS-SQL Server to back up to a network drive

When to use

If you are using MS-SQL Server to back up data to a network drive, use these procedures to change the account the MSSQLSERVER service uses to access the network drive. The default account for the service does not provide privileges outside of the service’s own system.

Before you begin

Make sure you have selected or created a user account that the MSSQLSERVER service can use to access the network drive.

Related information

For more information about backing up VitalSuite APPS and VitalSuite NET data, refer to “Back up VitalSuite APPS and VitalSuite NET data with MS-SQL Server”, on page 197.

Procedure

To give MS-SQL Server permission to back up to a network drive:

...........................................................................................................................................................................

1 From the Windows Control Panel, open the Services window.

...........................................................................................................................................................................

2 Right-click on the MSSQLSERVER service, and select Properties.

Result: The Properties window displays.

...........................................................................................................................................................................

3 Select the Logon tab.

...........................................................................................................................................................................

4 Specify an account and password that the MSSQLSERVER service can use to access the network drive.

Additional information: One way to do this is to set the account and password for the network drive the same as the account and password for the MSSQLSERVER service.

...........................................................................................................................................................................

5 Select OK and then close the Services window.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................204

Other backup considerations

..........................................................................................................................................................................................Overview

Purpose

This section provides general guidelines you should consider as you formulate your backup and restore policies.

Contents


Other data to include with your backup 205

Backup schedule guidelines 206

....................................................................205

Other data to include with your backup

..........................................................................................................................................................................................Other data to include with your backup

System records

In addition to backing up your databases and file systems, you should also keep a record of the following information:

• Computer name

• TCP/IP computer name (may be different from the computer name on Windows)

• TCP/IP configuration (IP address, subnet mask, gateway, domain list, and DNS address)

• Disk partition letters and partition sizes

• Drive letter and directory where the VitalSuite Performance Management product is installed

• Swap file configuration

• VitalSuite Performance Management product version number

Important! All of the databases, directories and files you back up are version-dependent. Make sure the data you use for a restore comes from the same VitalSuite Performance Management software version that is currently installed on your server.

Installation programs

In the event of a severe system failure, you may need to re-install your operating system, database product (MS-SQL Server or Oracle), as well as the VitalSuite Performance Management products. Therefore, the installation programs for these components should be kept readily available. Backing up these applications with your VitalSuite Performance Management data and file systems is outside the scope of this document.

....................................................................206

..........................................................................................................................................................................................Backup schedule guidelines

Purpose

This topic provides guidelines on when to schedule recurring backups of your VitalSuite Performance Management data. It is important to schedule back ups when other VitalSuite Performance Management processes are not running so data collection is not interrupted.

Guidelines

To minimize the data collection gap that occurs when a server or database needs to be restored, you should schedule backups daily. If you do not consider your VitalSuite Performance Management data to be critical, you can schedule weekly backups during the weekend.

Optimal time for backups

You should schedule backups for early in the evening because the following batch processes are performed by VitalSuite Performance Management products late at night:

• VitalSuite NET resource discovery is typically configured to start at 10:00 pm (server time) and can run from a few minutes to 5 or 6 hours depending on the number of resources being monitored. The start time can be configured.

• VitalSuite NET batch report generation starts at 2:30 am.

• VitalSuite APPS batch report generation and re-aggregation starts at midnight.

If possible, do not schedule backups when the above processes are running. You minimize the load on your server by not scheduling backups that overlap with these processes.

Late night backups

If you need to stop your database product for backups late at night, do this on Friday night only. On Saturday night (into Sunday morning) special report batches occur on VitalSuite NET and VitalSuite APPS that are only scheduled once a week. If you disable nightly report batches on other nights, the performance of the Web Console will be impacted the next day for users viewing reports.

Important! Once you have implemented your backup procedures, try to restore data from your backup so you can resolve any issues with your backup procedures while your VitalSuite Performance Management product is intact.

....................................................................207

Overview

Restore guidelines

..........................................................................................................................................................................................Overview

Purpose

This section provides guidelines for restoring VitalSuite Performance Management data.

Contents


Before you restore 208

Restore VitalSuite NET UNIX data 210

Restore VitalSuite APPS and VitalSuite NET data with MS-SQL Server 212

Attach databases 215

Restore file systems from a backup 217

....................................................................208

..........................................................................................................................................................................................Before you restore

Purpose

This topic provides guidelines you should read prior to restoring VitalSuite Performance Management data. The guidelines apply to recovering data on:

• The original VitalSuite Performance Management server

• A new server

Guidelines for recovering data on the original server

If you are restoring data to the original server, you may need to uninstall the VitalSuite Performance Management product to ensure a clean install from the product CD. If the database has been corrupted, you may also need to re-install the database product (MS-SQL Server or Oracle) including service packs/patchsets.

If possible, restore the VitalSuite Performance Management products to the same drive and directory. If you installed patches for your VitalSuite Performance Management product since the last version upgrade, re-apply the patches before restoring the data. Once you have re-installed your VitalSuite Performance Management product, you can restore your data.

Guidelines for recovering data on a new server

If you are restoring data to a new server, follow this process:

1. Install and configure the operating system and database product (MS-SQL Server or Oracle) and apply required patches.

2. Set up the machine name, IP configuration, security (domain and logins), disk partitions, and service packs to match the original server.

3. If your new server has a different IP address than the original server, obtain a new license key for the VitalSuite Performance Management product.

Additional information: Refer to the VitalSuite Performance Management Software Administrator’s Guide for information on how to obtain a new license key.

4. Test the new server’s network connectivity.

5. Install the VitalSuite Performance Management product on the new server.

Important! Make sure the version of the VitalSuite Performance Management product matches the version installed on the original server. In addition, the VitalSuite Performance Management product should be installed on the same drive and directory as the original server.

6. Rename the <install>/vscommon/vspatch directory.

Example: vspatch_old

7. Re-apply any patches you installed since the last VitalSuite Performance Management version upgrade.

....................................................................209

Before you restore

8. Restore your VitalSuite Performance Management data.

Additional information: Refer to the following topics for more information:

• “Backup guidelines for VitalSuite NET (Windows) and VitalSuite APPS”, on page 192.

• “Other backup considerations”, on page 204

9. If you have created collectors with MIBWorks, copy the configuration files to the \Config\Local or \Config\Default folder on the VitalSuite NET installation on the new server.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................210

..........................................................................................................................................................................................Restore VitalSuite NET UNIX data

When to use

Use this procedure to restore VitalSuite NET data using the bundled UNIX scripts.

Before you begin

Make sure you know the password of the system user account for your Oracle database.

Related information

For more information about restoring VitalSuite NET data, refer to:

• “Introduction to the VitalSuite NET UNIX backup and restore scripts”, on page 189

• “Before you restore”, on page 208

Procedure

To use the restore script, follow these steps:

...........................................................................................................................................................................

1 Read the guidelines provided in “Before you restore”, on page 208.

...........................................................................................................................................................................

2 Verify the backup files you want to use for the restore are located in the /<base directory>/vitalbackup directory.

...........................................................................................................................................................................

3 Open a terminal to the VitalSuite NET system and log in as root.

...........................................................................................................................................................................

4 Change to the following directory:

cd /<Installation Directory>/vitalnet/program

...........................................................................................................................................................................

5 Run the restore script as follows:

./vsrestore.sh <Base Backup Directory> <Weekday>

where <Base Backup Directory> is the same directory you specified during the backup, and <Weekday> is the extension on that file, such as Mon, Tue, or Wed.

Example: To restore last Wednesday’s backup file from the /tmp directory, you would execute the following command:

./vsrestore.sh /tmp Wed

...........................................................................................................................................................................

6 Enter y to confirm you want to restore using the specified backup files.

....................................................................211

Restore VitalSuite NET UNIX data

...........................................................................................................................................................................

7 Enter the password of the system user account for the Oracle database.

The restore process can take up to 45 minutes.

...........................................................................................................................................................................

8 If you have created collectors with MIBWorks, copy the configuration files (.cfg extensions) to the /config/local or /config/default directory of your VitalSuite NET installation.

Collectors created with MIBWorks are not restored with the automated script.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................212

Restore VitalSuite APPS and VitalSuite NET data with MS-SQL

..........................................................................................................................................................................................Server

When to use

Use this procedure to restore VitalSuite APPS or VitalSuite NET databases using MS-SQL Server.

When restoring databases from backups, note the following:

• If you are restoring data to a different location, such as to a different directory or drive letter, do not detach the existing database that has the same name.

• Always use the WITH REPLACE option on the restore.

• Typically, it takes twice as long to restore a database as it took to back it up

Before you begin

Make sure the database directory you are restoring exists on the server before you begin restoring data. MS-SQL Server does not create these directories during a database restore. Refer to “Databases to include in your backup”, on page 194 for a list of database directories.

Related information

For more information on restoring VitalSuite APPS data, refer to “Before you restore”, on page 208.

Procedure

To restore data using MS-SQL Server, follow these steps:

...........................................................................................................................................................................

1 Stop the VitalSuite Performance Management services.

Additional information: The System Status report displays the VitalSuite Performance Management services that are currently running on the system. Refer to the VitalSuite Performance Management Software Administrator’s Guide for information on viewing this report.

...........................................................................................................................................................................

2 If VitalSuite ART is installed on the same system as VitalSuite NET, refer to the VitalSuite Advanced Reporting Tool Administrator’s Guide for information on restoring VitalSuite ART data.

....................................................................213

Restore VitalSuite APPS and VitalSuite NET data with MS-SQL Server

...........................................................................................................................................................................

3 If the Real-time Event Analysis option is enabled on VitalSuite NET, stop the Real-time processes as follows:

a. Go to the /<Install_Dir>/Program directory

b. Run the following commandsRTAlarmStop.batRTGenStop.batRTSyncStop.bat

...........................................................................................................................................................................

4 Stop and restart MS-SQL Server to make sure there are no connections to the database(s).

You cannot restore data if MS-SQL Server is in use.

...........................................................................................................................................................................

5 Click Start | Programs | Microsoft SQL Server | Enterprise Manager to launch the Enterprise Manager.

...........................................................................................................................................................................

6 Click within the Enterprise Manager to expand the server on which you have installed VitalSuite APPS or VitalSuite NET.

Example

...........................................................................................................................................................................

7 Right-click on the Databases folder, and select All Tasks followed by Restore Database...

Result: The Restore Database window displays.

...........................................................................................................................................................................

8 From the Restore Database window, do the following:

a. Click the General tab

b. For Restore click Database.

c. Select the database to restore from the Restore as database field.

d. Select the same name in the Show backups of database field.

e. Click the check box for the backup copy from which you want to restore.

f. Click the Options tab and select the Force restore over existing database option.

....................................................................214

...........................................................................................................................................................................

9 Click OK to start the restore.

Result: A restore progress window displays followed by a message that the restore completed successfully.

...........................................................................................................................................................................

10 Run the re-attach script, as described in “Attach databases”, on page 215.

...........................................................................................................................................................................

11 Return to Step 8 on page 213 to restore the next database. Only one database can be restored at a time.

...........................................................................................................................................................................

12 Restart the following:

• MS-SQL Server

• VitalSuite APPS and VitalSuite NET services

...........................................................................................................................................................................E N D O F S T E P S

....................................................................215

Attach databases

..........................................................................................................................................................................................Attach databases

When to use

Once you restore data from a backup, follow this procedure to attach the VitalSuite Performance Management database you just restored.

The SQL attach scripts provided with your VitalSuite Performance Management product perform the following tasks:

• Attaches the specified database, if it is not already attached.

• Recreates the security (login and table ownership) for the database.

Before you begin

Before attaching a database, make sure you have restored the database as described in “Restore VitalSuite APPS and VitalSuite NET data with MS-SQL Server”, on page 212.

Related information

For more information about tasks to perform after restoring data, refer to “Restore VitalSuite APPS and VitalSuite NET data with MS-SQL Server”, on page 212.

Procedure

To attach a database:

...........................................................................................................................................................................

1 Open a command prompt window on the VitalSuite Performance Management server with the restored database.

...........................................................................................................................................................................

2 Navigate to the directory that contains the appropriate script for the database you restored.

Refer to the following table for the location of each database script.

Database name Script name Script location

VAMaster ms_attach_master.sql <Installidir>\VitalAnalysis\Data

VAAggr ms_attach_aggr.sql <Installidir>\VitalAnalysis\Data

VAPost ms_attach_post.sql <Installidir>\VitalAnalysis\Data

VAHConfig ms_attach_config.sql <Installidir>\VitalSolution\Data

VHMaster ms_attach_master.sql <Installidir>\VitalHelp\Data

VitalHelp ms_attach_post.sql <Installidir>\VitalHelp\Data

VNMaster ms_attach_master.sql <Installidir>\VitalNet\Data

....................................................................216

...........................................................................................................................................................................

3 Enter the following command (the “-E” parameter must be capitalized):

osql -E < ms_attach_ScriptName.sql > attach_ScriptName.log

where ScriptName is the name of the script identified in the previous step.

...........................................................................................................................................................................

4 If needed, use the ODBC Data Sources utility in the Control Panel to reconfigure the ODBC System DSNs.

Additional information: Refer to “VitalSuite Performance Management DSNs”, on page 106 for information on Window ODBC DSNs configuration.

...........................................................................................................................................................................E N D O F S T E P S

VNAggr ms_attach_aggr.sql <Installidir>\VitalNet\Data

VNPoller ms_attach_poller.sql <Installidir>\VitalNet\Data

Database name Script name Script location

....................................................................217

Restore file systems from a backup

..........................................................................................................................................................................................Restore file systems from a backup

When to use

Use this procedure to restore the following file systems from backup:

• Web-users directory tree (all VitalSuite Performance Management products)

• GroupList (VitalSuite APPS only)

• Batch email (VitalSuite NET only)

• MIBWorks collectors (VitalSuite NET only)

Before you begin

If your VitalSuite Performance Management product has been damaged, make sure to re-install the product from the CD before you restore any data.

Important! All of the databases, directories, and files you back up are version-dependent. Make sure that the data you use for a restore comes from the same VitalSuite Performance Management version that is currently installed on your server.

Related information

For more information about the file systems to include in your backup schedule, refer to “File systems to include in your backup”, on page 196.

Procedure

To restore the important file systems of your VitalSuite Performance Management servers:

...........................................................................................................................................................................

1 Rename or delete the existing web-users and grouplist directories.

...........................................................................................................................................................................

2 Copy the web-users and grouplist directory trees from the backup.

Important! Do not copy the entire Webroot directory tree. Copy only the web-users and grouplist tree.

...........................................................................................................................................................................

3 Restore the following directory trees:

• /<Installation directory>/vscommon/webroot/web-users

• /<Installation directory>/vscommon/webroot/Grouplist

...........................................................................................................................................................................

4 To restore the batch emails for VitalSuite NET, refer to “Configuration files for batch emails, heat charts, and reports”, on page 188 for the batch email files to restore.

....................................................................218

...........................................................................................................................................................................

5 If you have created collectors with MIBWorks, copy the configuration files (with .cfg extensions) to the /Config/Local or /Config/Default directory of your VitalSuite NET installation.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................219

9 Move VitalSuite NET databases

..........................................................................................................................................................................................Overview

Purpose

This document describes how to modify an existing install so that the databases can be stored in a different location other than the VitalSuite NET executables.

Contents

This technical note discusses the following topics:

Important information 221

Database files 222

Recommended location and directory names for the moved database files 224

Windows short names 225

Move VitalSuite NET databases 226

Process to move the VitalSuite NET databases 227

Query and save the sysfiles 228

Stop the VitalSuite NET services 230

Detach the database 232

Edit the SQL attach scripts 234

Edit the registry 236

Attach the database 238

Test and verification 240

Process to verify a successful database move 241

....................................................................220

Check the database configuration 242

Check the poller DSN configuration 244

Verify product operation 246

....................................................................221

Important information

..........................................................................................................................................................................................Overview

Purpose

This section discusses the database files, recommended location and directory names for the moved database files, and Windows short names.

Contents

This section discusses the following topics:

Database files 222



....................................................................222

..........................................................................................................................................................................................Database files

Purpose

It is a requirement of VitalSuite NET that the data files for a database be kept together. The transaction log file can be moved together with the database files, or moved to a different location.

File extension

The following table lists the file extension for each file type:

Database files

The following table lists the location and files names for the Master, Aggr, and Poller databases and attach SQL scripts:

File Type Extension

Master database files .MDF

Additional database data files .NDF

Transaction log .LDF

Database Location File name

VNMaster %INSTALLDIR%\VitalNet\Data\VNMaster • VNMCommon.ndf• VNMDomain.ndf• VNMImport.ndf• VNMInit.ndf• VNMLog.ldf• VNMSystem.mdf• VNMTemp.ndf• VNMStats.ndf

VNAggr %INSTALLDIR%\VitalNet\Data\VNAggr • VNACommon.ndf• VNAConfig.ndf• VNADomain.ndf• VNAImport.ndf• VNAInit.ndf• VNALog.ldf• VNAPoller.ndf• VNAStats.ndf• VNASystem.mdf• VNATemp.ndf

....................................................................223

Database files

Important! Do not change the names of the VitalSuite NET database files. If the files have been renamed, there are missing files, or additional files in the directory, do not perform the procedure for moving the database files and contact Lucent Technical Support.

VNPoller %INSTALLDIR%\VitalNet\Data\VNPoller • VNPImport.ndf• VNPInit.ndf• VNPLog.ldf• VNPPoller.ndf• VNPSystem.mdf• VNPTemp.ndf• VNPUtm.ndf• VNPCommon.ndf• VNPStats.ndf

Attach SQL scripts

%INSTALLDIR%\VitalNet\Data • ms_attach_aggr.sql• ms_attach_master.sql• ms_attach_poller.sql


....................................................................224

Recommended location and directory names for the moved database

..........................................................................................................................................................................................files

Purpose

This topic discusses the recommended location and directory names for the moved database files.

Directory structure

The following table lists the recommended directory structure:

Important! Do not mix the files for different databases in a single directory and avoid putting the files in the root directory.

Database files from... Place in directory named...

VNMaster VNMaster

VNAggr VNAggr

VNPoller VNPoller

....................................................................225

Windows short names

..........................................................................................................................................................................................Windows short names

Purpose

Windows short names must be used when editing the attach scripts and also in the registry.

Short name guidelines

Use the following guidelines to avoid the need for short names:

• A file or directory name that is alphanumeric plus the underscore, no spaces; and if there is a dot in the name, then only one dot, and only up to 8 characters before the dot and up to 3 characters after the dot.

Example: logfile.txt, vn_sql.bat

• A directory name that is alphanumeric and 8 characters or less.

Example: VSCommon, Data, VNMaster, VNAggr, VNPoller

Important! Windows names are case-insensitive.

Long name guidelines

Use the following guidelines to determine a short name:

• Issue the following command in a command prompt window: dir /x

Example: Here is a sample result where Program Files is shown as a short name (PROGA~1) and file mib2utm.txt is already in short name form:

E: \> dir /xDirectory of E:\06/14/2005 04:45p <DIR> .06/14/2005 04:45p <DIR> ..07/06/2004 09:51a 32,522 mib2utm.txt12/06/2004 11:43p <DIR> PROGRA~1 Program Files

Important! For readability, it is suggested that you enter the short names into the registry and attach scripts in uppercase letters.

• Always look up short names.

Example: Under certain conditions the short name for the directory named Program Files might be PROGRA~2 or PROGRA~3, etc.

....................................................................226

Move VitalSuite NET databases

..........................................................................................................................................................................................Overview

Purpose

This section discusses the process for moving VitalSuite NET database(s).

Contents


Process to move the VitalSuite NET databases 227


Stop the VitalSuite NET services 230





....................................................................227

Process to move the VitalSuite NET databases

..........................................................................................................................................................................................Process to move the VitalSuite NET databases

Process

To move the VitalSuite NET database(s), follow this process:

10. Decide where you intend to move the database(s) and make sure there is enough disk space. Decide whether you are going to move the database log file to the same location or to a different location from where you will move the database data files.

11. Perform a backup of each database you intend to move, as described in Chapter 8, “Back up and restore” on page 183.

12. Pre-create the directory/directories on the target file system. Find out any short names of those directories, as described in “Windows short names”, on page 225.

13. Query and save the sysfiles table of the database(s) you intend to move, as described in “Query and save the sysfiles”, on page 228.

14. Stop all VitalSuite NET processes, as described in “Stop the VitalSuite NET services”, on page 230.

15. Detach the database, as described in “Detach the database”, on page 232.

16. Move the database files to their destinations.

Important! Do not change the name of any of the files. It is recommended you COPY the files rather than move them. Leaving copies in the original location is a safety measure. The original files become a backup of the database. At the end of this procedure, when the databases are re-attached and working, the original database files can be deleted.

17. Edit the SQL attach script(s) to reflect the new database location(s), as described in “Edit the SQL attach scripts”, on page 234.

18. Edit the registry to reflect the new database location, as described in “Edit the registry”, on page 236.

19. Attach the database(s), as described in “Attach the database”, on page 238.

....................................................................228

..........................................................................................................................................................................................Query and save the sysfiles

When to use

Use this procedure to query and save the sysfiles table of the database(s) you intend to move.

Before you begin

Make sure that you:

• Read the important information about database files, recommended directory locations, and Windows short names on page 221

• Have access to Microsoft SQL Server Query Analyzer with administrator privileges and use the login administrator account, sa.

Related information

For more information about the process on moving the VitalSuite NET databases, refer to “Process to move the VitalSuite NET databases”, on page 227.

Procedure

To query and save the sysfiles table of the database:

...........................................................................................................................................................................

1 Select Start | Programs | Microsoft SQL Server | Query Analyzer.

Result: The Connect to SQL Server dialog box opens.

...........................................................................................................................................................................

2 If you select SQL Server authentication, enter sa as the Login name and password.

Result: An untitled Query window opens.

...........................................................................................................................................................................

3 Select VNMaster, VNAggr or VNPoller in the database drop-down list, depending on which database(s) you intend to move.

Important! If the database you want to move is marked SUSPECT, do not proceed with this procedure and contact Lucent Technical Support for assistance.

...........................................................................................................................................................................

4 In the menu bar, select Query | Results in Text.

...........................................................................................................................................................................

5 Enter one of the following query, depending on which database(s) you selected in Step 3:

Select * from VNMaster..sysfiles Select * from VNAggr..sysfilesSelect * from VNPoller..sysfiles

....................................................................229

Query and save the sysfiles

...........................................................................................................................................................................

6 Save the results of the query.

...........................................................................................................................................................................

7 Repeat Step 3 through Step 6 for each additional database you intend to move.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................230

..........................................................................................................................................................................................Stop the VitalSuite NET services

When to use

Use this procedure to stop the VitalSuite NET services.

Before you begin

Make sure that you:


• Have Windows administrator access on your server

Related information


Procedure

To stop the VitalSuite NET services:

...........................................................................................................................................................................

1 Select Start | Programs | Administrative Tools | Services.

Result: The Services window opens.

...........................................................................................................................................................................

2 Double-click on Tomcat.

Result: The Tomcat properties dialog box opens.

...........................................................................................................................................................................

3 Click Stop for each Tomcat service.

...........................................................................................................................................................................

4 Click OK.

Result: The Status column for BMC Patrol does not say “Started”.

....................................................................231

Stop the VitalSuite NET services

...........................................................................................................................................................................

5 Repeat Step 2 through Step 4 for the following services:

• Apache

• BMC Patrol

• RMI Registry Service for VitalSuite Performance Management software

• SQLSERVERAGENT

• VitalSuite Performance Management software AtBoot Scheduler

Important! When you stop the VitalSuite Performance Management software AtBoot Scheduler service, you will get the following error message:Error 997: Overlapped I/O operation is in progress.It is not a problem and should be ignored. Also you may get an additional message that AtBoot was not stopped. The message is an error and AtBoot is stopped.

...........................................................................................................................................................................

6 If you have a VNPoller on your server, complete the following steps:

a. Open a command prompt window.

b. Type the following:stopcollectorsstatuscollectors

Result: The statuscollectors command should return no rows once the collectors have stopped.

c. Type the following in the same command prompt window:vnkill java.exe

d. Repeat step 6c until you no longer see, java.exe in the task monitor process list.

e. Stop the MSSQLServer service.

f. Restart the MSSQLServer service.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................232

..........................................................................................................................................................................................Detach the database

When to use

Use this procedure to detach the database(s) that you intend to move.

Before you begin

Make sure that you:


• Have access to SQL Server Enterprise Manager and administrator privileges

Related information


Procedure

To detach the database:

...........................................................................................................................................................................

1 Select Start | Programs | Microsoft SQL Server | Enterprise Manager.

Result: The SQL Server Enterprise Manager console opens.

...........................................................................................................................................................................

2 In the left menu pane, navigate by clicking the plus (+) signs to open these levels in the following sequence:

• Microsoft SQL Server

• SQL Server Group

• Your SQL Server name or IP address

• Databases

Result: A list of database names currently attached to SQL Server is displayed.


...........................................................................................................................................................................

3 Right click on the database name you intend to move.

Result: A pop-up window opens.

...........................................................................................................................................................................

4 Select All Tasks | Detach Database.

Result: The database status should show there are no connections to the database.

....................................................................233

Detach the database

...........................................................................................................................................................................

5 Determine the following:

Result: The database name disappears from the left menu pane.

...........................................................................................................................................................................

6 Repeat Step 3 through Step 5 for each database that you intend to move.

...........................................................................................................................................................................

7 Exit SQL Server Enterprise Manager.

...........................................................................................................................................................................E N D O F S T E P S

If... Then...

There are no connections to the database Click OK to detach the database.

There are connections to the database Complete the following steps:

1. Click Clear to disconnect the database users.2. Click OK to disconnect those users and

proceed.3. Click No to notify those users.4. Click OK to detach the database.

....................................................................234

..........................................................................................................................................................................................Edit the SQL attach scripts

When to use

Use this procedure to edit the SQL attach scripts to reflect the new database location.

Before you begin

Make sure that you:


• Make a backup copy of the attach scripts that you will modify

Related information


Procedure

To edit the SQL attach script:

...........................................................................................................................................................................

1 Select the appropriate attach script for the database that you are moving.

...........................................................................................................................................................................

2 Open the file using Windows Notepad editor.

...........................................................................................................................................................................

3 Locate the lines near the beginning of the file which looks like the following example for the VNAggr database:EXEC sp_attach_db @dbname = N’VNAggr”,

@filename1 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNASystem.mdf’,@filename2 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNACommon.ndf’,@filename3 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNAConfig.ndf’,@filename4 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNAStats.ndf’,@filename5 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNAPoller.ndf’,@filename6 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNAImport.ndf’,@filename7 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNATemp.ndf’,@filename8 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNAInit.ndf’,@filename9 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNADomain.ndf’,@filename10 = N’E:\PROGRA~1\VitalNet\Data\VNAggr\VNALog.ldf’

go

Important! All the data files that end with .mdf or .ndf must be kept together in the same directory. The line with the file name ending in .ldf is the transaction log file. You can move that file to a different directory or keep the transaction log file in the same directory as the data files.

....................................................................235

Edit the SQL attach scripts

...........................................................................................................................................................................

4 Leave the @filename list on the left side of the equal sign (=) unchanged.

...........................................................................................................................................................................

5 After the first quoted string (‘) on the right side of the equal sign (=), edit each line to change the drive letter to the new location where the database file resides, and leaving the database file name at the end of the line unchanged. Use a backslash (\) to separate the directory levels.

Example: If you move the database files in the example above from the E drive to the F drive, then it will look like this:

EXEC sp_attach_db @dbname = N’VNAggr”,@filename1 = N’F:\PROGRA~1\VitalNet\Data\VNAggr\VNASystem.mdf’,@filename2 = N’F:\PROGRA~1\VitalNet\Data\VNAggr\VNACommon.ndf’,...

Important! When editing the attach SQL script, make sure to use the short name of any directory which has a long name and do not change the attach script file name.

...........................................................................................................................................................................

6 Save the changes to the file.

...........................................................................................................................................................................

7 Close the file.

...........................................................................................................................................................................

8 Repeat Step 1 through Step 7 for each database attach script that you are moving.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................236

..........................................................................................................................................................................................Edit the registry

When to use

Use this procedure to edit the registry to reflect the new database location.

Before you begin

Read the important information about database files, recommended directory locations, and Windows short names on page 221

Related information


Procedure

To edit the registry:

...........................................................................................................................................................................

1 Open a command prompt window.

...........................................................................................................................................................................

2 Type the following command:

regedit.exe

Result: The Registry Editor window opens.

...........................................................................................................................................................................

3 In the left menu pane, navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalNet

Result: You will see some or all of these components:

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalNet\Master

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalNet\Aggregator

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalNet\Poller

...........................................................................................................................................................................

4 Click on the folder icon next to the key name (Master, Aggregator, or Poller).

Result: A list of files are displayed in the right menu pane.

...........................................................................................................................................................................

5 Double click DBFileDir.

....................................................................237

Edit the registry

...........................................................................................................................................................................

6 Edit the directory path to the new location of the database files.

Important! The value should begin with the drive letter, colon, and a backslash. Use backslashes to separate the directory levels.

...........................................................................................................................................................................

7 When you have finish editing all the values, click OK.

Result: The change takes effect immediately.

...........................................................................................................................................................................

8 Double click DBLogDir.

...........................................................................................................................................................................

9 Edit the directory path to the new location of the database transaction log file.


...........................................................................................................................................................................



...........................................................................................................................................................................

11 Repeat Step 4 through Step 10 for each VitalSuite NET component (Master, Aggregator, or Poller).

...........................................................................................................................................................................

12 Exit the Registry Editor.

...........................................................................................................................................................................E N D O F S T E P S

Vital

....................................................................238

..........................................................................................................................................................................................Attach the database

When to use

Use this procedure to attach the database(s).

Before you begin

Make sure that you:



Related information


Procedure

To attach the database:

...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VNMaster, VNAggr or VNPoller in the database drop-down list, depending on which database you intend to attach.

...........................................................................................................................................................................

4 Select File | Open in the menu bar and navigate to the attach script in the %INSTALLDIR%\VitalNet\Data directory.

...........................................................................................................................................................................

5 Select the appropriate attach script for the database that you are attaching and visually inspect the script to make sure it is the correct one.

....................................................................239

Attach the database

...........................................................................................................................................................................

6 Click the green arrow at the top window to execute the script.

Result: If the following message is displayed, it can be ignored:

Server: Msg 15023, Level 16, State 1, Procedure sp_grantdbaccess, Line 126 User or role “DBA” already exists in the current database. The number of orphaned users fixed by updating users was 0. “DBA” added to role ‘db_owner”.

Important! If you get any other errors, stop following this procedure now and fix the problem before proceeding. Save a copy of the output of the attach script to be analyzed later and contact Lucent Technical Support for additional assistance.

...........................................................................................................................................................................

7 Repeat Step 3 through Step 6 for each database that you are attaching.

...........................................................................................................................................................................

8 Exit the Query Analyzer.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................240

Test and verification

..........................................................................................................................................................................................Overview

Purpose

This section discusses the process to test and verify that the moved database is successful.

Contents


Check the database configuration 242

Check the poller DSN configuration 244


....................................................................241

Process to verify a successful database move

..........................................................................................................................................................................................Process to verify a successful database move

Process

To verify if the database move is successful, complete the following process:

1. Check the database configuration of all the ODBC System DSNs associated with the moved database(s), as described in “Check the database configuration”, on page 242.

2. Check the poller DSN configuration associated with the moved database(s), as described in “Check the poller DSN configuration”, on page 244.

3. Reboot the servers to restart all the processes.

4. Use SQL Enterprise Manager to verify that you see all the databases appear.

5. Check that all the services are running.

6. Check the Windows System Event Log to see if there were any startup errors and if the server is a VNPoller, use the STATUSCOLLECTORS command to verify that the collectors are running.

7. Verify the product operation, as described in “Verify product operation”, on page 246.

....................................................................242

..........................................................................................................................................................................................Check the database configuration

When to use

Use this procedure to check the configuration and test all of the ODBC System DSNs associated with the moved database(s).

Before you begin

Make sure that you:

• Have completed the process to move the database, as described in “Process to move the VitalSuite NET databases”, on page 227.

• Know your SQL server password.

Related information

For more information about the process to verify if a database is moved successfully, refer to “Process to verify a successful database move”, on page 241.

Procedure

To check the database configuration:

...........................................................................................................................................................................

1 Select Start | Settings | Control Panel | Administrative Tools | Data Sources (ODBC).

Result: The ODBC Data Source Administrator window opens.

...........................................................................................................................................................................


Result: You should have the following System DSNs:

• VNMaster

• VNAggr

• VNPoller

• ToPollerDSN_<IP or servername>

...........................................................................................................................................................................

3 Double-click VNMaster to open its configuration wizard.

...........................................................................................................................................................................

4 Verify the value of the server IP address.

...........................................................................................................................................................................

5 Click Next.

...........................................................................................................................................................................

6 Click Client Connection.

....................................................................243

Check the database configuration

...........................................................................................................................................................................

7 Uncheck the checkbox next to Dynamically determine port.

...........................................................................................................................................................................

8 Verify the port number is 1433.

...........................................................................................................................................................................

9 Click OK.

...........................................................................................................................................................................

10 Close the dialog box.

...........................................................................................................................................................................

11 Set the logon to use with SQL Server authentication using ID and Password entered by the user.

...........................................................................................................................................................................

12 Set the Login ID to sa and enter your SQL Server sa password.

...........................................................................................................................................................................

13 Click Next.

...........................................................................................................................................................................

14 Verify that the database name displayed in the top is appropriate.

Example: VNMaster database for the ODBC DSN named VNMaster, VNAggr database for the ODBC DSN named VNAggr, and VNPoller database for the ODBC DSN named VNPoller.

...........................................................................................................................................................................

15 If you need to change the database name, click the checkbox to un-gray the field, make the corrections and click Next.

...........................................................................................................................................................................

16 Click Finish.

...........................................................................................................................................................................

17 Click Test Data source.

...........................................................................................................................................................................

18 Verify that the test is successful.

...........................................................................................................................................................................

19 Click OK.

...........................................................................................................................................................................

20 Repeat Step 3 through Step 19 for VNAggr and VNPoller.

...........................................................................................................................................................................

21 Close the configuration wizard.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................244

..........................................................................................................................................................................................Check the poller DSN configuration

When to use

The ToPollerDSN_ODBC DSN may have been named either with an IP address of your server or the server name. This name must match the name in the SQL databases you transferred from the old server. On the new server, the ODBC System DSN name was created for you by the installer but it is possible the ODBC DSN was named the other way on the older server; therefore the actual name of this DSN may be out of sync with the name registered in the SQL databases.

Use this procedure to check the poller DSN configuration and test the ODBC System DSNs associated with the moved database(s).

Before you begin

Make sure that you:

• Have completed the process to move the database, as described in “Process to move the VitalSuite NET databases”, on page 227.

• Know your SQL server password.

Related information


Procedure

To check the poller DSN configuration:

...........................................................................................................................................................................


...........................................................................................................................................................................

2 Enter the following command:

osql -E -Q select poller dsn from vnaggr.dba.vnpollerdsntable

Important! -E and -Q are case-sensitive, type them as uppercase letters.

Result: The query displays a list of database names.

...........................................................................................................................................................................

3 Select Start | Settings | Control Panel | Administrative Tools | Data Sources (ODBC).

Result: The ODBC Data Source Administrator window opens.

....................................................................245

Check the poller DSN configuration

...........................................................................................................................................................................


Result: You should have the following System DSNs:

• VNMaster

• VNAggr

• VNPoller

• ToPollerDSN_<IP or servername>

...........................................................................................................................................................................

5 Double-click ToPollerDSN_<IP or servername> to open its configuration wizard.

...........................................................................................................................................................................

6 Verify and correct the name of the DSN to match the result of the query in Step 2.

...........................................................................................................................................................................

7 Click OK.

...........................................................................................................................................................................

8 Close the dialog box.

...........................................................................................................................................................................

9 Set the logon to use with SQL Server authentication using ID and Password entered by the user.

...........................................................................................................................................................................

10 Set the Login ID to sa and enter your SQL Server sa password.

...........................................................................................................................................................................

11 Click Next.

...........................................................................................................................................................................

12 Click Finish.

...........................................................................................................................................................................

13 Click Test Data source.

...........................................................................................................................................................................

14 Verify that the test is successful.

...........................................................................................................................................................................

15 Click OK.

...........................................................................................................................................................................

16 Close the configuration wizard.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................246

..........................................................................................................................................................................................Verify product operation

When to use

Use this procedure to verify the product operation.

Before you begin

Make sure that you have completed the process to move the database, as described in “Process to move the VitalSuite NET databases”, on page 227.

Related information


Procedure

To verify product operation:

...........................................................................................................................................................................

1 Log on to VitalSuite NET.

...........................................................................................................................................................................

2 Select ADMIN | Servers | VitalNet | Properties in the menu tab.

Result: The VitalNet Server status page opens.

...........................................................................................................................................................................

3 Select the server whose database(s) were moved.

Result: The properties page shows all the databases and corresponding sizes.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................247

10 Move Analysis databases

..........................................................................................................................................................................................Overview

Purpose

This document describes how to modify an existing install so that the databases can be stored in a different location other than the Analysis executables.

Contents



Database files 249



Move Analysis databases 253

Process to move the Analysis databases 254


Stop the Analysis services 257








....................................................................248


..........................................................................................................................................................................................Overview

Purpose


Contents


Database files 249



....................................................................249

Database files

..........................................................................................................................................................................................Database files

Purpose

Databases no longer need to be kept in their default installation locations (%INSTALLDIR%\VitalAnalysis\Data directories). With a fresh install, the user can choose other locations for the Analysis database data files, and database transaction log files.

File extension


Database files


File Type Extension





VAMaster %INSTALLDIR%\VitalAnalysis\Data\VAMaster • VAMaster.mdf• VAMaster.ldf• VAMCommon.ndf

VAAggr %INSTALLDIR%\VitalAnalysis\Data\VAAggr • VAAggr.mdf• VAAggr.ldf• VAAggrTab1.ndf• VAAggrTab2.ndf• VAAggrTab3.ndf• VAAggrTab4.ndf• VAAggrTab5.ndf• VAAggrTab6.ndf• VAAggrTab7.ndf• VAAggrTab8.ndf• VAAggrTab9.ndf• VAACommon.ndf

....................................................................250

Important! Do not change the names of the Analysis database files. If the files have been renamed, there are missing files, or additional files in the directory, do not perform the procedure for moving the database files and contact Lucent Technical Support.

VAPost %INSTALLDIR%\VitalAnalysis\Data\VAPost • VAPost.mdf• VAPost.ldf• VABaseTab1.ndf• VABaseTab2.ndf• VABaseTab3.ndf• VABaseTab4.ndf

VAHConfig %INSTALLDIR%\VitalAnalysis\Data\VAHConfig • VAHConfig.mdf• VAHConfig.ldf

Attach SQL scripts

%INSTALLDIR%\VitalAnalysis\Data • ms_attach_aggr.sql• ms_attach_master.sql• ms_attach_post.sql

Attach SQL scripts

%INSTALLDIR%\VitalSolution\Data • ms_attach_config.sql


....................................................................251

Recommended location and directory names for the moved database files


..........................................................................................................................................................................................files

Purpose


Directory structure




VAMaster VAMaster

VAAggr VAAggr

VAPost VAPost

VAHConfig VAHConfig

....................................................................252


Purpose







Example: VSCommon, Data, VitalAnalysis, VSCommon, VAMaster, VAAggr, VAPost










....................................................................253

Windows short names

Move Analysis databases

..........................................................................................................................................................................................Overview

Purpose

This section discusses the process for moving Analysis database(s).

Contents


Process to move the Analysis databases 254


Stop the Analysis services 257





....................................................................254

..........................................................................................................................................................................................Process to move the Analysis databases

Process

To move the Analysis database(s), follow this process:





5. Stop all Analysis processes, as described in “Stop the Analysis services”, on page 257.

6. Restart MS-SQL server:

a. In the task bar, select Start | Programs | Microsoft SQL Server | Service Manager.

b. Click Start/Continue.







....................................................................255



When to use


Before you begin

Make sure that you:



Related information

For more information about the process on moving the Analysis databases, refer to “Process to move the Analysis databases”, on page 254.

Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VAMaster, VAAggr, VAPost or VAHConfig in the database drop-down list, depending on which database(s) you intend to move.


...........................................................................................................................................................................


...........................................................................................................................................................................


Select * from VAMaster..sysfiles Select * from VAAggr..sysfilesSelect * from VAPost..sysfilesSelect * from VAHConfig..sysfiles

....................................................................256

...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................257

Stop the Analysis services

..........................................................................................................................................................................................Stop the Analysis services

When to use

Use this procedure to stop the Analysis services.

Before you begin

Make sure that you:



Related information


Procedure

To stop the Analysis services:

...........................................................................................................................................................................

1 In the task bar, select Start | Programs | Microsoft SQL Server | Service Manager.

Result: The SQL Server Service Manager dialog box opens.

...........................................................................................................................................................................

2 Click Stop.

Result: The following message is displayed: “When MS-SQL server stops, these other services will also stop. Do you want to stop these services?”

...........................................................................................................................................................................

3 Click Yes to stop all the services.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................258


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................





• Databases



...........................................................................................................................................................................



...........................................................................................................................................................................



....................................................................259

Detach the database

...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

If... Then...





....................................................................260


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................

3 Locate the lines near the beginning of the file which looks like the following example for the VAAggr database:EXEC sp_attach_db @dbname = N’VAAggr’,

@filename1 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggr.mdf’,@filename2 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab1.ndf’,@filename3 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab2.ndf’,@filename4 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab3.ndf’,@filename5 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab4.ndf’,@filename6 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab5.ndf’,@filename7 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab6.ndf’,@filename8 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab7.ndf’,@filename9 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab8.ndf’,@filename10 =

....................................................................261


N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab9.ndf’,@filename11 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAACommon.ndf’,@filename12 = N’E:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggr.ldf’,

go


...........................................................................................................................................................................


...........................................................................................................................................................................



EXEC sp_attach_db @dbname = N’VAAggr’,@filename1 = N’F:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggr.mdf’,@filename2 = N’F:\PROGRA~1\VitalAnalysis\Data\VAAggr\VAAggrTab1.ndf’,...


...........................................................................................................................................................................


...........................................................................................................................................................................

7 Close the file.

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................262


When to use


Before you begin


Related information


Procedure


...........................................................................................................................................................................


...........................................................................................................................................................................


regedit.exe


...........................................................................................................................................................................


HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalAnalysis


• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalAnalysis\Master

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalAnalysis\Aggregator

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalAnalysis\Post

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalAnalysis\

...........................................................................................................................................................................

4 Click on the folder icon next to the key name (Master, Aggregator, Post).


...........................................................................................................................................................................


....................................................................263

Edit the registry

...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

11 Repeat Step 4 through Step 10 for each Analysis component (VAMaster, VAAggr, VAPost, VAHConfig).

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................264


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VAMaster, VAAggr, VAPost or VAHConfig in the database drop-down list, depending on which database you intend to attach.

...........................................................................................................................................................................

4 Select File | Open in the menu bar and navigate to the attach script in the %INSTALLDIR%\VitalAnalysis\Data directory.

...........................................................................................................................................................................


....................................................................265

Attach the database

...........................................................................................................................................................................


Result: The following message is displayed:

User has been dropped from current database.Granted database access to ‘DBA’‘DBA’ added to role ‘db_owner’.


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................266


..........................................................................................................................................................................................Overview

Purpose


Contents




....................................................................267



Process






....................................................................268


When to use


Before you begin

Make sure that you have completed the process to move the database, as described in “Process to move the Analysis databases”, on page 254.

Related information


Procedure


...........................................................................................................................................................................

1 Log on to the Analysis server.

...........................................................................................................................................................................

2 Select ADMIN | Servers | VitalAnalysis | Properties in the menu tab.

Result: The VitalAnalysis Server status page opens.

...........................................................................................................................................................................



...........................................................................................................................................................................E N D O F S T E P S

....................................................................269

11 Move Help databases

..........................................................................................................................................................................................Overview

Purpose

This document describes how to modify an existing install so that the databases can be stored in a different location other than the Help executables.

Contents



Database files 271



Move Help databases 274

Process to move the Help databases 275


Stop the Help services 278








....................................................................270


..........................................................................................................................................................................................Overview

Purpose


Contents


Database files 271



....................................................................271

Database files

..........................................................................................................................................................................................Database files

Purpose

Databases no longer need to be kept in their default installation locations (%INSTALLDIR%\VitalHelp\Data directories). With a fresh install, the user can choose other locations for the Help database data files, and database transaction log files.

File extension


Database files


Important! Do not change the names of the VitalHelp database files. If the files have been renamed, there are missing files, or additional files in the directory, do not perform the procedure for moving the database files and contact Lucent Technical Support.

File Type Extension





VHMaster %INSTALLDIR%\VitalHelp\Data\VHMaster • VHMaster.mdf• VHMaster.ldf• VHMCommon.ndf

VitalHelp %INSTALLDIR%\VitalHelp\Data\VHPost • VitalHelp.mdf• VitalHelp.ldf• VHPCommon.ndf

VAHConfig %INSTALLDIR%\VitalSolution\Data\VAHConfig • VAHConfig.mdf• VAHConfig.ldf

Attach SQL scripts

%INSTALLDIR%\VitalHelp\Data • ms_attach_master.sql• ms_attach_post.sql

Attach SQL scripts

%INSTALLDIR%\VitalSolution\Data • ms_attach_config.sql

....................................................................272


..........................................................................................................................................................................................files

Purpose


Directory structure




VHMaster VHMaster

VitalHelp VHPost

VAHConfig VAHConfig

....................................................................273

Windows short names


Purpose







Example: VSCommon, Data, VitalHelp, VSCommon, VHMaster, VHPost










....................................................................274

Move Help databases

..........................................................................................................................................................................................Overview

Purpose

This section discusses the process for moving Help database(s).

Contents


Process to move the Help databases 275


Stop the Help services 278





....................................................................275

Process to move the Help databases

..........................................................................................................................................................................................Process to move the Help databases

Process

To move the Help database(s), follow this process:





5. Stop all Help processes, as described in “Stop the Help services”, on page 278.










....................................................................276


When to use


Before you begin

Make sure that you:



Related information

For more information about the process on moving the Help databases, refer to “Process to move the Help databases”, on page 275.

Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VHMaster, VitalHelp or VAHConfig in the database drop-down list, depending on which database(s) you intend to move.


...........................................................................................................................................................................


...........................................................................................................................................................................


Select * from VHMaster..sysfiles Select * from VitalHelp..sysfilesSelect * from VAHConfig..sysfiles

....................................................................277


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................278

..........................................................................................................................................................................................Stop the Help services

When to use

Use this procedure to stop the Help services.

Before you begin

Make sure that you:



Related information


Procedure

To stop the Help services:

...........................................................................................................................................................................



...........................................................................................................................................................................

2 Click Stop.


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................279

Detach the database


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................





• Databases



...........................................................................................................................................................................



...........................................................................................................................................................................



....................................................................280

...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

If... Then...





....................................................................281



When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................

3 Locate the lines near the beginning of the file which looks like the following example for the VHMaster database:EXEC sp_attach_db @dbname = N’VHMaster’,

@filename1 = N’E:\PROGRA~1\VitalHelp\Data\VHMaster\VHMaster.mdf’,@filename2 = N’E:\PROGRA~1\VitalHelp\Data\VHMaster\VHMCommon.ndf’,@filename3 = N’E:\PROGRA~1\VitalHelp\Data\VHMaster\VHMaster.ldf’,

go


...........................................................................................................................................................................


....................................................................282

...........................................................................................................................................................................



EXEC sp_attach_db @dbname = N’VHMaster’,@filename1 = N’F:\PROGRA~1\VitalHelp\Data\VHMaster\VHMaster.mdf’,@filename2 = N’F:\PROGRA~1\VitalHelp\Data\VHMaster\VHMCommon.ndf’,...


...........................................................................................................................................................................


...........................................................................................................................................................................

7 Close the file.

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................283

Edit the registry


When to use


Before you begin


Related information


Procedure


...........................................................................................................................................................................


...........................................................................................................................................................................


regedit.exe


...........................................................................................................................................................................


HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalHelp


• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalHelp\Master

• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalHelp\Post

...........................................................................................................................................................................

4 Click on the folder icon next to the key name (Master, Post).


...........................................................................................................................................................................


....................................................................284

...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

11 Repeat Step 4 through Step 10 for each Help component (VHMaster, VitalHelp, VAHConfig).

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................285

Attach the database


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VHMaster, VitalHelp or VAHConfig in the database drop-down list, depending on which database you intend to attach.

...........................................................................................................................................................................

4 Select File | Open in the menu bar and navigate to the attach script in the %INSTALLDIR%\VitalHelp\Data directory.

...........................................................................................................................................................................


....................................................................286

...........................................................................................................................................................................


Result: The following message is displayed:

User has been dropped from current database.Granted database access to ‘DBA’‘DBA’ added to role ‘db_owner’.


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................287

Attach the database


..........................................................................................................................................................................................Overview

Purpose


Contents




....................................................................288


Process






....................................................................289

Verify product operation


When to use


Before you begin

Make sure that you have completed the process to move the database, as described in “Process to move the Help databases”, on page 275.

Related information


Procedure


...........................................................................................................................................................................

1 Log on to the Help server.

...........................................................................................................................................................................

2 Select ADMIN | Servers | VitalHelp| Properties in the menu tab.

Result: The VitalHelp Server status page opens.

...........................................................................................................................................................................



...........................................................................................................................................................................E N D O F S T E P S

....................................................................290

....................................................................291

12 Move ART databases

..........................................................................................................................................................................................Overview

Purpose

This document describes how to modify an existing install so that the databases can be stored in a different location other than the ART executables.

Contents



Database files 293



Move ART databases 297

Process to move the ART databases 298


Stop the ART services 301








....................................................................292


..........................................................................................................................................................................................Overview

Purpose


Contents


Database files 293



....................................................................293

Database files

..........................................................................................................................................................................................Database files

Purpose

Databases no longer need to be kept in their default installation locations (%INSTALLDIR%\VitalART\Data\VSReports directories). With a fresh install, the user can choose other locations for the ART database data files, and database transaction log files.

File extension


Database files


Important! It is a requirement of VitalART that the data files for VSReports and VNAPI be kept together. Do not change the names of the ART database files. If the files have been

File Type Extension





VSReports %INSTALLDIR%\VitalArt\Data\VSReports (Standalone)

• VSRCommon.ndf• VSReports.ldf• VSReports.mdf

VNAPI %INSTALLDIR%\VitalArt\Data\VNAPI(Standalone)

• VNAPI.mdf• VNAPI.ldf

VNMaster %INSTALLDIR%\VitalNet\Data\VNMaster (VitalART co-resident with VitalNet)

• VSRCommon.ndf• VSReports.ldf• VSReports.mdf• VNAPI.mdf• VNAPI.ldf

Attach SQL scripts

%INSTALLDIR%\VitalArt\Data • ms_attach_vision.sql (for VSReports database)

• ms_attach_vvvn.sql (for VNAPI database)

....................................................................294

renamed, there are missing files, or additional files in the directory, do not perform the procedure for moving the database files and contact Lucent Technical Support.

....................................................................295

Recommended location and directory names for the moved database files


..........................................................................................................................................................................................files

Purpose


Directory structure

It is suggested that the VSReports database files and the VNAPI database files be put in a directory named VSReports.


....................................................................296


Purpose







Example: VSCommon, Data, VitalArt, VSReports










....................................................................297

Windows short names

Move ART databases

..........................................................................................................................................................................................Overview

Purpose

This section discusses the process for moving ART database(s).

Contents


Process to move the ART databases 298


Stop the ART services 301





....................................................................298

..........................................................................................................................................................................................Process to move the ART databases

Process

To move the ART database(s), follow this process:





5. Stop all ART processes, as described in “Stop the ART services”, on page 301.










....................................................................299



When to use


Before you begin

Make sure that you:



Related information

For more information about the process on moving the ART databases, refer to “Process to move the ART databases”, on page 298.

Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VSReports or VNAPI in the database drop-down list, depending on which database(s) you intend to move.


...........................................................................................................................................................................


...........................................................................................................................................................................


Select * from VSReports..sysfiles Select * from VNAPI..sysfiles

...........................................................................................................................................................................


....................................................................300

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................301

Stop the ART services

..........................................................................................................................................................................................Stop the ART services

When to use

Use this procedure to stop the ART services.

Before you begin

Make sure that you:



Related information


Procedure

To stop the ART services:

...........................................................................................................................................................................



...........................................................................................................................................................................

2 Click Stop.


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................302


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................





• Databases



...........................................................................................................................................................................



...........................................................................................................................................................................



....................................................................303

Detach the database

...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

If... Then...





....................................................................304


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................

3 Locate the lines near the beginning of the file which looks like the following example for the VSReports database:EXEC sp_attach_db @dbname = N’VSReports’,

@filename1 = N’E:\PROGRA~1\VitalART\Data\VSReports\VSReports.mdf’,@filename2 = N’E:\PROGRA~1\VitalART\Data\VSReports\VSRCommon.ndf’,@filename3 = N’E:\PROGRA~1\VitalART\Data\VSReports\VSReports.ldf’

go


...........................................................................................................................................................................


...........................................................................................................................................................................


....................................................................305



EXEC sp_attach_db @dbname = N’VSReports’,@filename1 = N’F:\PROGRA~1\VitalART\Data\VSReports\VSReports.mdf’,@filename2 = N’F:\PROGRA~1\VitalART\Data\VSReports\VSRCommon.ndf’...


...........................................................................................................................................................................


...........................................................................................................................................................................

7 Close the file.

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................306


When to use


Before you begin


Related information


Procedure


...........................................................................................................................................................................


...........................................................................................................................................................................


regedit.exe


...........................................................................................................................................................................


HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalVision


• HKEY_LOCAL_MACHINE\SOFTWARE\VitalSuiteCommon\VitalVision\Master

...........................................................................................................................................................................

4 Click on the folder icon next to the key name (Master).


...........................................................................................................................................................................


....................................................................307

Edit the registry

...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

11 Repeat Step 4 through Step 10 for each ART component (VSReport, VNAPI ).

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................308


When to use


Before you begin

Make sure that you:



Related information


Procedure


...........................................................................................................................................................................



...........................................................................................................................................................................



...........................................................................................................................................................................

3 Select VSReports or VNAPI in the database drop-down list, depending on which database you intend to attach.

...........................................................................................................................................................................

4 Select File | Open in the menu bar and navigate to the attach script in the %INSTALLDIR%\VitalART\Data directory.

...........................................................................................................................................................................


....................................................................309

Attach the database

...........................................................................................................................................................................


Result: The following message is displayed if you run ms_attach_vvvn.sql:

The number of orphaned users fixed by updating users was 0.‘DBA’ added to role ‘db_owner’.‘DBA’ added to role ‘securityadmin’.‘DBA’ added to role ‘setupadmin’.


...........................................................................................................................................................................


...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

....................................................................310


..........................................................................................................................................................................................Overview

Purpose


Contents




....................................................................311



Process






....................................................................312


When to use


Before you begin

Make sure that you have completed the process to move the database, as described in “Process to move the ART databases”, on page 298.

Related information


Procedure


...........................................................................................................................................................................

1 Log on to the ART server.

...........................................................................................................................................................................

2 Select ADMIN | Servers | ART | Report in the menu tab.

Result: The VitalART Report page opens.

...........................................................................................................................................................................

3 Look at the page for the creation of the previous report.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................313

13 VitalSuite NET technical notes

..........................................................................................................................................................................................Overview

Purpose

This chapter provides technical information useful to the VitalSuite NET administrator.

Contents


Protocols and interface type codes 315

Protocols and protocol groups 316

Interface type codes 327

Adding VitalSuite NET resources manually 337

Add resources manually to VitalSuite NET 338

Resource configuration file 340

Resolve missing resource data in VitalSuite NET 343

Verify the collector is enabled 344

Verify the collector is running 346

Access the UTM status codes 348

Modify the default SNMP timeout value 352

Threshold parameters 354

Default quality index parameters for resource types 355

Network alarm threshold measurements 368

Using the System Application MIB to monitor applications 393

....................................................................314

Introduction 394

Install the CIAgent on Windows 395

Install the CIAgent on UNIX 397

Determine the applications to monitor on Windows 399

Determine the applications to monitor on UNIX 402

Configure the SAPPApplicationsTable 404

RMON2 flow limits 406

Introduction to RMON2 flow limits 407

Change the RMON2 flow limits used by VitalSuite NET 408

Example commands for changing RMON2 flow limits 410

Tivoli integration 411

Introduction 412

Configure Tivoli to launch VitalSuite NET from a pre-defined server 413

Configure Tivoli to launch VitalSuite NET from a selected server 415

Miscellaneous notes 417

Common issues and resolutions with NavisXtend 418

Shutdown commands for VitalSuite NET UNIX servers 420

Aggregation Editor utility 421

Change the resource limit in My Reports for VitalSuite NET on Windows 423

Change the resource limit in My Reports for VitalSuite NET on UNIX 425

....................................................................315

Overview

Protocols and interface type codes

..........................................................................................................................................................................................Overview

Purpose

This section describes the protocols that are enabled for VitalSuite NET traffic monitoring and also provides a list of interface type codes used by VitalSuite NET to determine resource names.

Contents


Protocols and protocol groups 316

Interface type codes 327

....................................................................316

..........................................................................................................................................................................................Protocols and protocol groups

Purpose

This section lists the protocols and protocol groups that are initially defined and enabled for traffic monitoring in VitalSuite NET. Protocol groups let you to monitor a set of related protocols as a single application on the Traffic Monitoring chart.

Protocol list

The following table lists the protocols alphabetically by protocol group, followed by the individual protocols. You can define and enable other protocols as described in the VitalSuite Administrators Guide.

Application/protocol Port

Email group

IMAP TCP Port 143

IMAP3 TCP Port 220

IMAP4S TCP Port 993

NNTP TCP Port 119

NNTPS TCP Port 563

POP2 TCP Port 109

POP3 TCP Port 110

POP3S TCP Port 995

QMTP TCP Port 209

SMTP TCP Port 25

SMTPS TCP Port 465

File Systems group

netbios-dgm UDP Port 138

netbios-ns UDP Port 137

netbios-ssn UDP Port 139

NFS (TCP) TCP Port 2049

....................................................................317

Protocols and protocol groups

Lotus Notes group

ccmail TCP Port 3264

Lotus Mail Tracking Agent Protocol (MTAP) TCP Port 3007

Lotus Notes TCP Port 1352

Oracle group

Oracle (TCP) TCP Ports 1525, 1527, 1529

Oracle (UDP) UDP Port 2005

Oracle mciautoreg TCP Port 1528

Oracle Names TCP Port 1575

Oracle Net8 Cman TCP Port 1630

Oracle Remote Data Base TCP Port 1571

Oracle-em1 TCP Port 1748

Oracle-em2 TCP Port 1754

Oracle-VP1 TCP Port 1809

Oracle-VP2 TCP Port 1808

Sybase group

Sybase Anywhere TCP Port 2638

Sybase DB Synch TCP Port 2439

Sybase SQL Any TCP Port 1498

VitalSoft group

VitalAgent TCP Port 3375

VitalSuite APPS Analysis functionality TCP Port 2474

VitalSuite APPS Help functionality TCP Port 3280

Web group

HTTP TCP Port 80

HTTP-mgmt TCP Port 280

http-rpc-epmap TCP Port 593


....................................................................318

HTTPS TCP Port 443

X-Windows group

X-Windows Ports TCP Ports 6000-6063

XDMCP TCP Port 177

Other protocols

3com-tsmux TCP Port106

914c/g TCP Port 211

ACAS TCP Port 62

ACI TCP Port 187

aed-512 TCP Port 149

anet TCP Port 212

ansanotify TCP Port 116

ansatrader TCP Port 124

appleqtc TCP Port 458

asip-webadmin TCP Port 311

at-3 UDP Port 203

at-5 UDP Port 205

at-7 UDP Port 207

at-8 UDP Port 208

at-echo UDP Port 204

at-nbp UDP Port 202

at-rtmp UDP Port 201

at-zis UDP Port 206

audionews TCP Port 114

audit TCP Port 182

Auditd TCP Port 48

AURP UDP Port 387


....................................................................319


auth TCP Port 113

BFTP TCP Port 152

BGP TCP Port 179

bl-idm TCP Port 142

BOOTPC UDP Port 68

BOOTPS UDP Port 67

CAllic TCP Port 216

CDC TCP Port 223

cfdptkt TCP Port 120

chargen TCP Port 19

cisco-fna TCP Port 130

cisco-sys TCP Port 132

cisco-tna TCP Port 131

cl/1 TCP Port 172

CMIP-agent TCP Port 164

CMIP-mgr TCP Port 163

Covia TCP Port 64

csi-sgwp TCP Port 348

CTF TCP Port 84

Daytime TCP Port 13

dbase TCP Port 217

DCP TCP Port 93

DEOS TCP Port 76

DHCPv6-client UDP Port 546

DHCPv6-server UDP Port 547

dixie TCP Port 96

DLS TCP Ports 197, 198


....................................................................320

dn6-nlm-aud TCP Port 195

dn6-smm-red TCP Port 196

DNS (TCP) TCP Port 53

DNS (UDP) UDP Port 53

DSP TCP Port 33

dsp3270 TCP Port 246

Echo UDP Port 7

emfis-cntl TCP Port 141

emfis-data TCP Port 140

erpc TCP Port 121

Exchange EPMAP TCP Port 135

Finger TCP Port 79

FTP TCP Port 20

FTP-Control TCP Port 21

FTPS TCP Port 989

FTPS-ctrl TCP Port 990

GACP TCP Port 190

genrad-mux TCP Port 176

Gopher TCP Port 70

gppitnp TCP Port 103

Graphics TCP Port 41

gss-xlicen TCP Port 128

HDAP TCP Port 263

HEMS TCP Port 151

hostname TCP Port 101

Hosts2-ns TCP Port 81

ibm-app TCP Port 385


....................................................................321


IMSP TCP Port 406

ingres-net TCP Port 134

IPX UDP Port 213

IRC TCP Port 194

IRCS TCP Port 994

is99c TCP Port 379

is99s TCP Port 380

ISI-GL TCP Port 55

ISO-IP UDP Port 147

ISO-TP0 TCP Port 146

ISO-TSAP TCP Port 102

ISO-TSAP-c2 TCP Port 399

jargon TCP Port 148

Kerberos UDP Port 88

KIS TCP Port 186

knet-cmp TCP Port 157

LA-Maint TCP Port 51

LDAP Directory Services TCP Port 389

LDAPS TCP Port 636

locus-con TCP Port 127

locus-map TCP Port 125

mailq TCP Port 174

mcidas TCP Port 112

metagram TCP Port 99

mfcobol TCP Port 86

microsoft-ds TCP Port 445

Microsoft-SQL-Server TCP Port 1433


....................................................................322

MPM TCP Port 45

MPM-flags TCP Port 44

MPM-send TCP Port 46

MPP TCP Port 218

MSG-AUTH TCP Port 31

MSG-ICP TCP Port 29

MSP TCP Port 18

multiplex TCP Port 171

mumps TCP Port 188

Name TCP Port 42

NAMP TCP Port 167

NAS TCP Port 991

NCP TCP Port 524

ndsauth TCP Port 353

netcp TCP Port 395

netsc-dev TCP Port 155

netsc-prod TCP Port 154

netviewdm1 TCP Port 729



netware-ip TCP Port 396

nextstep TCP Port 178

NFS (UDP) UDP Port 2049

NI-FTP TCP Port 47

NI-Mail TCP Port 61

NPP TCP Port 92

nsiiops TCP Port 261


....................................................................323


nss-routing UDP Port 159

NTP UDP Port 123

objcall TCP Port 94

ocbinder TCP Port 183

ocserver TCP Port 184

osu-nms TCP Port 192

pcmail-srv TCP Port 158

print-srv TCP Port 170

profile TCP Port 136

Prospero TCP Port 191

pwdgen TCP Port 129

QFT TCP Port 189

QOTD TCP Port 17

Radius UDP Port 1813

RAP TCP Ports 38, 257

Remail-ck TCP Port 50

Remedy_1098 TCP Port 1098

Remedy_1148 TCP Port 1148

remote-kis TCP Port 185

RIP UDP Port 520

RIPNG TCP Port 521

RIS TCP Port 180

RJE TCP Port 5

RLP TCP Port 39

RSVD TCP Port 168

rsvp-tunnel TCP Port 363

RTelnet TCP Port 107


....................................................................324

s-net TCP Port 166

SAFT TCP Port 487

SEND TCP Port 169

SET TCP Port 258

SFTP TCP Port 115

SGCP TCP Port 440

SGMP TCP Port 153

sgmp-traps UDP Port 160

smakynet TCP Port 122

SMPTE TCP Port 420

SMUX TCP Port 199

SNAGAS TCP Port 108

SNMP UDP Port 161

SNMP-Traps UDP Port 162

SNPP TCP Port 444

softpc TCP Port 215

SQL*NET TCP Port 66

sql-net TCP Port 150

sqlserv TCP Port 118

sqlsrv TCP Port 156

SRC TCP Port 200

SRMP TCP Port 193

SSH TCP Port 22

statsrv TCP Port 133

STMF TCP Port 501

SUNRPC (TCP) TCP Port 111

SUNRPC (UDP) UDP Port 111


....................................................................325


supdup TCP Port 95

Tacacs UDP Port 49

TACACS-DS TCP Port 65

tacnews TCP Port 98

TCP Port 24 TCP Port 24




Telnet TCP Port 23

TelnetS TCP Port 992

TFTP TCP Port 69

Time TCP Port 37

UAAC TCP Port 145

uarps TCP Port 219

UMA TCP Port 144

unify TCP Port 181

unitary TCP Port 126

UUCP-path TCP Port 117

Vettcp TCP Port 78

vmnet TCP Port 175

vmpwscs TCP Port 214

whoami UDP Port 565

Whois UDP Port 43

Whois++ UDP Port 63

XFER TCP Port 82

XNS-Auth TCP Port 56

XNS-CH TCP Port 54


....................................................................326

XNS-courier TCP Port 165

XNS-Mail TCP Port 58

XNS-Time UDP Port 52

xyplex-mux TCP Port 173

z39.50 TCP Port 210


....................................................................327

Interface type codes

..........................................................................................................................................................................................Interface type codes

Purpose

This topic lists the interface type (ifType) codes that VitalSuite NET includes in the names of discovered resources when an interface description (ifDescr) is not available. For more information about how discovered devices and resources are named, refer to the VitalSuite Performance Management Software Administrator’s Guide.

Descriptions

The following table lists the interface type codes and a description of each.

Interface type (ifType) Interface type description

Interface type code (ifTypeCode)

1 unknown other

2 regular1822 R1822

3 hdh1822 H1822

4 DDN X.25 X25

5 RFC877 X.25 X25

6 ethernet-cmsacd E

7 iso88023-csmacd E

8 iso88024-tokenbus TB

9 iso88025-tokenring TR

10 iso88026Man M

11 starlan SL

12 proteon10Mbit PT10M

13 proteon80Mbit PT80M

14 Hyperchannel HC

15 FDDI F

16 lapb LAPB

17 sdlc SDLC

18 DS1 DS1

19 e1 DS3

....................................................................328

20 basicISDN ISDN

21 primaryISDN IDSN

22 propPointToPointSerial PPP

23 ppp PPP

24 softwareLoopback L

25 eon EON

26 ethernet-3Mbit E

27 nsip NSIP

28 slip SLIP

29 ULTRA ULTRA

30 DS3 DS3

31 sip SIP

32 Frame Relay FR

33 RS232 RS232

34 Parallel Port PP

35 arcnet ARC

36 arcnetPlus ARC

37 ATM ATM

38 miox25 X25

39 sonet SONET

40 x25ple X25

41 iso8802211c LLC

42 localtalk LT

43 smdsDxi SMDS

44 Frame Relay Service FR

45 V.35 V35



....................................................................329


46 HSSI HSSI

47 HIPPI HIPPI

48 modem MODEM

49 AAL5 AAL5

50 sonetPath SONET-P

51 sonetVT SONET-VT

52 smdsIcip SMDS-ICI

53 propVirtual PV

54 propMultilink PMX

55 100BaseVG 100BaseVG

56 Fibre Channel FC

57 HIPPI Interface HIPPI-IF

58 Frame Relay Interconnect FR

59 ATM Emulated LAN for 802.3 LANE

60 ATM Emulated LAN for 802.5 LANE

61 ATM Emulated Circuit ATM-EC

62 100BaseT FE

63 ISDN and X.25 I-X25

64 CCITT V.11/X.21 V11

65 CCITT V.36 V36

66 CCITT G703 at 64 Kbps G703-64K

67 CCITT G703 at 2Mbps G703-2M

68 SNA QLCC QLLC

69 100BaseFX FE

70 Channel C

71 IEEE 802.11 Radio Spread Spectrum

RADIO-SS



....................................................................330

72 IBM System 360/370 OEMI Channel

IBM-OEMIC

73 IBM Enterprises Systems Connection

IBM-ESC

74 Data Link Switching DLSW

75 ISDN S/T Interface IDSN-S

76 ISDN U Interface ISDN-U

77 LAPD LAPD

78 IP Switching Objects IP-SO

79 Remote Source Route Bridging RSRB

80 ATM Logical Port ATMLogical

81 Digital Signal Level 0 DS0

82 Group of DS0s on the same DS1 DS0Bundle

83 bysync BSC

84 async ASYNC

85 Combat Net Radio CNR

86 OSO 802.5r DTR 8025RDTR

87 Enhanced Position Loc Reporting System

EPLRS

88 Appletalk Remote Access Protocol ARAP

89 Proprietary Connectionless Protocol

PROPCNLS

90 CCITT-ITU X.29 PAD protocol HOST-PAD

91 CCITT-ITU X.3 PAD Facility TERM-PAD

92 MultiProto Interconnect over FR FR-MPI

93 CCITT-ITU X.23 X23

94 Asymmetric Digital Subscriber Loop

ADSL



....................................................................331


95 Rate-Adapt Digital Subscriber Loop

RADSL

96 Symmetric Digital Subscriber Loop SDSL

97 Very H-speed Digital Subscriber Loop

VDSL

98 ISO 802.5 CRFP CRFP

99 Myricom myrinet MYRINET

100 Voice recEive & tranMit VOICEEM

101 Voice Foreign Exchange Office VOICEFXO

102 Voice Foreign Exchange Station VOICEFXS

103 Voice Encapsulation VOICEENCAP

104 Voice Over IP Encapsulation VOIP

105 ATM DXI ATM-DXI

106 ATM FUNI ATM-FUNI

107 ATM IMA ATM-IMA

108 PPP Multilink Bundle PPP-MLK

109 IBM IP Over Cdlc IP-CDLC

110 IBM common link access to workStation

IP-CLAW

111 IBM stacktoStack STK-2-STK

112 IBM Virtual IP Address IBM-VIPA

113 IBM Multi-protocol Channel support

MPC

114 IBM IP Over ATM IP-ATM

115 ISO 802.5j Fiber Token Ring 802.5J-TKN

116 IBM twinaxial data link control TDLC

117 Gigabit Ethernet GE

118 HDLC HDLC



....................................................................332

119 LAPF LAPF

120 V.37 V37

121 X25 Multi-Link Protocol X25-MLP

122 X25 Hunt Group X25-HG

123 Transp HDLC T-HDLC

124 InterLeave Channel INTR-CHNL

125 Fast Channel FAST

126 IP (for APPN HPR in IP Networks) IP-APPN

127 CATV Mac Layer CATV-MAC

128 CATV DownStream Interface CATV-DOWN

129 CATV UpStream Interface CATV-UP

130 Avalon Parallel Processor MPP-SWITCH

131 Encapsulation Interface TUNNEL

132 Coffee Pot COFFEE

133 Circuit Emulation Service CES

134 ATM SubInterface ATM-SUBIF

135 Layer 2 Virtual LAN using 802.1Q L2-VLAN

136 Layer 3 Virtual LAN - IP protocol L3IP-VLAN

137 Layer 3 Virtual LAN IPX protocol L3IPX-VLAN

138 IP over Power Lines digitalPowerline

139 Multimedia Mail over IP mediaMailOverIP

140 Dynamic Synchronous Transfer Mode

dtm

141 Data Communication Network dcm

142 IP Forwarding Interface ipForward

143 Multi-rate Symmetric DSL msdsl



....................................................................333


144 IEEE1394 High Performance Serial Bus

iee1394

145 HIPPI-6400 if-gsn

146 DVB-RCC MAC Layer dvbRccMacLayer

147 DVB-RCC Downstream Channel dvbRccDownstream

148 DVB-RCC Upstream Channel dvbRccUpstream

149 ATM Virtual Interface atmVirtual

150 MPLS Tunnel Virtual Interface mplsTunnel

151 Spatial Reissue Protocol SRP

152 Voice Over ATM voiceOverATM

153 Voice Over Frame Relay voiceOverFrameRelay

154 Digital Subscriber Loop Over ISDN idsl

155 Avici Composite Link Interface compositeLink

156 SS7 Signaling Link ss7SigLink

157 Prop. P2P wireless interface propWirelessP2P

158 Frame Forward Interface frForward

159 Multiprotocol over ATM AAL5 rfc1483

160 USB Interface usb

161 IEEE 802.3ad Link Aggregate ieee8023adLag

162 BGP Policy Accounting bgppolicyaccounting

163 FRF .16 Multilink Frame Relay frf16MfrBundle

164 H323 Gatekeeper h323Gatekeeper

165 H323 Voice and Video Proxy h323Proxy

166 MPLS MPLS

167 Multi-frequency signaling link mfSigLink

168 High Bit-Rate DSL - 2nd generation

hdsl2



....................................................................334

169 Multirate HDSL2 shdsl

170 Facility Data Link 4Kbps on a DS1 ds1FDL

171 POS interface POS

172 DVB-ASI Input dvbAsiIn

173 DVB-ASI Output dvbAsiOut

174 Power Line Communications plc

175 Non Facility Associated Signaling nfas

176 TR008 tr008

177 Remote Digital Terminal gr303RDT

178 Integrated Digital Terminal gr303IDT

179 ISUP isup

180 prop/Maclayer propWirelessMaclayer

181 prop/Downstream propWirelessDownstrm

182 prop/Upstream propWirelessUpstrm

183 HIPERLAN Type 2 Radio Interface hiperlan2

184 PropBroadbandWirelessAccesspt2multipt

propBWAp2Mp

185 SONET Overhead Channel sonetOverheadChannel

186 Digital Wrapper digitalWrapperOverhd

187 ATM adaptation layer 2 aal2

188 MAC layer over radio links radioMAC

189 ATM over radio links atmRadio

190 Inter Machine Trunks imt

191 Multiple Virtual Lines DSL mvl

192 Long Reach DSL reachDSL

193 Frame Relay DLCI End Point frDlciEndPt

194 ATM VCI End Point atmVciEndPt



....................................................................335


195 Optical Channel opticalChannel

196 Optical Transport opticalTransport

197 Proprietary ATM propAtm

198 Voice Over Cable Interface voiceOverCable

199 Infiniband infiniband

200 TE Link teLink

201 Q.2931 q2931

202 Virtual Trunk Group virtualTg

203 SIP Trunk Group sipTg

204 SIP Signaling sipSig

205 CATV Upstream Channel CATVUpstreamChannel

206 Acorn Econet econet

207 FSAN 155Mb Symmetrical PON interface

pon155

208 FSAN622Mb Symetrical PON interface

pon622

209 Transparent bridge interface bridge

210 Interface common to multiple lines linegroup

211 voice E&M Feature Group D voiceEMFGD

212 voice FGD Exchange Access North American

voiceFGDEANA

213 voice Direct Inward Dialing voiceDID

214 MPEG transport interface mpegTransport

215 6to4 interface sixToFour

216 GTP (GPRS Tunneling Protocol) gtp

217 Paradyne EtherLoop 1 pdnEtherLoop1

218 Paradyne EtherLoop 2 pdnEtherLoop2

219 Optical Channel Group opticalChannelGroup



....................................................................336

220 HomePNA ITU-T G.989 homepna

221 Generic Framing Procedure (GFP) gfp

222 Layer 2 Virtual LAN using Cisco ISL

ciscoISLvlan

223 Acteleis proprietary MetaLOOP High Speed Link

actelisMetaLOOP

224 FCIP Link fcipLink



....................................................................337

Overview

Adding VitalSuite NET resources manually

..........................................................................................................................................................................................Overview

Purpose

This section describes how to add resources to VitalSuite NET that were not detected during the discovery process.

Contents


Add resources manually to VitalSuite NET 338

Resource configuration file 340

....................................................................338

..........................................................................................................................................................................................Add resources manually to VitalSuite NET

When to use

Use this procedure to configure a VitalSuite NET Polling server to collect data for resources specified in custom configuration file.

Before you begin

Make sure you know the resources that you want to manually add to VitalSuite NET.

Related information

For information on viewing resource data in VitalSuite NET, refer to the VitalSuite Network Performance Management Software User’s Guide.

Procedure

To add resources manually:

...........................................................................................................................................................................

1 Create the resource configuration file, as described in “Resource configuration file”, on page 340.

...........................................................................................................................................................................

2 Copy the ResInsertUtil executable from the <install_dir>/vitalnet/program directory to the Polling server that will collect data for the resources specified in your resource configuration file.

...........................................................................................................................................................................

3 Ensure that the resource configuration file is in the same directory as the ResInsertUtil executable.

...........................................................................................................................................................................

4 If your Polling server is a UNIX machine, log in as vsadm with a password of vsadm.

Important! If your Polling server is a Windows machine, you do not need to perform this step.

...........................................................................................................................................................................

5 On the Polling server, open a Command Prompt (on Windows) or a Terminal window (on UNIX).

....................................................................339

Add resources manually to VitalSuite NET

...........................................................................................................................................................................

6 At the command line, navigate to the location of the ResInsertUtil executable and enter the following command:

resinsertutil <resource_configuration_file_name>

Important! If you do not provide a resource configuration file name, ResInsertUtil looks for a file named resinsert.cfg.

Result: The Polling server now collects data for the resources specified in the configuration file.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................340

..........................................................................................................................................................................................Resource configuration file

Overview

The resource configuration file is a file you can create with any plain-text editor, such as WordPad or vi. You can use a single configuration file for one or more resources, but each resource in the file requires its own resource definition.

Each resource definition is defined as a new resource or an added resource. New resource definitions must have values for all required fields. Added resource definitions use the field values of the resource definition preceding it, plus any field values in its own definition.

Resource definition fields

Each resource definition in the file uses some or all the fields described in the following table. The Table column indicates the database table modified for each field. The Description column provides a brief explanation of the field in relation to the resource. The Mandatory column indicates whether the field is required in the resource definition.

Field Table Description Mandatory

Dsid Config Dataset ID Yes

Devname Dev Device name Yes

Devip Dev Device IP address Yes

IfIndex If Interface index Yes (or IfSlot or IfPort)

IfSlot If Slot Yes (or IfIndex or IfPort)

IfPort If Port Yes (or IfPort or IfSlot)

Resname Res Display name Yes

IfSubPort If SubPort No

IfSpeed If Interface speed No

IfAuxIndex If Auxiliary index No

IfDescr If Interface description No

Subtype Config Dataset subtype No

CircuitIndex1 Config Circuit index No




....................................................................341

Resource configuration file

Format

The resource configuration file can have any name, but it must be formatted properly. Each resource in the file must have its own resource definition, arranged as follows:

[new/add] resource<field_name1> = <field_value1><field_name2> = <field_value2>...

Lines beginning with a pound sign (#) are comment lines, and are not used by VitalSuite NET when you run ResInsertUtil.

Sample resource configuration file

The example below shows a resource configuration file with three resource definitions. Because the second resource is similar to the first, its resource definition can use some of the same field values as the first resource definition. To accomplish this, the second resource definition is configured as an added resource. The second resource definition will use the same fields and values as the preceding resource definition. The fields and values defined in the second resource definition will overwrite or be added to the fields and values borrowed from the first resource definition.

# First resource definitionnew resourcedsid=24subtype=44devname=<device_name>devip=111.222.33.44


CollectorIndex1 Config Collector index No

CollectorIndex2 Config Collector index No

Auxid Config Auxillary index No

AuxStr Config Auxillary string No

CircuitSpeed1 Config Circuit speed No



CircuitService Config Circuit quality of service

No

GroupExtension Res Auxillary string No

Community Dev Community string No (defaults to public)

Field Table Description Mandatory

....................................................................342

resname=8868_20_101ifIndex=8868CircuitIndex1=20CircuitIndex2=101CircuitSpeed1=2000# Second resource definitionadd resourceresname=8868_20_102CircuitIndex2=102CircuitSpeed1=2500# Third resource definitionnew resourcedsid=25subtype=44devname=<device_name>devip=111.222.33.44resname=8868ifIndex=8868ifSpeed=4068000

....................................................................343

Overview

Resolve missing resource data in VitalSuite NET

..........................................................................................................................................................................................Overview

Purpose

This section describes a few tasks you can perform when data for a VitalSuite NET resource is not being displayed on the VitalSuite NET pages and reports.

Contents

This sections contains the following topics:

Verify the collector is enabled 344

Verify the collector is running 346

Access the UTM status codes 348

Modify the default SNMP timeout value 352

....................................................................344

..........................................................................................................................................................................................Verify the collector is enabled

When to use

Use this procedure to verify that the collector responsible for obtaining the missing resource data is enabled. If a collector is disabled, the associated resource is not displayed in the VitalSuite NET pages and reports.

Before you begin

Know the name of the resource for which VitalSuite NET is not collecting data.

Related information

For additional information on how to resolve missing resource data in VitalSuite NET, refer to:

• “Verify the collector is running”, on page 346

• “Access the UTM status codes”, on page 348

• “Modify the default SNMP timeout value”, on page 352

Procedure

To verify that the appropriate collector is enabled:

...........................................................................................................................................................................

1 In the Web Console, go to the Network page on the ADMIN tab.

...........................................................................................................................................................................

2 Click Collectors

Result: The Enable/Disable Collectors page displays.

...........................................................................................................................................................................

3 Scroll through the page to locate the collector type for the resource that is missing data.

...........................................................................................................................................................................

4 Ensure that the box next to the collector type is selected.

...........................................................................................................................................................................

5 If the box is empty, select the box and then click Submit.

...........................................................................................................................................................................

6 Wait for the next hourly aggregation period to complete and then check the VitalSuite NET pages and reports for data.

....................................................................345

Verify the collector is enabled

...........................................................................................................................................................................

7 If you have verified that the collector is enabled and the data is still missing, verify that the collector for that resource is running, as described in the next topic.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................346

..........................................................................................................................................................................................Verify the collector is running

When to use

Use this procedure to verify that the collector responsible for obtaining the missing resource data is running.

Before you begin

Make sure you have completed the procedures in “Verify the collector is enabled”, on page 344.

Related information


• “Verify the collector is enabled”, on page 344



Procedure

To verify that the collector is running:

...........................................................................................................................................................................

1 Open a command shell directly on the Polling server.

...........................................................................................................................................................................

2 Enter the following command:

statuscollectors

...........................................................................................................................................................................

3 If the appropriate collector is not running, perform one of the following:

• On Windows, restart the VitalSuite AtBoot Scheduler service.

• On UNIX, enter the startcollectors command.

Result: Any collectors that should be running are started.

...........................................................................................................................................................................

4 Run statuscollectors again to verify that the collector has started.

....................................................................347

Verify the collector is running

...........................................................................................................................................................................

5 Wait for the next hourly polling period to complete and then check VitalSuite NET pages and reports for data.

Important! Terminal Services Client does not return accurate data for the statuscollectors command. If you are using Windows and do not have direct access to the Polling server, and if the machine hosting the Polling server also has a Master or Aggregation server, use the following URL to obtain collector status: http://<server_address>/cgi-bin/VNstatus.cgi

...........................................................................................................................................................................

6 If data is still missing, use the UTM status codes to diagnose the problem as described in the next topic.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................348

..........................................................................................................................................................................................Access the UTM status codes

When to use

If data for a resource is missing from VitalSuite NET pages and you have verified that the collector for that resource is enabled and running, use this procedure to access the UTM status codes that can help diagnose the problem.

The UTM status codes indicate a status response for each attempted poll on a resource. Every poll has a status entry, which is recorded after every polling period.

Using the UTM status codes to diagnose the reason data might be missing involves running three queries. The first is run on the VNAggr database and enables you to learn the resource ID (resID) and dataset prefix for the appropriate collector. The second and third queries are run on the VNPoller database, using the resID and dataset prefix to learn the status codes for the polls.

Important! Do not make changes to the VitalSuite NET databases. Use the following procedure only to diagnose possible problems with data collection.

Before you begin

Make sure the collector responsible for collecting the missing resource data has been enabled and is running.

Related information





Procedure

To access the UTM status code for a resource:

...........................................................................................................................................................................

1 In the Web Console, note the displayed name of the resource that is missing data.

...........................................................................................................................................................................

2 Log in with VitalSuite NET administrator access to the Aggregation server.

...........................................................................................................................................................................

3 Run the following query on the VNAggr database, where <name> is part of the resource name as displayed on VitalSuite NET pages and reports:

select resid,displayname,dataset from resourceview where displayname like ‘%<name>%’

....................................................................349

Access the UTM status codes

...........................................................................................................................................................................

4 From the query results, locate the resource for which data is missing and note its resID and dataset.

...........................................................................................................................................................................

5 If necessary, log in with VitalSuite NET administrator access to the Polling server.

...........................................................................................................................................................................

6 Run the following query on the VNPoller database, where <prefix> is the dataset prefix and <resid> is the resource ID from the first query:

select status,count(#) from <prefix>utmstats where resid = <resid> group by status order by status

Result: This query returns a list of the UTM status codes for the specified collector, with the number of polls that returned each status. This information can help you identify whether there is a recurring problem with data collection for that resource type. Refer to “Collector status codes”, on page 349 for the meaning of each code.

...........................................................................................................................................................................

7 Run the following query on the VNPoller database, where <prefix> is the dataset prefix and <resid> is the resource ID noted from the first query:

select * from <prefix>utmstats where resid = <resid> and status != 0 and status != 5

Additional information: This query has the potential to return a large number of rows. Consider modifying the query to return more specific information. The results can help you identify problems for specific time frames.

Note the value in the status column of the query results. Refer to “Collector status codes”, on page 349 for the meaning of each code. Contact Lucent Technical Support if the code is anything other than 0, 1, 3, or 5, and you are unable to resolve the problem.

...........................................................................................................................................................................E N D O F S T E P S

Collector status codes

The following table describes the collector status codes.

Code Description

0 good—The collector was up and collected data.

1 timeout—The device was down, or was not reachable via SNMP. VitalSuite NET attempts to contact the device three times before this code is applied.

2 SNMP_noSuchName—A device was missing an OID for which VitalSuite NET is searching.

3 device_reset—The device was rebooted or the interface was reset, resetting counters and rendering some VitalSuite NET data calculations impossible.

....................................................................350

4 invalid_delta—Time between collection periods was either negative or could not be calculated.

5 first_delta—Indicates that no delta time could be calculated because only the start time is available. This code is used for the first polling period following a restart of a collector.

6 not_up—The device was not running.

7 invalid_data—VitalSuite NET has removed data for the resource because data-validation rules were violated.

8 validation_failure—VitalSuite NET has removed data for the resource because data-validation rules were violated.

101 SNMP_ERR_TOOBIG—The protocol data unit used was too big, preventing the resource from including data in a single SNMP transfer.

102 SNMP_ERR_NOSUCHNAME—The device was missing an OID for which VitalSuite NET is searching.

103 SNMP_ERR_BADVALUE—A SetRequest operation asked the agent to write an inappropriate value (for example, to write an integer where a text string is required).

104 SNMP_ERR_READONLY—A SetRequest operation attempted to write a variable that the operator is not allowed to write. Either the access mode is read-only or the variable’s MIB definition does not permit write access.

105 SNMP_ERR_GENERR—Generic error. All SNMPv2 errors that are not associated with a specific code are reported as generic errors.

106 SNMP_ERR_NOACCESS—The variable binding's name specified an existing or non-existent variable to which this request was denied access because it is not in the appropriate MIB view.

107 SNMP_ERR_WRONGTYPE—The variable binding's value field specified a type which is inconsistent with that required for all variables which share the same OID prefix as the variable binding's name.

108 SNMP_ERR_WRONGLENGTH—The variable binding's value field specified a length which is inconsistent with that required for all variables which share the same OID prefix as the variable binding's name.

109 SNMP_ERR_WRONGENCODING—The variable binding's value field contained an ASN.1 encoding which is inconsistent with that field's ASN.1 tag.

110 SNMP_ERR_WRONGVALUE—The variable binding's value field specified a value which could under no circumstances be assigned to the variable.

111 SNMP_ERR_NOCREATION—The variable binding's name specified a variable which does not exist and could not ever be created (even though some variables sharing the same OID prefix might under some circumstances be able to be created).

Code Description

....................................................................351

Access the UTM status codes

112 SNMP_ERR_INCONSISTENTVALUE—the variable binding's value field specified a value that could under other circumstances be held by the variable, but was inconsistent or otherwise unable to be assigned to the variable.

113 SNMP_ERR_RESOURCEUNAVAILABLE—The assignment of the value specified by the variable binding's value field to the specified variable requires the allocation of a resource which is presently unavailable.

114 SNMP_ERR_COMMITFAILED—The SetRequest operation failed.

115 SNMP_ERR_UNDOFAILED—The UndoRequest operation failed.

116 SNMP_ERR_AUTHORIZATIONERROR—The collector is not authorized to access the device.

117 SNMP_ERR_NOTWRITABLE—The variable binding's name specified a variable which exists but can not be modified, regardless of the value specified.

118 SNMP_ERR_INCONSISTENTNAME—The variable binding's name specified a variable which does not exist and can not be created under the present circumstances (even though it could be created under other circumstances).

Code Description

....................................................................352

..........................................................................................................................................................................................Modify the default SNMP timeout value

When to use

Use this procedure to modify the default SNMP timeout value so network resources have more time to respond to VitalSuite NET SNMP requests for data.

In some environments, network resources can be slow to respond to VitalSuite NET’s SNMP request for data. As a result, VitalSuite NET may not collect data for certain resources if they do not respond within the default SNMP timeout (5 seconds).

Important! Increasing the default SNMP timeout value only affects RMON and MIB2 resources, as well as resources for which you built a collector using MIBWorks. Changing the default SNMP timeout does not affect data polling time.

Before you begin

Use the UTM cause codes discussed in “Access the UTM status codes”, on page 348 to determine if the lack of resource data is due to an SNMP timeout error. If this is the case, you can extend the default SNMP timeout value to give your devices more time to respond to VitalSuite NET.

Related information





Procedure

To modify the default SNMP timeout:

...........................................................................................................................................................................

1 Using a database editor (such as Query Analyzer on Windows), increase the default SNMP timeout value by running the following command on each VitalSuite NET database:

UPDATE SysTable SET SysValue=<value> WHERE SysOption='COLLECTOR SNMP TIMEOUT'

where <value> is the number of microseconds the collectors have to respond to VitalSuite NET’s SNMP request. The default value is 5000000 (5 seconds).

...........................................................................................................................................................................

2 On the VitalSuite NET Polling server, restart the collector that you want to use the new SNMP timeout value.

....................................................................353

Modify the default SNMP timeout value

To restart a collector, go to a command prompt on the VitalSuite NET Polling server(s) and run the following command:

For RMON collectors:

stopcollectors rmoncollectorstartcollectors

For MIB2 collectors:

stopcollectors ifcollectorstartcollectors

For custom collectors created using MIBWorks:

stopcollectors ucollector-<dsid>startcollectors

where <dsid> is the data set ID of the custom collector.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................354

Threshold parameters

..........................................................................................................................................................................................Overview

Purpose

This section provides the default quality index parameters for VitalSuite NET resources and the default network alarm measurements.

Contents


Default quality index parameters for resource types 355

Network alarm threshold measurements 368

....................................................................355

Default quality index parameters for resource types

..........................................................................................................................................................................................Default quality index parameters for resource types

Purpose

This topic lists the default Quality Index Parameters for VitalSuite NET resource types. You can modify default parameters by selecting ADMIN | Thresholds | Quality index. Refer to the VitalSuite Performance Management Software Administrator’s Guide for more information

List of quality index parameters

The following table lists the default Quality Index Parameters for VitalSuite NET resource types.The metric used and any default values (upper limits unless noted otherwise) are listed in parentheses after the measurements.

Resource type Measured parameter SP only

VoIP

CCM Call Manager Percent Succeeded (%)Average Delay (%)Average Jitter (%)Average Packet Loss Ratio (%)Average Voice QoS (%)

CCM Call Manager Pair Percent Succeeded (%)Average Delay (%)Average Jitter (%)Average Packet Loss Ratio (%)Average Voice QoS (%)

CCM Partition Percent Succeeded (%)Average Delay (%)Average Jitter (%)Average Packet Loss Ratio (%)Average Voice QoS (%)

CCM Partition Pair Percent Succeeded (%)Average Delay (%)Average Jitter (%)Average Packet Loss Ratio (%)Average Voice QoS (%)

CCM IP Phone Calls Succeeded (%)Average Delay (%)Average Jitter (%)Average Packet Loss Ratio (%)Average Voice QoS (%)

....................................................................356

Avaya Gatekeeper Average Delay (%)Average Jitter (%)Average MOS (%)Average Packet Loss Ratio (%)Average Voice QoS (%)The Average Delay QI value is one third of the incoming average delay data. If you want to adjust the QI ranges for the Average Delay QI, determine the range based on a value that is one third of the incoming average delay data.

Avaya Gateway Average Delay (%)Average Jitter (%)Average MOS (%)Average Packet Loss Ratio (%)Average Voice QoS (%)The Average Delay QI value is one third of the incoming average delay data. If you want to adjust the QI ranges for the Average Delay QI, determine the range based on a value that is one third of the incoming average delay data.

Avaya IP Phone Average Delay (%)Average Jitter (%)Average MOS (%)Average Packet Loss Ratio (%)Average Voice QoS (%)The Average Delay QI value is one third of the incoming average delay data. If you want to adjust the QI ranges for the Average Delay QI, determine the range based on a value that is one third of the incoming average delay data.

Avaya VMM Average Delay (%)Average Jitter (%)Average MOS (%)Average Packet Loss Ratio (%)Average Voice QoS (%)The Average Delay QI value is one third of the incoming average delay data. If you want to adjust the QI ranges for the Average Delay QI, determine the range based on a value that is one third of the incoming average delay data.

BroadWorks App Server Percentage of MCP Res Alloc Failures (%)


....................................................................357


BroadWorks Media Server No Port Available Errors (#)

BroadWorks Net Server Percentage of Policy Request Failures (%)

VoIP Agent Stats Delay (ms)Jitter (msMOS (#)Packet Loss (%)

HSS Call Server Interface Average congestion (%)

HSS App Server Interface Average congestion (%)

Brix SCCP Network Active Test

Jitter (ms)Percentage of Lost Packets (%)MOS Score (#)Post Dial Delay (ms)RT Latency (ms)

Brix RTP Network Active Test

Reverse Jitter (ms)Forward Jitter (ms)Percentage of Reverse Lost Packets (%)Percentage of Forward Lost Packets (%)Reverse MOS Score (#)Forward MOS Score (#)Post Dial Delay (ms)RT Latency (ms)

Brix H323 Service Active Test

Forward Jitter (ms)Percentage of Lost Packets (%)MOS Score (#)Post Dial Delay (ms)Reverse Jitter (ms)RT Latency (ms)

Router CPU/Buffers

Lucent Router Utilization (%)

Lucent Brick Average Cache Memory (%)Average CPU (%)Average Main Memory (%)Average Packet Memory (%)Overall Utilization (%)

Cisco Router Buffer Allocation Failure (per second)Buffer Misses (per second)Buffer No Memory (per second) CPU Utilization (%)

Cisco CPU Average CPU Utilization (%)


....................................................................358

Cisco Memory Pool Memory Pool Utilization (%)

Cisco CIP CPU CPU Utilization (%) Memory Utilization (%)

Nortel Router Buffer Failure (%) Buffer Utilization (%) CPU Utilization (%) Memory Utilization (%)

Redback Router Utilization (%)

Enterasys CPU Utilization (%)

Enterasys Storage Storage (%)

Juniper System Average Buffer Pool Utilization (%) Average CPU Utilization(%)

Juniper ERX Cards Average CPU Utilization (%)

Juniper ERX NVS Utilization (%)

Juniper Netscreen Average CPU Utilization (%)Average Memory Utilization (%)Average Session Utilization (%)Overall Utilization (%)

PSAX CPU Utilization (%)

Lucent Core SwitchNode Utilization (%) ✔

3Com Router CPU Utilization (%)

Lucent Core Switch Cards Average CPU Utilization (%) ✔

Lucent Access Slot Memory

Average Busy Memory (#) Memory Allocation Fails (%) Memory Free Fails (%) Peak Busy Memory (#)

✔

Cisco PDSN System Congestion (%) ✔

Foundry System Peak CPU Utilization (%)Peak Memory Utilization (%)

UTStarcom FACN Congestion (%) ✔

UTStarcom PDSN-FACN Utilization (%) ✔


....................................................................359


WANs

WAN Circuit MIB II Broadcasts (% of total packets)Discards (% of total packets)Errors (% of total packets)Utilization (%)

HIgh Capacity WAN Broadcast Packets (%) Discarded Packets (%)Error Packets (%)Utilization (%)

MPLS MIB II Broadcast Packets (%)Discarded Packets (%)Error Packets (%)Utilization (%)

Cisco VPN Phase2 Tunnel Errors (%)

Cisco DS0 Statistics Utilization (%)

WAN DS1 Error DS1 Average Errors (%))DS1 Peak Errors (%)

WAN DS3 Error DS3 Average Errors (%)DS3 Peak Errors (%)

WAN SONET Error Line Average Errors (%) Line Peak Errors (%) Section Average Errors (%) Section Peak Errors (%)

RMON WAN Errors (% of total packets) Utilization (%)

Stratacom Voice Channel Discards (%)Utilization (%)

Stratacom Fast Packet Trunk

Drops (%) Errors (%) Utilization (%)

Juniper M/T MPLS Utilization (%)

Lucent Stinger - ADSL - CAP - Performance

Down to Up (%) Rx Signal Present (%)

✔

Lucent Stinger - ADSL - DMT - Performance

Down to Up (%) Rx Signal Present (%)

✔

Lucent Stinger - SDSL - Performance

Down to Up (%)Rx Signal Present (%)

✔


....................................................................360

Lucent Access WAN Line Perf

Percent of Non-working Channels (%)

Lucent Access High Capacity Interface

Utilization (%)

Frame Relay

Lucent Core FR DLCI Discards (%)Utilization (%)

✔

Frame Relay PVC Congestion (% of total packets) Discards (% of total packets) Invalid LMI (% of total time) Utilization (%)

RMON Frame Relay Congestion (%) Down Time (% of total time)Utilization (%)

Navis FR Trunk Broadcasts (%)Discards (%)Errors (%) Utilization (%)

✔

Navis FR PVC Utilization (%) ✔

CWM FR Connection Utilization (%)

Stratacom FR Port Drops (%) Errors (%)Utilization (%)

Stratacom FR Channel Discards (%)Utilization (%)

Navis FR L-Port Trunk Drops (%)Errors (%)Utilization (%)

✔

Navis FR Circuit Drops (%)Utilization (%)

✔

Navis FR UNI/NNI Drops (%)Errors (%)Utilization (%)

✔

CWM FR Port Utilization (%)

ATM


....................................................................361


ATM Trunk Errors (% of total cells) Utilization (%)

ATM PVC Errors (% of total cells) Utilization (%)

Lucent ATM Trunk Errors (% of total cells) Utilization (%)

Lucent ATM PVC Errors (% of total cells) Utilization (%)

Lucent Access CES CES PVC

Peak Utilization (%) ✔

Lucent Access CES PVC Percent Dropped (%)Peak Utilization (%)

✔

Lucent Access CES SPVC Percent Dropped (%)Peak Utilization (%)

✔

Lucent Access ATM Interfaces

Error Packets (%)Utilization (%)

✔

Navis ATM Trunk Drops (%) Errors (%) Utilization (%)

✔

Navis ATM PVC Drops (%)Utilization (%)

✔

Nortel Router ATM Trunk Bad Cells (#) Oversized (#)Utilization (%)

Nortel Router ATM PVC Bad Cells (#) Oversized (#)Utilization (%)

CWM BPX Trunk Utilization (%)

CWM IGX Trunk Utilization (%)

CWM ASI Connection Utilization (%)

CWM IGX FTP Trunk Utilization (%)

Nortel Passport ATM Trunk

Discards (%) Utilization (%)


....................................................................362

Centillion ATM Trunk Dropped Cells (#)No-signal Time (% of total time)Utilization (%)

Redback ATM Utilization (%)

Xylan ATM Trunk Utilization (%) Discard Rate (%)

Lucent Core ATM LPort Discard Rate (%)Utilization (%)

✔

Lucent Core ATM Trunk Discard Rate (%)Utilization (%)

✔

Lucent Core PVC In Discards (%) Utilization (%)

✔

Navis ATM Trunk Ext Drops (%)Errors (%)Utilization (%)

✔

Navis ATM Logical Port Trunk

Drops (%)Utilization (%)

✔

Navis ATM PVC Ext V8 Drops (%)Utilization (%)

✔

Navis ATM PVC Ext Drops (%)Utilization (%)

✔

Navis ATM Opti Trunk (Ckt)


✔

Navis ATM Logical Port UNI/NNI


✔

Navis ATMoMPLS Trunk Average Utilization (%) ✔

Juniper M/T ATMoMPLS Trunk

Outgoing Tail Queue Packet Drops (%)Trunk Utilization (%)

✔

Lucent Access ATM IfVCC Stats

Bad Cells (#) ✔

Lucent Access ATM VCC Stats

Bad Cells (#) ✔


....................................................................363


LANs

LAN Segment MIB II Broadcasts (% of total packets)Discards (% of total packets)Errors (% of total packets) Utilization (%)

High Capacity LAN Broadcast Packets (%) Discarded Packets (%) Error Packets (%)Utilization (%)

Lucent Brick Interface Discards (%)Errors (%)Average Utilization (%)

WLAN 802.11 Transmitted Fragments (%)Transmitted Frames (%)Failed Frame Transmits (%)

Ethernet RMON Collisions (% of total packets) Errors (% of total packets)Utilization (%)

Ethernet Hub Collisions (% of total packets) Errors (% of total packets)Utilization (%)

Token Ring RMON Errors (% of total packets)Events (% of total packets) Utilization (%)

Cisco CIP Sub-Channel Utilization (%)

Foundry Switch Port Utilization

Broadcasts (#)Discards (#)

SAN

SAN Port Congestion (%)Errors (%)Utilization (%)

SAN Class Congestion (%)

McData SAN Port Congestion (%)Errors (%)Utilization (%)

McData SAN Class Congestion (%)


....................................................................364

SAN Fabric Congestion (%)Errors (%)

Availability/Resp Time

Local-to-Remote Pings Returned (#)Response Time (ms)

Servers

BMC NT Server Server Errors (%)Page Faults (per second)

BMC NT CPU CPU Utilization (%)

BMC NT Logical Disks Disk Busy (%)

BMC UNIX Server Average CPU Utilization (%)

BMC UNIX Filesystem File System Utilization (%)

Compaq Server Utilization (%)

Compaq CPU CPU Utilization (%)

Compaq File System Utilization (%)

Compaq PCI Bus Utilization (%)

Compaq Disk Errors (%)Minimum Functional Test Values (%)

Servers (Host MIB) Utilization (per poll)

Server CPU CPU Utilization (%)

Server Disk Disk Failure (per poll) Disk Utilization (%)

NT Servers (Perf MIB) Cache Faults (per second) CPU Utilization (%)Interrupts (per second)Page Faults (per second)

NT Disk Disk Busy (%)

Sun Server Average Swap Utilization (%)Average Memory Utilization (%)

System Application App CPU Utilization (%)Memory Utilization (%)


....................................................................365


HSS Server Average Utilization (%)

HSS File System Average Disk Utilization (%)

Windows Server Metrics CPU Utilization (%)Free Disk Space (%)Used Page File (%)

Network Services

Cisco QoS Classmap Drops (%)Utilization (%)

Cisco QoS Police Drops (%)

Cisco QoS Queueing Discards (%)

Cisco QoS Traffic Shaping Drops (%)

Cisco QoS RED Random Drops (%)Tail Drops (%)Utilization (%)

Cisco CAR Drops (%)Utilization (%)

QIP DHCP Addr Cap DHCP Server Address used Utilization (%)

QIP DHCP Transactions DHCP Server Availability (%)

QIP DNS Transactions DNS Server Availability (%)

Alvarion WiMAX Services Data Loss (%)

Cisco SAA/IP SLA

SAA/IP SLA DHCP Pings Returned (#)Response Time (ms)

SAA/IP SLA DNS Pings Returned (#)Response Time (ms)

SAA/IP SLA FTP Pings Returned (#)Response Time (ms)

SAA/IP SLA HTTP Pings Returned (#)Response Time (ms)

SAA/IP SLA Ping Pings Returned (#)Response Time (ms)


....................................................................366

SAA/IP SLA TCP Pings Returned (#)Response Time (ms)

SAA/IP SLA UDP Pings Returned (#)Response Time (ms)

SAA/IP SLA DLSw Pings Returned (#)Response Time (ms)

Wireless

CDMA CELL qiCongestion (#)Congestion (%)qiDrops (#)Drops (%)qiUtilization (#)Utilization (%)

✔

Other Types

MIB-II IP Totals Discards (%) Errors (%) Missed (%)Throughput (%)

Cisco DSP Card Stats Utilization (%)

Cisco DSP Status Utilization (%)

Cisco Access Server Error (%)

Juniper M/T DCU Utilization (%)

Juniper M/T COS Congestion (%)Utilization (%)

Juniper M/T COC I/F Q Bytes Dropped (%)

Juniper ERX Traffic Class Percentage Bytes Dropped (%)Percentage Green Bytes Dropped (%)Percentage Red Bytes Dropped (%)Percentage Yellow Bytes Dropped (%)Utilization (%)

Juniper ERX Subscriber Subscriber Deny Responses (%)Subscriber Error Responses (%)Subscriber License Usage (%)

MIB-II ICMP Data Errors (%)Quenches (%)Unreached (%)


....................................................................367


Catalyst Bandwidth Utilization

Average Utilization (%)Peak Utilization (%)

Cisco Catalyst PS and FAN Status

Fan Major (%)Fan Minor (%)Fan Other (%)Ps1 Major (%)Ps1 Minor (%)Ps1 Other (%)Ps2 Major (%)Ps2 Minor (%)Ps2 Other (%)

Catalyst Temperature Alarm Status

Critical Temperature (%)Minutes in Critical Temperature (%)

Lucent Router - Ethernet In Collisions (#) In Errors (%) Out Carrier Loss (#) Out Collisions (#) Out Errors (%)Out Jabber Timeouts (#)Out No Carrier (#)In Frames (%)

Cisco PDSN Registrations Congestion (%) ✔

Cisco PPP Stats Utilization (%) ✔

Lucent Access Modem Stats

Percentage of Bad Modems (%)

Lucent Access Slot Stats Percentage of Slot Uptime (%)


....................................................................368

..........................................................................................................................................................................................Network alarm threshold measurements

Where to modify thresholds

Thresholds can be modified by selecting ADMIN | Thresholds | Alarms | Network thresholds in the Web Console. Refer to the VitalSuite Performance Management Software Administrator’s Guide for more information.

List of network alarm measurements

The following table lists the Network alarm measurements for each VitalSuite NET resource type. Default values are displayed in parentheses.

Resource type Measurement SP only

VoIP

CCM Call Manager Average Duration (under 2 seconds)Percent Succeeded (under 50%)Failed Calls (20 calls)Average Voice QoS (under 60%)Average Packet Loss Ratio (1%)Maximum Packet Loss Ratio (3%)Average Jitter (80ms)Maximum Jitter (120ms)Average Delay (100ms)Maximum Delay (200ms)Call Minutes (360 minutes/hour)Calls (120 calls/hour)

CCM Call Manager Pair Average Duration (under 2 seconds)Percent Succeeded (under 50%)Failed Calls (20 calls)Average Voice QoS (under 60%)Average Packet Loss Ratio (1%)Maximum Packet Loss Ratio (3%)Average Jitter (80ms)Maximum Jitter (120ms)Average Delay (100ms)Maximum Delay (200ms)Call Minutes (360 minutes/hour)Calls (120 calls/hour)

....................................................................369

Network alarm threshold measurements

CCM Partition Average Duration (under 2 seconds)Percent Succeeded (under 50%)Failed Calls (20 calls)Average Voice QoS (under 60%)Average Packet Loss Ratio (1%)Maximum Packet Loss Ratio (3%)Average Jitter (80ms)Maximum Jitter (120ms)Average Delay (100ms)Maximum Delay (200ms)Call Minutes (360 minutes/hour)Calls (120 calls/hour)

CCM Partition Pair Average Duration (under 2 seconds)Percent Succeeded (under 50%)Failed Calls (20 calls)Average Voice QoS (under 60%)Average Packet Loss Ratio (1%)Maximum Packet Loss Ratio (3%)Average Jitter (80ms)Maximum Jitter (120ms)Average Delay (100ms)Maximum Delay (200ms)Call Minutes (360 minutes/hour)Calls (120 calls/hour)

CCM IP Phone Average Duration (under 2 seconds)Percent Succeeded (under 50%)Failed Calls (20 calls)Average Voice QoS (under 60%)Average Packet Loss Ratio (1%)Maximum Packet Loss Ratio (3%)Average Jitter (80ms)Maximum Jitter (120ms)Average Delay (100ms)Maximum Delay (200ms)Call Minutes (360 minutes/hour)Calls (120 calls/hour)

Avaya Gatekeeper Average Duration (under 2 seconds)Average Voice QoS (under 80%)Average Packet Loss Ratio (1%)Peak Packet Loss Ratio (3%)Average Jitter (40msec)Peak Jitter (80msec)Average Delay (100msec)Peak Delay (200msec)Call Minutes (#)Calls (#)Average MOS (under 3.5)Minimum MOS (under 2.5)


....................................................................370

Avaya Gateway Average Duration (under 2 seconds)Average Voice QoS (under 80%)Average Packet Loss Ratio (1%)Peak Packet Loss Ratio (3%)Average Jitter (40msec)Peak Jitter (80msec)Average Delay (100msec)Peak Delay (200msec)Call Minutes (#)Calls (#)Average MOS (under 3.5)Minimum MOS (under 2.5)

Avaya IP Phone Average Duration (under 2 seconds)Average Voice QoS (under 80%)Average Packet Loss Ratio (1%)Peak Packet Loss Ratio (3%)Average Jitter (40msec)Peak Jitter (80msec)Average Delay (100msec)Peak Delay (200msec)Call Minutes (#)Calls (#)Average MOS (under 3.5)Minimum MOS (under 2.5)

Avaya VMM Average Duration (under 2 seconds)Average Voice QoS (under 80%)Average Packet Loss Ratio (1%)Peak Packet Loss Ratio (3%)Average Jitter (40msec)Peak Jitter (80msec)Average Delay (100msec)Peak Delay (200msec)Call Minutes (#)Calls (#)Average MOS (under 3.5)Minimum MOS (under 2.5)

BroadWorks App Server MCP Resource Alloc Failures (#)SIP Total Transactions (#)Total Attempts (#)Network Origination Attempts (#)Network Termination Attempts (#)NetTerm Attempts Answered (%)User Origination Attempts (#)User Termination Attempts (#)User Term Attempts Answered (%)Average Active Calls (#)Peak Active Calls (#)MCP Resource Alloc Fail Pcnt (25%)


....................................................................371


BroadWorks Media Server Average Ports Used (#)Peak Ports Used (#)No Port Available Errors (#)Peak Conference Ports Used (#)RTP Sessions (#)

BroadWorks Net Server Policy Requests (#)Policy Request Failures (#)Policy Req Failures Percentage (%)SIP Request Failures (#)

VoIP Agent Stats Forward R-factor (above 94, under 75)Forward MOS (above 4.4, under 3.8)Forward Delay (ms)Forward Packet Loss (%)Forward Jitter (ms)Reverse R-factor (above 94, under 75)Reverse MOS (above 4.4, under 3.8)Reverse Delay (ms)Reverse Packet Loss (%)Reverse Jitter (ms)Round Trip Delay (ms)Setup Delay (ms)TearDown Delay (ms)Ring Delay (ms)Number of Invites (count)

HSS Call Server Interface Authentication requests (#)Deregistration status queries (#)Percentage of failed authentications (%)Pct of failed Invite Location queries (%)Pct of failed server assignments (%)Pct of failed status queries (%)Registration status queries (#)Server assignment reg requests (#)Server assignment dereg requests (#)Invite Location queries (#)

HSS App Server Interface AS Registrations (#)Data Requests from AS (#)Data Uploads from AS (#)Failed AS Registrations (%)Failed Notifications to the AS (%)Failed Requests from AS (%)Failed Uploads from AS (%)User Data Notifications to AS (#)

HSS Database Average number of subscribers (#)Number of database transactions (#)Percentage of active subscribers (%)Pct failed database transactions (%)


....................................................................372

Brix SCCP Network Active Test

Conversational MOS (high 4.4, low 3.8)Conversational R-factor (high 94, low 75)Degr Codec (count)Degr Latency (count)Degr Packet Loss (count)Degr Jitter (count)Peak Jitter (count)Average RT Latency (count)Post Dial Delay (count)Post Pickup Delay (count)Average Jitter (count)Percentage of Lost Packets (%)Percentage of Out-of-Order Packets (%)

Brix RTP Network Active Test

Forward Conv MOS (high 4.4, low 3.8)Forward Conv RFact (high 94, low 75) Forward Degr Codec (count)Forward Degr Ltnc (count)Forward Degr Pkt Loss (count)Forward Degr Jitter (count)Peak Forward Jitter (count)Reverse Conv MOS (high 4.4, low 3.8)Reverse Conv RFact (high 94, low 75)Reverse Degr Codec (count)Reverse Degr Ltnc (count)Reverse Degr Pkt Loss (count)Reverse Degr Jitter (count)Peak Reverse Jitter (count)Avg RT Ltnc (count)Avg Forward Jitter (count)Pct Forward Lost Pkts (percent)Pct Forward OO Pkts (percent)Avg Reverse Jitter (count)Pct Reverse Lost Pkts (percent)Pct Reverse OO Pkts (percent)

Brix H323 Service Active Test

Conv MOS (high 4.4, low 3.8)Conv RFact (high 94, low 75) Degr Codec (count)Degr Ltnc (count)Degr Pkt Loss (count)Degr Jitter (count)Post Dial Delay (count)Peak Forward Jitter (count)Avg RT Ltnc (count)Avg Forward Jitter (count)Pct Lost Pkts (percent)Pct OO Pkts (percent)

Router CPU/Buffers


....................................................................373


Lucent Router Peak CPU Utilization (95%) Average CPU Utilization (80%)

Lucent Brick Peak Sessions (count)Average CPU (60%)Peak CPU (75%)Average Cache Memory (80%)Peak Cache Memory (95%)Average Main Memory (80%)Average Packet Memory (80%)Overall Utilization (95%)

Cisco Router Peak Utilization (95%) Minimum Free Memory (Kbytes)Peak Buffer Failures/Hour Peak Buffer No Memory Failures/HourAverage Utilization (80%)

Cisco CPU Peak CPU Utilization (85%)Average CPU Utilization (70%)

Cisco Memory Pool Peak Memory Pool Utilization (85%)Average Memory Pool Utilization (70%)

Cisco CIP CPU Peak CPU Utilization (85%) Peak Memory Utilization (85%) Mem Errors/Sec (20 ups)Average CPU Utilization (70%)Average Memory Utilization (70%)

Nortel Router Peak CPU Utilization (95%) Peak Buffer Utilization (%)Peak Memory Utilization (%) Peak Buffer Failures/HourAverage CPU Utilization (80%)

Redback Router Peak CPU Utilization (95%)Average CPU Utilization (80%)

Enterasys CPU Peak utilization (85%)Average utilization (70%)

Enterasys Storage Peak used storage (90%)Used storage (70%)

Juniper System Peak CPU Utilization (85%)Average CPU Utilization (70%)

Juniper ERX Cards Peak CPU Utilization (90%)Average CPU Utilization (80%)


....................................................................374

Juniper ERX NVS Peak Utilization (95%)Average Utilization (80%)

Juniper Netscreen Average CPU Utilization (80%)Average Memory Utilization (80%)Average Session Utilization (80%)Peak CPU Utilization (95%)Peak Memory Utilization (95%)Peak Session Utilization (95%)Peak Sessions (count)

PSAX CPU Peak CPU Utilization (95%)Average CPU Utilization (80%)

Lucent Core Switch Node Average Memory Utilization (80%)In Octets (under 100 per second)Out Octets (under 100 per second)Average CPU Utilization (80%)

✔

3Com Router Peak Utilization (95%)Average Utilization (80%)

Lucent Core Switch Cards Peak CPU Utilization (90%)Average Memory Utilization (90%)Percentage In Error Cells (15%)Percentage Out Discarded Cells (15%)Average CPU Utilization (90%)

✔

Lucent Access Slot Memory Peak Busy Memory (85 count)Memory Allocation Failures (85 count)Memory Free Failures (85 count)Average Busy Memory (70 count)

✔

Cisco PDSN System A10/A11 Session Failures (count)Active PCFs (count)Established Sessions (count)Maximum PFC Allowed (count)Maximum Sessions Allowed (count)Maximum User Failures (count)Total Average IP Flows (count)

✔

Foundry System Peak CPU Utilization (%)Peak Memory Utilization (%)Average CPU Utilization (%)Average Memory Utilization (%)

UTStarcom FACN Registration failure rate (%)Successful PCF registrations (count)Failed PCF registrations (count)PDSN communication failures (count)

✔


....................................................................375


UTStarcom PDSN-FACN Outstanding calls (count)Average CPU usage (%)Average memory usage (%)Missed heartbeats (count)Percent active calls level (%)Actual active calls (count)

✔

WAN

WAN Circuit MIB II Peak Utilization (95%)Errors (%) Discards (%)Average Utilization (80%)

High Capacity WAN Peak Utilization (95%)Errors (50%)Discards (50%)Average Utilization (80%)

MPLS MIB II Peak Utilization (95%)Errors (50%)Discards (50%)Average Utilization (80%)

Cisco VPN Phase2 Tunnel Dropped Packets (count)Errors (count)Average Utilization (kb/second)

Cisco DS0 Statistics Average DS0 Utilization (80%)Incoming Bit Rate (bps)Outgoing Bit Rate (bps)Incoming Packet Rate (pkts/second)Outgoing Packet Rate (pkts/second)Time DS0 In Use (%)

WAN DS1 Error Peak Error Ratio (60%)Total Violation (200)Average Error Ratio (30%)

WAN DS3 Error Peak Error Ratio (60%)Total Violation (200)Average Error Ratio (30%)

WAN SONET Error Section Peak Error Ratio (30%) Line Peak Error Ratio (80%)Total Line Violation (200 #)Total Section Violation (200 #)Section Average Error Ratio (30%)Line Average Error Ratio (30%)


....................................................................376

RMON WAN Peak Utilization (95%)Errors (%)Average Utilization (80%)

Stratacom Voice Channel Peak Utilization (2000 pps)Average Utilization (1000 pps)Discards (2%)

Stratacom Fast Packet Trunk Peak Utilization (95%)Average Utilization (80%)Dropped Packets (2%) Error Packets (2%)

Juniper M/T MPLS Peak Utilization (95%)Peak LSP Path Changes (5)Peak LSP State Transitions Average MPLS LSP Standby Paths (%)Average MPLS LSP Operational Paths (%)Average Utilization (80%)

Lucent Stinger - ADSL- CAP Perf

Rx Signal (1 off/on)ConnDownUp (100 count)

✔

Lucent Stinger - ADSL - DMT Perf

Rx Signal (1 off/on)ConnDownUp (100 count)

✔

Lucent Stinger - SDSL Perf Rx Signal (1 off/on)ConnDownUp (100 count)

✔

Lucent Access WAN Line Perf

Non-working Channels (70 count)

Lucent Access High Capacity Interface

Average Utilization (95%)Peak Utilization (80%)

Frame Relay

Lucent Core FR DLCI FECNs (under 100 per second)BECNs (under 200 per second)DE Packets (under 200 per second)ODE Packets (uner 200 per second)Average Utilization (90%)

✔

Frame Relay PVC Peak Utilization (150%)Percentage of Frames with FECNs (%)Percentage of Frames with BECNs (%)Average Utilization (80%)

Lucent Frame SPVC Out Utilization (80%)In Utilization (80%)


....................................................................377


RMON Frame Relay Peak Utilization (%)FECN Packet Ratio (%)BECN Packet Ratio (%)Average Utilization (%)

Navis FR Trunk Average Utilization (80%) ✔

Navis FR PVC Average Utilization (80%) ✔

CWM Frame Relay Connection

Average Utilization (80%)

Stratacom Frame Relay Port Peak Utilization (95%)Average Utilization (80%)DE Frames (2%)CRC Frames (2%)

Stratacom Frame Relay Channel

Peak Utilization (95%)Number of frames with FECNs (frames)Number of frames with BECNs (frames)Average Utilization (80%)Discards (2%)

Navis Frame Relay L-Port Trunk

Average Utilization (80%)Drops (5%)Errors (5%)

✔

Navis Frame Relay Circuit Average Utilization (80%)Drops (5%)FECNs (5%)BECNs (5%)DE Utilization (10%)ODE Utilization (10%)

✔

Navis Frame Relay UNI/NNI

Average Utilization (80%)Discards (5%)Errors (5%)

✔

CWM FR Port Average Utilization (80%)

ATM

ATM Trunk Peak Utilization (95%)Average Utilization (80%)Cell loss (%)

ATM PVC Peak Utilization (95%)Average Utilization (80%)Cell loss (%)


....................................................................378

Lucent Access CES CES PVC

Incoming Utilization on A (%)Outgoing Utilization on A (%)Maximum Utilization (%)

✔

Lucent Access CES PVC Percent Dropped on B (%)Percent Tagged on B (%)Incoming Utilization on A (%)Outgoing Utilization on A (%)Maximum Utilization (%)

✔

Lucent Access CES SPVC Percent Dropped on B (%)Percent Tagged on B (%)Incoming Utilization on A (%)Outgoing Utilization on A (%)Maximum Utilization (%)

✔

Lucent Access ATM Interfaces

Peak Utilization (%)Cell Loss (%)Sig Drop Cells (%)ILMI Drop Cells (%)PNNI Drop Cells (%)Average Utilization (%)Sig Incoming Cells (%)Sig Outgoing Cells (%)ILMI Incoming Cells (%)ILMI Outgoing Cells (%)PNNI Incoming Cells (%)PNNI Outgoing Cells (%)

✔

Lucent ATM PVC Total Peak Utilization (95%) Total Average Utilization (80%)

Lucent ATM SPVC Out Utilization (80%)Tagged A (80%)Dropped A (80%)In Utilization (80%)

Navis ATM Trunk Average Utilization (80%) ✔

Navis ATM QoS Trunk Average Utilization (80%) ✔

Navis ATM PVC Average Utilization (80%) ✔

Nortel Router ATM Trunk Peak Utilization (150%)Cell Loss Ratio (30%)Average Utilization (80%)

Nortel Router ATM PVC Peak Utilization (150%)Cell Loss (50%)Average Utilization (80%)

CWM BPX Trunk Average Utilization (80%)


....................................................................379


CWM IGX Trunk Average Utilization (80%)

CWM ASI Connection Average Utilization (80%)

CWM IGX FTP Trunk Average Utilization (80%)

Nortel Passport ATM Trunk Peak Utilization (150%)Cells Discarded (20%)Average Utilization (80%)

Centillion ATM Trunk Peak Utilization (150%)Cell Loss (50%)Average Utilization (80%)

Redback ATM Peak Utilization (95%)Average Utilization (80%)

Xylan ATM Trunk Peak Utilization (80%)Cell Loss Ratio (30%)Average Utilization (80%)

Lucent Core ATM LPort Errors (50%)Discards (5%)Trunk Utilization (80%)Available BW (under 20 bps)Average Utilization (80%)

✔

Lucent Core ATM Trunk Cell Loss Ratio (30%)Errors (30%)Average Utilization (80%)

✔

Lucent Core PVC Cell Loss Ratio (30%)Average Utilization (80%)

✔

Navis ATM Trunk Ext Average Utilization (80%)Errors (5%)Drops (5%)

✔

Navis ATM Logical Port Trunk

Average Utilization (80%)Drops (5%)

✔

Navis ATM PVC Ext V8 Average Utilization (80%)Drops (5%)

✔

Navis ATM PVC Ext Average Utilization (80%)Drops (5%)

✔

Navis ATM Opti Trunk Average Utilization (80%)Drops (5%)

✔

Navis ATM Logical Port UNI/NNI

Average Utilization (80%)Drops (5%)

✔


....................................................................380

Navis ATMoMPLS Trunk Physical Port Incoming Errors (cps)Physical Port Outgoing Discards (cps)Available Bandwidth (under 20 bps)Number of Virtual Circuits (count)Average Utilization (80%)

✔

Juniper M/T ATMoMPLS Trunk

Incoming OAM F4 AIS Cells (%)Outgoing Tail Queue Packet Drops (5%)Trunk Utilization (80%)Average Utilization (80%)

✔

Lucent Access ATM IfVCC Stats

Cell Loss Ratio (30%) ✔

Lucent Access ATM VCC Stats

Cell Loss Ratio (30%) ✔

LAN

LAN Segment MIB-II Peak Utilization (95%) Errors (%)Discards (%)Average Utilization (80%)

High Capacity LAN Peak Utilization (95%)Errors (50%)Discards (50%)Average Utilization (80%)

Lucent Brick Interface Average Utilization (80%)Peak Utilization (95%)Errors (50%)Discards (50%)

WLAN 802.11 Transmitted Frames (%)Transmitted Fragments (%)RTS Failures (%)FCS Errors (%)Failed Frame Transmits (%)Retransmitted Frames (%)Duplicate Frames Received (%)

Ethernet RMON Peak Utilization (60%)Percentage of Packets with Errors (%)Percentage of Packets with Collisions (%)Average Utilization (40%)

Ethernet Hub Peak Utilization (60%) Errors (%)Collisions (%)Average Utilization (40%)


....................................................................381


Token Ring RMON Peak Utilization (95%) Percentage of Packets with Errors (%)Number of Events/Number of Packets (%)Average Utilization (80%)

Cisco CIP Sub_Channel Peak Utilization (60%)Slow Down Requests (10 ups)Average Utilization (40%)

SMON VLAN Peak Utilization (1000000 bps)Average Utilization (10000 bps)

Foundry Switch Port Utilization

Peak Incoming Utilization (%)Peak Outgoing Utilization (%)Average Incoming Utilization (%)Average Outgoing Utilization (%)Average Discards (%)Average Broadcasts (%)

Extreme Interface Peak Received Utilization (95%)Peak Transmitted Utilization (95%)Average Received Utilization (95%)Average Transmitted Utilization (95%)

SAN

SAN Port Total Throughput (obj/sec)Busy/Rejected Frames (frames/sec)Frame Errors (frames/sec)Port Errors (%)Utilization (%)

SAN Class Class 1 Throughput (frames/sec)Class 2Throughput (frames/sec)Class 3Throughput (frames/sec)Class 1 Busy/rejected Frames (frames/sec)Class 2 Busy/rejected Frames (frames/sec)Class 3 Discards (frames/sec)

McData SAN Port Total Throughput (obj/sec)Busy/Rejected Frames (frames/sec)Frame Errors (frames/sec)Port Errors (%)Utilization (%)


....................................................................382

McData SAN Class Class 1 Throughput (frames/sec)Class 2Throughput (frames/sec)Class 3Throughput (frames/sec)Class 1 Busy/rejected Frames (frames/sec)Class 2 Busy/rejected Frames (frames/sec)Class 3 Discards (frames/sec)

SAN Fabric Incoming Frames (frames/sec)Outgoing Frames (frames/sec)Discards (2 frames/sec)Invalid CRCs (.5/sec)Invalid Transmission Words (.5/sec)Sync Loss (.5/sec)Sig Loss (.5/sec)Sequence Protocol Errors (.5/sec)Delimiter Errors (.5/sec)Address ID Errors (.5/sec)Link Resets (.5/sec)Offine Sequences (.5/sec)Link Failures (.5/sec)Busy/Rejected Frames (2 frames/sec)

Availability/Resp Time

Local-to-Remote Average Availability (%)Average Ping Received (%)Average Response Time (400 ms) Send alarm if no response during polling period (on/off)

Servers

BMC NT Server Errors (10%) Minimum Free Mem (10 bytes)Average CPU Utilization (75%)

BMC UNIX Server Minimum Free Mem (10 bytes)Free Swap (10%)Average CPU Utilization (75%)

Compaq Server File System Utilization (95%)Peak EISA Utilization (%)Peak PCI Utilization (%) Correctable Memory ErrorsAverage Utilization (80%)

Compaq Disk Recoverable Errors Minimum Test Value (under 80)Average Read (per sec) Average Write (per sec)


....................................................................383


Servers (Host MIB) Peak Utilization (95%)Disk Utilization (95%)Disk Allocation Failure (per hour)Average Utilization (80%)

NT Servers (Perf MIB) Average Page Faults (1000 per sec)Minimum Free Memory (bytes)Minimum Free Disk (Mbytes)Average Utilization (80%)

Sun Server Average System Load (4 count)Peak System Load (8 count)Average Memory Utilization (90%)Peak Memory Utilization (98%)Average Swap Utilization (80%(Peak Swap Utilization (95%)

Sun Host Disk Ave Storage Allocation Failures (count)Average Storage Used (%)Average System Number of Users (count)Average System Processes (%)Peak Storage Used (%)Peak System Processes (%)Storage Size (bytes)System Maximum Processes (count)

Sun Solaris Average CPU Idle (%)Average CPU Nice (%)Average CPU System (%)Average CPU Users (%)Average Disk 1 Transfers (%)Average Disk 2 Transfers (%)Average Disk 3 Transfers (%)Average Disk 4 Transfers (%)

System Application App Peak CPU Utilization (90%)Peak Memory Utilization (90%)Average CPU Utilization (80%)Average Memory Utilization (80%)

HSS Server Average CPU utilization (90%)Peak CPU utilization (98%)Average memory utilization (90%)Peak memory utilization (98%)

HSS File System Average file system utilization (90%)Peak file system utilization (95%)

Windows Server Metrics CPU Privileged Utilization (50%)CPU Utilization (95%)Free Disk Space (under 5%)Used Page File (80%)


....................................................................384

Windows Process Metrics Process CPU Usage (95%)

Network Services

Cisco QoS Classmap Peak Drops (90%)Peak Pre Utilization (90%)Peak Post Utilization (90%)Average Drops (50%)Average Pre Utilization (50%)Average Post Utilization (50%)

Cisco QoS Match Statement Peak Pre Utilization (90%)Average Pre Utilization (50%)Average Pre Packets (pps)

Cisco QoS Police Peak Exceeded Utilization (90%)Peak Conformed Utilization (90%)Peak Violated Utilization (90%)Average Exceeded Utilization (50%)Average Conformed Utilization (50%)Average Violated Utilization (50%)

Cisco QoS Queueing Peak Discards (90%)Average Discards (50%)Average Current Queue Size (octets)Average Discard Packets (pps)

Cisco QoS Traffic Shaping Peak Drops (70%)Peak Delays (70%)Average Drops (50%)Average Delays (50%)Average Active (50%)

Cisco QoS RED Peak Utilization (90%)Tail Drops (70%)Random Drops (70%)Queue Size (count)Average Utilization (50%)

Cisco CAR Peak Utilization (90%)Drops (70%)Maximum Burst (bytes)Average Utilization (50%)

Cisco VPN VRF Peak Configured VRFs (#)Peak Active VRFs (#)Peak Connected Interfaces (#)Average Configured VRFs (#)Average Active VRFs (#)Average Connected Interfaces (#)


....................................................................385


QIP DHCP Address Capacity

Addresses Unused (under 10%)Addresses Used (70%)Addresses Unavailable (70%)

QIP DHCP Transactions Service Available (under 100%)Peak Response Time (100 ms)Average Response Time (50 ms)

QIP DNS Transactions Service Available (under 100%)Peak Response Time (100 ms)Average Response Time (50 ms)

QIP DNS Errors Peak Received Errors (#)Peak Dynamic Update (#)Peak Sent Errors (#)Average Received Errors (#)Average Dynamic Update (#)Average Sent Errors (#)

QIP DNS Query Peak Queries (#)Peak Inverse Queries (#)Average Queries (#)Average Inverse Queries (#)

Alvarion WiMAX Services Average Connection Delay (ms)Average Throughput (KB/sec)Committed Burst Performance (%)Data Loss Indicator (%)Extra Burst Performance (%)Maximum Delay (ms)Standard Deviation Delay (ms)

Cisco SAA/IP SLA

SAA/IP SLA DHCP Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

SAA/IP SLA DNS Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

SAA/IP SLA FTP Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

SAA/IP SLA HTTP Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)


....................................................................386

SAA/IP SLA Jitter Backward Jitter (count)Backward Packet Loss (percent)Forward Jitter (count)Forward Packet Loss (percent)RTT Latency (ms)

SAA/IP SLA Ping Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

SAA/IP SLA TCP Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

SAA/IP SLA UDP Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

SAA/IP SLA DLSw Average Availability (%)Average Ping Received (%)Average Response Time (400 ms)

Wireless

CDMA CELL HO Blk due to Pwr Cntrl Ovld (%)HO Blk due to CE and PP Ofl (%)Orig and Term CE and PP Ofl (%)RF Failure Rate (%)Dropped Call Rate (%)CS PO (%)CDMA CCC OVLD (#)

✔

CDMA ECP DLN Processor Occupancy (%)Dropped Call Rate (%)Access Denial Rate (%)

✔

CDMA PAF Paging Channel Occupancy (%)Access Channel Occupancy (%)

✔

CDMA CDN CDN Processor Occupancy (%) ✔

CDMA AP AP IMS Buffer Overload (#)EIN Processor Occupancy (%)AP Processor Occupancy (%)

✔

CDMA CSN Link Node Processor Occupancy (%)Link Node Queue High-Water (%)

✔

Other Types


....................................................................387


MIB-II IP Totals Errors (50%)In Discards (5%) Missed (10%)Out Discards (5%)

Cisco DSP Card Stats Peak Utilization (80%/5%)Maximum Channels (under 5 count) Average Utilization (80%/5%)

Cisco DSP Status Average Utilization (85%/10%) Percentage Dangling Channels (15%)DSP Alarm Count (85 count) Average Availability (under 80%)

Cisco FW Connections Average Connections (count)Peak Connections (count)

Cisco Access Server Peak CMP Active DS0s (#)Rejected Calls (30%)Calls Cleared Abnormally (30%)No Resources (30%)Average CPM Active DS0s (#)Time B Channel in Use (80%)Voice B Channel in Use (80%)

Juniper M/T DCU Average Utilization (80%)Peak Utilization (95%)Average Packets (pps)Peak Packets (pps)

Juniper M/T COS Peak Utilization (95%)Average Utilization (80%)Percentage Bytes Dropped (20%)Percentage Packets Dropped (20%)

Juniper M/T COS I/F Q Percentage Packets Dropped (20%)Percentage Bytes Dropped (20%)

Juniper ERX Traffic Class Peak Utilization (95%)Average Utilization (80%)Percentage of Bytes Dropped (20%)Percentage of Packets Dropped (20%)

Juniper ERX Subscriber Peak Subscriber License Usage (85%)Subscriber Deny Responses (50%)Subscriber Error Responses (50%)

MIB-II ICMP Data Errors (50%) Unreached (5%) Quenches (10%)


....................................................................388

Catalyst Bandwidth Utilization

Peak Utilization (95%)Average Utilization (95%)

Cisco Catalyst PS and FAN Status

Ps1 Major (1 count)Ps1 Minor (1 count)Ps1 Other (1 count)Ps2 Major (1 count)Ps2 Minor (1 count)Ps2 Other (1 count)Fan Major (1 count)Fan Minor (1 count)Fan Other (1 count)

Cisco Temperature Alarm Status

Temperature High (1 count)Temperature Critical (1 count)

Lucent Router - Ethernet In Errors (95%)Out Errors (95%) Out No Carrier (count)Out Carrier Loss (count)Out Jabber TImeouts (count) Out Collisions (count)In Collisions (count) Total In Frames (count)

Cisco Call Manager Average Registered (count)Average Unregistered (count)Average Rejected (count)

AAA System Authentication and Accounting

Auth Requests Rate (Requests/second)Percentage of Auth Responses (%)Percentage of Auth Accepts (%)Percentage of Auth Rejects (%)Percentage of Auth Errors (%)Acct Requests Rate (Requests/second)Percentage of Acct Responses (%)Percentage of Acct Errors (%)

Checkpoint Average Connections (count)Average Hmem Utilization (80%)Average Kmem (MB)Peak Connections (count)Peak Hmem Utilization (95%)Peak Kmem (MB)

Checkpoint Interface Average Accepted Packets (count)Average Dropped Packets (count)Average Dropped Packets Percentage (%)Peak Accepted Packets (count)Peak Dropped Packets Percentage (%)


....................................................................389


Cisco PDSN PCF Stats Errors Total Session (count)Historical Maximum Connections (count)Total PCF Sessions (count)

✔

Cisco PDSN Registrations A11 Registrations Accepted (count)A11 Registrations Denied (count)A11 Registrations Discarded (count)A11 Registrations Received (count)Out-of-Resource Failures (count)Total Registration Failures (count)

✔

Cisco PDSN PPP Stats Active PPP Connections (count)Failed PPP Connections (count)PPP Auth-Stage Conn Failures (count)PPP Conn Init Requests Sent (count)PPP Connections Established (count)PPP IPCP-Stage Conn Failures (count)PPP LCP-Stage Conn Failures (count)Premature Term PPP Negotiations (count)

✔

iMerge Resource Utilization Active CPU Utilization Average (80%)Active CPU Utilization Peak (90%)Pri DSP Pool CPU Utilization Ave (80%)Pri DSP Pool CPU Utilization Peak (90%)Sec DSP Pool CPU Utilization Ave (80%)Sec DSP Pool CPU Utilization Peak (90%)

iMerge Traffic Total Call Attempts (65536 count)Pct Calls Failed—No Resources (20%)Percentage Call Origination Failures (20%)Percentage Call Termination Failures(20%)

iMerge QoS System Average Delay (500 count)Percent Packets Lost CPE to iMerge (20%)Percent Packets Lost iMerge to CPE (20%)Average Jitter CPE to iMerge (50 count)Average Jitter iMerge to CPE (50 count)Peak Jitter CPE to iMerge (50 count)Peak Jitter iMerge to CPE (50count)Discarded Packets (20 count)


....................................................................390

iMerge QoS PNG Average Delay (500 count)Percent Packets Lost CPE to iMerge (20%)Percent Packets Lost iMerge to CPE (20%)Average Jitter CPE to iMerge (50 count)Average Jitter iMerge to CPE (50 count)Peak Jitter CPE to iMerge (50 count)Peak Jitter iMerge to CPE (50 count)Discarded Packets (20 count)

iMerge QoS NonPNG

Average Delay (500 count)Percent Packets Lost CPE to iMerge (20%)Percent Packets Lost iMerge to CPE (20%)Average Jitter CPE to iMerge (50 count)Average Jitter iMerge to CPE (50 count)Peak Jitter CPE to iMerge (50 count)Peak Jitter iMerge to CPE (50 count)Discarded Packets (20 count)

iMerge QoS Study Group Average Delay (500 count)Percent Packets Lost CPE to iMerge (20%)Percent Packets Lost iMerge to CPE (20%)Average Jitter CPE to iMerge (50 count)Average Jitter iMerge to CPE (50 count)Peak Jitter CPE to iMerge (50 count)Peak Jitter iMerge to CPE (50 count)Discarded Packets (20 count)

Lucent Access Call Stats Analog Calls in Progress (cps)Digital Calls in Progress (cps)Frame Relay Calls in Progress (cps)Peak Analog Calls (cps)Peak Digital Calls (cps)Peak Frame Relay Calls (cps)High Water Mark Channels Used (count)

Lucent Access Modem Stats Percentage of Bad Modems (50%)Average Available Modems (count)Average Busy Modems (count)Average Suspect Modems (count)Average Disabled Modems (count)Average Dead Modems (count)

Lucent Access Slot Stats Percentage of Slot Uptime (under 50%)


....................................................................391


UTStarcom NMC NAS chassis temperature (count)NMC instability rate (%)Dynamic RAM capacity (count)Non-volatile RAM capacity (count)Failed NMC power-up tests (count)

✔

CDMA 1EV-D0 TP TP Dropped Packets (#) ✔

CDMA NAR Trunk Group Trunk Group Occupancy (%)Trunk Group Percent Overflow (%)

✔

CDMA NAR Sig Lnk Set Pct Time Link Unavailable (%) ✔

CDMA NAR Signal Ntwk Pct Isolated Signaling Pt (%) ✔

CDMA NAR Acc Delay Cells Blocked During AM Overload (#)Percent Tone Decoder Delay (%)

✔

CDMA NAR Tone Deco Tone Decoder Percent Overflow (%)Tone Decoder Mean Holding Time (#)

✔

CDMA NAR Mod Message MMP Receiver-Not-Ready Messages (#) ✔

CDMA NAR Msg Handler Base Level Loop Cycles (#) ✔

CDMA NAR Msg Sw Cntl MSC Base-Level Cycles (#) ✔

CDMA NAR MTP Pt Code Point Code Unavailability (#) ✔

CDMA NAR MTP Sig Lnk Duration of Unavail Signal Link (#) ✔

CDMA NAR Sw Mod Perf SM Processor PCT Occupancy (%) ✔

CDMA NAR Frm Pro Hnd Bandwidth Transmit Pct Occupancy (%)Bandwidth Receive Pct Occupancy (%)

✔

CDMA NAR PSU Ch Grp Percent Time in Overload (%) ✔

CDMA 1XEV-DO HDR PAF

Avg Active Connects (#) ✔

CDMA ISDN User Part Total Unsuccessful ISUP Attempts (#) ✔

CDMA MSC KPI Originating Requests Received (#) ✔

CDMA Proto Handler Percent Time in Overload (%) ✔

CDMA Signaling Link Signaling Link Unavailability (#) ✔

CDMA Signal Link Set Sig Link Set Unavailability (#) ✔

CDMA Switching Mod SM Processor Pct Occupancy (%) ✔


....................................................................392

CDMA Tone Decoder Tone Decoder Mean Holding Time (#) ✔

CDMA Trunk Group Trunk Group Percent Occupancy (%) ✔

CDMA Wireless Voco Vocoder Total Usage (%) ✔

CDMA NAR Com Module Com Module Processor Occupancy (%) ✔

CDMA NAR UConf Cts 3-port Conf Circuit Pct Ovfl (%)6-port Conf Circuit Pct Ovfl (%)3-port Conf Cct Mean Hold Time (#)6-port Conf Cct Mean Hold Time (#)3-port Conf Cct Pct Occupancy (%)6-port Conf Cct Pct Occupancy (%)

✔

CDMA NAR CTS CTS 0 Avc Pct Occ From SM (%)CTS 0 Avg Pct Occ Received (%)CTS 1 Avg Pct Occ From SM (%)CTS 1 Avg Occ Received in SM (%)CTS 0 Max Occ Sent From SM (%)CTS 0 Max Occ Received in SM (%)CTS 1 Max Occ Sent From SM (%)CTS 1 Max Occ Received in SM (%)

✔

CDMA NAR DLTU DLTU Usage (%) ✔

CDMA NAR DNU Sonet DNU-S Traffic Usage (%) ✔

CDMA NAR Hi Sp Trunk Pct Fwd Burst Attempts Blocked (%) ✔


....................................................................393

Overview

Using the System Application MIB to monitor applications

..........................................................................................................................................................................................Overview

Purpose

This section describes how to use the system application MIB to monitor applications in VitalSuite NET.

Contents


Introduction 394

Install the CIAgent on Windows 395

Install the CIAgent on UNIX 397

Determine the applications to monitor on Windows 399

Determine the applications to monitor on UNIX 402

Configure the SAPPApplicationsTable 404

....................................................................394

..........................................................................................................................................................................................Introduction

Monitoring capabilities

The System Application MIB provides a general system view of applications and processes installed on your systems. For example, VitalSuite NET can use the System Application MIB with the Host MIB to obtain CPU and memory usage statistics for important applications you want to monitor.

The System Application MIB monitors the following three types of resources:

• Overall application

• Processes belonging to an installed application

• Processes not belonging to any installed application

Supported versions

VitalSuite NET supports CIAgent versions 15.3 and earlier.

More information

For more information about the System Application MIB (RFC 2287), reference the official SNMP web site at www.snmp.com.

Configuration process

To enable VitalSuite NET to obtain performance statistics from a System Application MIB, follow this process:

1. Install the CIAgent on the system you want to monitor, as described in:

• “Install the CIAgent on Windows”, on page 395.

• “Install the CIAgent on UNIX”, on page 397

2. Determine the applications you want to monitor, and configure CIAgent to find those applications, as described in:

• “Determine the applications to monitor on Windows”, on page 399.

• “Determine the applications to monitor on UNIX”, on page 402

3. Configure the SAPPApplicationsTable with the names of the applications you want to monitor, as described in “Configure the SAPPApplicationsTable”, on page 404.

4. Run a device discovery, as described in the VitalSuite Performance Management Software Administrator’s Guide.

....................................................................395

Install the CIAgent on Windows

..........................................................................................................................................................................................Install the CIAgent on Windows

When to use

Use this procedure to install the CIAgent on a Windows server.

The CIAgent is a secure, standards-based agent that supports SNMP versions 1, 2, and 3 and comes bundled with the System-Level Application MIB.

Before you begin

Make sure that you understand the general configuration process for enabling VitalSuite NET to use a System Application MIB. This process is described in “Introduction”, on page 394.

Related information


Procedure

To install the CIAgent on Windows:

...........................................................................................................................................................................

1 Obtain a CIAgent from SNMP Research International, Inc. at www.snmp.com.

...........................................................................................................................................................................

2 Ensure that the Microsoft SNMP Service is installed on the system you want to monitor, as follows:

a. Open the Windows Control Panel.

b. Select Network.

c. On the Services tab, verify that SNMP Service is listed. If the SNMP Service is listed, proceed to Step 3. If the SNMP Service is not listed, continue with the following steps:

d. In the Services tab of the Network Window, click Add.

Result: The Select Network Service window appears.

e. Select SNMP Service, then click OK.

Result: A window asks for the location of your Windows files.

f. Provide the location of your Windows files, then click Continue.

Result: The Microsoft SNMP Properties window appears.

g. Provide SNMP information as required at your site, then click OK.

h. Click Close in the Network window.

i. Restart your computer, if prompted.

....................................................................396

...........................................................................................................................................................................

3 Ensure the Microsoft SNMP Service is deactivated on the system you want to monitor, as follows:

a. Open the Windows Control Panel.

b. Select Services.

c. Select SNMP from the Service list, then click Stop. Click Yes if you are prompted to verify whether you want to stop the SNMP Service.

d. Click Startup.

Result: The Service window opens.

e. Select the Manual Startup Type, then click OK.

f. In the Services window, click Close.

Important! Installing the Microsoft SNMP Service alters the Windows Service Pack. If you installed the SNMP Service, you must reinstall the Windows Service Pack. Obtain the latest version of the Windows Service Pack from Microsoft.

...........................................................................................................................................................................

4 Install the CIAgent on the system you want to monitor, according to the instructions provided by SNMP Research International.

...........................................................................................................................................................................

5 Verify the SNMP manager and SNMP agent can communicate, as follows:

a. Open a DOS window.

b. Navigate to the <CIAgent_install_directory>\bin folder.

c. Enter the following three commands to ensure the SNMP manager and SNMP agent can communicate. .\getmany -v1 localhost public iso.\getmany -v2c localhost public iso.\getmany -v3 localhost CharlieDChief iso

Result: With each successful command, the MIB variables in the agent will scroll on the DOS window.

d. When prompted for an authentication password, enter abracadabra. When prompted for a privacy password, enter alakazam.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................397

Install the CIAgent on UNIX

..........................................................................................................................................................................................Install the CIAgent on UNIX

When to use

Use this procedure to install the CIAgent on a UNIX server.

The CIAgent is a secure, standards-based agent that supports SNMP versions 1, 2, and 3 and comes bundled with the System-Level Application MIB.

Before you begin

Make sure that you understand the general configuration process for enabling VitalSuite NET to use a System Application MIB. This process is described in “Introduction”, on page 394.

Related information


Procedure

To install the CIAgent on UNIX:

...........................................................................................................................................................................

1 Obtain a CIAgent from SNMP Research International, Inc. at www.snmp.com.

...........................................................................................................................................................................

2 Deactivate the native SNMP agents on the Unix system, as follows:

a. Enter the following to determine whether any SNMP processes are running:ps -ef | grep snmp

b. If the command returns any processes, use the kill command for each process.kill -9 <process_ID>

...........................................................................................................................................................................

3 Install the CIAgent on the system you want to monitor, according to the instructions provided by SNMP Research International.

....................................................................398

...........................................................................................................................................................................

4 Verify the SNMP manager and SNMP agent can communicate:

a. Navigate to <CIAgent_install_directory>/bin.

b. Enter the following three commands to ensure the SNMP manager and SNMP agent can communicate. getmany -v1 localhost public isogetmany -v2c localhost public isogetmany -v3 localhost CharlieDChief iso

Result: With each successful command, the MIB variables in the agent will scroll in the terminal window.

c. When prompted for an authentication password, enter abracadabra. When prompted for a privacy password, enter alakazam.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................399

Determine the applications to monitor on Windows

..........................................................................................................................................................................................Determine the applications to monitor on Windows

When to use

Use this procedure to view the unique names of the applications you want to monitor.

To view the applications on a Windows system, you must manually browse the directories to determine which executable files you want to monitor. For each application, you must add information to the sappagt.cnf file, found in the CIAgent installation directory.

Before you begin

Make sure that you have installed the CIAgent, as described in “Install the CIAgent on Windows”, on page 395.

Related information

For more information about enabling VitalSuite NET to use the System Application MIB, refer to “Introduction”, on page 394.

Procedure

To configure a list of applications on your Windows system:

...........................................................................................................................................................................

1 Log into the system containing the applications you want to monitor.

...........................................................................................................................................................................

2 Use Windows Explorer to locate the executable files for the applications you want to monitor.

...........................................................................................................................................................................

3 Note the full paths to the executable files.

...........................................................................................................................................................................

4 On your VitalSuite NET system, use a text editor to open the \etc\srconf\agt\sappagt.cnf file.

...........................................................................................................................................................................

5 Under the commented lines of the sysApplInstallPkgEntry section of the sappagt.cnf file, add the following line for each application you want to monitor, where <ID> is a sequential number used to order the application list, <app_name> is the name of the application executable (with no extension), and <app_path> is the path to the application executable:

sysApplInstallPkgEntry <ID>u <app_name> <app_name> “Version 1.0” - 00000000 <app_path>

....................................................................400

Example

For example, if you want to monitor Microsoft SQL Server, Internet Explorer, and Apache Web server, the sysApplInstallPkgEntry section of the sappagt.cnf file would appear similar to the following:

# Entry type: sysApplInstallPkgEntry# Entry format:# sysApplInstallPkgIndex (unsigned)# sysApplInstallPkgManufacturer (text)# sysApplInstallPkgProductName (text)# sysApplInstallPkgVersion (text)# sysApplInstallPkgSerialNumber (text)# sysApplInstallPkgDate (text)# sysApplInstallPkgLocation (text)sysApplInstallPkgEntry 1u sqlservr sqlservr "Version 1.0" - 00000000 \ “C:\Program Files\Microsoft SQL Server\Mssql\Binn”sysApplInstallPkgEntry 2u iexplore iexplore "Version 1.0" - 00000000 \ “C:\PROGRAM Files\Plus!\Microsoft Internet”sysApplInstallPkgEntry 3u apache apache "Version 1.0" - 00000000 \ “C:\Program Files\VSCommon\Apache”

...........................................................................................................................................................................

6 Under the commented lines of the sysApplInstallElmtEntry section of the sappagt.cnf file, add the following line for each application you want to monitor, where <ID> is the same sequential number used for the application in the sysApplInstallPkgEntry section, <app_name> is the name of the application executable (with the .exe extension), and <app_path> is the path to the application executable:

sysApplInstallElmtEntry <ID>u <app_name> 5 00 <app_path> 0u 100u 80 00 0u 100u <ID>u

Example

Following the example in step 5, the sysApplInstallElmtEntry section of the sappagt.cnf file would appear similar to the following:

# Entry type: sysApplInstallElmtEntry# Entry format:# sysApplInstallElmtIndex (unsigned)# sysApplInstallElmtName (text)# sysApplInstallElmtType (integer)# sysApplInstallElmtDate (text)# sysApplInstallElmtPath (text)# sysApplInstallElmtSizeHigh (unsigned)# sysApplInstallElmtSizeLow (unsigned)# sysApplInstallElmtRole (bits)# sysApplInstallElmtModifyDate (text)# sysApplInstallElmtCurSizeHigh (unsigned)# sysApplInstallElmtCurSizeLow (unsigned)# sysApplInstallPkgIndex (unsigned)sysApplInstallElmtEntry 1u sqlservr.exe 5 00 “C:\Program Files\Microsoft SQL Server\Mssql\Binn” 0u 100u 80 00 0u 100u 1usysApplInstallElmtEntry 2u iexplore.exe 5 00 “C:\PROGRAM Files\Plus!\MICROSOFT Internet”

....................................................................401

Determine the applications to monitor on Windows

0u 100u 80 00 0u 100u 2usysApplInstallElmtEntry 3u apache.exe 5 00 “C:\Program Files\VSCommon\Apache” 0u 100u 80 00 0u 100u 3u

...........................................................................................................................................................................

7 Save and close the sappagt.cnf file.

...........................................................................................................................................................................

8 Restart the computer.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................402

..........................................................................................................................................................................................Determine the applications to monitor on UNIX

When to use

Use this procedure to view the unique names of the applications you want to monitor.

To view a list of application names on UNIX, use the snmpwalk command. This displays a list of all applications running on your Unix system that match a specified OID.

Before you begin

Make sure that you have installed the CIAgent, as described in “Install the CIAgent on UNIX”, on page 397.

Related information


Procedure

To create a list of applications on your Unix system:

...........................................................................................................................................................................

1 Log into the system containing the applications you want to monitor.

...........................................................................................................................................................................

2 At a command prompt, enter the following:

snmpwalk <server name or address> <community string> .1.3.6.1.2.1.54.1.1.1.1.3

where <server name> is either the hostname or IP address of the system and <community string> is the password for the SNMP agent, such as public.

Result: A list of all applications and associated processes displays.

Important! To make it easier to browse through this list, create a text file of the output as shown in this example: snmpwalk <server name> <community string> .1.3.6.1.2.1.54.1.1.1.1.3 >applist.txt

....................................................................403

Determine the applications to monitor on UNIX

...........................................................................................................................................................................

3 Write down the names of the applications you want to monitor.

Additional information: The unique name of each application appears after the OID. For example, you would note Netscape Communicator if you wanted to monitor the following application:

.iso.org.dod.internet.mgmt.mib.54.1.1.1.1.3.60 = “Netscape Communicator”

...........................................................................................................................................................................E N D O F S T E P S

....................................................................404

..........................................................................................................................................................................................Configure the SAPPApplicationsTable

When to use

Use this procedure to configure the SAPPApplicationsTable in your VitalSuite NET database to include the unique name of each application you want to monitor. VitalSuite NET only checks the SAPPApplicationsTable in the Polling server database for these applications.

Before you begin

Make sure you have done the following:

• Installed the CIAgent

• Determined the applications to monitor

Important! When connecting to the VitalSuite NET databases, log in using the “vnmdba” account to access the Master and Reporting servers, the “vnadba” to access the Aggregation server, and the “vnpdba” account to access the Polling servers. Other accounts will not allow you to modify the database tables. If you need the password to the “vnmdba”, “vnadba”, or “vnpdba” accounts, contact Lucent technical support.

Related information


Procedure

To configure the SAPPApplicationsTable:

...........................................................................................................................................................................

1 On the machine running the VitalSuite NET Polling server, connect to the VNPoller database using an SQL tool.

...........................................................................................................................................................................

2 Open the SAPPApplicationsTable.

....................................................................405

Configure the SAPPApplicationsTable

...........................................................................................................................................................................

3 Fill in the fields described in the following table:

Sample SAPPApplications table values

For example, you might modify the SAPPApplicationsTable for Microsoft SQL Server, Internet Explorer, and Apache Web server as follows:

...........................................................................................................................................................................

4 Update the SAPPApplicationsTable in the VNMaster and VNAggr databases with the same applications you entered in the VNPoller database.

Important! This step is not required because VitalSuite NET only checks the SAPPApplicationsTable in the VNPoller database. However, it is recommended you keep your databases consistent to minimize confusion.

Your system is now ready for device discovery, as described in Discovering Network Devices and Resources in the VitalSuite Performance Management Software Administrator’s Guide.

...........................................................................................................................................................................E N D O F S T E P S

Field Description

AppName Any name that helps you identify the application

AppNameWildcard The unique name of the application. You can use a wildcard (*) to truncate this name, such as entering “Netscape Commun*” for Netscape Communicator. However, each application must have a unique name in this field.You must use a regular expression for the AppNameWildcard field. Use literal characters when possible. Be aware that special characters perform various tasks in a regular expression. Avoid the following quoted characters unless you intend to make use of their special syntax: “.“, “*”, “?”, “+”, “(“, “)”, “{“, “}”, “[“, “]”, “^”, “$”, and “\”. If any of these characters are used improperly, VitalSuite NET might not discover the applications and might display a parse error in the device log.Do not use a wildcard that allows VitalSuite NET to discover multiple applications. For example, if you have more than one application that begins with the letters “sql” (such as sqlagent, sqlmangr, and sqlservr), do not use “sql*” because VitalSuite NET will assign the same name to all resources that match the specified name.

AppName AppNameWildcard

MS SQL Server sqlservr*

IExplorer iexplore*

Apache apache*

....................................................................406

RMON2 flow limits

..........................................................................................................................................................................................Overview

Purpose

This section describes RMON2 flow limits and how to change the default flow limits used by VitalSuite NET.

Contents


Introduction to RMON2 flow limits 407

Change the RMON2 flow limits used by VitalSuite NET 408

Example commands for changing RMON2 flow limits 410

....................................................................407

Introduction to RMON2 flow limits

..........................................................................................................................................................................................Introduction to RMON2 flow limits

Background

By default, VitalSuite NET is configured to stop collecting RMON2 traffic flows once a pre-configured limit is reached in the VitalSuite NET database. The reason for the limitation is that collecting RMON2 traffic flows is processor-intensive and can severely impair VitalSuite NET performance if the default limits are exceeded.

In VitalSuite NET, you can change the default limits by modifying the VitalSuite NET Polling server database.

Important! Be aware that changing the default RMON2 flow limits can compromise VitalSuite NET system performance.

Default limits

The default configuration is for VitalSuite NET to stop collecting RMON2 traffic flow data when either of the following limits is reached:

• Number of rows VitalSuite NET downloads from the alMatrixTopNTable on the RMON2 device exceeds 1,000.

• (average octets per flow) / (octects in latest flow) exceeds 100.

In other words, by default VitalSuite NET stops downloading flows once the octets in the latest flow are less than 1% of the average octets of the flows downloaded so far. VitalSuite NET downloads a minimum of 10 rows before calculating this ratio.

....................................................................408

..........................................................................................................................................................................................Change the RMON2 flow limits used by VitalSuite NET

When to use

Use this procedure to change the RMON2 flow limits used by VitalSuite NET.

Before you begin

Identify the VitalSuite NET Polling server responsible for collecting the RMON2 traffic flows you want to change.

Related information

For more information about changing RMON2 flow limits, refer to:

• “Introduction to RMON2 flow limits”, on page 407.

• “Example commands for changing RMON2 flow limits”, on page 410.

Procedure

To change the default RMON2 flow limits:

...........................................................................................................................................................................

1 On the VitalSuite NET Polling server responsible for collecting RMON2 traffic flows, open a database editor (like Query Analyzer on Windows).

...........................................................................................................................................................................

2 Make sure the VitalSuite NET Polling server database is selected in your database editor.

...........................................................................................................................................................................

3 Run the following command to change the default RMON2 flow limit:insert into collectorargstable values ('tmflowcollector' , '<argument>')

where <argument> can be any of the options described in “Arguments for the RMON2 flow limits command”, on page 409.

....................................................................409

Change the RMON2 flow limits used by VitalSuite NET

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

Arguments for the RMON2 flow limits command

.The following table lists the arguments associated with the command used to limit the RMON2 flow limits.

If you want to... Then...

Wait for the new limits to take effect

Do nothing. The new flow limits will automatically take effect after 1am when the RMON2 collector restarts.

Have the new limits take effect immediately and do not mind having a gap in data for all your resources

Do the following:1. Run the following command:stopcollectors tmflowcollector2. Wait at least 10 minutes for the collector to automatically restart.

Result: The new limits take effect once the RMON2 collector is back up and running.

Argument Description

-ccutoff <value> Sets the number of rows VitalSuite NET can download from the alMatrixTopNTable on the RMON2 device. Each row represents a traffic flow.

-cratio <value> Stops VitalSuite NET from downloading additional rows from the alMatrixTopNTable on the RMON2 device once the following equation exceeds the specified cratio value:(average octets per flow) / (octects in latest flow) where (average octets per flow) equals the average number of octets for the downloaded flows so far. VitalSuite NET automatically downloads a minimum of 10 rows (flows) to determine the average octets per flow.The largest octet counts are downloaded first. This means the data downloaded after the default 1% cratio threshold may not be of high importance.

-log 1 Turns on logging to the VNP<yyyymmdd>.log file. Only turn on logging for debug purposes when you need to verify that VitalSuite NET has correctly stopped downloading data for RMON2 flow limits once the specified threshold is reached. For example, if VitalSuite NET encounters a cutoff limit, the log file displays an entry such as:<date> <time> tmflow: <resource-name> cutoff at row <n1>Logging is turned off by default. If you have turned on logging and later want to turn it off, use the following argument: -log 0

....................................................................410

..........................................................................................................................................................................................Example commands for changing RMON2 flow limits

Purpose

This topic provides two examples for limiting the RMON2 flow limits.

Example 1

In this example, logging to the VNPyyyymmdd.log file has been enabled and the cutoff limit has been increased to 10,010. This means that VitalSuite NET can download up to 10,010 traffic flows instead of the default 1,000.

insert into collectorargstable values ('tmflowcollector' , '-ccutoff 10010 -log 1')

Example 2

In this example, the cutoff ratio occurs when at least ten flows have been downloaded and the last flow is less than half the running average octects per flow. This is the smallest realistic value of cratio that can be used.

insert into collectorargstable values (‘tmflowcollector’, ‘ –cratio 2’)

....................................................................411

Overview

Tivoli integration

..........................................................................................................................................................................................Overview

Purpose

This section describes how to configure Tivoli NetView to run VitalSuite NET.

Contents


Introduction 412

Configure Tivoli to launch VitalSuite NET from a pre-defined server 413

Configure Tivoli to launch VitalSuite NET from a selected server 415

....................................................................412

..........................................................................................................................................................................................Introduction

Purpose

This topic provides an overview of the Tivoli NetView integration which allows VitalSuite NET to be opened from the Tivoli NetView program.

Background

Tivoli NetView is a network monitoring software program that can discover the network and resources. The following are 2 ways you can open VitalSuite NET from the Tivoli NetView tool menu:

• Configuring the configuration file to open VitalSuite NET from a pre-defined server, as described in “Configure Tivoli to launch VitalSuite NET from a pre-defined server”, on page 413.

• Configuring the configuration file to open VitalSuite NET from a selected server, as described in “Configure Tivoli to launch VitalSuite NET from a selected server”, on page 415.

Definition of a pre-defined server

A pre-defined server is a server that has the name or IP address imbedded in the configuration file.

Definition of a selected server

A selected server is any VitalSuite NET server that has been discovered by Tivoli NetView.

Included files

Included with the Tivoli/VitalSuite NET integration package are the following files under the Tivoli directory:

File name Description

NetViewConfigForVN.txt Used to configure NetView to receive VitalSuite NET traps.

VitalNetTrapSNMPV2.mib Used to configure NetView to receive VitalSuite NET traps.

vnetconfig Used as a template to setup multiple VitalSuite NET server definitions each with different logins and passwords. When configuring the vnetconfig file, you also have the option to present the user with the standard VitalSuite NET login screen by removing the username and password in the configuration file.

....................................................................413

Configure Tivoli to launch VitalSuite NET from a pre-defined server

..........................................................................................................................................................................................Configure Tivoli to launch VitalSuite NET from a pre-defined server

When to use

Use this procedure to configure Tivoli to launch VitalSuite NET from a pre-defined server. A pre-defined server is a server that has the name or IP address imbedded in the configuration file.

Before you begin

Make sure that you have the file called vnetconfig, that is located on the VitalSuite NET CD in a top level directory named Tivoli.

Related information

For more information on how to use VitalSuite NET refer to the VitalSuite Network Performance Management Software User’s Guide.

Procedure

...........................................................................................................................................................................

1 Create a new directory named vnet inside the NetView registration folder.

Example: \usr\ov\registration\c\vnet

...........................................................................................................................................................................

2 Copy the file, vnetconfig, into the newly created folder.

...........................................................................................................................................................................

3 Open vnetconfig using an editor.

Important! If you are using UNIX, the file vnetconfig should comply with UNIX directory formats.

...........................................................................................................................................................................

4 Look for the following line in the vnetconfig file:Command ‘C:\\Program Files\\Internet Explorer\\IEXPLORE.EXE http://<SERVER>/cgi-bin/vslogin.exe?vsuser=<USERNAME>&password=<PASSWORD>’;

....................................................................414

...........................................................................................................................................................................

5 Make the following changes:

a. Change the entry <SERVER> to the name or IP address of the VitalSuite NET server to be launched from Tivoli NetView.

b. Change the entry <USERNAME> to the login VitalSuite NET username.

c. Change the entry <PASSWORD> to the password for the specified login VitalSuite NET username.

Important! If you do not want to place the password into a text file, then remove everything on the line from /cgi-bin up to but not including the final quote. This will bring up the standard VitalSuite NET login page when the menu selections are accessed.

...........................................................................................................................................................................

6 Save the file.

...........................................................................................................................................................................

7 Open the Tivoli NetView program.

Result: The option to launch a pre-defined VitalSuite NET server is available under the Tivoli NetView tools menu.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................415

Configure Tivoli to launch VitalSuite NET from a selected server

..........................................................................................................................................................................................Configure Tivoli to launch VitalSuite NET from a selected server

When to use

Use this procedure to configure Tivoli to launch VitalSuite NET from a selected server. A selected server is any VitalSuite NET server that has been discovered by Tivoli NetView.

Before you begin

Make sure that you have the file called vnetconfig, that is located on the VitalSuite NET CD in a top level directory named Tivoli.

Related information

For more information on how to use VitalSuite NET refer to the VitalSuite Network Performance Management Software User’s Guide.

Procedure

...........................................................................................................................................................................

1 Create a new directory named vnet inside the NetView registration folder.

Example: /usr/ov/registration/c/vnet

...........................................................................................................................................................................

2 Copy the file, vnetconfig, into the newly created folder.

...........................................................................................................................................................................

3 Open vnetconfig using an editor.

Important! If you are using UNIX, the file vnetconfig should comply with UNIX directory formats.

...........................................................................................................................................................................

4 Look for the following line in the vnetconfig file:Command ‘C:\\Program Files\\Internet Explorer\\IEXPLORE.EXE http://${OVWSelection1}/cgi-bin/vslogin.exe?vsuser=<USERNAME>&password=<PASSWORD>’;

...........................................................................................................................................................................

5 Make the following changes::

a. Change the entry <USERNAME> to the login VitalSuite NET username.

b. Change the entry <PASSWORD> to the password for the specified login VitalSuite NET username.

Important! If you do not want to place the password into a text file, then remove everything on the line from /cgi-bin up to but not including the final quote. This will bring up the standard VitalSuite NET login page when the menu selections are accessed.

....................................................................416

...........................................................................................................................................................................

6 Save the file.

...........................................................................................................................................................................

7 Open the Tivoli NetView program.

Result: The option to launch a selected VitalSuite NET server is available under the Tivoli NetView tools menu.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................417

Overview

Miscellaneous notes

..........................................................................................................................................................................................Overview

Purpose

This section describes common issues with NavisXtend and provides the commands to properly shutdown VitalSuite NET UNIX servers.

Contents


Common issues and resolutions with NavisXtend 418

Shutdown commands for VitalSuite NET UNIX servers 420

Aggregation Editor utility 421

Change the resource limit in My Reports for VitalSuite NET on Windows

423

Change the resource limit in My Reports for VitalSuite NET on UNIX

425

....................................................................418

..........................................................................................................................................................................................Common issues and resolutions with NavisXtend

About NavisXtend

The NavisXtend Statistics Server collects near real-time statistical information from networks and stores the information in a database that can be accessed by VitalSuite NET. For information on how to configure VitalSuite NET to collect information from a NavisXtend Statistics server, refer to the VitalSuite Performance Management Software Administrator’s Guide.

Common issues and resolutions

The following table lists some common problems that you might encounter when working with NavisXtend, and describes potential remedies.

Problem Tips and resolutions

NavisXtend Statistics server data is not downloading

• Verify that naviscollector -download is in the cron.txt file.• Verify that the NavisStat server section is configured correctly (refer to

the VitalSuite Performance Management Software Administrator’s Guide for more information).

• Check the VitalSuite NET Config/navis/ftplog file.• Check the VitalSuite NET Config/navis/ftpcmds file.• Verify that the download directory path is correct and available. Unless

other locations are named in vitalnet/config/navis/ftplocation.txt the data files are downloaded from the /opt/BulkStats/data/previous or /BulkStats/data/previous. The contents of the ftplocation.txt file overrides the default locations.

• Attempt to download manually to see whether the files exist.

NavisXtend Statistics server data is not being inserted into the database

• Verify that naviscollector -precache is in the cron.txt file.• Check the log file, vscommon/webroot/logs/VNNavis<date>.log for

error messages.• Duplicate data is not inserted.• Check whether the data files match the pre-described format.

Utilization is too high, too low, or incorrect

• Except for ATM PVC, the utilization is a computed percentage value in the data files.

• Verify whether VitalSuite NET’s utilization matches the one in the data files that were downloaded from the NavisXtend Statistics server.

Incorrect speeds are showing up in VitalSuite NET

• The resource speeds might have changed recently.• Run naviscollector without any options to incorporate the speeds in the

raw data files. Refer to the NavisCollector commands in the next section.

Navis resource names in VitalSuite NET are IP addresses

• Verify that naviscollector -update is in the cron.txt file.• Verify that the resource and resource name exists on the NavisCore

server.

....................................................................419

Common issues and resolutions with NavisXtend

There isn't a previous download directory on the NavisXtend Statistics server

If the previous day’s data is not stored on the NavisXtend Statistics server, then specify the current directory in the ftplocation.txt file and alter the times in the cron.txt file to the following:• Alter naviscollector -download to have a Previous Time of 1:15 AM,

and a New Time of 11:00 PM.• Alter naviscollector -precache to have a Previous Time of 2:15 AM, and

a New Time of 12:00 AM.• Alter naviscollector -update to have a Previous Time of 10:45 PM, and a

New Time of 9:30 PM.The naviscollector command inserts data into the VitalSuite NET database and incorporates speed changes seen in the FTP files, though not as fast as navisCollector -precache.The naviscollector -download option downloads data files via FTP.The naviscollector -precache option inserts data into the fastest mechanism by creating a cached list of resources. It does not update speed changes seen in the FTP files.The naviscollector -update option queries the NavisCore server to resolve names and ATM PVC speeds.

Problem Tips and resolutions

....................................................................420

..........................................................................................................................................................................................Shutdown commands for VitalSuite NET UNIX servers

Purpose

This topic provides the proper shutdown commands to use for rebooting and shutting down your VitalSuite NET and VitalSuite ART UNIX servers.

Shutdown command

To shut down and reboot, at the command line, enter:

% sync; shutdown -y -i6 -g5

Power down command

To power off the server without a reboot, at the command line enter:

% sync; shutdown -y -i5 -g5

....................................................................421

Aggregation Editor utility

..........................................................................................................................................................................................Aggregation Editor utility

Purpose

This topic describes the Aggregation Editor, which is a utility that changes the time your VitalSuite NET Polling and Aggregation databases aggregate data.

When to use the Aggregation Editor

The Aggregation Editor only needs to be run if you have a bulk collector in VitalSuite NET that collects data 15 minutes after the hour. For example, if your VitalSuite NET system collects data from iMerge or Wireless data sources, you need to use the Aggregation Editor.

Reason to use the Aggregation Editor

You need to use the Aggregation Editor to modify the aggregation time so alarm thresholds can be applied to certain resource types, such as iMerge and Wireless resources.

During the aggregation process, the alarm thresholds are tested and set for each resource that collected data in the previous hour. Because data collection for iMerge and Wireless occurs after the aggregation has run for the previous hour, the Wireless and iMerge datasets will not have alarms generated unless you change the aggregation time.

Command

To use the Aggregation Editor, enter the following command on each VitalSuite NET Polling and Aggregation server:

AggrEditor <start time> || AggrEditor <-restore>

The following table describes the operands used with the AggrEditor command.

Login requirements for UNIX

When running the Aggregation Editor on UNIX, you must be logged in as vsadm.

Recommended settings for iMerge

If you are monitoring iMerge devices, the following setting is recommended:

AggrEditor 40 10

Operand Description

<start time> Start minute of each hour for the poller aggregation (between 5 and 40).

-restore Restores the aggregation settings back to the system defaults.

....................................................................422

If you set the aggregation time to 40 10, make sure to schedule the iMerge data source for 35 or 36 minutes after the hour so VitalSuite NET has enough time to collect data from the iMerge data source before the new aggregation time.

Recommended settings for iMerge and Wireless

If you are setting up your VitalSuite NET system to collect data from both iMerge and Wireless data sources, contact Lucent Technical Support for the recommended aggregation settings.

....................................................................423

Change the resource limit in My Reports for VitalSuite NET on Windows

Change the resource limit in My Reports for VitalSuite NET on

..........................................................................................................................................................................................Windows

When to use

Use this procedure to change the maximum number of resources that can be included in a VitalSuite NET custom table-formatted report.

Before you begin

Ensure that you are familiar with the Windows registry settings of your computer.

Related information

For more information about using My Reports, refer to:

• VitalSuite Performance Management Software Administrator’s Guide

• VitalSuite Network Performance Management Software User’s Guide

Procedure

To change the resource limit in custom table-formatted reports for VitalSuite NET on Windows:

...........................................................................................................................................................................

1 Open a Command window.

...........................................................................................................................................................................

2 Enter regedit.

Result: The Registry Editor opens.

...........................................................................................................................................................................

3 In the Registry Editor, navigate to the HKEY_LOCAL_MACHINE\Software\VitalSuiteCommon\Vitalnet directory.

...........................................................................................................................................................................

4 Locate the VN_MYREP_MAXRES field.

If the VN_MYREP_MAX field... Then

Exists Proceed to Step 5.

Does not exist 1. Right-click in the right frame of the Registry Editor.2. Select New DWORD Value.3. Enter VN_MYREP_MAXRES as the name of the new field.4. Proceed to Step 5.

....................................................................424

...........................................................................................................................................................................

5 Right-click the VN_MYREP_MAXRES field, and select Modify.

Result: The Edit DWORD Value window opens.

...........................................................................................................................................................................

6 In the Value data field, enter the maximum number of resources you want allowed in custom reports.

...........................................................................................................................................................................

7 Click OK.

Note: No server reboot is required.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................425

Change the resource limit in My Reports for VitalSuite NET on UNIX

Change the resource limit in My Reports for VitalSuite NET on

..........................................................................................................................................................................................UNIX

When to use

Use this procedure to change the maximum number of resources that can be included in a VitalSuite NET custom table-formatted report.

Before you begin

Ensure that you are familiar with the registry settings of your computer.

Related information

For more information about using My Reports, refer to:

• VitalSuite Performance Management Software Administrator’s Guide

• VitalSuite Network Performance Management Software User’s Guide

Procedure

To change the resource limit in custom table-formatted reports for VitalSuite NET on UNIX:

...........................................................................................................................................................................

1 Open a command window.

...........................................................................................................................................................................

2 Log in as su.

...........................................................................................................................................................................

3 Enter the following command:cd $REGISTRY_DIR/HKEY_LOCAL-MACHINE/SOFTWARE/VitalSuiteCommon/VitalNet

...........................................................................................................................................................................

4 Enter the following command:vi param.dat

Result: The param.dat file opens in a text editor.

...........................................................................................................................................................................

5 Add the following line to the end of the param.dat file, where <maximum_resources> is the maximum number of resources you want allowed in custom reports:

"VN_MYREP_MAXRES" "<maximum_resources>" "4"

....................................................................426

...........................................................................................................................................................................

6 Save the param.dat file.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................427

A VitalSuite APPS Help functionality Mail, SNMP, and Remedy Gateways

..........................................................................................................................................................................................Overview

Purpose

This appendix provides instructions for installing VitalSuite APPS Help functionality gateways, creating the filters and template files needed to send events to your mail, SNMP, or Remedy system. Each gateway is described below.

VitalSuite APPS Help functionality mail gateway

The VitalSuite APPS Help functionality Mail Gateway lets the VitalSuite APPS Help functionality automatically send email messages to one or more addresses when specified events are reported to the server. The mail gateway is part of the VitalSuite Performance Management Open Gateway.

SNMP gateway

The SNMP (Simple Network Management Protocol) Gateway lets the VitalSuite APPS Help functionality automatically send an SNMP trap to an SNMP-based network management system, such as HP OpenView, when specified events are reported to the server. The SNMP gateway is part of the VitalSuite Performance Management Open Gateway

This chapter assumes that you are familiar with the details of the SNMP traps of your network management system

Remedy gateway

The Remedy Gateway lets the VitalSuite APPS Help functionality create and update tickets in Remedy based on events logged by the Help functionality.

....................................................................428

Contents

This appendix contains the following topics:

How the VitalSuite APPS Help functionality gateways work 430

How the Mail Gateway works 431

How the SNMP gateway works 433

How the VitalSuite APPS Help functionality integrates with Remedy 435

Mail and SNMP Gateway installation and upgrade 437

General considerations 438

Upgrade scenarios 439

Move a mail or SNMP gateway from a Master to Posting server 440

Pre-installation tasks for the mail and SNMP gateways 442

Install the mail and SNMP gateways 443

Customize your mail and SNMP gateway 445

Test the configuration 447

Overview of the MailGateway.ini and snmptrap.ini files 448

Introduction 449

Gateway settings validation tool 450

Ticket filters 452

Mail and SNMP gateway filter examples 454

Health record data fields 456

MailGateway.ini and snmptrap.ini examples 459

Overview of the mail and SNMP gateway template files 461

About the mail gateway template 462

Example of a mail template file 464

About the SNMP gateway template 466

Example of an SNMP trap template file 468

Remedy gateway installation 470

....................................................................429

Overview

Pre-installation tasks for the Remedy gateway 471

Install the Remedy gateway 472

Set up the Remedy demonstration schema 474

Customize your Remedy environment 476

Remedy gateway files 478

Overview of the remedy.ini file 479

Data maps 480

Data map examples 481

Data fields used in the remedy.ini file 484

Filters 486

Filter examples 487

Example of a remedy.ini file 489

....................................................................430

How the VitalSuite APPS Help functionality gateways work

..........................................................................................................................................................................................Overview

Purpose

This section describes how the VitalSuite APPS Help functionality mail and SNMP gateways integrate with your mail and SNMP servers.

Contents


How the Mail Gateway works 431

How the SNMP gateway works 433

How the VitalSuite APPS Help functionality integrates with Remedy 435

....................................................................431

How the Mail Gateway works

..........................................................................................................................................................................................How the Mail Gateway works

Overview

The Mail Gateway automatically sends an email message to one or more addresses when a specified event is reported. It uses an SMTP interface to send events to your email server.

If you have VitalSuite NET installed, VitalSuite NET network alarms are also sent to the VitalSuite APPS Help functionality Master server or Posting server and are included with the events.

By integrating VitalSuite APPS Help functionality with your email system, you can:

• Automate the process of notifying help desk personnel based on events logged by the VitalSuite APPS Help functionality server.

• Send update messages automatically from events (for example, notifying personnel when an alarm is cleared).

• Create a workflow that integrates the VitalSuite APPS Help functionality server with your help desk personnel for more timely problem resolution.

Where to attach the gateway

The gateway can be attached to one of the following:

• Master server—If you have more than one Posting server, it is recommended you attach the gateway to the Master server, but you can attach the gateway to an individual Posting server.

• Posting server—If you have only one Posting server, the gateway must be installed on the single Posting server.

Mail gateway .ini files

The following table lists the mail gateway .ini file names associated with the Master and Posting server.

Important! When the term MailGateway.ini or snmptrap.ini is used, substitute the term masterMailGateway.ini and mastersnmptrap.ini if you are attaching to a Master server

The VitalSuite APPS Help functionality server uses a customized MailGateway.ini file that contains ticket filters. These ticket filters control when an event should send a message to an email account.

For more information about creating ticket filters, refer to “Ticket filters”, on page 452.

Master Server Posting Server

masterMailGateway.ini MailGateway.ini

mastersnmptrap.ini snmptrap.ini

....................................................................432

How VitalSuite APPS Help functionality forwards events to your email server

After VitalAgents report events to the VitalSuite APPS Help functionality server, the server compares the events to the ticket filters in the MailGateway.ini file.

When an event matches the filter criteria in the file, an email message is created, formatted, and sent using the criteria in a mail template file. You can create one or more mail template files for sending event-based messages to more than one person.

Important! Data transferred between the VitalAgent clients and the VitalSuite APPS Help functionality server is encrypted. The data between the server and the email system is not encrypted.

VitalAgentIT client

VitalAgent clientsEngineering

Email serverHelp serverWeb Console

....................................................................433

How the SNMP gateway works

..........................................................................................................................................................................................How the SNMP gateway works

Overview

When a specified event is reported to the server, the SNMP Gateway automatically sends trap information to such network management systems (NMS) as HP OpenView. The SNMP Gateway uses an SNMP trap to send events to the network management system.

By integrating VitalSuite APPS Help functionality with a network management system, you can:

• Automate the process of notifying network managers (for example, HP OpenView users) about application problems, based on events logged by the VitalSuite APPS Help functionality server.

• Send SNMP traps automatically from events (for example, alerting an HP OpenView server of a connection failure).

• Better monitor network performance by creating a workflow that integrates the VitalSuite APPS Help functionality server with your network management administrator.

Function of the snmptrap.ini file

The VitalSuite APPS Help functionality server uses a customized snmptrap.ini file that contains ticket filters. These ticket filters control when an event sends trap information to the network management server.

For more information, refer to “Ticket filters”, on page 452.

How the VitalSuite APPS Help functionality forwards events to your NMS

As events are reported from VitalAgent and VitalAgentIT clients to the VitalSuite APPS Help functionality server, the event is compared to the ticket filters in the snmptrap.ini file. When an event matches the filter criteria in the snmptrap.ini file, an SNMP trap is created and sent using the criteria in an SNMP trap template file. You can create one or more template files for sending one or more event-based SNMP traps.

Important! Data transferred between the VitalAgent clients and the server is encrypted. The data between the VitalSuite APPS Help functionality server and the network management system is not encrypted.

....................................................................434

VitalAgentIT client


Network managementserver

Help server

SNMPtrap

Web Console

....................................................................435

How the VitalSuite APPS Help functionality integrates with Remedy

..........................................................................................................................................................................................How the VitalSuite APPS Help functionality integrates with Remedy

Benefits of integrating the VitalSuite APPS Help functionality with Remedy

Trouble-ticketing or help desk systems are used for the following purposes:

• To log calls about trouble situations.

• To track and resolve network and system problems.

By integrating the VitalSuite APPS Help functionality with your existing trouble ticketing system, you can:

• Automate the process of creating tickets based on events logged by the server rather than calls from users.

• Update existing tickets automatically from events (for example, clearing a ticket when an alarm is cleared).

• Upload alarm data directly to your help desk application from the VitalSuite APPS Help functionality server.

• Create a workflow that integrates the VitalSuite APPS Help functionality server with your trouble-ticketing system for a complete troubleshooting solution.

Important! If you have VitalSuite NET installed, VitalSuite NET network alarms are also sent to the VitalSuite APPS Help functionality Master server or Posting server and included with the events.

How the VitalSuite APPS Help functionality opens trouble tickets in Remedy

The Posting server uses a customized remedy.ini file that contains filters. These filters control when an event should open or modify a trouble ticket in the Remedy AR system, as shown in the following figure.

For more information about creating filters, refer to “Ticket filters”, on page 452.

VitalAgentIT client


Third-party trouble-ticketingfault management system

Help serverWeb Console

....................................................................436

The remedy.ini file also contains data maps that are used to move selected data from the VitalSuite APPS Help functionality server to the Remedy AR system. A detailed knowledge of the Remedy system is required to create the remedy.ini file because the maps relate VitalSuite APPS Help data to your Remedy database schema. For more information on creating data maps, refer to “Data maps”, on page 480.

Important! Data transferred between VitalAgents and the Posting server is encrypted. The data between the VitalSuite APPS Help functionality server and the Remedy system may also be encrypted depending on the Application Programming Interface (API) provided by the Remedy system.

....................................................................437

Overview

Mail and SNMP Gateway installation and upgrade

..........................................................................................................................................................................................Overview

Purpose

This section provides the information needed to install the Mail and SNMP gateways.

Contents


General considerations 438

Upgrade scenarios 439

Move a mail or SNMP gateway from a Master to Posting server 440

Pre-installation tasks for the mail and SNMP gateways 442

Install the mail and SNMP gateways 443

Customize your mail and SNMP gateway 445

Test the configuration 447

....................................................................438

..........................................................................................................................................................................................General considerations

When you have only one Posting server

When only one Posting server is installed, alarm collection is disabled on the Master server to eliminate duplication of effort in collecting, correlating, and retaining alarms.

For environments with only one Posting server, note the following:

• Alarm collection on the Master server is disabled. Alarms have only one ticket sequence.

• Posting server alarms generate VitalSuite APPS Help heat charts, reports, and My Vital reports.

• The Posting server’s database generates Administrative pages such as viewing preferences and agent search lists.

• If a second Posting server is added, data collection on the Master is automatically triggered.

Impact of removing a Posting server

If you remove a Posting server from a 9.2 or later environment where two Posting servers are installed, then you must reconfigure the remaining Posting server gateways to match the specifications configured on the Master Gateway.

If the VitalSuite APPS Help functionality 9.1 is installed with only one Posting server, Master Gateways should NOT be configured. If only there is only one Posting server then the Gateways should be configured on the Posting server only.

....................................................................439

Upgrade scenarios

..........................................................................................................................................................................................Upgrade scenarios

Purpose

This topic describes the actions you need to take when upgrading from previous releases of the Help functionality of VitalSuite APPS.

Scenarios

The following table describes the required actions for various upgrade scenarios.

If… Then…

You perform a new installation of the current release

No special handling is required.

You upgrade from version 9.2 or later with no Master Gateways installed


You upgrade from version 9.2 or later in a multiple Posting server environment…


You upgrade from version 9.2 or later with Master Gateways installed in a single Posting server

It is strongly recommended that the Gateways be moved from the Master server to the Posting server because the Master server no longer collects data in a single Posting server environment.

You upgrade from version 9.2 or later with a single Posting server and you want the filters defined on the Master Gateways to apply to the alarms on the Posting server

To have the filters work for the Posting server, follow the procedure “Move a mail or SNMP gateway from a Master to Posting server”, on page 440.

You upgrade from version 9.2 or later with Master Gateways previously configured in your installation

You need to move your Master Gateway filters to the remaining Posting server (see “Move a mail or SNMP gateway from a Master to Posting server”, on page 440).

....................................................................440

..........................................................................................................................................................................................Move a mail or SNMP gateway from a Master to Posting server

When to use

Use this procedure to move an existing mail or SNMP gateway currently attached to the Master server to a Posting server.

Before you begin

Select the Posting server that you want to have a mail or SNMP gateway.

Related information

For more information about the mail and SNMP gateways, refer to the following:

• “How the Mail Gateway works”, on page 431

• “How the SNMP gateway works”, on page 433

Procedure

To move the Master gateways to the Posting server:

...........................................................................................................................................................................

1 Install the same gateway(s) on the Posting server by going to <install_dir>/Program Files/VSCommon/Webroot/ and running helpdesk.exe.

...........................................................................................................................................................................

2 Do one of the following

...........................................................................................................................................................................

3 To apply the filters on the Master server gateway to the new Posting server gateway:

a. Verify that the filters in the Master server file are different than the filters in the Posting server file.

The gateway filter files are located in the <install_dir>/VitalHelp/Config/ directory, and have the following names:

• Mail Gateway filter file: mastermailgateway.ini (Master server) and mailgateway.ini (Posting server).

• SNMP Gateway filter file: mastersnmpgateway.ini (Master server) and snmpgateway.ini (Posting server).

To... Then...

Apply the existing filters and conditions for the Master server gateway to the new Posting server gateway

Proceed to the next step.

Redefine filters and conditions on the new Posting server gateway

Refer to “Overview of the MailGateway.ini and snmptrap.ini files”, on page 448 for information on creating filters.

....................................................................441

Move a mail or SNMP gateway from a Master to Posting server

b. If you are moving an SNMP gateway from a Master server to a Posting server, copy the filters located in mastersnmpgateway.ini to snmpgateway.ini.

If you are moving a Mail gateway from a Master server to a Posting server, copy the filters located in mastermailgateway.ini to mailgateway.ini.

c. Edit these filters on the corresponding Posting server template file.

The file for the Mail Gateway is mailtemplate.ini and the file for the SNMP Gateway is snmptemplate.ini. Both of these files reside on the Posting server.

For more information, refer to “Overview of the mail and SNMP gateway template files”, on page 461.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................442

..........................................................................................................................................................................................Pre-installation tasks for the mail and SNMP gateways

Purpose

Follow these pre-installation tasks before installing the mail and SNMP gateways

Pre-installation tasks

Complete these tasks before installing a mail or SNMP gateway:

1. Read the VitalSuite Application Performance Management Software Release Notes at: http://www.lucent.com/support. If you do not have a user ID and password, click the Access and Registration link on the Support site to obtain your login information

2. Shut down open Internet browser and anti-virus programs on your desktop. It is also recommended that you close all other open programs.

3. Obtain the following:

• The name of your SMTP server and a list of email senders and recipients for the Mail Gateway installation.

• The IP address of your SNMP server for the SNMP Gateway installation.

4. Log in to the designated Master server, using the same Windows administrator account (system account) used to install the VitalSuite APPS Help functionality.

5. Verify that the base VitalSuite APPS Help functionality has already been installed on the Master server.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................443

Install the mail and SNMP gateways

..........................................................................................................................................................................................Install the mail and SNMP gateways

When to use

Use this procedure to install the mail and SNMP gateways.

Before you begin

Make sure that you have completed the pre-installation tasks described in “Pre-installation tasks for the mail and SNMP gateways”, on page 442.

Related information

For general information about the mail and SNMP gateways, refer to the following:

• “How the Mail Gateway works”, on page 431.

• “How the SNMP gateway works”, on page 433.

Procedure

To install the Mail or SNMP Gateway:

...........................................................................................................................................................................

1 On the VitalSuite APPS Help functionality server, start the HelpDesk Install program by double-clicking on the Helpdesk.exe executable (located in the \VSCommon\Webroot directory).

Result: The VitalHelp Server Installation Welcome window displays.

...........................................................................................................................................................................

2 Click Next to start the HelpDesk installation.

Result: A window opens for each Gateway component that lets you confirm that you want to install that Gateway at this time.

...........................................................................................................................................................................

3 To install a gateway component, click Yes in the dialog box for that Gateway.

Result: The Installation window opens for the Gateway components for which you selected Yes.

...........................................................................................................................................................................

4 Enter the requested information:

• The IP address of your SMTP server and a list of email senders and recipients for the Mail Gateway installation.

• The IP address of your SNMP server for the SNMP Gateway installation.

Result: This information is automatically written to the .ini and template files for those products.

....................................................................444

Important! When using the Helpdesk.exe installation program to change or add an IP address, the server information is appended to the MailGateway.ini or snmptrap.ini file. To change the server, you must edit the .ini file to comment out the first server IP address. Use the IP address and not the server name in this file. The .ini file is located at <drive>:\Program Files\VitalHelp\Config.

...........................................................................................................................................................................

5 Click OK.

Result: After you finish installing the gateway components, a window opens indicating that the installation has been successfully completed.

...........................................................................................................................................................................

6 Click Finish to complete the installation.

...........................................................................................................................................................................

7 After installing the Mail or SNMP Gateway on your server, perform the following post-installation tasks:

• “Customize your mail and SNMP gateway”, on page 445

• “Test the configuration”, on page 447

...........................................................................................................................................................................E N D O F S T E P S

....................................................................445

Customize your mail and SNMP gateway

..........................................................................................................................................................................................Customize your mail and SNMP gateway

When to use

Use this procedure to customize your mail and SNMP gateways.

Before you begin

Make sure that you have installed the mail and SNMP gateways, as described in “Install the mail and SNMP gateways”, on page 443.

Related information

For general information about the mail and SNMP gateways, refer to:

• “How the Mail Gateway works”, on page 431.

• “How the SNMP gateway works”, on page 433.

Procedure

To customize your Mail or SNMP Gateway:

...........................................................................................................................................................................

1 Customize the MailGateway.ini or snmptrap.ini file to upload only the data you want.

Refer to “Overview of the MailGateway.ini and snmptrap.ini files”, on page 448 to customize this file.

...........................................................................................................................................................................

2 Customize one or more template files (mailtemplate.ini or snmptemplate.ini).

To create this file, refer to:

• “About the mail gateway template”, on page 462 for the mailtemplate.ini file.

• “About the SNMP gateway template”, on page 466 for the snmptemplate.ini file.

....................................................................446

...........................................................................................................................................................................


...........................................................................................................................................................................E N D O F S T E P S

If... Then...

You installed the gateway component after you had already installed the VitalSuite APPS Help functionality

Restart the server by stopping and restarting the VitalHelp service from the Windows Services screen.

Important! The services will not restart if there are syntax errors in the mailgateway.ini or snmptrap.ini file. To view any syntax errors, refer to a log file at a path similar to <drive>:\Program Files\VSCommon\webroot\ logs\ vhs20030512.log

You customized one or more of your gateway files but already had the gateway component installed

Reinitialize the gateway:1. In the ADMIN tab, click Thresholds.2. Click VitalHelp gateways under Notification in the menu

frame.3. Click Reinitialize for the corresponding OpenGateway

module(s) that you want to reinitialize.

....................................................................447

Test the configuration

..........................................................................................................................................................................................Test the configuration

When to use

Use this procedure to test that events are properly forwarded to your email or SNMP server.

Before you begin

Make sure that you have installed and customized your mail or SNMP gateway.

Related information

For more information about installing and customizing mail and SNMP gateways, refer to:

• “Install the mail and SNMP gateways”, on page 443

• “Customize your mail and SNMP gateway”, on page 445

Procedure

...........................................................................................................................................................................

1 For testing purposes, add a filter to the MailGateway.ini or snmptrap.ini file to trigger an email message or SNMP trap when any VitalSuite APPS Help event occurs.

Important! You must wait the number of seconds specified in the qcheck variable before an email message or SNMP trap is sent. During testing you may alter the value of the qcheck variable in the MailGateway.ini or snmptrap.ini file.

Important! The MailGateway.ini and snmptrap.ini files shipped with the VitalSuite APPS Help functionality have a default filter. The default filter sends email and SNMP trap information when an error event occurs more than 10 times.

...........................................................................................................................................................................

2 Create some events that should be tracked.

These events should meet your upload criteria.

...........................................................................................................................................................................

3 Verify that the events you created are forwarded to your email or network management system.

...........................................................................................................................................................................

4 If you do not receive email messages after creating the associated events, check:

• For syntax errors in the following path: Program Files\VSCommon\Webroot\logs\vhs<yearmonthday>.log (for example, VHS20030601).

• That your mail server supports SMTP.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................448

Overview of the MailGateway.ini and snmptrap.ini files

..........................................................................................................................................................................................Overview

Purpose

This section provides an overview of the MailGateway.ini and snmptrap.ini files.

Contents


Introduction 449

Gateway settings validation tool 450

Ticket filters 452

Mail and SNMP gateway filter examples 454

Health record data fields 456

MailGateway.ini and snmptrap.ini examples 459

....................................................................449

Introduction

..........................................................................................................................................................................................Introduction

Main sections of the .ini files

The MailGateway.ini file and snmptrap.ini files have two main sections:

How to edit the .ini files

You can use any text editor to modify the MailGateway.ini or snmptrap.ini file for your implementation. By default, the file resides in the <Drive>:\<install_dir>\VitalHelp\Config directory. We recommend that you create a test environment to verify that the desired information is being uploaded from the server to your email or network management server before full-scale deployment.

How to validate the .ini file contents

You can use a command-line utility, GatewayCheck.exe to check the MailGateway.ini and snmptrap.ini files for errors. For more information, refer to “Gateway settings validation tool”, on page 450.

Section Includes

Server The IP address of the mail or network management server, a retries variable, and a qcheck variable. The retries variable specifies the number of times the server sends an email message or SNMP trap if an error occurs. The qcheck variable specifies the maximum number of seconds before an email message or SNMP trap is sent after an event occurs.

Filters One or more ticket filters for each event. Refer to “Ticket filters”, on page 452 for more information.

....................................................................450

..........................................................................................................................................................................................Gateway settings validation tool

Purpose

This topic describes the gateway validation tool, GatewayCheck.exe. This utility checks for errors in the default MailGateway.ini and snmptrap.ini files. It does not check MailTemplate.ini or Remedy initialization files.

GatewayCheck.exe looks for the following problems:

• Syntax errors, line by line

• Duplicate entries for sections and subsections in the file

• Incorrect types for each parameter that requires values, such as alpha, numeric, non-zero requirements

• Out-of-range values for parameters that require values

• Incorrect selections for parameters that have a predefined list

• Incorrect values for parameters that have been defined in a database table

Operation

GatewayCheck.exe is located in the default program files directory for the Master server. The following table describes the command options:

Validation results

The results of the validation print in the Windows command window. The filename is followed by lines for each error, one to a line, with the text that causes the error enclosed by carets (^). You must identify whether the error is due to syntax problems, an incorrect type, out of range value, or incorrect selection.

Example: The following line indicates that some text “updat” on line 20 causes an error:

20: actions=added,^updat^

Option Description

-f Mandatory. Specifies the file to validate. Values can be either:

• mailgateway.ini• snmptrap.ini

-h Prints command options and use information.

....................................................................451

Gateway settings validation tool

Allowed values

The following table lists the allowed values for various sections and subsections that are validated:

Section Subsection Parameter Valid value

Server server String or legal IP address

retries Integer within range 0-10. No default

qcheck Positive number within range 1-120. Default is 60.

qlimit Positive number within range 10-10,000. Default is 1,000.

Filter events From 1 to 16 number that are recorded in VHCAuseMapTable or ‘ALL’

Example: events=e1,e2,e6,e23

Example: events=ALL

actions One or more of the following selections separated by commas:

• activated• added• aged• cleared• deleted• updated

Example: actions=aged,updated

info Valid filename

condition vhfield operator value

operator

....................................................................452

..........................................................................................................................................................................................Ticket filters

Purpose of filters

Ticket filters are used to evaluate whether or not events should trigger an email message or SNMP trap. You can create one or more ticket filters for each event.

Filter format

Use the following format when you create ticket filters:

[server#:filter#]events=eventIDactions=added, updated, aged, cleared, deleted, activatedcondition#=vhfield operator valueinfo=template_file_name

Parts of a filter

The following table describes each part of a filter.

Criterion Description

server# The server number represents the email server or network management system to which this filter applies. You can specify more than one server to which you want to send email messages or SNMP traps. You can simply edit the MailGateway.ini or snmptrap.ini file to add a server, or use the Helpdesk.exe installation program (described in “Install the mail and SNMP gateways”, on page 443). When you use Helpdesk.exe, server information is appended to the .ini file.

filter# The filter number is a unique number that represents each filter. A record must pass all criteria in a filter before an email message or SNMP trap is sent. If multiple ticket filters specify the same event, only one of the ticket filters must be satisfied. In other words, each entry in a filter is AND’ed together. Separate ticket filters for the same event are OR’ed.

events This field specifies the ID numbers for one or more events on which this filter triggers. Separate multiple events with commas. For example, if the event is 3050 (Client CPU load), an email message or SNMP trap is sent when this event occurs and the rest of the filter criteria is met.For a list of events and their ID numbers, refer to the VitalSuite Application Performance Management Software Help Functionality List of Events document, which can be accessed at: http://www.lucent.com/support.If you do not have a user ID and password, click the Access and Registration link on the support site to obtain your login information.

actions This field contains one or more of the following, separated by a comma: added, updated, deleted, cleared, activated, or aged. You can also use the ALL keyword to indicate all actions.

....................................................................453

Ticket filters

condition This field specifies the conditions that must be met in order to upload an event. The format of this field is the health record data field name followed by an operator such as =, < >, >, >=, <, <=, then a value. Each of the health record data fields is described in “Health record data fields”, on page 456. For the VHCount and VHNumClients data fields, the % operator indicates every nth occurrence. For example, VHCount % 10 means that this condition is met when the specified event has occurred 10 times, 20 times, 30 times, and so on. This is useful because it limits the number of email messages or SNMP traps that are sent for a particular problem.

info This field provides the name of the email template or SNMP trap template file you want used for this filter. You can specify different template files for different ticket filters. The template files must be in the <Drive>:\Program Files\VitalHelp\Config directory.


....................................................................454

..........................................................................................................................................................................................Mail and SNMP gateway filter examples

Purpose

This topic provides various filter examples you can use as a foundation for creating your own filters.

Example 1

The following two ticket filters specify that an email message is sent when event 3050 is reported if the number of clients reporting this event is a multiple of 5 OR if the total occurrences of this event is a multiple of 10.

[10.10.10.101:filter1]events=3050actions=added,updatedcondition1=VHCount % 10info=”mailtemplate.ini”

[10.10.10.101:filter2]events=3050actions=added,updatedcondition1=VHNumClients % 5info=”mailtemplate.ini”

Example 2

In the following filter, an email message is sent when event 3050 is reported if the number of clients reporting this event is greater than 5 AND the total occurrences of this event is a multiple of 10.

[10.10.10.101:filter1]events=3050actions=added,updatedcondition1=VHCount % 10condition2=VHNumClients > 5info=”mailtemplate.ini”

Email filter example

The following filter sends an email message when an event is sent to the server:

[10.10.10.101:filter1]events=ALLactions=ALLinfo=”mailtemplate.ini”

....................................................................455

Mail and SNMP gateway filter examples

SNMP trap filter example

This filter sends an SNMP trap when an event is added to the server.

[10.10.10.101:filter1]events=ALLactions=ALLinfo=”snmptemplate.ini”

Email filter example

This filter sends an email message when two or more VitalAgent clients report this event.

[10.10.10.101:filter1]events=3053actions=added,updatedcondition1=VHNumClients > 2info=”mailtemplate.ini”

SNMP trap filter example

This filter sends an SNMP trap when event 3053 happens to a single VitalAgent client more than two times.

[10.10.10.101:filter1]events=3053actions=added,updatedcondition1=VHCount > 2info=”snmptemplate.ini”

....................................................................456

..........................................................................................................................................................................................Health record data fields

Overview

Whenever an event is logged, a health record is created and data is recorded in each of the health record fields described in the table in this topic. These fields are used as the filter criteria in the MailGateway.ini and snmptrap.ini files and determine which events trigger the email message or SNMP trap.

The fields are also used in the template files (Mailtemplate.ini and snmptemplate.ini) that determine the content of the email message or SNMP trap.

Field names

The following table describes the health record data fields.Use the field names provided in your filter criteria, email messages, and SNMP traps.

Field name Description

VHAlarmId Unique ID that identifies the problem (alarm) location as identified by VitalAgent:3000 = server3001 = network3002 = client3003 = modem3005 = network3006 = network3007 = network3008 = network3009 = network3010 = network3011 = network3016 = server

VHAppId Unique ID that identifies the application that encountered the problem. Refer to “Application IDs”, on page 458 for a detailed list of the applications and the associated numbers.If you place an “i” in front of the field name, an integer value is returned that represents the application.

VHCauseId Unique ID that identifies the cause of the event. This is the event number that is used in the event field of a filter. This field, therefore, cannot be used in the condition field of a filter.

VHClientId Unique ID sent by the VitalAgent client to identify itself. For correlated events, this ID identifies the first client to report the event.

....................................................................457

Health record data fields

VHComments Text that the user entered into the comment field of the VitalHelp Diagnosis window.

VHCorrClients Encoded list (binary data) of client names that reported the event. Because this field is represented in binary, it cannot be used in the condition field of a filter.

VHCount Number of times the event was reported for a particular client or the total number of client counts when there are correlated events.

VHDetails Encoded (binary data) event information. Because this field is represented in binary, it cannot be used in the condition field of a filter.

VHDomainId Unique ID that identifies the name of the domain.

VHEndTime The most recent time the event was reported.

VHEventValue Number that further identifies the cause of the event. This value is the same as the subID in the VitalSuite Application Performance Management Software Help Functionality List of Events.

VHGroupId Unique ID that identifies the group of the client. If the client is remote, this value is 1; otherwise, this value is either the user-defined group ID for this client or the subnet that the client uses.

VHNumClients Number of unique clients that reported the event.

VHRecNum Ticket (record) number.

VHServerId Unique ID that identifies the server.

VHStartTime First time the event was reported.

VHStatus Event status:4 = yellow (warning)5 = red (failure)

VHTicketStatus Ticket status:0 = unknown1 = new4 = closed7 = aged out

VHTicketType Indicates if the event is single or correlated:0 = unknown1 = single2 = correlated

VHTranId Application transaction ID number.

VHUpdateTime Last time the record status was changed.


....................................................................458

Application IDs

The following table shows a list of application IDs.

VHAppID Application name

21 FTP

23 Telnet

25 email

53 DNS

80 Web

119 News

135 MS-RPC

139 File/Print

143 IMAP

389 LDAP

443 WebSecure

1352 LotusNotes

1433 MS-SQL

1498 Sybase

1525 Oracle

1755 NetShow

3264 cc:Mail

7070 RealPlayer

9304 Castanet

9305 Exchange

....................................................................459

MailGateway.ini and snmptrap.ini examples

..........................................................................................................................................................................................MailGateway.ini and snmptrap.ini examples

Purpose

This topic provides examples of the MailGateway.ini and snmptrap.ini files.

MailGateway.ini example

The following is an example of a complete MailGateway.ini file. Use this example to help generate your own MailGateway.ini file.

[10.10.10.101]server=xyz.comretries=3qcheck=2

[10.10.10.101:filter1]events=ALLactions=ALLinfo="mailtemplate.ini"

; info specifies the template file used to generate the mail message format; List of VitalHelp health record fields

; Field name Description; VHRecNum Record number; VHDomainId Domain id (CANNOT be a stringname i.e. VHDomainID); VHGroupId Group id (e.g. subnet); VHAlarmId Problem location (client, server, network, etc); VHCauseId Problem type; VHAppId Application id; VHTranId Transaction id; VHServerId Server id; VHClientId Client id; VHCount Number of occurrences of this problem; VHEventValue Event specific value; VHStartTime First time event occurred; VHEndTime Last time event occurred; VHUpdateTime Last time event changed state

Filter based on VitalAgent type

The following example shows a filter based on the type of VitalAgent.

; List of VHAgentType values

; 0 unknown

; 3 automon

; 5 vitalagent

....................................................................460

; 6 vitalagent IT

; 7 mid tier

;

;[10.10.10.101:filter1]

;events=ALL

;actions=added, updated

;condition1=iVHAgentType=3

Important! If All VitalAgent types are selected in the server configuration no filter is necessary.

snmptrap.ini example

The following is an example of a complete snmptrap.ini file. Use this example to help generate your own snmptrap.ini file.

[10.10.10.101]server=xyz.comretries=3qcheck=2

[10.10.10.101:filter1]events=ALLactions=ALLinfo="snmptemplate.ini"

; info specifies the template file used to generate the snmp trap; List of VitalHelp health record fields

; Field name Description; VHRecNum Record number; VHGroupId Group id (e.g. subnet); VHAlarmId Problem location (client, server, network, etc); VHCauseId Problem type; VHAppId Application id; VHTranId Transaction id; VHServerId Server id; VHClientId Client id; VHCount Number of occurrences of this problem; VHEventValue Event specific value; VHStartTime First time event occurred; VHEndTime Last time event occurred; VHUpdateTime Last time event changed state

....................................................................461

Overview

Overview of the mail and SNMP gateway template files

..........................................................................................................................................................................................Overview

Purpose

This section provides an overview of the mail gateway and SNMP gateway template files.

The VitalSuite APPS Help functionality uses a template file to compose the email message or SNMP trap it sends when the filter criteria is satisfied. The template file is specified in each filter. The template files for the Mail Gateway and SNMP Gateway components are different.

Contents


About the mail gateway template 462

Example of a mail template file 464

About the SNMP gateway template 466

Example of an SNMP trap template file 468

....................................................................462

..........................................................................................................................................................................................About the mail gateway template

Sections of the mail gateway template file

Each mail template file has three sections:

Important! To send different email messages to different people, you must create multiple mail template files. You can then create different ticket filters, with each specifying a unique mail template file.

How to edit the template file

You can use any text editor to modify the default mailtemplate.ini file for your implementation. The mailtemplate.ini file must be placed in the following relative location <drive>:\<install-directoryname>\VitalHelp\Config. It is recommended that you create a test environment to verify that the desired email message is being sent before full-scale deployment.

You can create one or more mail template files for each event.

Format

Template files are created in the following format:

[MAILTEMPLATE]

sender=<emailaddress>recipients=<emailaddress>,<emailaddress>,<...>subject=[string] or <VHfield1>:<VHfield2> on <VHfield3>message=[string]:<VHfieldx>[string]:<VHfieldy>[string]:<VHfieldz>

If you want to change the email sender, you can include a sender section after the recipients section by using the following format:

[email protected]

All health record data fields used in the mail template file must be enclosed in angle brackets (< >). In the subject section, you can include any combination of strings and data fields.

Section Description

Sender Includes the email address of the senderRecipients—Includes the email address of each person to which you want this email message sent. Email addresses are separated by commas.

Subject Provides the subject line of the message. It can include health record data fields such as the VHClientID

Message Provides the content of the message, which is usually one or more health record data fields.

....................................................................463

About the mail gateway template

The message section should be formatted on a single line. If you want to specify a new line, you must end the preceding line with “\n” to indicate a new line. You can also include a URL in the message so the recipient can go directly to the Web Console to view the event that triggered the email message.

....................................................................464

..........................................................................................................................................................................................Example of a mail template file

Purpose

This topic shows an example of a mail template file and the associated email message. Use this example to help generate your own mail template file.

Mail template example

[MAILTEMPLATE]

sender= [email protected]= [email protected],[email protected]

subject= <VHStatus>: <VHCauseId> on <VHClientId> - Ticket # <VHRecNum>

message= PROBLEM DETAILS: \n \n Ticket #:<VHRecNum> \n Domain ID:<VHDomainId> \n Group id:<VHGroupId> \n Problem location:<VHAlarmId> \n Problem Description:<VHCauseId> \n Application:<VHAppId> \n Client machine:<VHClientId> \n # of Occurrences:<VHCount> \n Event values:<VHEventValue> \n Problem Start Time:<VHStartTime> \n Problem End Time:<VHEndTime> \n Status:<VHStatus> \n Problem Ticket Status:<VHTicketStatus> \n TicketType:<VHTicketType> \n Server machine:<VHServerId> \n Comments:<VHComments> \n \n ---------------- \n URL to VitalHelp Console: \n http://<VHServer>/vhconsole \n \n URL to Event Detail: \n http://<VHServer>/cgi-bin/vhcgi.exe?TestName=eventDetails&RecNum=<VHRecNum>&EventId=<iVHCauseId>&EventValue=<VHEventValue>&AppId=<iVHAppId>&TranId=<iVHTranId>

[COMMENT]

; Use angle brackets (<>) to delimit VitalHelp field names (see; below) used in the subject or mail message. “\n” can be used to put; line breaks in the mail message.

; Field name Description; VHRecNum Record number; VHDomainId Domain id (CANNOT be a stringname i.e. VHDomainId); VHGroupId Group id (e.g. subnet); VHAlarmId Problem location (client, server, network, etc); VHCauseId Problem type; VHAppId Application id; VHTranId Transaction id; VHServerId Server id; VHClientId Client id; VHCount Number of occurrences of this problem; VHEventValue Event specific value; VHStartTime First time event occurred; VHEndTime Last time event occurred; VHUpdateTime Last time event changed state

....................................................................465

Example of a mail template file

; VHStatus Event status (warning, error, etc); VHTicketStatus Ticket status (new, pending, closed, etc); VHTicketType Ticket type (single, correlated); VHComments Event comments (from VH console); VHNumClients Number of correlated clients; VHCorrClients Correlated client information; VHDetails Event specific detailsList of VitalHelp event ids

Example email message

The following is an example of an email message sent by the mail template file shown in the previous example.

From: VitalHelp.Server <VitalHelp.Server>To: [email protected] <[email protected]>Date: Monday, October 05, 1998 4:55 PMSubject: error: HTTP Page transfer failure on serveradmin.xyz.com - Ticket # 787

PROBLEM DETAILS:

Ticket #:787Group id:UnknownProblem location:ClientProblem Description:HTTP Page transfer failureApplication:45Client machine:serveradmin.xyz.com# of Occurrences:1Event values:411Problem Start Time:Mon Oct 05 16:55Problem End Time:Mon Oct 05 16:55Status:errorProblem Ticket Status:newTicketType:singleServer machine:sun2.xyz.com

---------------- URL to VitalHelp Console:http://sun2.xyz.com/vhconsole

URL to Event Detail: http://sun2.xyz.com/cgi-bin/vhcgi.exe?TestName=eventDetails&RecNum=787&EventId=153&EventValue=411&AppId=45&TranId=1

....................................................................466

..........................................................................................................................................................................................About the SNMP gateway template

Sections of the SNMP gateway template

Each SNMP Gateway template file has two sections:

To send different SNMP traps based on different events, you must create multiple SNMP trap template files. You can then create different ticket filters, with each specifying a unique SNMP trap template file.

How to edit the SNMP gateway template

You can use any text editor to modify the default snmptemplate.ini file for your implementation. The snmptemplate.ini file must be placed in the <Drive>:\<install-directoryname>\VitalHelp\Config directory. It is recommended that you create a test environment to verify that the desired SNMP trap is sent before full-scale deployment.

You can create one or more template files for each event.

Format

Template files are created in the following format:

[header]enterprise=object_identifiergeneric-trap-type=generic_typespecific-trap-type=specific_type

[varbinds]1=varbind#12=varbind#2.n=varbind#n

Header details

In the header section, include the object identifier (OID), the generic trap type, and the specific trap type that you want in the corresponding header fields of the SNMP trap. The other two SNMP trap header fields (the address of the sending agent and the timestamp) are provided by the gateway interface.

Section Description

Header Includes the header field values specific to the SNMP trap that you want to generate.

SNMP trap varbind list Provides the varbind list specific to the SNMP trap that you want to generate. For example, for the HP OpenView trap shown on page 469, the varbind list would contain the application ID of the event, the host name of the machine running snmpCollect, and the error message.

....................................................................467

About the SNMP gateway template

varbind details

The varbinds section is optional and depends on the specific SNMP trap that you are generating. Include a value for each varbind as appropriate for your specific SNMP.

When specifying a varbind value, use a value with the correct data type for that varbind. The SNMP Gateway supports the following three ASN.1 data types:

The default object identifier (OID) for a varbind is the OID given in the enterprise field of the header section. To specify a different OID for a varbind, use a slash (/) after the varbind number, followed by the OID. For example:

4/.1.3.6.1.4.1.11.2.17.1.0.58720265=[server <VHServerId>]

ASN.1 data types Format Example

OCTET STRING Enclose OCTET STRINGs in square brackets ([]). OCTET STRINGs can include field names enclosed in angle brackets (<>).

[server <VHServerId>]

OBJECT IDENTIFIER

Begin OBJECT IDENTIFIERs with a period (.).

.1.3.6.1.4.1.11

INTEGER (or any SNMP data type compatible with INTEGER, for example, “Counter”)

INTEGERs are either a sequence of numbers or a field name preceded by an “i”.

....................................................................468

..........................................................................................................................................................................................Example of an SNMP trap template file

Purpose

This topic contains an example of a complete SNMP trap template file that generates an SNMP trap specific to HP OpenView. Use this example to help generate your own template file.

Example

[header]enterprise=.1.3.6.1.4.1.11.2.17.1generic-trap-type=6specific-trap-type=58720265

[varbinds]1=1012=VHClientId3=04/.1.3.6.1.4.1.11.2.17.1.0.58720265=[server "<VHServerId>": event "<VHCauseId>" reported by <VHCount> agents]

[COMMENT]

; Use angle brackets (<>) to delimit VitalHelp field names (see; below) used in the varbind list. The lowercase "i" as the first ; character of a VitalHelp field name indicates that this is an; integer field. Use the field name with the "i" in any varbind that; needs an integer value. An integer field may be used in a varbind; that needs a string value by removing the leading "i". Fields; without a leading "i" have string values only and cannot be used; in integer varbinds.

; Field name Description

; iVHRecNum Record number; iVHGroupId Group id (e.g. subnet); iVHAlarmId Problem location (client, server, network, etc); iVHCauseId Problem type; iVHAppId Application id; iVHTranId Transaction id; iVHServerId Server id; iVHClientId Client id; iVHCount Number of occurrences of this problem; iVHEventValue Event specific value; iVHStartTime First time event occurred; iVHEndTime Last time event occurred

....................................................................469

Example of an SNMP trap template file

; iVHUpdateTime Last time event changed state; iVHStatus Event status (warning, error, etc); iVHTicketStatus Ticket status (new, pending, closed, etc); iVHTicketType Ticket type (single, correlated); VHComments Event comments (from VH console); iVHNumClients Number of correlated clients; VHCorrClients Correlated client information; VHDetails Event specific details

Example of an SNMP trap

The following is an example of an SNMP trap sent by the template file shown in the previous example.

Wed Jun 03 12:43:44 2004 199.0.204.2 server "lab-pc1": event "Connection failed" reported by 3 agents

....................................................................470

Remedy gateway installation

..........................................................................................................................................................................................Overview

Purpose

This section provides instructions for installing the Remedy gateway.

Contents


Pre-installation tasks for the Remedy gateway 471

Install the Remedy gateway 472

Set up the Remedy demonstration schema 474

Customize your Remedy environment 476

....................................................................471

Pre-installation tasks for the Remedy gateway

..........................................................................................................................................................................................Pre-installation tasks for the Remedy gateway

Purpose

This topic describes the pre-installation tasks you need to complete before installing the Remedy gateway.

Pre-installation tasks

Complete the following tasks before installing your Remedy gateway:

1. Read the VitalSuite Application Performance Management Software Release Notes at: http://www.lucent.com/support.If you do not have a user ID and password, click the Access and Registration link on the support site to obtain your login information.

2. Shut down any open Internet browser and anti-virus programs on your desktop. It is also recommended that you close all other open programs.

3. Obtain the name of your Remedy server and a Remedy user name and password that will allow the VitalSuite APPS Help functionality server to create trouble tickets in the Remedy AR system.

4. Log in to the designated Posting server, using the same Windows administrator account (system account) used to install the base product.

5. Verify that the base product has already been installed on the Posting server.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................472

..........................................................................................................................................................................................Install the Remedy gateway

When to use

Use this procedure to install the Remedy gateway

Before you begin

Make sure you have completed the “Pre-installation tasks for the Remedy gateway”, on page 471.

Important! The Remedy Gateway must be installed on the Posting server for the VitalSuite APPS Help functionality to interact with Remedy. When you install the VitalSuite APPS Help functionality, the Helpdesk.exe installation program for the Remedy Gateway is automatically installed on your Posting servers. You can then use the Helpdesk.exe installation program to install the Remedy Gateway on each Master server or Posting server.

Related information

For general information about the Remedy gateway, refer to “How the VitalSuite APPS Help functionality integrates with Remedy”, on page 435.

Procedure

To install the Remedy Gateway:

...........................................................................................................................................................................

1 On each Posting server, start the HelpDesk Install program by double-clicking on Helpdesk.exe (located in the \VSCommon\Webroot directory).

Result: The VitalHelp Server Installation Welcome window opens.

...........................................................................................................................................................................

2 Click Next to start the HelpDesk installation.

Result: A window opens that lets you confirm that you want to install the Remedy Gateway at this time.

...........................................................................................................................................................................

3 Click Yes to install the Remedy Gateway.

Result: The VitalHelp Server Remedy Installation window opens.

....................................................................473

Install the Remedy gateway

...........................................................................................................................................................................

4 Enter the requested information (name of the Remedy server, your Remedy user name and password) and click OK.

Important! Note the following:

• The Remedy user name you enter must have rights to create new records and update the fields for the schemas specified in the remedy.ini file.

• The user name and password are case-sensitive.

Result: A window asks if you want to install the Mail Gateway at this time. Then, one opens that asks if you want to install the SNMP Gateway at this time. After you have finished installing the gateway components, a window opens indicating that the installation has been successfully completed.

...........................................................................................................................................................................

5 Click Finish to complete the installation.

...........................................................................................................................................................................

6 After installing the Remedy Gateway on your Posting server, refer to the following post-installation tasks:

• “Set up the Remedy demonstration schema”, on page 474.

• “Customize your Remedy environment”, on page 476.

...........................................................................................................................................................................E N D O F S T E P S

....................................................................474

..........................................................................................................................................................................................Set up the Remedy demonstration schema

When to use

Use this procedure to set up a demonstration schema in Remedy that shows how the VitalSuite APPS Help functionality and Remedy can be integrated. After examining this demo, you can modify your own Remedy environment to include these capabilities.

Before you begin

Know how to use the Remedy Admin tool provided with your Remedy product. For more information, refer to your Remedy documentation.

Related information

For general information about the Remedy gateway, refer to “How the VitalSuite APPS Help functionality integrates with Remedy”, on page 435.

Procedure

To use the demonstration files to create a demonstration schema:

...........................................................................................................................................................................

1 Using the Remedy Admin tool, import the schema definition file (vshd.def).

Additional information: For the location and description of the definition file, refer to “Description of the Remedy demonstration files”, on page 475.

Result: Two schemas are created—VS:HelpDesk and VS:Diagnosis—and two active links.

...........................................................................................................................................................................

2 Using the Remedy Import tool, import the sample data file (vshd.arx) into the VS:HelpDesk schema.

Additional information: For the location and description of the sample data file, refer to “Description of the Remedy demonstration files”, on page 475.

...........................................................................................................................................................................

3 Using the Remedy Import tool, import the diagnosis data (vsdxrx.csv) into the VS:Diagnosis schema.

Result: The VS:HelpDesk schema refers to the VS:Diagnosis schema for the diagnosis information.

Important! You need to install the VS:Diagnosis schema only once in your environment.

...........................................................................................................................................................................

4 To start forwarding records from your VitalSuite APPS Help functionality server to the VS:HelpDesk schema, append the demonstration remedy.ini file to your remedy.ini file and place it in the <drive>:\Program Files\VitalHelp\Config directory.

....................................................................475

Set up the Remedy demonstration schema

...........................................................................................................................................................................

5 Restart the server by opening the Windows Services screen and stopping and restarting the VitalHelp service.

...........................................................................................................................................................................

6 Open the VS:HelpDesk Remedy schema.

Result: Two buttons are displayed in the VS:HelpDesk schema:

• Show Diagnosis, which lets you display diagnostic information directly from your Remedy window.

• Run Tests, which lets you run remote tests directly from your Remedy window.

Important! The Run Tests button in the VS:HelpDesk sample schema works only if the VitalSuite APPS Help functionality server is installed in the default directory (<drive>:\Program Files\VitalHelp).

...........................................................................................................................................................................

7 Refer to “Customize your Remedy environment”, on page 476 to customize your own environment using the examples provided.

...........................................................................................................................................................................E N D O F S T E P S

Description of the Remedy demonstration files

The Remedy Gateway is installed with example files in the <drive>:\Program Files\VitalHelp\Helpdesk\Remedy\backup directory. These files include an example remedy.ini file and several other files that can be imported to Remedy to install and set up a demo.

The following table describes each of the demonstration files:

File name Description

remedy.ini An example file with filters and data maps used to transfer event data to Remedy.

readme.txt Describes how to use the files in this directory to integrate the VitalSuite APPS Help functionality and Remedy.

vshd.def A Remedy export file that provides the definitions of two schemas: VS:HelpDesk and VS:Diagnosis. Two active links are also included: VS:Run Tests and VS:Show Diagnosis.

vsdxrx.csv Provides diagnosis data for the Remedy VS:Diagnosis schema.

vshd.arx Provides sample data for the demonstration schema (VS:HelpDesk).

....................................................................476

..........................................................................................................................................................................................Customize your Remedy environment

When to use

Use this procedure to incorporate the Show Diagnosis and Run Tests buttons into your Remedy environment. These buttons are described in “Set up the Remedy demonstration schema”, on page 474.

Before you begin

Know how to use the Remedy Admin tool provided with your Remedy product. For more information, refer to your Remedy documentation.

Related information

For more information about customizing your Remedy environment, refer to “Set up the Remedy demonstration schema”, on page 474.

Procedure

To customize your Remedy environment:

...........................................................................................................................................................................

1 Select the schema you want to modify.

...........................................................................................................................................................................

2 Create active links and buttons, which are similar to the ones in VS:HelpDesk, in the selected schema.

Additional information: For more details on this topic, refer to the instructions provided in the file: <drive>:\Program Files\VitalHelp\Helpdesk\Remedy\backup\readme.txt

...........................................................................................................................................................................

3 Customize the remedy.ini file to upload only the data you want.

Additional information: Use the information in “Overview of the MailGateway.ini and snmptrap.ini files”, on page 448 to customize this file.

....................................................................477

Customize your Remedy environment

...........................................................................................................................................................................

4 Do the following:

Important! The services will not restart if there are syntax errors in the remedy.ini file. To view any syntax errors, refer to a log file <drive>:\Program Files\VSCommon\webroot\logs\vhs20030612.log.

...........................................................................................................................................................................

5 After modifying the remedy.ini file, add some events that you know meet your upload criteria. Forcing events from the VitalSuite APPS Help functionality to Remedy helps you verify that your configuration performs the way you planned.

...........................................................................................................................................................................E N D O F S T E P S

If... Then...

You installed the Remedy Gateway after you had already installed the VitalSuite APPS Help functionality

Restart the server by stopping and restarting the VitalHelp service from the Windows Services screen.

You customized your remedy.ini file but already had the Remedy Gateway installed

Reinitialize the gateway:1. In the ADMIN tab, click Thresholds.2. Click VitalHelp gateways under Notification in

the menu frame.3. Click Reinitialize for the corresponding

OpenGateway module(s) that you want to reinitialize.

....................................................................478

Remedy gateway files

..........................................................................................................................................................................................Overview

Purpose

This section describes the Remedy gateway files you need to configure to update for the VitalSuite APPS Help functionality to create and modify events in your Remedy system.

Contents


Overview of the remedy.ini file 479

Data maps 480

Data map examples 481

Data fields used in the remedy.ini file 484

Filters 486

Filter examples 487

Example of a remedy.ini file 489

....................................................................479

Overview of the remedy.ini file

..........................................................................................................................................................................................Overview of the remedy.ini file

Main sections of the remedy.ini file

The remedy.ini file has three main sections, as described in the following table.

How to edit the remedy.ini file

You can use any text editor to create a remedy.ini file for your implementation. The completed file should be placed in the <drive>:\Program Files\ VitalHelp\Config directory.

We recommend that you create a test environment to verify that the desired information is being uploaded from the VitalSuite APPS Help functionality server to your Remedy application before full-scale deployment.

Section Includes

Server The name of the Remedy server and the user name and password that allow the VitalSuite APPS Help functionality server to log into the Remedy server. This information is specified during the installation process. This section can also include a retries variable that specifies the number of retries if an error occurs when adding or updating a help desk record.The user name and password must be for a user who has permission to update the data fields specified by the maps later in the file.

Maps One or more maps for each action. For a list of supported maps, refer to “Data maps”, on page 480.

Filters One or more filters for each event. For a list of supported filters, refer to “Filters”, on page 486.

....................................................................480

..........................................................................................................................................................................................Data maps

Purpose of maps

Maps are used to specify how data is loaded into the Remedy database schema. For example, a map can specify that the cause ID be placed in the Remedy Short Description field. Maps are used only if a given event has passed the filters specified earlier in the remedy.ini file.

Verify that your remedy.ini file has a map for each action for which you want to forward data to your help desk system.

Important! A data map can perform only two functions in the Remedy system. It can create a record or modify a record. The AddedMap data map is the only type of map that can add a record to Remedy, all other maps can only modify existing records. The Remedy Gateway cannot be used to delete records from the Remedy database.

A separate map may be generated for each action. If no map is set for a specific action, then no data can be uploaded to Remedy even if the filter criteria is met.

Actions and map types

The following table lists the supported actions and map types.

Each map of a given type should be numbered to ensure that the correct map is used.

Important! The AddedMap data map must contain an entry for each field required by your help desk schema that does not have a default value. It is strongly recommended that all other maps also meet this requirement.

Action Map type

When an event is added AddedMap

When an event is cleared ClearedMap

When an event is deleted DeletedMap

When an event is update UpdatedMap

When an event is reactivated ActivatedMap

When an event is aged out AgedMap

....................................................................481

Data map examples

..........................................................................................................................................................................................Data map examples

Example of an AddedMap data map

An example of a data map follows:

[10.10.10.101:AddedMap1]]table=VS:HelpDeskStatus=VHTicketStatusSeverity=VHStatusShort Description=#VHCauseIdLocation=#VHAlarmIdVHRecId=VHRecNumVHGroupId=#VHGroupIdVHTranId=VHTranIdVHTicketType=#VHTicketTypeVHServer=#VHServerIdVHClient=#VHClientIdApplication=#VHAppIdOccurrences=VHCountVHSubId=VHEventValueVHEventId=VHCauseIdNumCorrClients=VHNumClientsCorrClientInfo=#VHCorrClientsDetails=#VHDetailsComments=#VHComments

Characteristics

The provided example has the following characteristics:

• The item to the left of the equals sign is the name of a field in the Remedy database schema.

• The value to the right of the equals sign is the value or data field value that should be placed in the specified Remedy field. For a list of data fields, refer to “Data fields used in the remedy.ini file”, on page 484.

• The “#” in front of a field name removes the name of the field and enters only the value of the field in the Remedy database.

• Literal strings to the right of the equals sign must be enclosed in square brackets ([...]).

....................................................................482

Line descriptions

The following table describes each line in the example AddedMap data map.

Map line Description

[10.10.10.101:AddedMap1] Identifies this section as the first map for add actions for the Remedy help desk defined as the server IP address of 10.10.10.101.

table=VS:HelpDesk Defines the name of the Remedy database schema into which data is being loaded.

Status=VHTicketStatus Defines the variable (VHTicketStatus) that is written into the Remedy Status field.

Severity=VHStatus Defines the variable (VHStatus) that is written into the Remedy Severity field.

Short Description=#VHCauseId Defines the variable that is written into the Remedy Short Description field. In this case, only the value of the VHCauseId variable is written, not the variable name.

Location=#VHAlarmId Defines the variable (VHAlarmId) that is written into the Remedy Location field.

VHRecId=VHRecNum Defines the variable (VHRecNum) that is written into the Remedy VHRecld field.

VHGroupId=#VHGroupId Defines the variable (VHGroupId) that is written into the Remedy VHGroupId field.

VHTranId=VHTranId Defines the variable (VHTranId) that is written into the Remedy VHTranld field.

VHTicketType=#VHTicketType Defines the variable (VHTicketType) that is written into the Remedy VHTicketType field.

VHServer=#VHServerId Defines the variable (VHServerId) that is written into the Remedy VHServerId field.

VHClient=#VHClientId Defines the variable (VHClientId) that is written into the Remedy VHClientId field.

Application=#VHAppId Defines the variable (VHAppId) that is written into the Remedy VHAppId field.

Occurrences=VHCount Defines the variable VHCount that is written into the Remedy Occurrences field.

VHSubId=VHEventValue Defines the variable VHEventValue that is written into the Remedy VHSubId field.

VHEventId=VHCauseId Defines the variable VHCauseId that is written into the Remedy VHEventId field.

....................................................................483

Data map examples

Examples of other data maps

Data maps can be created for other actions such as updating a record, aging, clearing, deleting, or activating records. However, once a help desk record has been created, the VitalSuite APPS Help functionality can only modify the record, not remove it. Examples of other data maps follow:

[server1:UpdatedMap1]Comments=#VHCommentsStatus=VHTicketStatusVHTicketType=#VHTicketTypeNumCorrClients=VHNumClientsCorrClientInfo=#VHCorrClientsWork Log=[updated by VitalHelp server]

[server1:AgedMap1]Status=VHTicketStatusWork Log=[aged out by VitalHelp server]

[server1:ClearedMap1]Status=VHTicketStatusWork Log=[cleared in VitalHelp server]

[server1:DeletedMap1]Status=VHTicketStatusWork Log=[deleted from VitalHelp server]

[server1:ActivatedMap1]Status=VHTicketStatusWork Log=[reopened in VitalHelp server]

NumCorrClients=VHNumClients Defines the variable VHNumClients that is written into the Remedy NumCorrClients field.

CorrClientInfo=#VHCorrClients Defines the variable (VHCorrClients) that is written into the Remedy CorrClientInfo field.

Details=#VHDetails Defines the variable (VHDetails) that is written into the Remedy Details field.

Comments=#VHComments Defines the variable (VHComments) that is written into the Remedy Comments field.

Map line Description

....................................................................484

..........................................................................................................................................................................................Data fields used in the remedy.ini file

Purpose of data fields

Whenever an event is logged, data is recorded for each of the fields described in this topic. When you create a data map, you must specify which health record data fields you want to upload to Remedy and where to place them.

Data field descriptions

The following table describes the health record data fields. Use the field names provided in the following table in your data maps.


VHAlarmId Unique ID that identifies the problem (alarm) location as identified by VitalAgent:3000 = server3001 = network3002 = client3003 = modem3005 = network3006 = network3007 = network3008 = network3009 = network3010 = network3011 = network3016 = server

VHAppId Unique ID that identifies the application that encountered the problem. Refer to “Application IDs”, on page 458 for a detailed list of the applications and the associated numbers.If you place an “i” in front of the field name, an integer value is returned that represents the application.

VHCauseId Unique ID that identifies the cause of the event. This is the event number that is used in the event field of a filter. This field, therefore, cannot be used in the condition field of a filter.

VHClientId Unique ID sent by the VitalAgent or VitalAgentIT to identify itself. For correlated events, this ID identifies the first client to report the event.

VHComments Text that the user entered into the comment field of the VitalHelp Diagnosis window.

VHCorrClients Encoded list (binary data) of client names that reported the event. Because this field is represented in binary, it cannot be used in the condition field of a filter.

....................................................................485

Data fields used in the remedy.ini file

VHCount Number of times the event has been reported for a particular client or the total number of client counts when there are correlated events.

VHDetails Encoded (binary data) event information. Because this field is represented in binary, it cannot be used in the condition field of a filter.

VHDomainId Unique ID that identifies the name of the domain.

VHEndTime The most recent time the event was reported.

VHEventValue Number that further identifies the cause of the event.

VHGroupId Unique ID that identifies the group of the client. If the client is remote, this value is 1; otherwise, GROUPID is the subnet that the client uses.

VHNumClients Number of unique clients that reported the event.

VHRecNum Ticket (record) number.

VHServerId Unique ID that identifies the server.

VHStartTime First time the event was reported.

VHStatus Event status:4 = yellow (warning)5 = red (failure)

VHTicketStatus Ticket status:0 = unknown1 = new4 = closed7 = aged out8 = deleted

VHTicketType Indicates if the event is single or correlated:0 = unknown1 = single2 = correlated

VHTranId Application transaction ID number.

VHUpdateTime Last time the record status was changed.


....................................................................486

..........................................................................................................................................................................................Filters

Purpose of filters

Filters are used to evaluate whether events should trigger a data upload from the VitalSuite APPS Help functionality server to the Remedy system. You can create one or more filters for each event.

Format

Filters are created in the following format:

[server1:filter#]events=eventIDactions=added, updated, aged, cleared, deleted, activatedcondition#=<vhfield><operator><value>

Parts of a filter

The following table describes each part of a filter.

A record must pass all criteria in a filter before it is forwarded to Remedy. If multiple filters specify the same event, only one of the filters must be satisfied for the record to be forwarded to Remedy. In other words, each entry in a filter is AND’ed together. Separate filters for the same event are OR’ed.


events This field specifies the ID numbers for one or more events on which this filter triggers. Separate multiple events with commas. For example, if the event is 3050 (Client CPU load), when this event occurs and if the rest of the filter criteria is met, data is sent to the Remedy system. The VitalSuite Application Performance Management Software Help Functionality List of Events gives a list of valid events.

actions This field contains one or more of the following, separated by a comma: added, updated, deleted, cleared, activated, or aged.

condition# This field specifies the conditions that must be met in order to upload an event. The format of this field is the health record data field name followed by an operator such as =, < >, >, >=, <, <=, then a value. For example, VHCount > 10 means that this condition is met when the specified event has occurred more than 10 times.

....................................................................487

Filter examples

..........................................................................................................................................................................................Filter examples

Purpose

This topic provides examples of how you can write filters.

Example 1

The following two filters specify that event 3050 is forwarded to server1 if the total occurrences of this event is a multiple of 10 OR if the number of clients reporting this event is a multiple of 5.

[server1:filter1]events=3050actions=added,updatedcondition1=VHCount % 10

[server1:filter2]events=3050actions=added,updatedcondition2=VHNumClients % 5

Example 2

In the following filter, event 3050 is forwarded to server1 when the total occurrences of this event is a multiple of 10 AND the number of clients reporting this event is greater than 5.

[server1:filter1]events=3050actions=added,updatedcondition1=VHCount % 10condition2=VHNumClients > 5

Example 3

This filter forwards data about event 3053 to Remedy when this event occurs to a single client more than two times.

[server1:filter1]events=3053actions=added,updatedcondition1=VHCount > 2

....................................................................488

Example 4

This filter forwards data about event 3053 to Remedy when two or more clients report this event.

[server1:filter1]events=3053actions=added,updatedcondition1=VHNumClients > 2

Example 5

This filter forwards data to Remedy whenever any event is reported to the VitalSuite APPS Help functionality server.

[server1:filter1]events=ALLactions=ALL

....................................................................489

Example of a remedy.ini file

..........................................................................................................................................................................................Example of a remedy.ini file

Purpose

This topic provides an example of a complete remedy.ini file. Use this example to help generate your own remedy.ini file.

Example

; This is a VitalHelp (VH) help desk configuration file for the ; sample "VS:HelpDesk" schema (a clone of the "HD-HelpDesk" schema ; supplied by Remedy). This config file is supplied as an example ; of the "remedy.ini" file needed in the ...\VitalHelp\Config ; directory. A stub file, with the server/user/password ; information entered by the person that installed VH, is placed ; there by the installation -- but it must be edited to fit your ; environment.

; The server sections contain the info provided at installation ; time. The password is encrypted (the "Demo" user has no ; password). The "retries=0" line CAN be used when testing your ; map file for errors. This line disables retries if an error ; occurs when adding or updating a help desk record. If you do add ; this line, remember to either remove it or change it to a ; reasonable value after testing.

; The "table=" entry is the default table for a map that doesn't ; explicitly specify a table.

[server1]server=lab-pc1user="Demo"password=retries=0table=VS:HelpDesk

; The map sections contain the information needed to create an ; entry in a help desk table/schema. This includes the mapping ; between the VH event data and the help desk schema fields. In ; particular, the "added" maps must contain an entry for each ; required help desk schema field that does not have a default. ; There are one or more maps for each of the six VH actions in ; standard "<name> = <value>" format. The <name> field may be ; "table" or a help desk field name or id. The <value> field may ; be a number, a string optionally enclosed in square brackets ; "[]", or one or more VH fields (see list below). By default, a ; title (label) is provided for each VH field; preceding the field ; name with a pound sign "#" suppresses the title.

; Note! you can not use the delete -- or any other -- map to delete ; a record from the help desk system. Once a record has been ; created, it can only be updated.

....................................................................490

[server1:AddedMap1]table=VS:HelpDeskStatus=VHTicketStatusSeverity=VHStatusShort Description=#VHCauseIdLocation=#VHAlarmIdVHRecId=VHRecNumVHDomainId=name of domainVHGroupId=#VHGroupIdVHTranId=VHTranIdVHTicketType=#VHTicketTypeVHServer=#VHServerIdVHClient=#VHClientIdApplication=#VHAppIdOccurrences=VHCountVHSubId=VHEventValueVHEventId=VHCauseIdNumCorrClients=VHNumClientsCorrClientInfo=#VHCorrClientsDetails=#VHDetailsComments=#VHComments

[server1:UpdatedMap1]Comments=#VHCommentsStatus=VHTicketStatusVHTicketType=#VHTicketTypeNumCorrClients=VHNumClientsCorrClientInfo=#VHCorrClientsWork Log=[updated by VitalHelp server]

[server1:AgedMap1]Status=VHTicketStatusWork Log=[aged out by VitalHelp server]

[server1:ClearedMap1]Status=VHTicketStatusWork Log=[cleared in VitalHelp server]

[server1:DeletedMap1]Status=VHTicketStatusWork Log=[deleted from VitalHelp server]

[server1:ActivatedMap1]Status=VHTicketStatusWork Log=[reopened in VitalHelp server]

; The filter sections contains the information that determines ; which VH events are forwarded to the help desk system. The ; selection is made by using the events=, actions=, and ; conditionX=fields.

....................................................................491


; The events= field is a list of one or more VH event ids; separated by commas. The VHEventId field of a health record is ; compared to the values in this list; if there is a match, the; record passes this part of the filter.

; The actions= field is one or more of 'activated',; 'added','aged', 'cleared', 'deleted', or 'updated'. If the; action being done to the health record matches one of the; actions in the list, the record passes.

; The conditionX= fields are in the format: <VH-field> <oper>; <value> where <VH-field> is a valid VH health log record field ; name, <oper> is one of =, <>, >, >=, <, <=, and <value> is a; number or string. If the condition specified is met, the record ; passes.

; A record must pass all criteria in a filter for it to be; forwarded. In other words, the criteria of a filter are ANDed; together. If multiple filters specify the same event, only one ; of the filters need be satisfied for the record to be forwarded ; to the help desk. In other words, separate filters for the same ; event are ORed together.

; Examples:

; [server1:filter1]; events=3050; actions=added,updated; condition1=VHCount > 10

; [server1:filter2]; events=3050; actions=added,updated; condition2=VHNumClients > 5

; In these two filters, event 3050 (client cpu load) will be; forwarded to 'server1' when a VH record is added or updated if ; the number of clients reporting this event is greater than 5 OR ; the total occurrences of this event exceeds 10.

; [server1:filter1]; events=3050; actions=added,updated; condition1=VHCount > 10; condition2=VHNumClients > 5

; In this filter, event 3050 (client cpu load) will be forwarded ; to 'server1' when a VH record is added or updated if the number ; of clients, reporting this event is greater than 5 AND the total ; occurrences of this event exceeds 10.

....................................................................492

;[server1:filter1]; events=3053; actions=added,updated; condition1=VHCount > 2

; This filter forwards the event when the number of times it; occurs to a single client exceeds two.

; [server1:filter1]; events=3053; actions=added,updated; condition1=VHNumClients >= 2

; This filter forwards the event when two or more clients report ; it.

; The filter below forwards all events for all actions to; 'server1'. This is the filter used to forward events to; "VS:HelpDesk".

[server1:filter1]events=ALLactions=ALL

; List of VitalHelp health record fields

; Field name Description; VHRecNum Record number; VHDomainId Name of domain; VHGroupId Group id (e.g. subnet); VHAlarmId Problem location (client, server, network, etc); VHCauseId Problem type; VHAppId Application id; VHTranId Transaction id; VHServerId Server id; VHClientId Client id; VHCount Number of occurrences of this problem; VHEventValue Event specific value; VHStartTime First time event occurred; VHEndTime Last time event occurred; VHUpdateTime Last time event changed state; VHStatus Event status (warning, error, etc); VHTicketStatus Ticket status (new, pending, closed, etc); VHTicketType Ticket type (single, correlated); VHComments Event comments (from VH console); VHNumClients Number of correlated clients; VHCorrClients Correlated client information; VHDetails Event specific details

List of VitalHelp event ids

; Id Description; 1 Transaction failure; 2 Low throughput

....................................................................493


; 3 Long transaction time; 4 High server delay; 5 High server load; 6 Connection refused; 7 Connect failed; 8 Send packet loss index; 9 Receive packet loss index; 10 Unknown application; 11 Low receive throughput; 12 High network delay; 101 DNS query failure; 126 Page transfer failure; 151 SMTP hello failure; 152 SMTP send failure; 153 POP3 login failure; 154 POP3 receive failure; 155 POP3 delete failure; 3050 Client CPU load; 3051 Client low memory; 3052 Client IP configuration; 3053 Client DNS configuration; 3056 Client datalink errors; 3057 Client altDNS configuration; 3061 Client TCP errors; 3100 Modem state; 3101 Modem baud rate; 3102 Modem DTE configuration; 3103 Modem DUN errors; 3150 ISP route status; 3154 Intranet route status; 3155 Internet route status; 3157 Network IP errors

....................................................................494

Example of setting a Mail Gateway filter based on VitalAgent type

The following example has been added to mailgateway.ini to show how to set up a filter based on VitalAgent type. (If All VitalAgent types are selected in the Web Console, there is no need for a gateway VitalAgent filter).

VHAgentType values Example filter (Automon)

0 = unknown

;[10.10.101.10:filter1];events=ALL;actions=added, updated;condition1=iVHAgentType=3

3 = Automon

4 = VitalAgent

6 = VitalAgentIT

7 = Mid-tier

....................................................................495

..........................................................................................

..........................................................................................

Index

A accessing the help system, xvaccounts, 38actions

Mail Gateway, 452Remedy AR System, 486SNMP Gateway, 452

addingregistry flags, customized VitalAgent

icon, 182VitalSuite NET resources manually, 337

addresses, list of URLs, 154Aggregation Editor, 421aggregation time, changing, 421Analysis database, move, 247animated bitmaps, customizing, 179ART database, move, 291attaching databases, 215authentication server, remote

accounts, 38adding accounts, 39enabling, 42passwords, 39required administrators, 38using, 37vslistuser utility, 40

authentication, remote, 37

B back upother considerations, 205schedule, 206

backing upVitalSuite APPS databases, 194VitalSuite APPS file systems, 196VitalSuite NET databases, 187, 189VitalSuite NET file systems, 189

..........................................................................................

backupconsiderations for VitalSuite NET

UNIX, 186considerations for VitalSuite NET

Windows, 193guidelines for VitalSuite NET UNIX,

185procedures for VitalSuite APPS and

VitalVitalSuite NET, 197procedures for VitalSuite NET UNIX,

190script for VitalSuite NET data, 189to a network drive, 203UNIX script, 189

bitmaps, icons, 179bmp icon animation files, 179branding

guidelines, 170login page, 173My Reports page, 175My Vital page, 176reports pages, 174Web console, 172Web Console pages, 170

browser settingsanimated gif settings, 144recommended for Mozilla, 152recommended for Netscape, 152recommended standard settings, 145

C certifying authorities, SSL, 20change

VitalSuite APPS IP address, 77VitalSuite NET IP address on UNIX, 60VitalSuite NET IP address on Windows,

50CIAgent UNIX installation, 397CIAgent Windows installation, 395command line options of VCC, 159command options, VAServerMapTable

utility, 161comment, how to comment, xix

....................................................................496

..........................................................................................

common sign-on, 37conditions


config.html, 14conventions, typographical, xivcookies, 144, 152corporate logos, 170cron.log, 117, 128, 135custom images, 172customer_message.txt, 177customizing

icons, 179icons, registry setting, 182login page, 173My Reports page, 175My Vital page, 176reports pages, 174VitalAgent bitmaps, 179VitalAgent icon, 179

D datafields, described, 456, 484maps

actions, 480

example, 480

for help desk integration, 480

database configuration tables, customized icons, 182

database directoriesbacking up in VitalSuite NET, 189IP address update, VitalSuite APPS

Analysis functionality, 85IP address update, VitalSuite NET, 61,

66VitalSuite APPS, 194VitalSuite NET, 187

databases, attaching, 215disk check interval, 157

..........................................................................................

..........................................................................................

distributed environment IP address change, VitalSuite APPS Analysis functionality, 92

documentation set, xviVitalSuite APPS, xviVitalSuite NET, xvii

documentation, order additional, xixdownloading

list of URLs, 154Transact Toolkit, 154VitalAgentIT, 154

DSNodbc.ini file, 69, 72resolving servermaptable issues, 160VitalSuite NET IP address change, 62,

69

E education services, xvemail systems, 431error log, creating, 138event ID


F file systems, restoring, 217files

backing upin VitalSuite APPS, 196

in VitalSuite NET, 189

Helpdesk.exe file, 443MailGateway.ini file, overview, 448mailtemplate.ini file, 464remedy.ini file

data fields, 484

example, 489

overview, 479

snmptemplate.ini file, example, 468

....................................................................497

..........................................................................................

..........................................................................................

snmptrap.ini fileexample, 460

overview, 448

vsdxrx.csv file, 474vshd.arx file, 474vshd.def file, 474

filtershelp desk integration, 486Mail Gateway, 452SNMP Gateway, 452SNMP Gateway examples, 455

find utility, log files, 138firewall considerations, 3flags, registry settings, VitalAgent custom

icons, 182flow limits for RMON2, 407FTP

Secure Shell, 32, 33SSH public key authentication, 34

G gatewaysmail filter, VitalAgent types, 494moving Master Gateway to Posting

server, 440reinitialize, 446, 477using with VitalSuite APPS Help

functionality, 427guidelines

backup schedule, 206corporate branding, 170customizing VitalAgent icon, 179

H Help database, move, 269help desk system

API, 436creating data maps, 480creating filters, 486customizing, 476example schema, 475

..........................................................................................

integrating with VitalSuite APPS Help functionality, 435

help, accessing, xvHelpdesk.exe file, 443

I iconsbitmaps for, 179corporate branding, 172VitalAgent, 179

ifType codes, 327images, customizing pages, 172installing

CIAgent on UNIX, 397CIAgent on Windows, 395Mail Gateway component, 442Remedy component, 471SNMP Gateway component, 442

interface type codes, 327Internet Explorer, recommended settings,

144, 152IP addresses

bypass a proxy server, 146changing for VitalSuite APPS, 77changing in a VitalSuite NET UNIX

environment t, 60changing in a VitalSuite NET Windows

environment, 50Configuration server, 79database scripts

VitalSuite APPS Analysis functionality multi-server, 92

VitalSuite APPS Analysis functionality single-server, 89

VitalSuite APPS single-server, 86

database update, 85MS-SQL Server, 85new license key, 95server reboot, 155servers and registry key, 94VitalAgent upload targets, 79

....................................................................498

..........................................................................................

VitalAgentIT client retarget, 98VitalSuite NET Master as System

Master, 83VSSyncTimeTable, 83

L log filescomplete list for VitalSuite APPS

Analysis functionality, 129complete list for VitalSuite APPS Help

functionality, 135complete list for VitalSuite NET, 118location, 116using the find utility, 138VAServerMap utility, 161, 163VitalSuite APPS Analysis functionality

examples, 132VitalSuite NET examples, 123

log files, VitalSuite APPS Analysis functionality

cron.log, 128VAA....log, 128VAC....log, 128VAG....log, 128VAQ....log, 129VAR....log, 129VSW....log, 129

log files, VitalSuite APPS Help functionalitycron.log, 135VHS.log, 135VSW....log, 135

log files, VitalSuite NETcron.log, 117VN_Discovery, 117VNDD....log, 117VNE....log, 117VNS....log, 117VNT....log, 117VSC....log, 118VSP....log, 118

loginlocal server password, 39remote authentication server, 39

..........................................................................................

login message, 177logo size recommendations, 170logos

adding to Web console, 172corporate, 170

logs, VCC for VitalSuite APPS Analysis functionality uploads, 159

M mailGateway

actions, 452

condition, 453

creating filters, 452

event ID, 452

health record data fields, 456

installing, 442


template file, 464, 468Mail Gateway, 427MailGateway.ini file, overview, 448message, adding to login page, 177missing resource data, resolving, 343move databases

Analysis, 247ART, 291Help, 269VitalSuite NET, 219

Mozillabrowser settings, 152proxy settings, 152

MS-SQL Serverdatabase tables, 85enabling to back up to a network, 203Enterprise Manager, 85IP address change scripts, 85

MS-SQL, ODBC, 8My Reports, chaning maximum number of

resources included, 423, 425

....................................................................499

..........................................................................................

..........................................................................................

..........................................................................................

N Navis Identity Software, 37, 42NavisXtend, resolving common problems,

418Netscape

browser settings, 152proxy settings, 152

network alarm measurements, VitalSuite NET resource types, 368

nightly sync, deleting obsolete source addresses, 83

O ODBCMS-SQL, 8Oracle, 8VitalSuite APPS Analysis functionality

data transfer, 6openURL utility, 107Oracle, ODBC, 8

P passwords, 39performance enhancements, enhancements,

139performance, VitalSuite NET, performance

enhancements, 139port 2474, reconfiguring, 9port numbers, firewall considerations, 3port, VitalSuite APPS Analysis functionality

registry and services tasks, 13verification, file modification, 14Web Console configuration, 11

printingPDFs, 156using the web browser, 156

protocolsport numbers, 3VitalSuite NET-defined defaults, traffic

monitoring, 316proxy servers

bypassing in Internet Explorer, 146VCC command line option for, 159

..........................................................................................

..........................................................................................

proxy settingsMozilla, 152Netscape proxy setting, 152

Q quality index parameters, VitalSuite NET resource types, 355

R RADIUS, 37, 42rebooting, UNIX servers, 420registry variables

for creating VitalAgent upload logs, 159for custom icons, 182for disk check interval, 157

reinitialize, gateways, 446, 477Remedy AR System

actions, 486application programming interface

(API), 436condition, 486customizing, 476data fields, 484data maps, 480event ID, 486example schema, 475filters, 486

remedy.ini filedata fields, 484example, 489overview, 479

remote authentication, 37accounts, 38administrator, 38

remote authentication serveraccounts, 38adding accounts, 39enabling, 42passwords, 39required administrators, 38using, 37

remote authentication server vslistuser utility, 40

....................................................................500

..........................................................................................

replacing corporate logos, 170reports, printing, 156resolving missing resource data, 343resources

changing maximum allowed in My Reports, 423, 425

restarting services, 97restore

file systems, 217guidelines, 208UNIX script, 189using VitalSuite NET UNIX script, 210VitalSuite APPS and VitalSuite NET,

212RMON2 flow limits, 407

changing, 408

S schema for Remedy AR System, 475Secure Shell FTP, 32, 33

public key authentication, 34secure socket layer (SSL)

disabling on UNIX, 30disabling on Windows, 25enabling on UNIX, 27enabling on Windows, 22overview, 20

servers, protocols and port numbers, 3services

restarting, 97VitalHelp, 97

shutting down, UNIX servers, 420SNMP

Gatewayactions, 452

condition, 453

creating filters, 452

event ID, 452

health record data fields, 456

installation instructions, 442

..........................................................................................


network management systems, 433timeout, 352

SNMP Gateway, 427snmptrap.ini file

example, 460overview, 448

source address, nightly sync, 83SSH protocol, 33SSL

disabling on UNIX, 30disabling on Windows, 25enabling on UNIX, 27enabling on Windows, 22overview, 20

stopping CIAgent on UNIX, 397stopping CIAgent on Windows, 395System Application MIB, 394system tray icon, customizing, 179

T technical notes and tips, 141technical support, xixtext message, adding to login page, 177thresholds

network alarm measurements, 368quality index parameters, resource types,

355timeout, changing default value for SNMP,

352tips and technical notes, 141training, education services, xvTransact Toolkit, downloading, 154transactions

VitalAgent, 5VitalSuite APPS Analysis functionality,

6VitalSuite APPS Help functionality, 7VitalSuite NET, 7

trouble ticketing systems, 435

....................................................................501

..........................................................................................

..........................................................................................

troubleshootingagent accelerator keys, 158connection issues, 165tips, 164VCC log file, 159Windows services, 166

typographical conventions, xiv

U UNIX backup script, 189UNIX restore script, 189URLs

additional documentation, xixlist of common, 154technical support, xv

V VAA....log, 128VAC....log, 128VAG....log, 128VAQ....log, 129VAR....log, 129VAS.txt, 161VAServerMap utility, command options,

161VAServerMapUtil.exe, 160VAU.txt, 163VCC

command line options, 159log file, 159

verifyingserver addresses, 165services, 166

VHS....log, 135VitalAgent

Automon, downloading, 154icons, customizing, 179port, VitalSuite APPS Analysis

functionality data, 9VCC program, 159

VitalAgent icon, customizing, 179

VitalAgentITdownloading, 154retargeting after IP address change, 98

VitalSuite APPS Analysis functionalityagent posting port, 9port 2474 reconfigure, 9resolving database DNS issues, 160

VitalSuite APPS documentation set, xviVitalSuite APPS Help functionality

data maps, 480Gateways, single/multiple Posting

servers, 438HelpDesk installation, 471integrating with

email systems, 431

help desk applications, 435

SNMP network management systems, 433

Mail Gateway VitalAgent filter, 494moving Master Gateways to a Posting

server, 440using with

Mail Gateway, 427

SNMP Gateway, 427

VitalSuite Apps, see VitalSuite APPSVitalSuite ART, see VitalSuite Advanced

Reporting ToolVitalSuite NET database, move, 219VitalSuite NET documentation set, xviiVitalSuite NET, adding resources manually,

337VN_Discovery....txt, 117VNDD....log, 117VNE....log, 117VNS....log, 117VNT....log, 117VSC....log, 118vsdxrx.csv file, 474vshd.arx file, 474vshd.def file, 474

....................................................................502

..........................................................................................

vslistuser utility, 40vsopenURL utility, 107

use cases, 111VSP....log, 118VSSyncTimeTable, 83VSW....log, 129, 135

W Web browser, recommended settings, 144, 152

web_disk_space_check_interval, 157Windows, troubleshooting services, 166

tech ref guidemasuninetinet.uninet.net.mx/docs/vitalsuite/adv10.pdf · 2006-04-11 · change the...

Documents