Lucent Gateway Platform

Advanced Traffic Collection for the

Advanced Reporting System
Installation & Setup Guide

Part Number 255-400-202R9.8.0.0

Issue 7, November 23, 2005
Software Version 9.8.0.0
Lucent Technologies - Proprietary
This document contains proprietary information
of Lucent Technologies and is not to be disclosed or used
except in accordance with applicable agreements

Copyright  2005 Lucent Technologies

Unpublished and Not for Publication
All Rights Reserved
Copyright 2005 by Lucent Technologies. All Rights Reserved.

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.

For permission to reproduce or distribute, please contact the following:

Product Development Manager 1 888-LTINFO6 (domestic)

1-317-322-6848 (international)

Notice

Every effort has been made to ensure that the information in this document was complete and accurate at the time of printing. However,
information is subject to change.

Mandatory customer information

Safety

Always observe the Safety Instructions when operating the system.

Trademarks

All trademarks and service marks specified herein are owned by their respective companies.

Ordering information

The order number of this document is 255-400-202R9.8.0.0

Support

Technical support

Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document.

Information product support

To comment on this information product online, go to http://www.lucent-info.com/comments or email your comments to comments@lucent.com.
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

Table of Contents
1. Overview................................................................................................................................................5
2. About This Issue ....................................................................................................................................5
3. Advanced Reporting System with Advanced Traffic Collection Setup Overview................................5
4. Advanced Reporting System Licensing Overview ................................................................................6
5. Prepare and Install or Upgrade the Advanced Traffic Collector ...........................................................6
5.1 Overview....................................................................................................................................6
5.2 Advanced Traffic Collector Hardware Partitioning...................................................................7
5.2.1 Minimum Configuration Option ....................................................................................8
5.2.2 Standard Configuration Option......................................................................................8
5.2.3 Ideal Configuration Option ............................................................................................9
5.3 Optimize Disk Layout for the Advanced Traffic Collector .......................................................9
5.4 Installing or Upgrading the Advanced Traffic Collector Server ...............................................9
5.5 Install Oracle and StatsCollector on the Advanced Traffic Collector Server ..........................10
5.5.1 Required Solaris Patches for Oracle ............................................................................10
5.5.2 Required Solaris Packages for Oracle..........................................................................11
5.5.3 Install Optional External Package SMCtop .................................................................12
5.5.4 Install Oracle................................................................................................................12
5.6 Install or Upgrade the StatsCollector Software .......................................................................13
5.7 Prepare the EMS Server for ARS with ATC ...........................................................................21
5.8 Set Reporting Switch Properties ..............................................................................................22
5.9 Set the PlexView Server Oracle Database to support Advanced Reporting............................24
6. Edit the List of Switches Reporting to StatsCollector .........................................................................25
7. Advanced Reporting System Installation.............................................................................................25

Lucent Technologies 3 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Notes:

4 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

1. Overview
This document is a step-by-step guide to installing or upgrading the PlexView
Advanced Traffic Collection Software.

Note: If you are installing the Advanced Reporting System without the
optional Advanced Traffic Collector, you do not need this procedure.

The Advanced Traffic Collector is an application that reports into the

Advanced Reporting System. It samples the TSAA (Lucent Statistical
Analysis Application) and TCA (Traffic Collection Application) software that
resides in the Billing and Traffic System. An Advanced Reporting System
with the Advanced Traffic Collector can generate reports with switch traffic
information.

Note: The ATC (Advanced Traffic Collector) is part of the Advanced

Reporting System. The TCA (Traffic Collection Application) is part of
the Billing and Traffic System. The ATC collects information from the
TCA. ATC requires TCA, but TCA does not require ATC.

2. About This Issue

This document has been updated from Issue 6 to Issue 7 to separate the Oracle
installation from the installation of the Advanced Traffic Collector software.
The Advanced Traffic Collector software installation has also been updated
and now runs from a user-friendly GUI.

3. Advanced Reporting System with Advanced Traffic Collection Setup Overview

This overview presents guidelines that you should consider when planning
where to co-locate servers before deploying the Advanced Reporting System
with Advanced Traffic Collection into your network.

The Advanced Traffic Collector is a distributed application consisting of

many servers. The Advanced Traffic Collection system supports either
centralized or distributed data collection architectures, allowing extensive
scalability and flexibility. That flexibility is necessary to capture and analyze
large volumes of data.

Co-locating some servers supports best performance practices. For example:

• Having the EMS and the Advanced Traffic Collector on the same subnet
assures optimum system performance for inter-machine communication
• Having the Business Objects client on the same subnet as the EMS assures
best performance when exporting a universe or creating and executing
reports

Lucent Technologies 5 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Instructions for optimizing the Advanced Traffic Collector server’s database

layout to enhance performance within each server are included within this
document.

You must know the name of each switch that the Advanced Traffic Collector
will collect statistics on prior to running the StatsCollector software
installation. The name must be identical to the switch’s SID name as
displayed in the status bar of the EMS Navigator.

The Advanced Reporting System with Advanced Traffic Collection is a

distributed application that must be installed sequentially according to these
instructions. All installation steps are listed in order. For some advanced third-
party software configurations that goes beyond the scope of a general
installation and configuration, you will be referred to the third party
software’s company’s installation or configuration instructions.

Note: A qualified IT professional should do all installations or upgrades.

Each installation section in this document is presented in the sequence that

leads to a correct installation.

4. Advanced Reporting System Licensing Overview

The PlexView Advanced Traffic Collection software requires a license. The
EMS licensing form that you can use to apply for a license is included on a
licensing disk in your CD package. After submitting the forms, please allow
two business days for licenses to be emailed to you prior to installing this
PlexView Advanced Traffic Collection software.

5. Prepare and Install or Upgrade the Advanced Traffic Collector

5.1 Overview

The Advanced Traffic Collector application runs on its own Sun server and
has its own database. The traffic collector does not depend on the EMS in any
way. The EMS depends on the advanced traffic collector for traffic statistics
and will establish an ODBC connection to the advanced traffic collector
server to access traffic data. The PlexView Advanced Traffic Collector
software provides the StatsCollector database and the StatsCollector
application for the Advanced Traffic Collector server.

Note: The ATC (Advanced Traffic Collector) requires that a switch report
billing and traffic information to the TCA (Traffic Collection
Application) software. That TCA application, part of the BTS (Billing
and Traffic System), must be configured and running for the ATC to
collect traffic statistics.

6 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

Note: The server that will be the Advanced Traffic Collector must not have
any prior versions of Oracle on it. If it does, Oracle must be
COMPLETELY uninstalled before installing the PlexView Advanced
Traffic Collection software. Verify that all Oracle files in /var are
removed as well. Failure to completely uninstall Oracle can produce
undesirable results.

The StatsCollector software is shown in the following figure.

Figure 1. StatsCollector on the Advanced Traffic Collector Server

5.2 Advanced Traffic Collector Hardware Partitioning

The Advanced Traffic Collector server has three hardware partitioning options
listed in the Advanced Reporting System Software Release Notice. The three
options are:

• Minimum configuration
• Standard configuration
• Ideal configuration

Note: An IT professional should execute your configuration choice.

Lucent Technologies 7 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

This section provides details about partitioning. Options include:

5.2.1 Minimum Configuration Option

Use one 36G hard drive or two 36G hard drives with one drive acting as a
mirror. The operating system (OS) and Oracle database reside on the same
physical disk partition, but this degrades performance.

The commands to check your setup are:

swap-l
df-k
Set up these partition parameters:

• Swap 2 GB
• / 4 GB
• /usr 4 GB
• /opt Allocate the remaining space

Note: The same configuration applies whether the dual server disk is mirrored
by Sun Solstice or by Veritas Volume Manager.

Note: If mirroring is not used, the system should be periodically backed up, so
that the data can be recovered if the disk fails.

5.2.2 Standard Configuration Option

Use two 36G hard drives. To improve performance, put the operating system
and the Oracle database on separate physical disk partitions.

Set up these partition parameters for disk 1:

• Swap 2 GB
• / 4 GB
• /usr 4 GB
• /opt Allocate the remaining space

Set up these partition parameters for disk 2:

• /opt/PlexView/Oracle/ora02 36 GB

Note: Periodic backups are required.

8 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

5.2.3 Ideal Configuration Option

Use Two 36G hard drives with one drive acting as a mirror and use a RAID
Level 5 device for data read/write. Putting the operating system and Oracle on
separate physical disk partitions on the active drive and putting the Oracle
data on a RAID device eliminates the need for periodic backups.

Set up these partition parameters for the disks:

• Swap 2 GB
• / 4 GB
• /usr 4 GB
• /opt Allocate the remaining space

For the RAID level 5 device:

• Mount as /opt/PlexView/Oracle/ora02

Note: Periodic backups are not required.

5.3 Optimize Disk Layout for the Advanced Traffic Collector

The Advanced Traffic Collector can process high-volume traffic data if you
optimize its physical database layout. System performance will improve if you
add additional physical disk drives and map them to the Oracle data
directories. Lucent recommends that each directory map to a separate disk.

Note: An IT professional should perform this disk layout setup.

Mount the additional disks to the following directories:

/opt/PlexView/Oracle/ora02/oradata/statsdw/data
/opt/PlexView/Oracle/ora02/oradata/statsdw/system
/opt/PlexView/Oracle/ora02/oradata/statsdw/rbs
/opt/PlexView/Oracle/ora02/oradata/statsdw/index
/opt/PlexView/Oracle/ora02/oradata/statsdw/redo
5.4 Installing or Upgrading the Advanced Traffic Collector Server

If you are installing the Advanced Reporting Traffic Collection Stats Collector
Install CD for the first time, use the Install section 5.5 then skip to section 1.1.

Lucent Technologies 9 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

If you are upgrading the Advanced Reporting Traffic Collection Stats

Collector software, go to Upgrade section 1.1.

5.5 Install Oracle and StatsCollector on the Advanced Traffic Collector Server

For a new installation, you must first install Oracle, and then install the
Advanced Traffic Collector software.

Note: For upgrades, do not perform this procedure. Go to section 1.1.

Caution: Using the install files to perform an upgrade will result in the loss of
all data in the StatsCollector’s Oracle database. To preserve existing
data, use the upgrade procedure.

This section contains the installation procedure for the Oracle 8.1.7.4
software. Use the provided instance of Oracle.

Note: Using a different instance of Oracle than the one provided with your
PlexView software voids your customer support agreement.

This procedure describes installing Oracle 8.1.7.4 in a new installation or for

system recovery. Oracle installation is not required for an upgrade.

Note: This procedure is not required when the Oracle database is already
present on the machine.

Note: This installation should be performed by an IT professional.

5.5.1 Required Solaris Patches for Oracle

OS Solaris 8 or 9 must have the following patches:

Solaris 8 requires:

• 111721-04, SunOS 5.8: Math Library (libm) patch

• 112003-03, SunOS 5.8: Unable to load fontset ... iso-1 or iso-15
• 112138-01, SunOS 5.8: usr/bin/domainname patch
• The J2SE Patch Cluster for Solaris 8

The J2SE patch cluster for Solaris 8 contains the following files:

• 108528-23, SunOS 5.8: kernel update patch

• 108652-66, X11 6.4.1: Xsun patch
• 108773-18, SunOS 5.8: IIIM and X I/O Method patch
• 108921-16, CDE 1.4: dtwm patch

10 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

• 108940-53, Motif 1.2.7 and 2.1.1: Runtime lib

• 108987-13, SunOS 5.8: Patch for patchadd and patchrm
• 108989-02, /usr/kernel/sys/acctctl & /.../exacctsys patch
• 108993-18, SunOS 5.8: LDAP2 client, libc, ... lib. Patch
• 109147-24, SunOS 5.8: linker patch
• 110386-03, SunOS 5.8: RBAC Feature Patch
• 111023-02, SunOS 5.8: /kernel/fs/mntfs and ... sparcv9/mntfs
• 111111-03, SunOS 5.8: /usr/bin/nawk patch
• 111308-03, SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch
• 111310-01, SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch
• 112396-02, SunOS 5.8: /usr/bin/fgrep patch

Solaris 9 requires:

• 112233-11, SunOS 5.9: Kernel Patch

• 111722-04, SunOS 5.9: Math Library (libm) patch

Patch Determination Procedure

To determine whether an operating system patch is installed, enter a command

similar to the following:

# /usr/sbin/patchadd -p | grep patch_number

If an operating system patch is not installed, download it from

<http://sunsolve.sun.com>
and install it.

Note: The patch versions shown are minimum versions. Higher versions of
the same patches are also supported.

5.5.2 Required Solaris Packages for Oracle

These packages are additional options to the basic OS installation and are
required for the software to operate properly.

Solaris 8 and 9 must include the following packages:

• i. SUNWarc
• ii. SUNWbtool
• iii. SUNWhea
• iv. SUNWlibm
• v. SUNWlibms
• vi. SUNWsprot
• vii. SUNWsprox
• viii.SUNWtoo

Lucent Technologies 11 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

• ix. SUNWi1of
• x. SUNWi1cs
• xi. SUNWi15cs
• xii. SUNWxwfnt

Package Determination Procedure

To determine whether the required packages are installed, enter a command

similar to the following:
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm
SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of
SUNWi1cs SUNWi15cs SUNWxwfnt

If a package is not installed, then install it. See your operating system or
software documentation for information about installing packages.

5.5.3 Install Optional External Package SMCtop

A "top" package populates the trace health file. Download and install the
SMCtop package.

1. Point your browser at <http://sunfreeware.com>

2. Select from the following options:

• For Solaris 8: top-3.5.1-sol8-sparc-local.gz

• For Solaris 9: top-3.5.1-sol9-sparc-local.gz

5.5.4 Install Oracle

Oracle 8.1.7.4 is bundled into the Oracle database software provided with
your software.

1. Login as root.

2. Mount the Oracle Install CD-ROM provided.

3. Change the directory to …/install

4. Start the installation process by executing ./install.sh

5. Immediately, you will see a prompt to specify what kind of a database

instance you want created:

• plxdb (EMS server)

• statsdw (Advanced Reporting system)

Select only the database instance that supports the software you are installing.

12 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

6. The installation script will check for the Solaris patches and packages
listed in the requirement above. If any of these patches or packages are not
present, the system will prompt for their installation.

7. During the installation, the system will prompt for a reboot if it modified
the kernel parameters. If prompted, reboot the system. After the reboot, go
back to Step 1 of this procedure and perform this procedure again.

When finished, the script will display that the install has completed
successfully. 0.

Note: This installation should take 15 to 30 minutes from initiation to

completion.

The Oracle installation automatically makes the following changes to the

system:

• Sets the kernel parameters in the file /etc/system.

• Reserves TCP port 1521 for Oracle in the file /etc/services
• Creates three user groups:
o dba
o oinstall
o plxusers
• Creates default users:
o oracle
o plx

You can view the user groups in the file /etc/group.

You can view users in the file /etc/passwd.

The Oracle installation is complete. Continue with the next section.

5.6 Install or Upgrade the StatsCollector Software

There are two ways to install or upgrade the software:

• Using the X-windows GUI

• From the command line

The X-windows installation is listed as a procedure. The command line

method, for those who do this repeatedly only, are included at the end of this
section.

The procedure for installing or upgrading the software is exactly the same. 1.1

1. Mount the PlexView Advanced Reporting Traffic Collection Stats

Collector Install CD in the CD drive.

Lucent Technologies 13 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

2. Change your directory to the directory containing Stats.bin.

3. Type ./Stats.bin.

The system will respond with: preparing to install...

The following screen will appear:

Figure 5-2. StatsCollector Installation Introduction Screen

4. Click the Next button to proceed with the installation. The license
agreement screen will appear as shown in the following figure.

14 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

Figure 5-3. License Agreement Screen

5. Click the Next button. The terms of the license agreement are displayed as
shown in the following figure.

Lucent Technologies 15 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Figure 5-4. License Agreement Terms Screen

6. To accept the terms of the license agreement, click the Next button. The
path screen is displayed as shown in the following figure.

16 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

Figure 5-5. Choose Install Folder Screen

7. Accept the default installation location (recommended) or enter an

installation path and click the Install button. First a preparation screen will
appear. Then the installation splash screen with a progress bar will appear
as shown in the following figure.

Lucent Technologies 17 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Figure 5-6. Installation Input Screen

8. At the completion of the installation, the installation input configuration

screen will appear as shown in the following figure.

18 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

Figure 5-7. Installation Input Configuration Screen

Use Server’s
Hostname

9. Add the List of switches to report Advanced Traffic statistics to

StatsCollector.

10. Change or Accept the values for the installation above and click Next.

Note: To add to or delete a switch to collect statistics for Advanced Traffic

Collection from, see the section in this document titled Edit the List of
Switches Reporting to StatsCollector.

Note: The switch names in the List of Switches field must be identical to the
switch’s SID name as displayed in the status bar of the EMS Navigator.

Note: See the description in the EMS installation procedure titled PlexView
Server Installation with a NAT’d Firewall for more information about
using the server’s hostname.

The system will respond with a screen showing that the StatsCollector is being
configured. This will be followed by an Install Complete screen, as shown in
the following figure.

Lucent Technologies 19 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Figure 5-8. Install Complete

11. Click the Done button when the Server installation is complete.

12. If required in your application, update the DNS (Domain Name Server)
that is local to the server to resolve the hostname and the IP address.

Note: For an upgrade being performed by an expert, you can avoid using X-
windows and instead, logged in as root, and using the menu driven
console method, enter:

# ./Stats.bin -i console

You have completed this part of the installation procedure. 0.

20 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

5.7 Prepare the EMS Server for ARS with ATC

There are three steps to be performed on the EMS to support the Advanced
Reporting System (ARS) with Advanced Traffic Collection (ATC).

• Provision the EMS to access the ATC server data.

• Optimize the EMS’s Oracle database for ATC server data.
• Load WebIntelligence on the EMS and provision it for Advanced
Reporting.

This document includes the first two steps. The third step is covered in the
Advanced Reporting System Installation and Setup Guide. Loading
WebIntelligence is part of the standard Advanced Reporting System
installation.

Figure 2. EMS Server in an Advanced Reporting System

To provision the EMS correctly, you must know:

• The location and name of each remote ATC server, or the IP address if no
Domain Name Server is set up
• The name of every switch that each ATC server will collect statistics on

You can use any PlexView client to configure the EMS to support advanced
reporting. All necessary information can be entered into the Add or Modify
switch dialogs.

Lucent Technologies 21 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Refer to the PlexView EMS Installation documentation for instructions on

how to install or upgrade the EMS or the PlexView client.

Note: An IT professional should perform this setup and installation.

5.8 Set Reporting Switch Properties

From a PlexView client, set the reporting switch properties in the EMS. This
must be done for every switch that will report through the Advanced
Reporting System.

1. From the PlexView client, highlight the switch you want to receive
Advanced Reporting data from, right-click it and select Modify.

2. From the Modify Switch screen, provision CPU Performance Monitoring

and the Advanced Reporting section, as shown in the following figure.

22 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

Figure 3. Configuration Screen with StatsCollector Information

3. Fill-in the fields as follows:

• CPU Monitoring: Under Performance Monitoring (PM)>Disabled by

default. Monitors the active SP’s CPU

Note: The CPU Monitoring field may be under the Stats Configuration tab or
the Configuration tab, depending on the release of EMS software.

Under Advanced Reporting:

• Host Name: hostname or IP address of the ATC server

Note: If using the hostname, make sure that any DNS in your network can
resolve the hostname.

Lucent Technologies 23 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

• Global Database Name: statsdw.telica.com

Note: Lucent recommends not changing the Global Database Name from the
default of statsdw.telica.com.

Note: The Global Database Name, if not statsdw.telica.com must match the
database identifier in the tnsnames.ora file in the Oracle database.

4. Click Apply to save the settings or Ok to save the settings and exit. 0.

5.9 Set the PlexView Server Oracle Database to support Advanced Reporting

The Oracle database already installed in the EMS has a default number of
open_links=4. This number of links is insufficient to accept input from
multiple Advanced Traffic Collectors when creating report views and must be
changed. To change the maximum number of open links, perform the
following steps:

1. Access the file using the following path:

/opt/PlexView/Oracle/ora01/app/oracle/admin/
plxdb/pfile/<initplxdb.ora>
2. Open the file and find the number of open links. The default is
open_links=4. This default may not be present in some files.
3. Change the number to open_links=50, or if the default does not
exist, add the command to the file.

4. Save the file.

5. To complete this procedure, perform one of these two choices: 0.

• Reboot the EMS server.

• Shutdown Oracle and restart it. If you don’t know how, reboot the server.

You have completed all tasks related to the installation or upgrading of the
Advanced Traffic Collection software.

24 of 26 Lucent Technologies
Advanced Traffic Collection Installation and Setup
Section 141-300-001 Issue 7, November 18, 2005

6. Edit the List of Switches Reporting to StatsCollector

You can modify the StatsCollector software to add or remove switches
reporting advanced traffic information.

Note: This is not required. You should have entered the reporting switches
during installation. 0.

Note: Never terminate the StatsCollector software by using the kill command.
If you use the kill command, the StatsCollector threads could terminate
during database operations, producing undesirable results that include,
but are not limited to, performing lengthy database rollbacks.

1. To stop the StatsCollector software, type:

/opt/PlexView/Stats/CurrRel/Stats.sh stop
2. Edit the /opt/PlexView/Stats/CurrRel/stats.cfg properties file. Set the
following properties accordingly:

switches=<comma-separated list of switches

stats will be collected for>

Note: The switch name in the TSAA software in the Billing and Traffic
application and the switch names in the StatsCollector software in the
Advanced Traffic Collector must all be identical to the switch’s SID
name as displayed in the status bar of the EMS Navigator.

3. To start the StatsCollector software, type:

/opt/PlexView/Stats/CurrRel/Stats.sh start

7. Advanced Reporting System Installation

To install or upgrade the Advanced Reporting system, refer to the Advanced

Reporting System Installation and Setup Guide.

Lucent Technologies 25 of 26
Installation and Setup Advanced Traffic Collection
Issue 7, November 18, 2005 Section 141-300-001

Notes:

26 of 26 Lucent Technologies