unix-based element management system · 2019-02-18 · radview-hpov/lite unix-based element...

RADview-HPOV/Lite Unix-Based Element Management System

Version 1.7

USER

'S M

AN

UA

L

The Access Company

RADview-HPOV/Lite Unix-Based Element Management System

Version 1.7

User’s Manual

Notice

This manual contains information that is proprietary to RAD Data Communications Ltd. (“RAD”). No part of this publication may be reproduced in any form whatsoever without prior written approval by RAD.

Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other intellectual property or other proprietary rights relating to this manual and to the RADview-HPOV/Lite are proprietary products of RAD protected under international copyright law and shall be and remain solely with RAD.

You shall not copy, reverse compile or reverse assemble all or any portion of the manual or the RADview-HPOV/Lite. You are prohibited from, and shall not, directly or indirectly, develop, market, distribute, license or sell any product that supports substantially similar functionality as the RADview-HPOV/Lite, based on or derived in any way from the RADview-HPOV/Lite. Your undertaking in this paragraph shall survive the termination of this Agreement.

This Agreement is effective upon your opening of the RADview-HPOV/Lite package or to downloading it and shall continue until terminated. RAD may terminate this Agreement upon the breach by you of any term hereof. Upon such termination by RAD, you agree to return to RAD the RADview-HPOV/Lite and all copies and portions thereof.

For further information contact RAD at the address below or contact your local distributor.

International Headquarters RAD Data Communications Ltd.

24 Raoul Wallenberg St. Tel Aviv 69719 Israel Tel: 972-3-6458181 Fax: 972-3-6498250 E-mail: [email protected]

North America Headquarters RAD Data Communications Inc.

900 Corporate Drive Mahwah, NJ 07430 USA Tel: (201) 529-1100, Toll free: 1-800-444-7234 Fax: (201) 529-5777 E-mail: [email protected]

© 1994–2008 RAD Data Communications Ltd. Publication No. 217-210-05/08

mailto:[email protected]�


License Terms

RAD hereby grants a non-exclusive, nontransferable worldwide license to the licensee of this software product to use and install this RAD software product on one workstation only, in object code only for the sole and internal purpose of configuring, monitoring and managing RAD’s hardware products.

Title. All claims to the contrary contained herein notwithstanding, title in and to this RAD software product and documentation, including but not limited to, all copyright, patent, trade secret rights, and intellectual property rights shall remain in and with RAD. The licensee of this software product shall not copy, reverse compile or reverse assemble all or any portion of this software product.

Copies. This RAD software product and documentation shall not be copied, in whole or in part, except as explicitly permitted by RAD or for internal backup or archival purposes.

Warranty

RAD does not warrant that this software product is free from errors and/or will run properly on all computer hardware and/or operating systems. RAD does not warrant that this software product will meet requirements of its licensee or operate in the combinations which may be selected for use by a licensee or the end users or that the operation of this software product will be uninterrupted or error free.

THE WARRANTIES ABOVE ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Limitation of Liability

RAD’s cumulative liability to you or any other party for any loss or damages resulting from any claims, demands, or actions arising out of or relating to this Agreement and the RADview-HPOV/Lite shall not exceed the sum paid to RAD for the purchase of the RADview-HPOV/Lite. In no event shall RAD be liable for any indirect, incidental, consequential, special or exemplary damages or lost profits, even if RAD has been advised of the possibility of such damages.

This Agreement shall be construed and governed in accordance with the laws of the State of Israel.

RADview-HPOV/Lite Ver. 1.7 i

Contents

Chapter 1. Introduction

1.1 Overview.................................................................................................................... 1-1 System Features ..................................................................................................... 1-1

Fault Management ............................................................................................. 1-1 Configuration Management ................................................................................ 1-2

Supported Products and Generic Functions ............................................................. 1-2 1.2 System Requirements ................................................................................................ 1-5

Hardware Requirements.......................................................................................... 1-5 Software Requirements .......................................................................................... 1-5

Chapter 2. Installation and Setup

2.1 Package Contents ...................................................................................................... 2-1 2.2 Installation ................................................................................................................. 2-1

Installation Sequence .............................................................................................. 2-1 Installing the Informix Database .............................................................................. 2-2 Installing the RADview-HPOV/Lite Package ............................................................... 2-3

2.3 Post-Installation Steps ............................................................................................... 2-6 Creating Unix User .................................................................................................. 2-6 Defining the Unix User Environment ........................................................................ 2-8 Installing Licenses ................................................................................................... 2-9

2.4 Uninstalling the RADview Package ............................................................................ 2-11 Uninstalling RADview-HPOV/Lite ............................................................................ 2-11 Uninstalling the Informix Database ........................................................................ 2-11

Chapter 3. Operation

3.1 Running the HPOV Platform ........................................................................................ 3-1 Starting an HPOV session ........................................................................................ 3-2 Changing HPOV Password ....................................................................................... 3-2

3.2 Using the HPOV GUI ................................................................................................... 3-3 Using the RADview-HPOV/Lite WAN Maps ................................................................ 3-3 Working in the HPOV Window ................................................................................. 3-4

WAN Map Terminology ....................................................................................... 3-4 Map Application Rules ........................................................................................ 3-5 Moving Between Map Windows .......................................................................... 3-6 Moving Objects on the Map ................................................................................ 3-6

Compiling Private RAD MIB ...................................................................................... 3-7 Creating a Net ........................................................................................................ 3-7

Preparing Node Names and Internet Addresses .................................................. 3-8 Network Topology .............................................................................................. 3-8 Creating a Net Hierarchy .................................................................................... 3-8

Creating an Agent for a RAD Device ........................................................................ 3-9 Setting Selection Name and Selection Name Format ......................................... 3-10 Setting Agent SNMP Parameters ....................................................................... 3-11 Deleting an Agent ............................................................................................ 3-13 Changing Agent Attributes................................................................................ 3-13

Monitoring Agents ................................................................................................ 3-14 Displaying Alarm Categories .................................................................................. 3-14 Ending an HPOV session ........................................................................................ 3-14

Table of Contents User's Manual

ii RADview-HPOV/Lite Ver. 1.7

Chapter 4. Configuration Management

4.1 Setting the HPOV System Parameters ......................................................................... 4-1 Propagating the HPOV Map Status Color .................................................................. 4-1 Disabling HPOV Autodiscovery ................................................................................. 4-1 Disabling Automatic Deletion of Nodes ................................................................... 4-2 Setting Polling Interval, Timeouts, and Retries ......................................................... 4-2

4.2 Licensing ................................................................................................................... 4-3 Network Size .......................................................................................................... 4-4 Equivalent Node Weights ........................................................................................ 4-4 Bundled License Points ........................................................................................... 4-5 Calculating License Points ....................................................................................... 4-5 Working with the License Service Manager .............................................................. 4-6

Viewing the Installed License Points ................................................................... 4-6 Viewing the Managed Element List ..................................................................... 4-8 Adding a License .............................................................................................. 4-10 Removing a License .......................................................................................... 4-11 Starting and Stopping the License Service ......................................................... 4-12 Configuring the Server Side License Ports ......................................................... 4-13 Configuring the Client Side License Ports .......................................................... 4-14

4.3 Performing Automatic Configuration Upload (ACU) ................................................... 4-15 Configuring the TFTP Server for ACU ...................................................................... 4-15 Manually Starting or Stopping the ACU Server ........................................................ 4-17 Launching the ACU Client Application .................................................................... 4-18 Summary of ACU Tasks ......................................................................................... 4-20 Configuring ACU TFTP Settings .............................................................................. 4-21 Configuring ACU Profiles ....................................................................................... 4-22

Adding a Profile ................................................................................................ 4-23 Editing a Profile ................................................................................................ 4-24 Selecting Nodes for a Profile ............................................................................ 4-26 Removing a Profile ........................................................................................... 4-27 Deactivating a Profile ....................................................................................... 4-28 Activating a Profile ........................................................................................... 4-28 Refreshing the List of Profiles .......................................................................... 4-28

Performing Immediate Configuration Upload ......................................................... 4-28 Working with the ACU Report Table ....................................................................... 4-30

Filtering the Report .......................................................................................... 4-32 Refreshing the Report ...................................................................................... 4-37 Saving the Report ............................................................................................ 4-37 Printing the Report ........................................................................................... 4-39 Clearing the Report .......................................................................................... 4-40

Accessing Help ...................................................................................................... 4-41 Closing the ACU Client Application ......................................................................... 4-42

4.4 Performing Backup and Restore ............................................................................... 4-43 Backup and Restore Requirements ........................................................................ 4-43 Configuring Backup and Restore ............................................................................ 4-44

Configuring Backup and Restore Scripts Manually.............................................. 4-44 Configuring Backup and Restore Files ............................................................... 4-44

Backing Up System Components ........................................................................... 4-47 Restoring System Components .............................................................................. 4-48

4.5 Transferring Files Using TFTP .................................................................................... 4-50 Configuring the TFTP Server .................................................................................. 4-50 Opening the TFTP File Transfer Application ............................................................ 4-51 Changing the TFTP Default Settings ....................................................................... 4-53

User's Manual Table of Contents

RADview-HPOV/Lite Ver. 1.7 iii

Editing the TFTP Database .................................................................................... 4-54 Adding a Product Profile ................................................................................... 4-54 Selecting the File to Download ......................................................................... 4-61 Editing Product Data ........................................................................................ 4-61

Selecting Nodes for TFTP ...................................................................................... 4-64 Adding Agents for TFTP Operations .................................................................. 4-66

Transferring Files Using TFTP ................................................................................. 4-67 Viewing TFTP File Transfer Reports ........................................................................ 4-74 Saving the TFTP Database ..................................................................................... 4-77 Using Help ............................................................................................................ 4-77

Exiting the Application ...................................................................................... 4-77 4.6 Viewing the Net Inventory ........................................................................................ 4-78

Opening the Application ........................................................................................ 4-78 Filtering the Display .............................................................................................. 4-80 Editing an Entity ................................................................................................... 4-82 Expanding/Collapsing Sublevels ............................................................................. 4-82

4.7 Setting Net Date and Time ....................................................................................... 4-83 Setting Net Date and Time .................................................................................... 4-83 Setting Automatic Update of Date and Time .......................................................... 4-84

Chapter 5. Performance Management

5.1 Viewing Product Statistics .......................................................................................... 5-1 5.2 Collecting Statistics from VMUX-400 Units .................................................................. 5-1

System Requirements ............................................................................................. 5-1 Managing Statistics Data ......................................................................................... 5-2 Statistics Collection Sequence ................................................................................. 5-4 Starting the Statistics Collection Application ............................................................ 5-5 Configuring Statistics Collection .............................................................................. 5-7

Viewing Group Descriptors and Performing Operations ....................................... 5-7 Adding a Group Descriptor ................................................................................. 5-9 Changing a Group Descriptor ............................................................................ 5-11 Renaming a Group Descriptor ........................................................................... 5-14

Starting/Stopping Statistics Collection Process ...................................................... 5-15 Viewing the Navigation Tree .................................................................................. 5-16

Finding a Node ................................................................................................. 5-16 Collapsing the Navigation Tree ......................................................................... 5-17 Expanding the Navigation Tree ......................................................................... 5-17 Displaying/Hiding the Navigation Tree ............................................................... 5-17

Displaying the Map ............................................................................................... 5-18 Viewing the Statistics Chart ................................................................................... 5-18

Trend View ....................................................................................................... 5-18 Detailed View ................................................................................................... 5-20

Chapter 6. Security Management

6.1 Overview.................................................................................................................... 6-1 6.2 Administering Users in the HPOV Environment ............................................................ 6-1

Adding Users .......................................................................................................... 6-1 Changing User Password ......................................................................................... 6-3 Defining User Security Access Levels ....................................................................... 6-4 Changing User Security Capabilities ......................................................................... 6-5 Removing Users ...................................................................................................... 6-8 Viewing User Security Access Privileges ................................................................... 6-8

Table of Contents User's Manual

iv RADview-HPOV/Lite Ver. 1.7

Displaying the Security Log ..................................................................................... 6-8

Chapter 7. Fault Management

7.1 Managing Alarms ........................................................................................................ 7-1 7.2 Testing the Unix User Environment ............................................................................. 7-1

Testing with User Environment Tool.................................................................... 7-1 Testing with Commands ..................................................................................... 7-4

7.3 Frequently Asked Questions ....................................................................................... 7-6 7.4 Technical Support ...................................................................................................... 7-7

Appendix A. Migration Guide

Index

RADview-HPOV/Lite Ver. 1.7 Overview 1-1

Chapter 1

Introduction

1.1 Overview

RADview-HPOV/Lite is a user-friendly SNMP-based element management system that provides monitoring and configuration of network elements. Integrated into HP OpenView Windows NNM SNMP platform, RADview-HPOV/Lite supports map services such as color-coded network status indication.

System Features

RADview-HPOV/Lite includes the following features:

• Supports inband and out-of-band management

• Presents networks and their components in an easy-to-view graphical map format. Maps can be grouped according to hierarchies and their sub-levels. User-defined graphics can be included

• “Learns” the network by automatically discovering SNMP-manageable elements

• Polls nodes at periodic intervals or on user command, and relays the results of the polls by a combination of messages, color codes, log files, and other actions

• Prints log and map reports

• Gathers real-time statistics that can be displayed in line graph, bar chart, or tabular format

• Includes MIB compiler and browser to facilitate control of third-party equipment

• Provides fast automatic network recovery following discovery of a fault condition

• Allows for security control at the lobe and segment levels

• Supports HTTPS security protocol in agent configuration

• Runs under Unix.

Fault Management

RADview-HPOV/Lite monitors the network, detects events, and helps isolate problems and minimize network downtime. Network status changes are displayed graphically at the network, device, card, and port levels. RADview-HPOV/Lite supports multiple map levels, enabling graphic display of the hierarchical network

Chapter 1 Introduction User’s Manual

1-2 Overview RADview-HPOV/Lite Ver. 1.7

structure. A problem occurring at a lower level is forwarded to intermediate and upper levels for easy problem detection and isolation. Comprehensive log files of all traps are maintained, including identification of the trap source, event description, and date/time stamp. Information in the log is categorized according to severity level, and can be sorted, filtered, and exported to file.

Configuration Management

Configuration and diagnostics are performed through simple and user-friendly access to ConfiguRAD directly from the topology map (GUI cut-through), by double-clicking a network icon.

For some packet switch products that are not supported by ConfiguRAD, double-clicking the network icon opens a Telnet session.

TFTP-based software and configuration transfer capabilities allow distribution of new software versions or configuration files to multiple network elements simultaneously, while collecting statistics and presenting reports on the process status. Configuration files can also be collected and distributed.

Some features (for example, TFTP-based SW download) are available only when they are supported by the device agent. See Table 1-1 for details.

Supported Products and Generic Functions

Table 1-1 shows the products supported by RADview-HPOV/Lite, and the functions supported for each product. The symbol + indicates that the function is supported, the symbol – indicates that the function is not supported.

Table 1-1. Products and Functions Supported by RADview-HPOV/Lite

Product Description TFTP File Transfer

Net Inventory

Net Date and Time

Net Clear Alarms

APD-8 Multiprotocol FRAD providing easy,

cost-effective access to a packet

switching network

+ – – –

APS-8/16/24 Multiprotocol FRAD/Switches providing

easy, cost-effective access to packet

switching network, as well as packet

switching capability for both X.25 and

Frame Relay

+ – – –

Egate-20 Ethernet-over-E1/T1 gateway that

aggregates and switches traffic from

Fast Ethernet, over up to eight E1 or

T1 circuits

+ + – –

Note

Note

User’s Manual Chapter 1 Introduction

RADview-HPOV/Lite Ver. 1.7 Overview 1-3


Net Inventory

Net Date and Time

Net Clear Alarms

Egate-100 Ethernet aggregator, grooming

Ethernet traffic carried over PDH

(E1/T1) over SDH into a Gigabit

Ethernet MAN

+ + – –

FPS-8 Multiprotocol FRAD/switch designed for

a Regional or Central Office

environment that provides fast, easy

and cost-effective access to a packet

switching network

+ – – –

RIC-155 Converter that provides simple and

efficient connection of Fast Ethernet

traffic over STM-1/OC-3 lines

+ + + +

RIC-155GE Converter that provides simple and

efficient connection of Gigabit Ethernet

traffic over STM-1/OC-3c lines

– – – –

RIC-622GE Converter that provides simple and

efficient connection of Gigabit Ethernet

traffic over STM-4/OC-12c lines

– – – –

RICi-E1/T1 Ethernet CLE (Customer-Located

Equipment) providing a demarcation

point between the private LAN and the

operator’s network, bridging between

Fast Ethernet and E1/T1

+ + – –

RICi-E3/T3 Ethernet CLE (Customer-Located




Fast Ethernet and E3/T3

+ + – –

RICi-4E1/T1,

RICi-8E1/T1

Intelligent converters connecting Fast

Ethernet LANs over four or eight

bonded E1/T1 circuits

+ + – –

RICi-16E1/T1 Network Termination Unit (NTU)

connecting Fast Ethernet LANs over

16 bonded E1/T1 circuits

+ + – –

RICi-155GE Network termination unit (NTU) that

bridges between Gigabit Ethernet

networks and STM-1/OC-3c networks

+ + - -

RICi-622GE Network termination unit (NTU) that

bridges between Gigabit Ethernet

networks and STM-4/OC-12 networks

+ + - -


1-4 Overview RADview-HPOV/Lite Ver. 1.7


Net Inventory

Net Date and Time

Net Clear Alarms

RICi-SE Ethernet CLE (Customer-Located




Fast Ethernet and Serial interface

+ + – –

SPS-3S/6/12 FRAD/PAD and multiprotocol packet

switches providing easy, cost-effective

access to packet switching network

+ – – –

SPS-4 FRAD/switch providing easy,

cost-effective access to packet

switching network, as well as packet

switching capability for both X.25 and

Frame Relay

+ – + –

VMUX-400 Compact standalone unit optimizing

GSM Abis and Ater traffic and

transporting it over either an E1 link, a

Serial link, or an Ethernet link

+ + – –

User’s Manual Chapter 1 Introduction

RADview-HPOV/Lite Ver. 1.7 System Requirements 1-5

1.2 System Requirements

RADview-HPOV/Lite package version 1.7 can be installed on a Unix platform that is compatible with HP Openview, according to the following hardware and software requirements.

Hardware Requirements

The following are the hardware requirements for networks consisting of up to 150 managed elements:

• Sun Fire V210 Server with XVR-100* graphics card or Sun Ultra 25

• Minimum free disk space in /opt partition: from 1 GB to 2 GB (depending on the amount of applications installed)

• 600 MB for Informix (in any partition)

• 2 GB RAM

• 4 GB swap file (as a minimum, the swap file must be twice the RAM size)

• For each three additional simultaneous users (X-session) add 1 GB RAM and 1 CPU

• For each additional simultaneous open zoom application add 75MB RAM

• Color monitor (17-inch minimum) supporting 1152 × 900 resolution or higher with depth 24

• CD drive.

For larger networks consisting of more than 150 managed elements, see FAQ 1168 at the RAD Technical Support website.

Software Requirements

The following software is required:

• SUN Solaris Version 10, Nov 2006 or later

Verify that the option to include Solaris 64-Bit Support is selected during Solaris installation

• CDE 1.4 or higher

• HP OpenView NNM Version 7.5 or later

For up to 250 managed elements, HPOV NNM Starter Edition is sufficient. However, if you manage more than 250 elements you must also purchase the appropriate HPOV license.

RADview-HPOV/Lite supports only Solaris Version 10 (released in November 2006). No other versions are supported. For example, Versions 2.5.1, 2.6, 2.7, and 2.8 are not supported.

Note

Note

Note


1-6 System Requirements RADview-HPOV/Lite Ver. 1.7

RADview-HPOV/Lite Ver. 1.7 Installation 2-1

Chapter 2

Installation and Setup This section describes the procedures to install the RADview-HPOV/Lite package.

Do not change the IP address of the Unix station after installing Informix or HPOV.

A workaround is to add an additional virtual IP address by executing the following commands:

• ifconfig hme0:1 <new_IP> plumb

• ifconfig hme0:1 <new_IP> up

• where hme0 is the Ethernet interface that can be seen by typing ifconfig -a.

2.1 Package Contents

The RADview-HPOV/Lite application package includes the following items:

• RADview-HPOV/Lite Installation CD

• RADview-HPOV database (Informix) CD

• Installation guide

• Technical documentation CD.

2.2 Installation

Installation Sequence

The RADview-HPOV/Lite package should be installed only after Solaris 10 and HPOV NNM 7.5 are installed on the station. For more information about the installation of these platforms, refer to their documentation.

The RADview-HPOV/Lite package must be installed in the following sequence:

• Install the database

• Install RADview-HPOV/Lite

• Create Unix user for RADview and define user environment

• Install license.

Note

Note

Chapter 2 Installation and Setup Installation and Operation Manual

2-2 Installation RADview-HPOV/Lite Ver. 1.7

Installing the Informix Database

Figure 2-1 and Figure 2-2 show examples of Informix installation screens. Make sure you close all running applications before initiating the Informix installation script.

To perform the Informix installation:

1. Log in as root.

2. Type: csh

3. Insert the RADview-HPOV database CD into the CD drive.

4. Type: cd /cdrom/cdrom0/informix

5. Type: ./informix.install

6. When prompted, type the Informix home directory path /export/home/informix.

During the Informix installation the /etc/system file is automatically updated. The installation script prompts you to confirm a system reboot, so that the modification can take effect.

7. When prompted, confirm the system reboot.

Figure 2-1. Informix Installation, Starting

8. When the reboot completes, log in as user root.

9. Type: csh

10. Type: cd /cdrom/cdrom0/informix

11. To finish Informix installation, type: ./informix.install

Informix installation continues until complete, at which time the prompt (#) reappears.

Note

Installation and Operation Manual Chapter 2 Installation and Setup


Figure 2-2. Informix Installation, Completing

Installing the RADview-HPOV/Lite Package

Installation takes between five and twenty minutes depending on the hardware platform. Informix must be installed and online before installing the RADview-HPOV/Lite package.

To install the RADview components:

1. Log in as user root.

2. Type: csh

3. Type: source /<INFORMIXDIR>/.mng164_inf.csh

Replace <INFORMIXDIR> with your Informix installation directory (for example /export/home/informix).

4. Insert the RADview-HPOV/Lite installation CD into the CD drive.

5. Type: cd /cdrom/cdrom0/radview

6. Verify that Informix is running by typing: onstat –

If Informix is online the following message appears:

INFORMIX-OnLine version 7.31.UDI - -On-Line- -

If Informix is not online, stop the installation of RADview-HPOV/Lite, and perform the actions necessary to get Informix online.

7. Type: ./install_gui.rad

The RADview-HPOV/Lite Installation dialog box appears.

Note


2-4 Installation RADview-HPOV/Lite Ver. 1.7

Figure 2-3. RADview-HPOV/Lite Installation Dialog Box

8. Click <OK>.

The RADview-HPOV/Lite installation product list appears in the installation dialog box.

Figure 2-4. RADview-HPOV/Lite Installation Product List, Product Selection

9. Click <Select All>.

The bullet next to the selected product is colored green.

Figure 2-5. RADview-HPOV/Lite Installation Product List, Products Selected

10. Click <Install>.



The Informix installation directory confirmation dialog box appears.

Figure 2-6. Informix Installation Directory Confirmation Dialog Box

11. Perform one of the following:

If the Informix installation directory is correct, click <Yes>.

The installation completes. Continue at step 13.

If the Informix installation directory is not correct, click <No>.

A dialog box prompts you for the Informix installation path.

Figure 2-7. Informix Installation Path Dialog Box

12. Type the Informix installation path and click <OK>.

If the path is correct, the installation completes. Continue at step 13.

If the path name is not correct, an error message appears informing you that the directory does not exist. In such a case, click <OK> and re-enter the path in the Informix Path Dialog Box.

Figure 2-8. Incorrect Informix Installation Directory Dialog Box

If this is an upgrade of an existing installation, then after the confirmation of Informix installation directory, the Upgrade dialog box appears. Click <Overwrite> to complete the installation.

Note


2-6 Post-Installation Steps RADview-HPOV/Lite Ver. 1.7

Figure 2-9. RADview Installation – Upgrade Dialog Box

13. Once the Informix installation directory has been confirmed and the initial components have been installed, Installation Done appears in green in the middle of the RADview-HPOV/Lite Installation dialog box and Success appears at the bottom of the dialog box.

Figure 2-10. RADview Installation Complete

14. Click <Finish> to exit the installation procedure.

15. Restart the workstation.

2.3 Post-Installation Steps

Before opening RADview-HPOV/Lite, you must create a Unix user for RADview, and then set the user environment to include the variables needed for RADview-HPOV/Lite, HPOV, and Informix. It is recommended that you select C as the user's SHELL.

Creating Unix User

To create a Unix user:

1. Log in as root user.

2. Type: smc


RADview-HPOV/Lite Ver. 1.7 Post-Installation Steps 2-7

The Open Toolbox dialog box appears with the Solaris Management Console in the background.

3. Select the Server Toolbox tab, and choose your server name from the Server dropdown box.

4. From the Toolboxes list, select This Computer and click Open.

The Solaris Management Console for the selected computer is displayed.

5. From the Navigation pane, select System Configuration > Users.

The Log In menu is displayed.

6. Log in using Administrator credentials (root).


7. From the Navigation pane, select System Configuration > Users > User Accounts.

8. From the Action menu, select Add User > With Wizard.

The Add New User wizard is initiated.

9. In the Add New User wizard, do the following:

a. Enter the user information and click <Next>.

b. Define the user identification number (it is recommended to use the default), and click <Next>.

c. Define and confirm the new user password, and click <Next>.

d. Select the new user primary group (it is recommended to use the default), and click <Next>.

e. Create the new user home directory (e.g. /export/home) and click <Next>.

f. In the mail server dialog box, click <Next>.

g. Review the new user information and click Finish.


Figure 2-11. Reviewing the New User Details



10. Right-click the icon of the newly created user and select Properties.

11. From the General tab set the Login Shell to C Shell.

12. From the Console menu, select Exit to close the Solaris Management Console.

13. Reboot the management station to put the changes into effect.

14. Log in as the newly created user.

15. Select Common Desktop Environment (CDE) as the default desktop.

16. Edit the .cshrc file in the user home directory to add /usr/local/bin /usr/sbin to the following command: set path = ($path /usr/local/bin /usr/sbin) so that the command line appears as: set path = ($path /usr/local/bin /usr/sbin)

17. Save the .cshrc file.

Defining the Unix User Environment

The RADview post-installation user environment tool automates all post-installation procedures and completes the installation of RADview UNIX-based products. The script is written in csh. It can be used by both a new user and an existing user to test the user environment.

To set the user environment for a new user:

1. After you create a new user and log in as the new user, type: /opt/MNG/MNGVIEWHP/bin/user_env.csh

The script sets the user environment. The user files are edited automatically.

***************************************************************

* RADview User Environment *

* *

* This script should run only on a Unix server, that is *

* a dedicated RADview-HPOV installation. *

* *

* This script sets the User Environment variables for a *

* newly created user and performs User Environment tests *

* for an existing user. *

* *

* Run this script as RADview user and not as root. *

* *

* This script must run under csh environment only. *

* *

* User Environment variables are written into the *

* logfile user_env.log in the users home directory. *

**************************************************************

Setting User Environment for a new RADview user...


RADview-HPOV/Lite Ver. 1.7 Post-Installation Steps 2-9

Setting user files:

/export/home/radview/.login

/export/home/radview/.dtprofile

User Environment files set successfully.

Editing user file /export/home/radview/.cshrc

Adding HPOV NNM /bin directory to the users path.

-------------------------------------------------------------------------

User Environment parameters set successfully. |

Logout and login again to activate the new User Environment. |

Run this script again after login to test the User Environment settings.|

---------------------------------------------------------------------------

Figure 2-12. RADview User Environment Tool – New User

2. A message appears prompting you to log out and re-login (to activate the changes).

3. Run the script again to test the user environment.

Installing Licenses

Each RADview license is associated with a single management station. This station is identified by its host ID for UNIX-based stations or its IP/MAC address for Windows-based stations.

If you need a RADview license for an order that was placed without the host ID, you can contact the RAD Ordering Department at [email protected] and provide your RADview order number and the host ID of the management station. The license is then issued and sent to you promptly.

If you need the RADview license to be sent to you again, you can contact the RAD Export Department at [email protected] and provide your RADview order number or invoice number. The license is then sent to you promptly.

If you do not know for which host ID to request the license, refer to Frequently Asked Questions in Chapter 7, or to FAQ 6171 at the RAD Technical Support website.

You must install a license before you can start to work with RADview-HPOV/Lite maps. The license is installed from the HPOV environment. For further details on the HPOV environment, refer to Chapter 3.

To install a license:

1. Log into Solaris with the user name and password that you created in the post-installation steps (see Creating Unix User).





2. In the terminal window, type: ovw &.

The HPOV root window appears.

3. In the HPOV root window, select Misc > RADview/OV > Login.

The Login dialog box appears.

4. Type in user name root and the password for root, and click <OK> to complete the login process.

5. In the HPOV root window, select Misc > RADview OV > License Service Manager to open the License Service Manager.

6. Select File > Add License.

The Open License File dialog box appears.

Figure 2–13. License Server Manager –Open License File Dialog Box

7. Locate and select the desired license file, and click <Save>.

You must be logged into HPOV as root to install licenses.

Note


RADview-HPOV/Lite Ver. 1.7 Uninstalling the RADview Package 2-11

2.4 Uninstalling the RADview Package

Uninstalling RADview-HPOV/Lite

To uninstall RADview-HPOV/Lite:

1. Log in as su.

2. Type: csh

3. Type: source/opt/OV/bin/ov.envvars.csh

4. Type: source/opt/MNG/MNGVIEWHP/bin/mng164_uninstall.csh

Uninstalling the Informix Database

To uninstall the Informix database:

1. Log in as su

2. Type: csh

3. Type: setenv INFORMIXDIR <informix home directory>

4. Type: <informix home directory>/i_uninstall

5. Type y in the three consecutive confirmation messages (listed in Figure 2-14).

6. Using admintool, remove the Informix user and group.

7. Remove Informix-marked lines from the /etc/system file. These lines start with: * informix additions – enabling semaphores and end with: * end informix additions

Figure 2-14. Uninstalling Informix


2-12 Uninstalling the RADview Package RADview-HPOV/Lite Ver. 1.7

User’s Manual Chapter 3 Operation

Transferring Files 3-1

Chapter 3

Operation This chapter describes the following operation activities:

• Running the HPOV Platform – starting to work with the HPOV environment

• Using the HPOV GUI – using the various control options available from the HPOV graphic user interface (GUI). These options include:

Using the RADview-HPOV/Lite WAN Maps

Working in the HPOV Window

Creating an Agent for a RAD Device.

3.1 Running the HPOV Platform

The HP OpenView (HPOV) environment provides the basic user interface by which nets and node agents are created. All these functions are available via the HPOV root window.

To start working with the HPOV environment:

1. In the Terminal window, type: ovw &.

The HPOV root window appears.

Figure 3-1. HPOV Root Window

Chapter 3 Operation User’s Manual

3-2 Running the HPOV Platform RADview-HPOV/Lite Ver. 1.7

Starting an HPOV session

To begin a session in the HPOV environment, you must log in.

To log in to the HPOV environment:

1. In the HPOV root window, select Misc > RADview/OV > Login.


Figure 3-2. Login Dialog Box

2. Type in your user name and password.

If this is the first time the system is being used or users have not yet been created in the system, enter the system with user name root and user password root.

3. Click <OK>.

If you enter an incorrect password the Access Denied dialog box appears. Click <OK>.

Figure 3-3. Access Denied Dialog Box

Changing HPOV Password

For security reasons, it is recommended to change the initial HPOV user password.

To change the HPOV user password:

1. From the submap screen select Misc > RADview/OV > Login.


2. Click <Change Password>.


RADview-HPOV/Lite Ver. 1.7 Using the HPOV GUI 3-3

The Change Password dialog box appears (see Figure 3-4).

Figure 3-4. Change Password Dialog Box

3. Type your old password into the Old Password field.

4. Type your new password into the New Password field.

5. Type your new password into the Verify New Password field to confirm your new password.

6. Click <OK>.

3.2 Using the HPOV GUI

This section describes the HP OpenView (HPOV) features that allow you to create and monitor nets and agents.

Multiple Java™ zoom applications can be launched on the same node (i.e. of the same agent) on Java-based products. Java™ does not recognize applications that were previously opened; it does not direct the user to the session that is already open.

Using the RADview-HPOV/Lite WAN Maps

Hierarchical WAN maps are the basis of the RADview-HPOV/Lite HP OpenView network management system. The user can create and modify a map using the HP OpenView menu commands. This chapter focuses on operations relating to nets containing WAN agents. For complete information about HP OpenView (HPOV) map functions, refer to the HP OpenView Windows User Guide.

WAN units are a generic term for managing all RAD WAN units.

Note

Note


3-4 Using the HPOV GUI RADview-HPOV/Lite Ver. 1.7

RADview-HPOV/Lite includes the following levels of maps:

• The top level of maps, called the root map, contains a WAN hierarchy that is automatically created by RADview-HPOV/Lite the first time the system is started up.

• Double-clicking on the WAN hierarchy opens up the next level, or WAN submap, containing one or many nets. Each WAN submap is further broken down at the lowest map level into a collection of units.

As nets and WAN agents are created (see Creating a Net and Creating an Agent for a RAD Device), each is represented by a single node (icon) on the lowest level map. An agent can be selected by clicking on it. A selected agent is surrounded by a dark gray box. Once an agent is selected, all relevant HPOV commands can be utilized. For ease of viewing, multiple map levels can be viewed simultaneously. Current network status can be easily monitored, as the network map presents status messages. Color-coded icons show the status of each net or WAN agent at a glance (for more information, see Monitoring Agents)..

Working in the HPOV Window

Each HPOV map window contains the map name in the title bar and eleven entries in its menu bar: Map, Edit, View, Performance, Fault, Tools, Options, Window, Misc, and Help. In addition to the HPOV map window menus, each object on the map has an object-specific menu, called a symbol menu, that can be accessed by right-clicking the mouse.

The button box at the bottom of the window contains command buttons for navigating between map levels: Close, Home, Root, Parent, Quick Navigator, Pan and Zoom, RADview Zoom, Port Labeling, and About HPOV.

An alarm window is used to display traps and event messages that arrive from active network elements. The following event lists are available:

• Error alarms

• Threshold alarms

• Status alarms

• Configuration alarms

• Application alert alarms

• Problem diagnosis alarms

• All alarms.

This chapter focuses on the HPOV operations that are necessary for the RADview-HPOV/Lite system. For more detailed information about HPOV operation, refer to the HP OpenView Windows User Guide.

WAN Map Terminology

The following terms are used when working with WAN maps:

• WAN root submap icon – Icon in the root map. Double-clicking this icon displays the top level of the WAN map hierarchy.



• WAN root submap – Submap opened when the Wan root submap icon is double-clicked. The submap includes WAN submap icons.

• WAN submap icon – Icon on the WAN root map. Double-clicking this icon displays a WAN submap of agent icons.

• WAN submap – Submap opened when the WAN submap icon is double-clicked. The submap includes WAN Agent icons.

• WAN agent icon – Icon in the WAN submap. Double-clicking this icon displays WAN device information.

Map Application Rules

The WAN map hierarchy includes sets of rules that govern the usage of submaps and icons at each level of the map hierarchy. These levels are:

• General WAN application level

• Root level

• WAN root map level

• WAN submap level

• Connection level.

General WAN Application Rules

The following usage rules apply to all levels of the WAN map hierarchy:

• In any map, no two items can have the same name.

• Any WAN submap or WAN agent appearing in different maps of the same hierarchy must be indicated in each location by the same type of icon.

• A connection name cannot be identical to a WAN item name within the same hierarchy.

Root Level Rules

The following rules apply to the HPOV root map:

• There must always be exactly one WAN root submap icon.

• You cannot delete the WAN root submap icon.

• Double-clicking on the WAN root submap icon opens the WAN root submap.

WAN Root Map Level Rules

The following rules apply to the WAN root map:

• Only WAN submap icons can appear in this map.

• The icons in this map cannot be connected.

• Double-clicking on a WAN submap icon opens the appropriate WAN submap.

• The WAN submap icon color reflects the status of the WAN agents in that hierarchy.



WAN Submap Level Rules

The following rules apply to the WAN submap:

• Icons of any type can appear in this map.

• The icons in this map can be connected.

• After you add a WAN agent icon, RADview-HPOV/Lite automatically polls the agent for its status, and adds a color indication of connectivity and alarm status for each agent, as follows:

Red Agent is disconnected, or is connected with active critical alarms

Orange Agent is connected with active major or faulty state alarms

Yellow Agent is connected with active event alarms or active minor state

alarms

Cyan Agent is connected with no alarms but pending tests, or with active

warning alarms (with or without pending tests)

Green Agent is connected and has no alarms or pending tests

Moving Between Map Windows

Each map and submap is contained in a separate window. You can view multiple map levels simultaneously, but only one map window can be the active window at a given time. There are four ways to move to another map window:

• If the desired window is already open, click its title bar

• Use the Home, Root, and Parent buttons to move to a window at a higher level than the current window

• Double-click the desired WAN hierarchy or WAN submap icon to open the lower-level window

• In the WAN hierarchy map, use the vertical arrow under the menu bar to move up and down among maps.

Moving Objects on the Map

To move an object to a different location on the map:

• Drag the object name to the new position.

To remove an object and its attributes from the map file:

1. Select the object.

2. From the Edit menu, click <Delete> and then select From this submap or From all submaps.

3. Click <OK> to confirm.

Use caution when deleting objects. If the selected node is a hierarchy node, all information pertaining to its children is erased from the database.

Caution



Compiling Private RAD MIB

It is necessary to compile the RAD MIB on the HPOV platform if you intend to:

• Use a MIB browser for either GET or SET SNMP variable MIB in a device

• Receive traps for a RAD device, with no RADview installed in the system.

To install RAD MIB on HPOV:

1. Log into the Unix workstation as superuser.

2. Insert the RADview-HPOV/Lite Installation CD into the CD drive.

3. Type: cd /cdrom/cdrom0

4. In a separate terminal window, type: ovw & to start HPOV.

5. With the HPOV map open, enter the required user name and password.

6. From the Options menu (HPOV > Options) in the HPOV map, select Load/Unload MIBs: SNMP.

The Load/Unload MIBs:SNMP dialog box appears.

7. From the Load/Unload MIBs: SNMP dialog box, select <Load…>.

The Load/Unload MIBs:SNMP / Load MIB from File dialog box appears.

8. In the Filter field type /cdrom/cdrom/* and click <Filter>.

9. Locate the /cdrom/cdrom0/ directory under Directories.

10. Select RAD.MIB under Files and click <OK> to load the MIB.

A message is displayed, confirming that the RAD MIB is being loaded.

11. Click <OK> to approve the load of the Trap/Notification macro.

12. When the installation is complete the RAD MIB becomes available in the Load/Unload MIBs: SNMP dialog box.

13. Click <Close> to close the Load/Unload MIBs: SNMP dialog box.

Creating a Net

A net is a collection of units connected by communication links that can be configured as a group. A single standalone unit is a special type of net. Using RADview-HPOV/Lite, you can define nets, plan WAN agent connections, and configure nets as desired.

At the net level, the following information is displayed:

• Net topology

• Communication status of each WAN agent with the management station

• Operational status of each WAN agent, as the information is passed from the ports to the modules and to the WAN agent

• Operational status of the links connecting WAN agents.

At the WAN agent level, the following Information is displayed:

• Operational status of the agent



• Operational status of each card, including its ports

• Test status of each card, including its ports.

Preparing Node Names and Internet Addresses

Before you can create a new map, or add nodes to an existing map, you must know the IP address and host name for each node. The IP address must be written in dot notation, in which no single value exceeds 255 (for example, 125.4.254.11). Host names can be written with normal alphanumeric characters (for example, "bridge1"). Refer to the TCP/IP protocol software documentation for details of how to assign IP addresses and add them to the TCP/IP protocol hosts file.

Network Topology

Before creating a map, you must know the topology of the network, e.g., which interfaces are connected to which ports.

Creating a Net Hierarchy

RADview-HPOV/Lite automatically creates the root level of the maps, containing a WAN hierarchy icon. Below the WAN hierarchy are WAN submaps. Once a WAN submap has been defined, you can define individual WAN agents at the lowest map level.

To create a WAN submap:

1. In the root map, double-click the WAN hierarchy icon to open the submap.

2. From the Edit menu, select <Add Object>.

A dialog box opens with a selection of object classes (object palette).

Figure 3-5. Network Object Palette

3. Click the network type to display the network objects.



Creating an Agent for a RAD Device

You must create an agent for a RAD device in order to manage it.

To define an object for a RAD device:

1. Double-click a WAN submap to open a WAN agent map.

2. From the Edit menu, select <Add Object>.

A dialog box opens with a selection of object classes (object palette).

Figure 3-6. Connector Palette for the Device Agent (PS and RIC family)

3. Click the appropriate Net Device icon (from the choices in Symbol Class) to display the class net device objects.

4. Hold down the left mouse button while you drag the desired agent to the map.

5. Release the mouse button.

The Add Object dialog box appears.



Figure 3-7. Add Object

6. Enter a label for the object and select Yes to display the label on the map. The label is the node label, a string of up to 15 alphanumeric characters with no spaces (hyphens are permitted), that identifies the node on the map. It does not have significance outside RADview-HPOV/Lite.

Setting Selection Name and Selection Name Format

HP Open View identifies objects by their selection name, therefore each object must have a selection name. The length of a selection name is limited by the maximum number of characters allowed for file names by the operating system, or by 256 characters, whichever is lower. There are three ways to set a selection name:

• Enter text for the selection name in the Selection Name field

• Click <Set Selection Name> to display the set selection name dialog box. This box lists all the names that have been assigned to the object. Select a selection name from any of the names already assigned to the object, or enter text for the selection name of the object

• If no selection name is provided, HP Open View uses the name entered in the Label field as the selection name of the object.



It is not recommended to modify an icon’s selection name after it is already created and zoomed at least once. Instead, create a new node with new parameters.

Enter the selection name in one of the following formats:

• For an agent node, the selection name is the Internet host name for the object. The name must be valid and have an entry in the host's database. Alternatively, type the IP address in dot notation (for example, 192.1.0.1)

• For a hierarchy node, the selection name can be any string of alphanumeric characters(for example, "New York")

After the selection name is entered, the node appears on the map, with the information as specified. The information is automatically updated through periodic polling.

Setting Agent SNMP Parameters

Once the agent is added to the map, you can modify the default SNMP configuration. The SNMP parameters for all agents are defined using the SNMP configuration dialog box.

If you are using HPOV Version 7.51, then you must access the SNMP Configuration screen as the Unix root user.

To access the SNMP Configuration screen as root user:

1. Open a Terminal window.

2. In the Terminal window, change to superuser by typing su in the command line. Enter the superuser password when prompted.

3. To launch SNMP configuration, type in the command line: /opt/OV/bin/xnmsnmpconf

The SNMP configuration dialog box appears (see Figure 3-8).

To access the SNMP Configuration screen as regular user:

• From the Options menu, select SNMP Configuration.


Note



Figure 3-8. SNMP Configuration Dialog Box

The SNMP configuration dialog box consists of two main sections:

• The top portion of the dialog box contains the following three selection lists for the selected node or group of nodes:

SNMP configuration parameters for individual nodes

SNMP configuration parameters for a group of nodes selected via wildcard IP address

Default SNMP settings

• The bottom portion of the dialog box contains data entry fields for modifying existing parameters or entering new SNMP configuration parameters.

The following SNMP parameters can be modified using this dialog box:

Get Community – The community name that RADview-HPOV/Lite uses for SNMP Get operations.

Set Community – The string representing the community name in SNMP Set operations.



Timeout – The amount of time that RADview-HPOV/Lite waits for a response before retrying an SNMP request to the agent.

Retry Count – The maximum number of retries that RADview-HPOV/Lite performs before concluding that an agent is unreachable.

Status Polling – The frequency with which the application queries the agent status. This field is not relevant; the value actually used is taken from the Misc. > RADview/OV > General > Status Polling dialog box (see Chapter 4 for details).

To add new SNMP configuration parameters:

1. Enter the new information in the fields in the bottom half of the screen.

2. Click <Add>.

The definition is added to the appropriate selection list.

3. Click <Apply> and <OK> to save the changes.

To modify existing SNMP configuration parameters:

1. Highlight the entry in one of the selection lists.

The current definitions appear in the fields in the bottom half of the screen.

2. Make any desired changes and click <Replace>.

The modifications appear in the appropriate selection list.


Deleting an Agent

To delete a WAN agent:

1. Select the agent that you want to delete.

2. From the Edit menu, select either Delete from this Submap or Delete from all Submaps.

A delete confirmation dialog box appears.

Figure 3-9. Confirm Delete

3. Click <OK> to confirm the deletion.

Changing Agent Attributes

Map objects can be modified using the object's Symbol menu.



To modify a map object:

1. Right-click the node to open the Symbol menu.

2. Select Object Properties > General Attributes.

The Symbol Description dialog box appears.

3. Modify Label as desired.

4. Click <OK>.

You are prompted for confirmation of the modifications before saving. The Symbol Description dialog box closes and you return to the active map window.

Monitoring Agents

HPOV automatically polls each node in the network for connectivity status at specified intervals, and changes the color of the agent's background based on the results of the poll. The minimum default time between two successive polls is four seconds, and can be modified using the Status Polling command.

In addition, RADview-HPOV/Lite polls the agents itself, maintaining its own database for RAD agents in the system. Newly created agents are automatically added to the database. The agents are monitored for the presence of active alarms and tests. For information on displaying alarms, refer to Chapter 7.

Displaying Alarm Categories

In the RADview-HPOV/Lite screen, you can open the Alarm Categories window in order to select the type of traps and event messages for display. This window contains a choice of six types of alarm lists (see Figure 3-10).

Figure 3-10. Alarm Categories Window

Ending an HPOV session

To end your HP OpenView session you must log out.

To log out:

1. From the submap screen select Misc>RADview/OV>Logout.



The Logout dialog box appears.

Figure 3-11. Logout Dialog Box

2. Click <OK>.

User’s Manual Chapter 4 Configuration Management

RADview-HPOV/Lite Ver. 1.7 Setting the HPOV System Parameters 4-1

Chapter 4

Configuration Management This chapter describes the following configuration activities:

• Setting the HPOV System Parameters

• Licensing

• Performing Automatic Configuration Upload (ACU)

• Performing Backup and Restore

• Transferring Files Using TFTP

• Viewing the Net Inventory

• Setting Net Date and Time.

4.1 Setting the HPOV System Parameters

Setting the HPOV system parameters includes the following:

• Propagating the HPOV Map Status Color

• Disabling HPOV Autodiscovery

• Disabling Automatic Deletion of Nodes

• Setting Polling Interval, Timeouts, and Retries.

Propagating the HPOV Map Status Color

By default, the network node manager (NNM) does not propagate alarms. This can cause a mismatch between the hierarchy and the underlying nodes.

To set HPOV map status color propagation:

1. From the HPOV Map menu, click Properties.

2. In Compound Status, select Propagate Most Critical.

Disabling HPOV Autodiscovery

It is recommended to disable autodiscovery to avoid detection of irrelevant network elements, and to prevent overloading the management station.

Chapter 4 Configuration Management User’s Manual

4-2 Setting the HPOV System Parameters RADview-HPOV/Lite Ver. 1.7

To disable autodiscovery:

1. From the Options menu, click Network Polling Configuration.

2. Make sure all of the options are cleared in the General and IP Discovery tabs.

Disabling Automatic Deletion of Nodes

It is recommended to disable the option of automatically deleting nodes from the HPOV map, to avoid possible problems with managing devices and with global NMS applications (such as TFTP File Transfer).

To disable the delete nodes option:

1. From the Option menu, click Network Polling Configuration.

2. In the Status Polling tab, verify that Delete Nodes if Down for… option is cleared.

Setting Polling Interval, Timeouts, and Retries

RADview-HPOV/Lite automatically polls networks nodes periodically.

To set the polling interval time:

1. From the Misc. menu, select RADview/OV > General > Status Polling.

2. Set the desired polling interval. The default polling interval is five minutes.


Each SNMP request (for example an SNMP poll) has a timeout. A retry can be defined to compensate for the connectionless nature of the SNMP protocol. The timeout and retry values are defined using the SNMP Configuration screen.

If you are using HPOV Version 7.51, then you must access the SNMP Configuration screen as the Unix root user.

To access the SNMP Configuration screen as root user:



3. To launch SNMP configuration, type in the command line: /opt/OV/bin/xnmsnmpconf


To access the SNMP Configuration screen as regular user:

• Select SNMP Configuration from the Options menu.


To define the polling timeouts and retries in the SNMP configuration screen:

1. In the Target field, type the IP address of the node you plan to manage.

Note


RADview-HPOV/Lite Ver. 1.7 Licensing 4-3

2. In the Get community field, type the get community privilege password as defined in the device.

3. In the Set community field, type the set community privilege password as defined in the device.

4. In the Timeout field, type 10.0.

5. n the Retry count field, type 2.

6. Click <Add>, and then <OK> to implement the changes.

Figure 4-1. SNMP Configuration Window

4.2 Licensing

The RADview-HPOV/Lite licensing mechanism protects the system by restricting its installation to the specific host for which the license was generated. Product-specific licenses can be ordered in incremental sizes, to allow optimal correlation between the types of managed devices and size of the network, and the price of the management system.


4-4 Licensing RADview-HPOV/Lite Ver. 1.7

The RADview-HPOV/Lite licensing mechanism does not restrict or limit simultaneous usage by different users in Client-Server applications (RADview-EMS, RADview-SC/MDM, RADview-SC/TDMoIP or RADview-SC/Vmux), or in UNIX-based systems that are accessed simultaneously by several users via X-terminals (RADview-HPOV).

For full licensing terms, see the RADview-HPOV/Lite license agreement included in the RADview-HPOV/Lite package.

Network Size

Each SNMP network element managed by RADview-HPOV/Lite is subject to a license. Modules within a chassis, or non–SNMP devices that are managed by a central RAD SNMP–based unit, are not subject to a license. For example, cards within a DXC–30 chassis or a remote ASMi–52 modem connected to the DXC–30 do not require a license. Only the DXC–30 node requires a license. As another example, consider an LRS–24 modem rack, which allows you to manage not only the modem cards installed in the specific rack, but also the remote modems connected to these cards. In this case, only the LRS–24 requires a license. Standalone managed cards like HTU, HCD, and FOM are subject to a license.

Equivalent Node Weights

Each RAD manageable device is assigned an Equivalent Node Weight (ENW). Different devices are assigned different ENW values according to their complexity (starting from the lowest value of 1). The more complex the device, the higher the ENW. Managing a device with a higher ENW requires a larger number of license points.

A RAD node whose type cannot be identified by the License Server (such as when the device is disconnected or the NMS does not have the correct community name) is assigned a default value of 500.

Table 4–1 lists the equivalent node weights for RAD devices supported by RADview-HPOV/Lite.

Table 4–1. Equivalent Node Weights

Device ENW

APD-8 8

APS-8, APS-16 8

APS-24 8

Egate-20 25

Egate-100 130

FPS-8 8

RIC-155 8

RIC-155GE 10

Note



Device ENW

RICi-E1/T1 3

RICi-E3/T3 5

RICi-4E1/T1 5

RICi-8E1/T1 7

RICi-16E1/T1 22

RICi-155GE 55

RICi-622GE 60

RICi-SE 3

SPS-4 8

SPS-3S, SPS-6, SPS-12 8

Vmux-400 24

Bundled License Points

Every RADview package includes free-of-charge bundled license points that allow you to manage a small- to-medium-sized network (depending on the actual devices managed by the system). A larger network requires you to purchase and install additional license points, as the network expands.

Table 4–2 lists the RADview Lite packages and their bundled license points.

Table 4–2. Bundled Licenses

Platform Bundled License Points (Free of Charge)

RADview-HPOV/Lite 300

RADview-PC/Lite 100

Calculating License Points

To determine the number of license points required to manage a given network, perform the following calculation:

• Number of License points (for each product) = (Product type ENW) x (Number of elements of this product).

• When your network consists of different product types, total the number of license points for all product types.

However, since a particular number of license points is bundled within every RADview-HPOV/Lite package, the actual number of license points required can be calculated as follows:

Required license points = Total Number of License points (for all types) − RADview-HPOV/Lite package bundled license points.



The following is an example of calculating license points for a network to be managed by RADview-HPOV/Lite, with the following elements:

• Ten Egate-20 units

• Four RICi-E1/T1 units

• Two RICi-155GE units.

Referring to the equivalent node weights in Table 4–1, we find that:

• Egate-20 = 25 ENW

• RICi-E1/T1 = 3 ENW

• RICi-155GE = 55 ENW.

Referring to the bundled license points in Table 4–2, we find that the RADview-HPOV/Lite package includes a 300–point free–of–charge bundled license.

Thus, the license you need to order = ⎨(10x25) + (4x3) + (2x55)⎬ – 300 = 72.

Since the actual license size that is needed to manage the given network is 372, and 300 points are bundled free of charge within the RADview-HPOV/Lite package, you only need to order 72 additional license points.

To simplify the calculations for larger networks that contain many different products, use the RADview License Calculator. available online at the RAD distributor website.

Working with the License Service Manager

The License Service Manager application is a tool that is used to manage the License Server. The License Service Manager can be used to:

• Add/remove license files received from RAD

• Manage installed licenses

• View expiration dates

• View a list of all managed elements in the network, and their most recent access date/time

• View the Equivalent Node Weight (ENW) of managed elements.

To open the License Service Manager:

• Select: Misc > RADview OV > License Service Manager

The License Service Manager opens.

For UNIX stations, you must log into the system before opening the License Service Manager application.

Viewing the Installed License Points

The General tab (see Figure 4–2) allows you to check the potential growth of the system (for adding additional managed elements) by comparing the total installed license points with the consumed license points

Note

http://raddist-internal.rad.com/RADCnt/MediaServer/19150_RADview_Calc.xls�

http://raddist-internal.rad.com/Home/0,,3,00.html�

http://raddist-internal.rad.com/Home/0,,3,00.html�



The installed licenses table lists all the installed license files, and includes information on the license size, type of license (permanent or temporary) and host information.

Each entry in the table describes either a license with points or a license for a specific product or feature.

If a temporary license has expired, it is displayed as a red line in the table.

Figure 4–2. License Service Manager – General Tab

Table 4–3. License Status

Parameter Possible Values / Notes

Total installed license

points

Total license points to which you are entitled (for all valid licenses that have

not expired)

Consumed license points License points that you have already used (for elements managed by

RADview-HPOV/Lite)

ID Unique identifier given by RAD to a license file

Licnse points/Products License points included in the license file, or product(s) for which the license

is valid

Exp. Date Expiration date of a temporary license, or indication that license is permanent

Host Identifier Possible values for Unix: HOST ID, MAC Address, or Any Host

Possible values for Windows: IP Address, MAC Address, or Any Host

Platform Platform for which the license was generated (UNIX or Windows)

If your license is about to expire, or has already expired, an alert message appears every time you open an HPOV map, and every six hours subsequently (see Figure 4–3).



Figure 4–3. License Expiration Warning

Viewing the Managed Element List

The Managed Element List tab displays all the devices that are managed by RADview-HPOV/Lite.

Figure 4–4. Managed Element List



Figure 4–5. Managed Element List (Cont.}

Table 4–4. Managed Element List Parameters

Parameter Function

IP Address IP address of managed element

Name Selection name of managed element

Type Type of managed element

ENW Equivalent Node Weight of managed element

Last Host IP IP address of the last host management station that used managed element

Last Time Used Last date and time that managed element was used

• You can manage one agent from different RADview-HPOV/Lite maps without requiring an additional license. The RADview-HPOV/Lite license service makes sure that different logical representations of the same network element do not require duplicate licenses.

• A managed element is deleted from the list when it is deleted from the map of the client. If you delete it while this application is open, the change is not reflected in the Managed Element List until you refresh the entry (File > Refresh).

• By default, the display is ordered by IP Address. You can sort the list by clicking any column.

Note



Adding a License

To add a license file:

1. Display the License Service Manager – General tab.

2. Select File > Add License.

The Open License dialog box appears.

3. Locate and select the desired license file, and click <Save>.

The data of the new file is added as a new row in the General tab.

4. If the license file already exists, a message is displayed: This License already exists. Click <OK> and select the entry again.

The consumed license points must be less than the total license points.

Figure 4–6. License Server Manager –File Menu

Note



Figure 4–7. License Server Manager –Open License File Dialog Box

Removing a License

To remove a license file:

1. Click the General tab in the License Service Manager.

2. Select one of the rows (a license file).

3. Select File > Remove License.

If the selected row has a red background, it is removed from the General tab list.

If the removal of this row causes the Total Installed License Points to be greater than or equal to the Consumed License Points, the row is removed from the General tab list.



If the removal of this row causes the Total Installed License Points to be less than the Consumed License Points, the following warning message is displayed:

Figure 4–8. Remove License Warning

Click <OK> to confirm, or <Cancel> to cancel this operation.

If you click <OK>, the row is removed from the General tab list. You cannot continue to use management services until another valid license is added.

Each tab of the License Service Manager must be refreshed separately.

Starting and Stopping the License Service

The Service Console allows you to start or stop the License Server.

Figure 4–9. Action Menu

To start the License Server:

1. In the License Service Manager, select Action > Service Console.

2. In the Service Action field select Start, and click <Set>.

After a polling cycle completes, or after you select File >Refresh, the title bar of the License Service Manager contains: License Service Manager (Connected).

To stop the License Server:

1. In the License Service Manager, select Action > Service Console.

2. In the Service Action field select Stop, and click <Set>.

A message is displayed: Stopping License Server operation.

3. Click <OK> to confirm.

After a polling cycle completes, or after you select File >Refresh, the title bar of the License Service Manager contains: License Service Manager (Disconnected).

Note



Figure 4–10. Service Console

Configuring the Server Side License Ports

You can configure the Server side and the Client side via the License Service Manager Options menu.

Server Side configuration is applicable only if the Client and Server are installed on the same computer.

To configure the Server Side:

1. In the License Service Manager, select Options > Server Side Configuration.

2. Enter Socket Port and INS Port.

3. Click <Set>.

Figure 4–11. Server Side Configuration

Table 4–5. Server Side Configuration Parameters

Parameter Function

Socket Port Socket Port of the Server

Valid values: ≥ 1000 (blank is not a valid value)

INS Port INS Port of the Server


Note



Configuring the Client Side License Ports

To configure the Client Side:

1. Select Options > Client Side Configuration.

2. Select the Server CORBA Mode, and then enter Socket Port, INS Port, and Server IP Address.

3. Click <Set>.

Figure 4–12. Client Side Configuration

Table 4–6. Client Side Configuration Parameters

Parameter Function

Server CORBA Mode For future use

Socket Port Socket Port of the Server


INS Port INS Port of the Server


Server IP Address Server IP Address

A server and all its connected clients must always share the same values in the communication ports fields. If you make any changes to the Server Side Configuration, you must restart the License Server before they can take effect.

Note


RADview-HPOV/Lite Ver. 1.7 Performing Automatic Configuration Upload (ACU) 4-15

4.3 Performing Automatic Configuration Upload (ACU)

The Automatic Configuration Upload (ACU) application automatically initiates a periodic backup of the configuration of a predefined list of RAD devices. It is based on client/server architecture. The ACU application initiates the backup by requesting the device agents to start an upload TFTP session of Configuration and User files.

ACU can be used with products that support the TFTP option: Configuration Upload (see Table 4-13 on page 4-59).

For every RAD device in the predefined list, the ACU Server sends a request to start Trivial File Transfer Protocol (TFTP) to upload the Configuration and User files. The RAD device agent is responsible for the TFTP session; the ACU Server only sends a request to the agent to start a TFTP session. The result (success/failure) of every TFTP session is determined by the SNMP trap that is received from the agent, or by timeout (where result = failure).

The ACU Client is a graphical application that allows you to view and configure parameters of the ACU Server, as well as to display results of upload sessions that have completed. Any number of Client applications can be opened simultaneously. Uploads take place if the Server is running, even if the Client is closed.

The Client can configure the following Server parameters:

• Date and Time to start the upload

• Time interval for the upload sessions

• Location of the uploaded files

• TFTP parameters

• Nodes in the agent list.

Configuring the TFTP Server for ACU

Verify that the TFTP Server is enabled before you begin the ACU application.

To set up the TFTP server:

1. Ping the connected agent from the TFTP Server, to check that the agent is connected to the station running the TFTP Server.

2. Login as root.

3. Create the directory in which to save the ACU file. Type: mkdir –p <directory name> (e.g. mkdir –p /export/home/tftp).

4. If you plan to perform ACU, save the software code file in the directory you created in the previous step.

Note


4-16 Performing Automatic Configuration Upload (ACU) RADview-HPOV/Lite Ver. 1.7

5. Change the permission of the directory you created to Read/Write: Type: chmod -R 777 <TFTP_boot_dir> (e.g. chmod –R 777/export/home/tftp).

6. Edit the /etc/inetd.conf file in order to enable the TFTP Server and to specify the location of the ACU files. Follow the next steps to edit the /etc/inetd.conf file using the Text Editor.

a. Right-click in the desktop and select Text Editor from the Application menu.

b. From the File menu select Open.

c. Type: /etc in the Enter Path or File Name field.

d. Click <Update>.

e. Type: inetd.conf in the Enter a File Name field.

f. Click <OK>.

g. Search for the line starting with #tftp. (e.g. # tftp dgram udp). Remove the # sign and remove 6 from udp6 (see Figure 4-13 for an example of the inetd file).

h. At the end of that line is the text –s <TFTP_boot>. Change <TFTP_boot> to the directory you just created. (e.g. /export/home/tftp).

If the tftp line in the inetd.conf file does not begin with #, this means that the TFTP Server is already enabled. In this case you can use either the specified <TFTP_boot> directory or change it and follow the next steps.

7. Save the inetd.conf file with the current changes. From the File menu, select Save and then Close the Text Editor.

8. Reboot the UNIX workstation: Type: sync Type: init 6

Note



Figure 4-13. File Edit for the TFTP Server

Manually Starting or Stopping the ACU Server

The ACU server automatically starts when the workstation is booted up. However, the root user can start or stop the ACU server manually if necessary.

Before stopping the ACU server, it is recommended to close the ACU client application (refer to Closing the ACU Client Application).

To start the ACU server:



3. Type /etc/rc3.d/S99AcuServer start to start the ACU server.

To stop the ACU server:



3. Type /etc/rc3.d/S99AcuServer stop to stop the ACU server.

Note



Launching the ACU Client Application

Before starting the ACU client application, ensure that RADview HPOV and a TFTP server are running. If the TFTP Server is not running when the ACU application tries to initiate an upload session, the error message shown below appears. This message appears for any activity that requires the TFTP server to be running.

Figure 4-14. TFTP Disabled Error Message

To log in:

1. Log in to Solaris as a RADview HPOV user.

2. Type ovw & in the terminal window.

HP OpenView is launched.

3. Log in to RADview:

a. Select: Misc > RADview/OV > Login…

b. Use the Default Administrator Account to log into the system: User: root/ password: root

c. Click <OK>.

Only RADview HPOV administrators are privileged to use the ACU application.

To launch the ACU client application:

• Select: Misc > RADview/OV > General > Auto Config Upload:Start Client to start the ACU client.

Note



Figure 4-15. Launching the ACU Client Application

If the ACU server is running, the ACU main window appears (see Figure 4-17), containing the Report Table. If the ACU Server is not running, an error message is displayed (see Figure 4-16) and the ACU client does not start.

Figure 4-16. ACU Server Disabled Error Message



Figure 4-17. ACU Client main window

The Report Table window displays entries according to the selected level of detail, showing currently defined automatic upload profiles and agents, along with the results/last status of the uploads.

For each ACU profile, the Report Table shows:

• Node Name – Selection name of the node (agent) belonging to the profile

• Type (OID) –RAD device OID as defined in the NMS database

• Time –Date/time of last event such as SNMP transaction/trap, or creation/removal of directory

• File Type –Indicates Configuration or User. The User type is applicable only for some legacy agents. The report contains separate rows for Configuration and User files. If the File Type is not relevant to the row in the Report Table, it contains three dashes.

• Last Status –The last status reported by the device agent

• File’s Location: – Location of uploaded files.

You can schedule an automatic upload for a preset date and time, by setting the profile parameters for the desired time and interval, and selecting nodes for the profile (see Configuring ACU Profiles).

When the starting date and time for an upload arrives, the upload session is initiated by the ACU Server, if the profile is active. When the upload session has completed, the result is displayed in the Report Table.

Summary of ACU Tasks

Table 4-7 lists the ACU tasks and the corresponding commands.



Table 4-7. ACU Tasks

Task Dialog Box and Parameter Location

Path

Configuring ACU

TFTP Settings

ACU TFTP Settings dialog box

(Figure 4-18)

Options

General TFTP Settings

Configuring profiles

(Use this option to

schedule uploads.)

ACU Profiles window

(Figure 4-19)

Options

Profile

Uploading configuration

immediately

Upload Configuration

Confirmation dialog box

(Figure 4-25)

Configuration

Upload Now

Filtering report Report Table Filter dialog box

(Figure 4-28)

Configuration

Report

Report Table Filter

Refreshing report There is no dialog box. Configuration

Report

Refresh

Saving report as file Save Report dialog box

(Figure 4-36)

Configuration

Report

Save As…

Printing report Print Report dialog box

(Figure 4-39)

Configuration

Report

Print

Clearing report Clear Report dialog box

(Figure 4-40)

Configuration

Report

Clear

Exiting ACU application Exit ACU dialog box (Figure 4-44) Configuration

Exit

Configuring ACU TFTP Settings

The ACU application uses TFTP to perform uploads from the RAD devices.

To set the ACU TFTP parameters:

1. From the Options menu select General TFTP Settings.

The TFTP Settings dialog box appears (see Figure 4-18). Table 4-8 describes the parameters in the TFTP Settings dialog box.

2. Enter File’s Location or press <Browse> to select File’s Location.

3. Enter values for Total Timeout and Retry Timeout.

4. Press <Set> to close the TFTP Settings dialog box and apply your settings.



Figure 4-18. TFTP Settings

Table 4-8. TFTP Settings

Parameter Function

TFTP Server IP Due to UNIX security, it must be the local computer. This parameter cannot

be changed.

File’s Location The path where all upload directories are created and saved

For UNIX: Must be an existing directory under the TFTP home directory For PC : Must be an existing directory

Default: TFTP home directory

Total Timeout (sec) The maximum amount of time during which the agent tries to perform the

configuration upload via TFTP, including multiple retry attempts

1 to 600

Default = 60

Retry Timeout (sec) The maximum amount of time during which the agent tries once to perform

the configuration upload via TFTP

1 to 120

Default = 15

Note: Retry timeout must be less than Total timeout.

Configuring ACU Profiles

An ACU profile consists of a defined time interval and a set of nodes (agents) for which to perform the upload. The ACU Profiles window displays the details of all the currently defined automatic upload profiles. Each profile is shown on a single row.

To display the ACU Profiles window:

• In the Report Table, select Options > Profiles.

The ACU Profiles window appears (see Figure 4-19).



Figure 4-19. ACU Profiles Window

The color of each row indicates the profile’s status:

• Green – The profile is active. Automatic configuration uploads are performed for the objects belonging to the profile.

• Gray – The profile is not active. Automatic configuration uploads are not performed for the objects belonging to the profile.

Adding a Profile

To add a profile:

1. In the ACU Profiles window, click Add.

The Add Profile dialog box appears (see Figure 4-20).

2. Enter the profile parameters according to Table 4-9.

3. Click Set to close the Add Profile dialog box and save the profile data.

The new profile is shown in the ACU Profiles window.



Figure 4-20. Add Profile Dialog Box

Editing a Profile

1. In the ACU Profiles window, select the profile that you wish to edit, and click Edit.

The Edit Profile dialog box appears (see Figure 4-21).

2. Edit the profile parameters according to Table 4-9.

3. Click Set to close the Edit Profile dialog box and save the changed profile data.



Figure 4-21. Edit Profile Dialog Box

Table 4-9. Profile Parameters

Parameter Function

Start Date Date of first upload session (a new date must be in the future)

Default value: current date

Start Time Time of first upload session (a new time must be in the future)

00:20 – 23:20

Default value = 00:20

Note: The upload times are set for 20 min. after the hour to allow for periodic tasks that might be performed hourly, and avoid processor overload.

Time Intervals Time period for periodical upload sessions

1 Hrs, 2 Hrs, 3 Hrs, 4 Hrs, 5 Hrs, 6 Hrs, 8 Hrs, 12 Hrs, 1 Day, 2 Days, 3 Days,

1 Week, 10 Days, 2 Weeks, 30 Days

Default value = 1 Day

No. of Saved Sessions Number of upload sessions shown in report or number of directories in root

3–1000

Default value = 30

Note: If No. of Saved Sessions (“n”) is larger than the number of existing Upload sessions, then only the last “n” sessions are saved in the Reports. Also, the last “n” directories that were created are saved.

Activity Specifies whether this profile is Active or Not Active



Parameter Function

Next Session Time

(Read only)

Date and nearest time of next upload

Equals (<Start Date & Time> + K*<Time Interval>) where K is integer,

or, if is any session was missed - it is the nearest XX:20 (HH:MM).

Timeout Values Determines whether the profile uses the timeout value from the ACU TFTP

Settings, or uses its own timeout values

General – The TFTP timeout values (see Table 4-8) are used for this profile. The

Total Timeout and Retry Timeout parameters are not accessible for the profile if

Timeout Values parameter is set to General.

Specific – This profile uses the Total Timeout and Retry Timeout as timeout values

Total Timeout The maximum amount of time during which the agent tries to perform the

configuration upload via TFTP, including multiple retry attempts

1 to 600

Default = 60

Retry Timeout The maximum amount of time during which the agent tries once to perform the

configuration upload via TFTP

1 to 120

Default = 15

Note: Retry timeout must be less than Total timeout.

Selecting Nodes for a Profile

You can add nodes or remove nodes for a specific profile, by using the Object Selection dialog box (see Figure 4-22). To open the Object Selection dialog box, select the profile in the ACU Profiles window, and click Object Selection.

In the Object Selection dialog box, the Objects window contains a tree showing the WAN map hierarchy, with nodes that support the ACU application. The profile window contains the nodes selected for the profile. The selected nodes are colored as follows:

• Black – the node was selected from the active map

• Purple – the node was selected from a map that is no longer the active map

• Blue – the node was selected from a map that is not recognized by HPOV.

• If you want to add nodes from a different WAN map than that currently active, you can open the desired WAN map, and then click <Reload Map> to load the map hierarchy into the Objects window.

• If you add objects to the active WAN map, click <Refresh Objects> to load the new objects into the Objects window.

To add node objects to a profile:

• In the Object Selection dialog box, select the node in the Objects window and click Add.

The node is removed from the Objects window, and appears in the profile window.

Note



To remove node objects from a profile:

• In the Object Selection dialog box, select the node in the profile window and click Remove if the node is colored black or blue. You must click Delete to remove nodes that are colored purple.

The node is removed from the profile window, and appears in the Objects window.

When you have completed adding/removing nodes, click Set to close the Object Selection dialog box.

Figure 4-22. Object Selection Dialog Box

Removing a Profile

To remove a profile:

1. In the ACU Profiles window, select the profile that you wish to remove, and click Remove.

A dialog box appears prompting you to confirm the removal of the profile (see Figure 4-23).

2. Click OK.

The profile does not appear in the list of profiles.



Figure 4-23. Remove Profile Confirmation

Deactivating a Profile

You can deactivate a profile to stop uploads from being performed for objects corresponding to the profile.

• In the ACU Profiles window, select the profile that you wish to deactivate, and click Deactivate.

In the ACU Profiles window, the row containing the profile is colored gray. Uploads are not performed for objects corresponding to the profile.

Activating a Profile

You can activate an inactive profile to start uploads for objects corresponding to the profile.

• In the ACU Profiles window, select the profile that you wish to activate, and click Activate.

In the ACU Profiles window, the row containing the profile is colored green. Uploads are performed for objects corresponding to the profile.

Refreshing the List of Profiles

• In the ACU Profiles window, click Refresh.

The list of profiles is refreshed.

Performing Immediate Configuration Upload

To upload a configuration immediately:

1. From the Configuration menu, select Upload Now.

The Upload Now dialog box appears with a list of profiles and nodes that can be uploaded.



Figure 4-24. Upload Now Dialog Box

2. Select the profiles in the list for which you would like to upload the configuration immediately, and click <Set>.

The Automatic Configuration Upload confirmation dialog box appears, prompting you to confirm immediate configuration upload for the specified number of profiles and nodes.

Figure 4-25. Upload Now Confirmation Dialog Box

3. Click OK.

The upload sessions are initiated by the ACU Server. While the uploads are being performed, the following status bar messages are displayed:

“Uploading (Started at <HH:MM:SS>)”

“Uploading - <x> from <y> nodes already uploaded”

“Uploading - <x> from <y> nodes already uploaded (Iteration No. 2)”, in the event that a second or further retry is performed.

When all the upload sessions have completed, the Report Table displays the results of the uploads.

During the upload session, all menus are disabled (except Report→Save As…/ Print… and Help).

Note



Working with the ACU Report Table

The Report Table can be filtered to show varying levels of details, or specific agents. It can also be sorted by columns.

Figure 4-26. ACU Report Table

The Last Status column indicates the status of the last operation. See Table 4–10 for a list of possible messages, and the color of the rows in the report table.

Table 4–10. ACU Status Messages

Message (Standard TFTP messages) Color

Connecting… White

Connected. Transferring Data White

Giving up. Server does not respond Red

File successfully transferred Green

File not found Red

Illegal TFTP operation Red

Unknown transfer ID Red

Server overflow Red

No available UDP port Red

No available connection Red

Illegal file mode Red

Illegal PDU size Red

Rebooting... Red



Device successfully upgraded Red

Device successfully rebooted Red

No SNMP connectivity Red

Connection with agent is lost. No Indication for

End-of-TFTP Process

Red

Unknown sysObjectID Red

Access violation Red

File already exists Red

No such user Red

TFTP server does not exist Red

Wrong license format Red

License ID already used Red

Created new directory White

Directory removed Yellow

TFTP Server not in service Red

TFTP Root does not exist Red

Unable to create Upload directory Red

Unable to create Upload file Red

Agent reject request to Upload file Red

Unknown error Red

Time-Out. Node didn’t finish TFTP session Red

Can’t remove Directory Red

The Report table can be sorted by any of its columns by clicking the column heading. For instance, you can sort the report table by its last status colors by clicking the Last Status column heading (see Figure 4-27).



Figure 4-27. ACU Report Table – Sorted According to Last Status

Filtering the Report

You can filter the table by:

• Report detail level – display profile only, profile and node, or detailed information

• Agent types – display only rows corresponding to specific agent types

• Profiles – display only rows corresponding to specific profile

• Number of sessions displayed.

You can filter the reports by using the Report Table Filter dialog box (see Figure 4-28), which appears when you select Configuration > Report > Report Table Filter.

Figure 4-28. Report Table Filter

To filter the report level detail:

1. In the Report Table Filter dialog box, select the desired Report Level (see Figure 4-29):



Profiles only – One row is displayed per profile

Profiles and nodes – One row is displayed per node (agent)

Detailed – One row is displayed for each phase of the upload operation, with empty lines separating the upload sessions.

2. Click Set to save your changes

The Report Table is shown with the selected detail level. See Figure 4-30 through Figure 4-32 for examples of the different detail levels.

Figure 4-29. Report Level Filtering

Figure 4-30. ACU Report Table – Profiles Only



Figure 4-31. ACU Report Table – Profiles and Nodes

Figure 4-32. ACU Report Table – Detailed

To filter the agent types displayed:

1. In the Report Table Filter dialog box, click Edit next to Non-Displayed Agent Types.

The Edit Filtered Agent Types dialog box appears (see Figure 4-33).

2. Use the Add and Remove buttons to move agents between the displayed and non-displayed lists.

3. Click OK to save your changes.

The Edit Filtered Agent Types dialog box closes.

4. Click Set to close the Report Table Filter dialog box.

In the Report Table, agent types from the non-displayed list are not shown.



Figure 4-33. Edit Filtered Agent Types

To filter the profiles displayed:

1. In the Report Table Filter dialog box, click Edit next to Non-Displayed Profiles.

The Edit Filtered Profiles dialog box appears (see Figure 4-34).

2. Use the Add and Remove buttons to move profiles between the displayed and non-displayed lists.

3. Click OK to save your changes.

The Edit Filtered Profiles dialog box closes.

4. Click Set to close the Report Table Filter dialog box.

In the Report Table, profiles from the non-displayed list are not shown.



Figure 4-34. Edit Filtered Profiles

To filter the number of sessions displayed:

1. In the Report Table Filter dialog box, enter the desired value in Max Number of Displayed Sessions.

2. Click Set to save your changes

In the Report Table, the selected number of sessions is displayed. If more sessions exist than the number to be displayed, the more recent sessions are displayed. See Figure 4-35 for an example of displaying maximum three sessions.



Figure 4-35. ACU Report Table – Maximum of Three Sessions Displayed

Refreshing the Report

To refresh the report table:

• From the Configuration menu, select Report and then Refresh.

The report table entries are refreshed.

Saving the Report

The currently displayed ACU report (filtered or full) can be saved in the following file formats:

• CSV – Comma separated values; can be viewed in Microsoft Excel or any other compatible viewer.

• PDF – Portable document format; can be viewed in Adobe Reader or any other compatible viewer.

• HTML – Can be viewed in any browser.

To save the ACU report to a file:

1. From the Configuration menu, select Report and then Save As.

The Save dialog box appears (see Figure 4-36).

2. From the Save In list box, select the target directory.

3. In File Name, enter the file name and then select its type (CSV, PDF, or HTML)

4. Click Save.



The report is saved as specified. See Figure 4-37 and Figure 4-38 for examples of the report saved in CSV and PDF format, respectively.

Figure 4-36. Save Dialog Box

Figure 4-37. ACU Report in CSV Format



Figure 4-38. ACU Report in PDF Format

Printing the Report

To print the report:

1. From the Configuration menu, select Report and then Print.

The Print dialog box appears (see Figure 4-39).

2. Enter the Print parameters.

3. Click Print.

The report is printed.



Figure 4-39. Print Dialog Box

Clearing the Report

You can clear the Report Table of all displayed profiles.

To clear the report:

1. From the Configuration menu, select Report and then Clear.

The Clearing Report confirmation dialog box appears (see Figure 4-40).

2. Press <OK>.

The Report Table is cleared of all displayed profiles (see Figure 4-41).

Figure 4-40. Clearing Report Dialog Box



Figure 4-41. Report Table, Cleared

Accessing Help

The Help menu provides access to the user manual and details about the application.

Figure 4-42. Help Menu

To access the user manual:

• In the Automatic Configuration Upload window, select Help > User’s Manual.

The user manual is displayed.

To display details about the application:

• In the Automatic Configuration Upload window, select Help > About.

Details about the application are displayed.



Figure 4-43. ACU Details Window

Closing the ACU Client Application

To exit the ACU client application:

1. From the Configuration menu select Exit.

The Exit Automatic Configuration Upload confirmation dialog box appears (see Figure 4-44).

2. Press <OK>.

The ACU client application closes.

Figure 4-44. Exit ACU Dialog Box


RADview-HPOV/Lite Ver. 1.7 Performing Backup and Restore 4-43

4.4 Performing Backup and Restore

RADview-HPOV/Lite system components are backed up and restored by the Backup/Restore scripts. This includes:

• Database backup – backs up the entire database.

• RV backup – backs up HPOV security files.

• License backup – backs up the RADview-HPOV/Lite license files

• Map backup – backs up the map: HPOV or RADview-NTM contents of all existing maps.

There is no backup and restore support for TFTP files. If you would like to back up TFTP files, refer to Defining Backup/Restore for Additional Files.

You can perform both the backup and restore operations from the same machine or from different machines.

Backup and Restore Requirements

• The Backup and Restore scripts require Informix version 7.3 or higher, or Oracle 10g.

• The same installations of RADview-HPOV/Lite (packages and products) and Informix (home directory) are required on both the source station and destination stations.

Do not use the Backup & Restore tool with one EMS station and one non-EMS station.

• The same version of the Backup/Restore scripts should be used in the process (the Restore script verifies this requirement).

• When backing up/restoring the map, the same map version should be installed on the source and destination stations.

• When backing up/restoring the database, the same Informix version should be installed on the source and destination stations.

If Informix is used as a database, four files are placed in the /opt/MNG/MNGVIEWHP/bin directory: mng164_backup, mng164_restore, mng164_backup.xml, and mng164_restoreAnswers.

If Oracle is used as a database, the files import.sql, drop_ems.sql, and drop_netdbs.sql are placed in the /opt/MNG/MNGVIEWHP/bin directory.

Note

Notes

Note


4-44 Performing Backup and Restore RADview-HPOV/Lite Ver. 1.7

Configuring Backup and Restore

Configuring Backup and Restore Scripts Manually

The RADview-HPOV/Lite Backup and Restore scripts should be installed as part of the RADview-HPOV/Lite setup. Some manual configuration may be needed for Informix or Oracle.

To configure the Backup and Restore scripts when Informix is used:

1. Log in as a RADview user.

2. Verify that the INFORMIXDIR environment variable is defined, by typing: env | grep INF

The following text should appear (Replace <INF_HOME> with the Informix installation directory, for example, /export/home/informix, or /opt/informix). If the text does not appear, check your installation): INFORMIXDIR=<INF_HOME> INFORMIXSERVER=mng164 INFORMIXSQLHOSTS=<INF_HOME>/etc/sqlhosts

3. Verify that the onconfig.ows file exists in the <INF_HOME>/etc directory, and then change the following three lines in it as shown: TAPEDEV /backup_destination TAPEBLK 128 TAPESIZE 2000000

4. Save the changes to the onconfig.ows file.

The Backup and Restore scripts are ready for use.

To change the onconfig.ows file, you must have root user permission. This can be accomplished in two ways:

• Change to root user by typing su and when prompted, the root password. Then open the file using a text editor application, e.g. vi.

– Or –

• Log in (via the CDE window) as a root user and edit the file using a text editor application.

To configure the Backup and Restore scripts when Oracle is used:

No operations.

Configuring Backup and Restore Files

Before backing up or restoring files, the following backup configuration files located in the opt/MNG/MNGVIEWHP/bin directory must be configured:

• mng164_backup.xml file. This file includes:

Information about the backup/restore version

Configuration parameters for the backup and restore process

Parts of the RADview-HPOV/Lite system to be backed up/restored

Backup destination directory in which to create backup files

Note



Restore source directory from which to take restored files.

• mng164_backup_extra file. This file lists additional files to be backed up in addition to default files.

The mng164_backup.xml file is automatically created. The mng164_backup_extra file must be created and added to the directory.

Setting Parameters in the mng164_backup.xml File

The following sections explain how to configure parameters in the mng164_backup.xml file.

Defining the Database Type

You must define the type of database to be backed up/restored.

To define the database type:

• Set the values for the following parameters:

Oracle Database Parameter Value

<dbtype_oracle> true

<dbtype_informix> false

Informix Database Parameter Value

<dbtype_oracle> false

<dbtype_informix> true

Defining Full or Partial Backup/Restore

The backup/restore operation is performed separately for the database, RV, license, and map. Accordingly, you can choose to backup/restore selected system components, or perform a full backup/restore operation.

To define a full backup/restore:

1. Open the mng164_backup.xml file.

2. Set the full_backup/full_restore value to true.

To define a partial backup/restore:


2. Set the full_backup/full_restore value to false.

3. Set the values of the parts you want to backup/restore to true and the values of the unwanted parts to false.

To define the IP address of a station where backup is performed:


2. Set <used_ip_address_backup> to your station’s IP address.

Note



To define the IP address of a station where restore is performed:


2. Set <used_ip_address_restore> to your station’s IP address.

Defining the Backup/Restore Location

By default, the backed-up files are located in the opt/MNG/MNGVIEWHP/bin directory. You can change the location of this directory by changing its value in the mng164_backup.xml file.

Defining Backup/Restore Mode

There are two modes for backup:

• Simple backup

• DateTime backup – based on date and time.

In simple backup mode, during the backup process a new directory named WORKING is created under the opt/MNG/MNGVIEWHP/bin directory. Once the backup is completed successfully, WORKING is renamed to CURRENT, in accordance with the following conditions:

• If a CURRENT directory already exists, the old one is first renamed to PREVIOUS.

• If any errors occurred during the backup process, the WORKING directory is renamed to PARTIAL (if there was already a directory named PARTIAL, it is removed).

In dateTime backup, each backup creates a new directory under the opt/MNG/MNGVIEWHP/bin directory with a unique name according to the current time and date, e.g. 18-7-2005-11.51.03. In this mode, no PARTIAL directory is created if an error occurs.

To define the required backup mode as simple or dateTime:

• Change the relevant values in the mng164_backup.xml file to true or false according to the required mode.

Defining Backup/Restore for Additional Files

You can use the backup/restore scripts to back up and restore additional files that do not belong to the RADview application and are not backed up by default. The additional backed-up files are compressed into the mng164_backup_extra.cpio file.

To enable backup/restore of additional files:

1. Set the value of the <extra_restore> parameter to true.

2. Configure the mng164_backup_extra file, as explained in the following paragraphs.

To add additional files/directories to be backed up/restored, you must define them in the mng164_backup_extra file, located in the opt/MNG/MNGVIEWHP/bin directory. If the file does not exist, you must create it.



For the extra files to be backed up/restored, the <extra_restore> parameter in the mng164_backup.xml file must be set to true.

The mng164_backup_extra file contains one line for each file/directory to be backed up/restored. You must include the full paths and file names, for example:

/export/home/testing/BITMAPS/informix.gif

/export/home/testing/BITMAPS/oracle.gif

/export/home/testing/.cshrc

/export/home/testing/832474bf.lic

/opt/MNG/MNGVIEWHP/bin/mng164_backup.xml

Do not include the following:

• Nonexistent files

• Asterisks

• Blank rows.

Backing Up System Components

In case SC-TDMoIP is installed and you want to back up the database, open the /opt/MNG/MNGVIEWHP/WAN/bin/sc/mng164_sc_tdmoip_server file and verify that there is no & sign at the end of the file.

You can run the backup script without an input argument or with one input argument. The default value for running the script is:

/opt/MNG/MNGVIEWHP/bin/mng164_backup

If you have several required XML files (where each XML file defines which component has to be backed up and restored) you can run the backup script as follows:

/opt/MNG/MNGVIEWHP/bin/ mng164_backup <FILENAME>.xml (<FILENAME> stands for the name of the XML file)

The XML file must be a legal configuration file with correct syntax, otherwise the scripts might not work properly.

To run the backup process:

1. Type su and when prompted, type the root password.

2. If the Informix database s being used, verify that the Informix server is online, by typing onstat.

The following text appears if the Informix server is online: Informix Dynamic Server Version 7.31.UD1 -- On-Line – Up 00:03:29 -- 12352 Kbytes

3. Verify that the full path of the backup destination is defined in the mng164_backup.xml file.

Note

Note

Note



4. Perform one of the following to run the backup:

If you want to run the backup by using the mng164_backup.xml file, type: /opt/MNG/MNGVIEWHP/bin/mng164_backup

Alternatively, if you want to run the backup by using a different XML file, type: opt/MNG/MNGVIEWHP/bin/mng164_backup <FILENAME>.xml (<FILENAME> stands for the name of the required file).

Once the backup operation is completed, two files are located in the relevant directory according to the backup mode. One file is a compressed file containing all the backed-up data (mng164_backup.tar.Z), and the second is the backup log file (mng164_backup.log). If the backup was successful, the WORKING directory is renamed to CURRENT.

Read mng164_backup.log carefully to verify that there were no warnings/errors during the backup process.

• The backup can be performed when RADview-HPOV/Lite is online.

• During map backup, if HPOV is used, the OVbackup utility is used. It has two modes of backup: operational and analytical. The default backup is operational; Analytical backup is required when you use Data Warehouse or SNMP collector.

If you want to perform an analytical backup, change the HPOV_ANALYTICAL variable value in the backup script to true. In this case, the backup process does not run if the size of the OV analysis database exceeds 2GB (the default OV value).

Restoring System Components

Before running the restore script, check that:

• The directory of the mng164_backup.tar.Z source file is compatible with the restore_source value in the mng164_backup.xml file. Change the value if needed according to the source directory.

• The backup log file indicates that all the parts you want to restore were backed up successfully. Otherwise, the script exits with an error message.

To run the restore process:

1. Type su and when prompted, type the root password.

2. Close HPOV.

3. Stop any existing Service Center server (TDM, TDMoIP, or Vmux) if it is running on the station.

4. Verify that the restore source directory is defined with full path in the mng164_backup.xml file, and check that the correct mng164_backup.tar.Z file exists in this directory.

5. Activate a tcsh or csh shell by typing tcsh or csh.

Note

Notes



6. Perform one of the following to run the restore:

If you want to run the restore by using the mng164_restore.xml file, type: /opt/MNG/MNGVIEWHP/bin/mng164_restore

Alternatively, if you want to run the restore by using a different XML file, type: /opt/MNG/MNGVIEWHP/bin/mng164_restore <FILENAME>.xml (<FILENAME> stands for the name of the required file).

7. The following confirmation message appears: Restore will overwrite all your current data, do you want to continue?

8. Type y to continue.

The restore starts. The figure below shows an example of the messages that are displayed during the restore process.

Figure 4-45. Restore Process Messages

The restore process may take between 10 and 15 minutes, depending on the amount of data being restored. Let the process run until it completes. Stopping the restore process while it is running may cause database corruption and other problems.

9. After the restore operation is completed, the file mng164_restore.log is placed in the restore source directory. Read mng164_restore.log carefully to check if all the selected parts were successfully restored.

License restore can only be performed on the same station on which the backup process was performed.

10. Activate a tcsh or csh shell by typing tcsh or csh.

11. If an application requiring the EMS server is running on the station (e.g. RV-EMS-NGN, etc.), then to start the EMS server, type: /etc/rc3.d/S98RvEmsServer start

12. Start the ACU server by typing: /etc/rc3.d/S99AcuServer start

To restore a backed-up file on another computer:

1. Create a new directory named CURRENT in /opt/MNG/MNGVIEWHP/BACKUP on a computer where you intend to restore a previously backed up file. For example: mkdir /opt/MNG/MNGVIEWHP/BACKUP/CURRENT.

2. Copy the backed-up file to the CURRENT folder.

3. In the /opt/MNG/MNGVIEWHP/bin directory configure the mng164_backup.xml file for the required type of backup/restore operation.

Caution

Note


4-50 Transferring Files Using TFTP RADview-HPOV/Lite Ver. 1.7

4.5 Transferring Files Using TFTP

TFTP File Transfer is a RADview system application. The TFTP File Transfer application provides you with a tool for upgrading software embedded in RAD devices, or performing upload/download of device configuration. The TFTP File Transfer application is based on the following principles:

• TFTP protocol is used for file transfer

• The agent acts as a TFTP client, while the TFTP server is installed on the host

• The application manages multiple downloads to several agents at the same time according to the date and time settings

• During the TFTP process, the agent sends traps to the NMS to indicate the download status.

Configuring the TFTP Server

Before you can use the TFTP File Transfer application, you must configure the TFTP server.

To configure the TFTP server:

1. Ping the connected agent from the TFTP server, to make sure that the agent is connected to the station running the TFTP server.

2. Log in as root user: type su and when prompted, type the root password.

3. Create the directory in which to save the transferred files. Type: mkdir –p <directory name> (e.g. mkdir –p /export/home/tftp)

4. If you plan to perform TFTP File Transfer, save the software code file in the directory created in the previous step.

5. Change the permission of the directory created previously to read/write: Type: chmod -R 777 < directory name> (e.g. chmod –R 777 /export/home/tftp)

6. Edit the /etc/inetd.conf file in order to enable the TFTP server and to specify the location of the TFTP File Transfer files. Follow these steps to edit the /etc/inetd.conf file using the Text Editor:

a. Right-click the desktop and from the Application menu select Text Editor.

b. From the File menu select Open to open the Text Editor.

c. Type: /etc in the Enter Path or File Name field.

d. Click Update.

e. Type: inetd.conf in the Enter a File Name field.

f. Click OK.

g. Search for the line starting with #tftp. (e.g., # tftp dgram udp6). Remove the # sign and remove 6 from udp6.


RADview-HPOV/Lite Ver. 1.7 Transferring Files Using TFTP 4-51

h. At the end of that line is the text –s <TFTP_boot>. Change <TFTP_boot> to the directory created previously. (e.g., /export/home/tftp).

If the tftp line in the inetd.conf file does not begin with #, this means that the TFTP server is already enabled. In this case you can use the specified <TFTP_boot> directory or change it and follow the next steps.

i. Save the inetd.conf file with the current changes. From the File menu, select <Save> and then <Close> the Text Editor.

7. Reboot the UNIX workstation: Type: sync Type: init 6

8. Perform the following steps after the reboot:

a. Type: svcs |grep tftp.

No output should result. If you get the message in section (h), then your configuration is already set.

b. Type: inetconv. This command converts all entries from /etc/inetd.conf to SMF entries.

c. Type: svcs |grep tftp.

The following is displayed:

Figure 4-46. Adjusting the TFTP Server

Opening the TFTP File Transfer Application

Before starting the TFTP File Transfer application, ensure that RADview-HPOV/Lite and a TFTP server are running.

To start the TFTP application:

1. Login to Solaris as a RADview-HPOV/Lite user.

2. Type: ovw & from an X-terminal window.

3. Login to RADview-HPOV/Lite:

a. From the Misc menu select RADview/OV > Login.

b. Use the Default Administrator Account to log into the system: User: root, password: root

c. Click <OK>.

4. From the Misc menu select RADview/OV > General> TFTP File Transfer Application (see Figure 4-47).

The TFTP File Transfer window appears (see Figure 4-48).

Note



Only RADview HPOV administrators are allowed to use the TFTP File Transfer application.

Figure 4-47. Opening TFTP File Transfer Menu

Figure 4-48. TFTP File Transfer – Opening Window

When using the TFTP File Transfer application for the first time, the initial configuration includes the following procedures:

• Defining agents and associated download data in the TFTP database (see Editing the TFTP Database)

• Adding agents from the map to the TFTP operation list (see Adding Agents for TFTP Operations)

• Selecting agents in the TFTP Operation tab for immediate or scheduled download, then reviewing the operation details (see Transferring Files Using TFTP)

Note



• Checking the report details in the Report tab (see Viewing TFTP File Transfer Reports).

Changing the TFTP Default Settings

To configure the TFTP default settings, you use the configuration menu.

Figure 4-49. Configuration Menu

To change the TFTP default settings:

1. From the Configuration menu select Default Settings.

The Default Settings dialog box appears (see Figure 4-50).

2. Configure the default settings parameters as specified in Table 4-11.

3. Click <Set>.

Figure 4-50. TFTP Default Settings Dialog Box

Table 4-11. TFTP Default Parameters

Parameter Function

TFTP Server IP The IP address of the TFTP server for the selected object.

Exclude TFTP Directory Path Selected, Cleared

Default Value: Selected

Reboot Timeout (sec)

(10–4000 seconds)

The reboot timeout setting for the selected object.

The TFTP File Transfer application waits for this period

for the Cold Start trap after performing a reboot.



Parameter Function

Timeout (sec)

(10–4000 seconds)

Default value: 60 seconds

Retry Timeout (sec) Default value: 15 seconds

Ping Timeout (msec) Default value: 100 milliseconds

Editing the TFTP Database

The Edit Database dialog box (see Figure 4-51) allows you to add, modify, or remove product profiles. The displayed information is taken from the OIDs (Object IDs) of the product types stored in the TFTP database.

Adding a Product Profile

To add a new product:

1. From the Configuration menu select Edit Database

The Edit Database dialog box appears (see Figure 4-51).

2. Click <Add>.

The Add Product dialog box appears (see Figure 4-52).

3. Fill in the fields as specified in Table 4-12.

4. Define the S/W Download file. There are two methods:

In the S/W Download File field, type the name of the S/W Download File. There is no need to specify the full path, just the file name.

Or

Follow the procedure in Selecting the File to Download.

5. Click <Set>.

The message Database saved appears at the bottom of the screen.

6. On the Edit Database dialog box, click <Close>.



Figure 4-51. Edit Database Dialog Box (Before Products Added)



Figure 4-52. Add Product Dialog Box

Table 4-12. Add/Edit Product Parameters

Parameter Function

Select Product The object ID (product type) of the selected product

SubSystem Download Indicates whether this feature is needed for the selected product,

and the subsystems needed for download

TFTP Server IP The IP address of the TFTP server for the selected product



Parameter Function

Reboot Timeout (sec) The reboot timeout setting for the selected product

The TFTP File Transfer application waits for this period for the Cold

Start trap after performing a reboot

All the following fields except the last two fields are enabled only if

the product(s) selected via the Selected (All) Nodes field support(s)

the field

S/W Download File The S/W Download file path and name on the TFTP server for the

selected product. The S/W Download <Browse> button opens a

standard Open File dialog box for locating the TFTP File Transfer file

S/W Upload File The S/W Upload file path and name on the TFTP server for the

selected product. The S/W Upload <Browse> button opens a


Config Download File The configuration download file path and name on the TFTP server

for the selected product. The <Browse> button opens a standard

Open File dialog box for locating the TFTP File Transfer file

Config Upload File The configuration upload file path and name on the TFTP server for

the selected product. The <Browse> button opens a standard Open

File dialog box for locating the TFTP File Transfer file

Note: In Config. Upload there is no need to select Reset Only

Additional S/W File The product’s Software Download file path and name on the TFTP

server for the selected product. The <Browse> button opens a


Note: This parameter is not relevant for all products

Statistics Upload File The product’s statistics upload file path and name on the TFTP

server for the selected product. The <Browse> button opens the

Select File to Download dialog box for locating the TFTP File

Transfer file


User Download File The product’s user download file path and name on the TFTP server

for the selected product. The <Browse> button opens the Select

File to Download dialog box for locating the TFTP File Transfer file


User Upload File The product’s user upload file path and name on the TFTP server for

the selected product. The <Browse> button opens the Select File to

Download dialog box for locating the TFTP File Transfer file


SW Backup Download

File

The software file to download when backup is required

SW Backup Upload File The software file to upload when backup is required



Parameter Function

File Name Within

Product

The product file name uses any file name from the file system list

(depending on the user). This field is applicable mainly for the User

Download File, User Upload File, and Statistics Upload File, options

Note: User must enter file name

License Download File License file location

Timeout (sec) The time when a break automatically occurs when a predefined

interval of time has passed. See Table 4-13 for default value for the

particular product.

Retry Timeout (sec) Retry between the specified number of attempts. See Table 4-13 for default value for the particular product.

Cancel SNMP Retries

for Reset Operation

If the Set Response for the Reset command is not received by NMS

(lost), the NMS sends the Reset command (SNMP retry) again. This

retry resets the redundant card as well, causing services to stop for

a period of time. In order to avoid loss of service, the user can

cancel the retries (this is the default setting for the devices with

this problem).

Default: Cleared

The TFTP File Transfer application provides a number of functions, listed in Table 4-13.

Some RAD products do not support all the download options offered by the TFTP File Transfer application. Also, some RAD products may have recommended settings for TFTP variables that are specific for them. Refer to Table 4-13 for the TFTP File Transfer options and recommended TFTP values that are relevant for your product.



Table 4-13. TFTP File Transfer Options – by Product

Product

Name

Reboot

Timeout

(sec)

SW

Downld

Config

Downld

Config

Upld

Additional

SW Downld

Statistics

Upld

User

Downld

User

Upld

File

Name

Within

Product

Timeout

(sec)

SW

Upld

SW

Downld

to Bkp &

Swap

Main and

Bkp SW

SW

Upload

from

Bkp

License

Downld

Subsys

Downld

APD-8 300 – + – – – – – – 300 – – – – –

APS-8 300 – + – – – – – – 300 – – – – –

APS-16 300 – + – – – – – – 300 – – – – –

APS-24 300 – + – – – – – – 300 – – – – –

Egate-20 300 + + + – – – – – 300 + – – – –

Egate-100 300 + + + – – – – – 300 + + + + –

FPS-8 300 + + – – – – – – 300 – – – – –

RIC-155 300 + – – – – – – – 300 – – – – –

RICi-E1 300 + + + – – – – – 200 + – – – –

RICi-T1 300 + + + – – – – – 200 + – – – –

RICi-E3 300 + + + – – – – – 200 + – – – –

RICi-T3 300 + + + – – – – – 200 + – – – –

RICi-4E1 300 + + + – – – – – 300 + – – – –

RICi-4T1 300 + + + – – – – – 300 + – – – –

RICi-8E1 300 + + + – – – – – 300 + – – – –

RICi-8T1 300 + + + – – – – – 300 + – – – –

RICi-16E1 300 + + + – – – – – 300 + – – – –

RICi-16T1 300 + + + – – – – – 300 + – – – –



Product

Name

Reboot

Timeout

(sec)

SW

Downld

Config

Downld

Config

Upld

Additional

SW Downld

Statistics

Upld

User

Downld

User

Upld

File

Name

Within

Product

Timeout

(sec)

SW

Upld

SW

Downld

to Bkp &

Swap

Main and

Bkp SW

SW

Upload

from

Bkp

License

Downld

Subsys

Downld

RICi-155GE 300 + + + – – – – – 300 – – – – –

RICi-622GE 300 + + + – – – – – 300 – – – – –

RICi-SE 300 + + + – – – – – 200 + – – – –

SPS-3S 300 – + – – – – – – 300 – – – – –

SPS-4 300 + – – – – – – – 300 – – – – –

SPS-6 300 – + – – – – – – 300 – – – – –

SPS-12 300 – + – – – – – – 300 – – – – –

VMUX-400 300 + + + – – – – – 300 – – – – –

• (+) means supported and (–) means unsupported

• The Reboot Timeout (sec) and Timeout (sec) values are the default values for these products, and should be used in the Add Product dialog box.

Notes

Installation and Operation Manual Chapter 4 Configuration Management


Selecting the File to Download

To select the file to download:

1. In the Add Product dialog box (see Figure 4-52) or the Edit Product dialog box (see Figure 4–55), click <Browse> next to the S/W Download File field.

The Select File dialog box appears (see Figure 4–53).

2. In the Enter Path Or Folder Name field, type the name of the directory of the TFTP file.

3. Select the folder name and file name.

4. Click <Select File>.

Click <Update> if the directory and file were changed from another computer; this updates the directory and file names.

Figure 4–53. Select File Dialog Box

Editing Product Data

To edit product data:

1. From the Configuration menu select Edit Database.

The Edit Database dialog box appears (see Figure 4–54).

2. Select the product that you want to edit.

Note

Chapter 4 Configuration Management Installation and Operation Manual


3. Click <Edit>.

The Edit Product dialog box appears (see Figure 4–53).

4. In the Edit Product dialog box, fill in the fields as specified in Table 4-12.

5. Define the S/W Download (or other Operation) file. There are two methods:

In the S/W Download (or other Operation) file field, type the name of the S/W Download (or other Operation) file. There is no need to specify the full path, just the file name.

Or

Follow the procedure in Selecting the File to Download.

6. Click <Set>.

7. In the Edit Database dialog box, click <Close>.

Figure 4–54. Edit Database Dialog Box



Figure 4–55. Edit Product Dialog Box

To remove a product from the product database:

1. From the Configuration menu select Edit Database

The Edit Database dialog box appears (see Figure 4–54).

2. Select the product you want to delete.



3. Click <Remove>.

A confirmation message is displayed: Removing <Product Name>.

4. Click <OK>.

When entering a file name for the first time, you can enter any name. During the Configuration Upload process, the selected file is replaced by a file with the same name, containing the device configuration.

Selecting Nodes for TFTP

You can select all agents or specific agents for S/W and Configuration Transfer operations via the Operation tab (see Figure 4–56).

You can perform TFTP file transfer operations on all nodes or selected nodes. You can add nodes individually or from the map to link products to specific IP addresses.

Figure 4–56. Operation Tab

When the Operation tab first appears, it is empty. Open the Edit Database tab first to define the initial parameters.

Note

Note



Table 4–14. TFTP File Transfer Parameters in Operation Tab

Parameter Function

Host Name The name of the agent. By default, the name of the selected node is

displayed

IP Address The IP address of the agent. By default, the IP address of the selected

node is displayed

Product Name Product names of the selected nodes

Server IP Address The IP address of the server, as assigned for this mode in the TFTP

database

File Location The location of the file. By default, the UNIX/PC Windows user home

location is displayed, according to the type of station running the present

application

Last Operation Last selected operation for each node:

S/W Download Only, S/W Download & Reboot, Config. Download Only,

Config. Download & Reboot, Config. Upload, Additional SW Download

Only, Additional SW Download & Reboot, Statistics Upload, User Download

Only, User Upload, Reset Only

SW Upload from Backup The software file to upload when backup is required

SW Upload The name of the file to upload

SW Download to Backup The software file to download when backup is required

Swap Main and Backup SW If the Swap Main and Backup SW operation is successful (when set has been accepted by the agent), the last status displays Operation Performed with a green background. Otherwise, the status displays No SNMP connectivity with a red background.

Last Status Last TFTP status of each Node. The default is blank.

This column displays the last TFTP status of each node as detailed in

Table 4–18. The row displaying the last TFTP status of each node has a

color-coded background as detailed in Table 4–18. The column is empty

before clicking the <Set> button and/or confirming all messages prompting

for confirmation related to the [All Nodes Operation…] or [Selected Nodes

Operation…] Dboxes. After clicking the <Set> button, the column is

automatically filled in for the selected nodes according to the tftpStatus

MIB object received directly by NMS upon request or received with the

tftpStatusChangeTrap each time the status changes. The column displays

the last status only so the last status received always overwrites the

previous status.

Schedule The date and time a TFTP file transfer is scheduled to occur.

[All Nodes Operation...] Performs operation for all nodes in list

[Selected Nodes Operation...] Opens a selection list box to choose operation for selected nodes

[Add from Map…] Opens a selection list box containing all nodes on map

[Remove] Removes an agent



In order to upgrade an agent’s software, you must reboot (reset) the agent after downloading the software. In some cases, you may want to reboot the device later at a specific time. Therefore, when required, you can select an operation that includes Download Only for file download only, an operation that includes Reset Only for rebooting at a specific time after successfully downloading the software, or an operation that includes Download & Reboot for complete software upgrade.

Adding Agents for TFTP Operations

You can add agents directly from the HPOV map to the agent list in the Operation tab.

To add agents from the map:

1. In the Operation Tab, click <Add from Map…>.

The Add Agent from Map dialog box appears (see Figure 4–57). As RADview-HPOV/Lite polls all the agents, it lists in the dialog box the agents that are in the TFTP database and are on the map. When it finishes, the status bar at the bottom of the screen displays Ready.

2. Select the node(s) to be added.

3. Click <Set>.

The node(s) are added to the list in the Operation tab.

The host names in the list in the Operation tab are not updated if they are changed in the map after being added in the Operation tab.

Note

Note



Figure 4–57. Add Agents from Map Dialog Box

To remove an agent from the Operation tab:

1. Select a node from the list displayed in the Operation tab.

2. Click <Remove>.

The node is removed from the list in the Operation tab.

Transferring Files Using TFTP

This section explains how to transfer files using TFTP File Transfer.



Figure 4–58. TFTP File Transfer – Operation

To perform TFTP file transfer operations:


Select the specific nodes on which you want to perform Software Download from the list (hold down <Shift> while dragging the mouse to select several nodes) and then click <Selected Nodes Operation>. This can be used in case of unsuccessful TFTP transfer. Select only those nodes where the transfer of new software was not successful, according to the Last Status column, and reinitialize the TFTP session.

The Selected Nodes Operation dialog box appears (see Figure 4–59).

Click <All Nodes Operation>

The All Nodes Operation dialog box appears.

2. If using Selected Nodes Operation, select any S/W and Configuration Transfer operation. Only options that are supported by all nodes of the list are selectable (see Figure 4–61).



Figure 4–59. Selected Nodes Operation Dialog Box, Scheduling Enabled



Figure 4-60. Selected Nodes Operation Dialog Box, Scheduling Not Enabled



Figure 4–61. Selected Nodes Operation Dialog Box – Selection

3. Configure the parameters as specified in Table 4–15.

4. Select Enable and select a date and time if you wish to schedule the transfer rather than start it immediately, and click <Set>.

A confirmation message appears.

Figure 4–62. Selected Nodes Operation Dialog Box – Confirmation

5. Click <OK>.



If schedule was enabled, the Last Status column shows the transfer has been scheduled.

Figure 4–63. TFTP File Transfer – Scheduled operation

6. After allowing time for the transfer to finish, or after the scheduled time if scheduled operation was performed, check the status reported in the Last Status column (see Figure 4–64) to determine whether the download was successful. Additional information is available via the Report Tab (see Viewing TFTP File Transfer Reports).

Figure 4–64. TFTP Dialog Box – Operation Tab, Successful Transfer



In order to upgrade an agent’s software, you must reboot (reset) the agent after downloading the software. In some cases, you may want to reboot the device later at a specific time. Therefore, when required, you can select an operation that includes Download Only for file download only, an operation that includes Reset Only for rebooting at a specific time after successfully downloading the software, or an operation that includes Download & Reboot for complete software upgrade.

Table 4–15. Selected Nodes Operation Parameters

Parameter Function

Operation Select any TFTP file transfer operation.

Values: SW Download Only, SW Download & Reboot, Config. Download Only, Config Download & Reboot, SW Upload, Config. Upload, Reset Only

Default: SW Download Only

Note: Only options that are supported by all nodes of the list are selectable.

File Name Enter the file name.

Note: This field is optional. If left blank, the file name is taken from the database.

File Name Format Values: As Selected per Product, As Selected per Product + Host Name, As Selected Per Product + Host Name + Time Stamp

Note: This property is only enabled for configuration options.

Schedule

Enable Check to enable a scheduled file transfer.

Date Select the date for the scheduled file transfer.

Time Select the time for the scheduled file transfer.

When the operation selected in the Operation tab, [All Nodes Operation...] or [Selected Nodes Operation...] includes Download & Reboot, NMS performs the operations shown in Table 4-16.

Table 4-16. Download & Reboot NMS Operations

Product Operation

Egate-20 A

Egate-100 A

RIC-155 B

RICi-E1/T1 A

RICi-E3/T3 A

RICi-4E1/T1 A

RICi-8E1/T1 A

RICi-16 A

Note



Product Operation

RICi-155GE A, when Software Download & Reboot is performed

B, when Configuration Download is performed

RICi-622GE A, when Software Download & Reboot is performed

B, when Configuration Download is performed

RICi-SE A

VMUX-400 A - when Software Download & Reboot is performed

C – when Configuration Download & Reboot is performed

Legend:

A = Same as Download Only + Reset. Same as Download Only (above) + upon successful completion, activate the Reset process.

B = Same as Download Only. For these products, no additional operation is needed, because these products automatically perform a Reboot after downloading TFTP.

C = Same as Config Download + after receiving Set Response OK, expecting Sanity Check trap. If Sanity Check trap result is OK or Warning, the operation succeeded

If you select TFTP and Reboot, the software version of the nodes is replaced and the system resets. Depending on the reboot time of the specific device, traffic downtime is experienced.

Viewing TFTP File Transfer Reports

The Report tab (see Figure 4–65) lists messages that provide a history of the software download process. Reports are generated during every software download procedure. The Report parameters are listed in Table 4–17. Messages are listed in Table 4–18.

Only agents for which Download/Upload is currently in process are displayed in this tab. A new row is added each time tftpStatusChangeTrap is received..

Reports are based on traps from the agent. In order to receive traps, the workstation running the TFTP file transfer application must be registered as a manager in the agent.

Note

Warning



Figure 4–65. TFTP File Transfer – Report Tab

Table 4–17. TFTP File Transfer – Report Tab Parameters

Parameter Function

Date Local date at the NMS when the message was registered

Time Local time at the NMS when the message was registered

Host Name Name of the relevant agent

IP Address IP address of the relevant agent

Product Name Name of product for which file transfer process is being

reported

Status Status of the download process (see Table 4–18)



Table 4–18. Status Messages

Message (Standard TFTP messages) Color

Connecting… Yellow

Connected. Transferring Data Yellow

Giving up. Server does not respond Red

File successfully transferred Green

File not found Red

Illegal TFTP operation Red

Unknown transfer ID Red

Server overflow Red

No available UDP port Red

No available resources Red

Illegal file mode Red

Illegal PDU size Red

Rebooting... Yellow

Device successfully upgraded Green

Device successfully rebooted Green

No SNMP connectivity Red

Device not responding after expiration of reboot

timer

Red

Incorrect File Red

IP Address format of the node is not valid Red

Unknown sysObjectID Red

Agent is busy with another TFTP session.

Operation will not be performed

Red

SNMP request failed Red

Access violation Red

Disk full or allocation exceeded Red

File already exists Red

No such user Red

TFTP server does not exist Red

Wrong license format Red

License ID already used Red

Sheduled Yellow



<Operation selected> scheduled for

<yyyy:mm:dd hh:mm:ss >

Executing scheduled operation

Scheduled operation has been canceled

To remove messages from the Report tab:

• In the Report tab, select a row and click <Remove>, or click <Remove All> to clear all messages from the list.

Saving the TFTP Database

If you keep the TFTP application open for a long time you should save the database periodically to avoid losing parameter data in the event of a power failure.

To save the database:

• From the Configuration menu, select Save Database.

Using Help

You can access the online user manual and information about the TFTP application via the Help menu.

To access the user manual:

• From the Help menu, select Help > User’s Manual.

To access information about the TFTP application:

• From the Help menu, select Help > About Application.

Exiting the Application

When you select Configuration > Exit to exit TFTP:

• If there is at least one scheduled entry that was not performed, the following dialog box is displayed:

Figure 4-66. Exit Dialog Box (Scheduled Operation Exists)


4-78 Viewing the Net Inventory RADview-HPOV/Lite Ver. 1.7

• Else, the following dialog box is displayed:

Figure 4-67. Exiting Application Dialog Box (No Scheduled Operation)

Click <OK> in both cases, to exit the application.

4.6 Viewing the Net Inventory

The Net Inventory application allows you to display an Inventory Table (see Figure 4–69) for all products that support the Entity MIB. Refer to Chapter 1 for a list of devices that support the Net Inventory function.

The HPOV map should be open when activating Net Inventory for the first time. When you start the Net Inventory application, it reads information from all nodes representing agents on the map that support Entity MIB.

Opening the Application

To open the Net Inventory application:

• In the HPOV Map select Misc > RADview/OV > General > Net Inventory.

Figure 4–68. Opening the Net Inventory Application

The first time you start the Net Inventory application, you are prompted to confirm the data refresh, as it is a potentially time-consuming operation. Click <OK> to continue.

Note


RADview-HPOV/Lite Ver. 1.7 Viewing the Net Inventory 4-79

The Inventory Table window appears (see Figure 4–69). The Inventory Table parameters are listed in Table 4–19

Figure 4–69. Net Inventory Opening Window

The table is a hierarchical system. When you click the icon to the left of an entity, the tree expands to display all entities that have the selected component ID in their entPhysicalContainedIn MIB parameter. You can sort each column if the left-hand tree is at the node level.

In order to save/print the entire display, verify that no rows are selected (click <Ctrl> and the left mouse button to deselect any selected rows).

Table 4–19. Net Inventory Table Parameters

Parameter Function

Entity Unique value that identifies the physical entity

Desc. Description of the entity

Class Class of the entity

Possible values: Modem, Chassis, Back–Plane, Slot, PS, Sensor, Card, Fan, Port, CPU, Stack (Stack of chassis (real or virtual) intended to be grouped together as multiple chassis entities)

Note: A chassis that is connected to one or more remote chassis returns a virtual stack as its “parent”. This virtual stack is the “parent” of all remote chassis connected to the same “parent”. Managed Remote chassis is not taken into account, and is not part of the virtual stack.

HW ver. Hardware revision of the entity

SW ver. Software revision of the entity

FW ver. Firmware revision of the entity

FW usually applies to ASIC

Name Name of entity

Note



Parameter Function

Serial No. Read/Write field containing the entity serial number (read from the entity hardware)

Alias Read/Write field containing the alias name for the entity

FRU Indicates whether entiry is Field Replaceable Unit

True – this entity can be replaced in the field

False – this entity cannot be replaced in the field

Asset ID (CSL) Identification information added to the entity. It can be used to

indicate the Configuration Status Letter (CSL) of the unit component.

[Filter…] Opens a dialog box to filter the entity

[Edit…] Opens a dialog box to edit the parameters of the selected row

[Close] Closes the application

[Print…] Prints all selected rows

[Save to File…] Saves all selected rows

[Expand All] Expands all entities to display all subordinates down to the lowest

level

[Collapse All] Closes all tree entries to display node level only

[Help] Displays Help file

About Displays info about the program, such as version and licensing

information

[Refresh] Opens the following submenu:

Synchronize All Refreshes information for all displayed entities

Refresh Selected Refreshes information for selected entities

Remove Selected Removes selected entities from net inventory

table.

Add New Nodes

from Map

Adds new entities to inventory table, containing

data of nodes that were added to map

Last Refresh NMS time when the last refresh was performed

Filtering the Display

You can display only nodes that you wish to view.

To filter display:

1. In the Inventory Table, select Filter> Filter.

The Inventory List Filter dialog box appears (see Figure 4–70).

2. Select whether you want to filter on:

All Map Nodes

Displayed Nodes Only.


RADview-HPOV/Lite Ver. 1.7 Viewing the Net Inventory 4-81

Only one selection can be made at a time.

3. Click any parameters that you want to use as a filter, and enter the filter criteria.

4. Click <OK>.

Only those Nodes that have entities matching all the filter criteria are displayed.

• Filtering is not case–sensitive.

• The only wild card character that can be used in the Edit boxes is *.

Figure 4–70. Inventory List Filter Dialog Box

Table 4–20. Inventory List Filter Parameters

Parameter Function

Filter on all map nodes Perform filtering on all map nodes

Filter on displayed nodes only Perform filtering on displayed nodes

Node If selected, enter node name value for filtering

Desc If selected, enter description value for filtering

Class If selected, choose value from dropdown list for filtering: Modem,

Chassis, Back-Plane, Slot, PS, FAN, Sensor, Card, Port, Stack, CPU

HW ver. If selected, enter hardware revision value for filtering

SW ver. If selected, enter software revision value for filtering

FW ver. If selected, enter firmware revision value for filtering

Name If selected, enter name value for filtering

Serial No. If selected, enter serial number value for filtering

Note

Note



Parameter Function

Alias If selected, enter alias value for filtering

FRU If selected, choose Yes or No from dropdown list to filter for field

replaceable units or non-field replaceable units

Asset ID If selected, enter asset ID value for filtering

Editing an Entity

To edit an entity:

1. In the Inventory Table, select an entity (row) and click <Edit>.

The Edit dialog box appears (see Figure 4–71).

2. Modify the desired parameters.

3. Click <Set>.

Figure 4–71. Edit Dialog Box

Expanding/Collapsing Sublevels

To expand/collapse sublevels of an entity:

• In the Inventory Table, double–click an entity.

To expand all sublevels of all entities in a tree:

• In the Inventory Table, click <Expand All>.

All tree entries are displayed to the lowest level (see Figure 4–72).

To collapse all sublevels of all entities in a tree:

• In the Inventory Table, click <Collapse All>.

All tree entries are displayed at the node level (see Figure 4–69).


RADview-HPOV/Lite Ver. 1.7 Setting Net Date and Time 4-83

Figure 4–72. Expand All

4.7 Setting Net Date and Time

RADview-HPOV/Lite has two date and time functions:

• Set the date and time for managed units via a single screen

• Automatically update date and time parameters of agents according to NMS clock.

Refer to Chapter 1 for a list of devices that support the date and time function.

Setting Net Date and Time

RADview-HPOV/Lite allows you to set the date and time for all managed units via a single screen.

To set net date and time:

1. From the Misc. menu, select RADview/OV > General > Net Date and Time.

The Net Date and Time dialog box appears (see Figure 4–73).

2. Select the required device from the Remaining Products list and move it to the Selected Products list.

3. Select the time format from one of the following options:

User Time – allows you to configure date and time

NMS time – This automatically sets the date and time according to the NMS clock.


4-84 Setting Net Date and Time RADview-HPOV/Lite Ver. 1.7

4. Enter the Date and Time parameters if you selected User Time:

Date – Day/Month/Year

Time – Hour/Minute/Second.

5. Click <Set> to implement the changes.

Figure 4–73. Net Date and Time Dialog Box

Setting Automatic Update of Date and Time

RADview-HPOV/Lite can automatically update date and time parameters for the agents.

• Closing HP OpenView does not affect the automatic update.

• If the automatic update was activated and the station reboots, the update is still performed with the same settings.

To set the parameters for automatic update of date and time:

1. From the Misc. menu, select RADview/OV > General> Date and Time Auto Mode. Do not click an agent icon on the WAN map.

The Date and Time Auto Mode dialog box appears (see Figure 4–74).

Note


RADview-HPOV/Lite Ver. 1.7 Setting Net Date and Time 4-85

2. Select the required device from the Remaining Products list and move it to the Selected Products list.

3. Set the update period and update time.

4. Click <Set> to implement the changes.

Figure 4–74. Date & Time Auto Mode dialog Box


4-86 Setting Net Date and Time RADview-HPOV/Lite Ver. 1.7

RADview-HPOV/Lite Ver. 1.7 Collecting Statistics from VMUX-400 Units 5-1

Chapter 5

Performance Management

5.1 Viewing Product Statistics

Product statistics are available only for VMUX-400 units.

5.2 Collecting Statistics from VMUX-400 Units

The Statistics Application collects statistics from VMUX-400 units and displays them in graph form.

The main features of this application are:

• Statistics Collection

Collecting statistics data from Vmux-400 by using TFTP

Saving the collected data in files (in CSV format) at the Network Management Station (NMS).

• Statistics Display

Displaying statistics graphically (e.g., graph line)

Filtering the displayed data (e.g., for a certain time window).

System Requirements

Before using this application for a Network Element (NE), you should verify:

• A TFTP Server is activated and properly configured in the NMS

• The read & write communities for the node are correct

• The NMS IP address exists in the agent’s manager list

• The trap rad.tftpStatusChangeTrap is not masked in the agent

• There is enough free disk space for the statistics files. For example the disk space needed for a Vmux-400 device with one bundle is 2 MB per day. Therefore, 10 Vmux-400 units that have five bundles require 100 MB per day and 3 GB per month.

If you change NE name or SNMP properties in the SNMPc map, you must open the statistics application GUI and reload the updated data from the map.

Chapter 5 Performance Management Installation and Operation Manual

5-2 Collecting Statistics from VMUX-400 Units RADview-HPOV/Lite Ver. 1.7

Managing Statistics Data

The NMS stores the following information for each data type per NE type:

Data Type Type of statistics data in each file, combination of:

• Data type (running/current/intervals)

• Interface type and number (e.g., port 1, bundle 5, etc.)

Data Resolution Minimum time difference between two sequential data samples. Obviously, it is one of the most significant attributes that defines how much data can be collected in each file.

Time Interval Time period of statistics data in each file. This time period is used in most cases when collecting data from an Agent. Refer also to Agent Max Interval.

Agent Max Interval Maximum time period of statistics data that can be saved in an agent. This time period is used whenever the statistics application needs to “fill gaps” in an agent’s missing data. This is used particularly when collecting data from an agent for the first time.

NE Type Data Type Data Resolution Time Interval Agent Max Interval

Vmux-400 Running counters of all bundles 1 second 15 minutes 1 hour

The NMS database stores the following information for each NE:

Information Description RO/RW

Name Name of the NE (taken from map). RO

IP Address IP Address of the NE RO

NE Type NE Type RO

Collection Activation Whether or not NE is activated (Collection Activation = “Enable”).

Only when activated – the statistics application should collect data for

this NE.

RW

Collection Period The time period that the statistics application should save data for this

NE.

Whenever collected data exceeds the Collection Period, the old data is

automatically deleted.

RW

Collection Timer The time of the next statistics collection (that should be initiated by

the statistics application). Format can be Date & Time, countdown

time, etc.

RO

Installation and Operation Manual Chapter 5 Performance Management



Interfaces List List of all NE interfaces that include collected data in NMS database.

List is updated within collections.

RO

The statistics application stores the following interface information for each NE:


Interface Name Name of the interface (e.g., Bundle5). RO

Collected Data All statistics data (counters) that is collected for this NE RO

The statistics application manages the data files received from the NEs as follows:

• Convert data files into ASCII format

• Arrange files in folders, using a folder for each NE (NE name)

• Save all ASCII files of an NE under its folder

• Manage calendar day (full or partial day) files for each interface of an NE

The ASCII file name format includes the following segments (separated by underscore):

Segment Description

Name ASCII string (e.g., device IP Address)

NE Type Vmux-400

Interface Bundle number

NMS Date YYYY-MM-DD (ISO format) of the last data sample

Example: 172.52.150.76_Vmux-400_Bundle5_2006-10-10

The following tables shows the MIBs that are supported for the statistics application.

Table 5-1. MIBs Supported for the Statistics Application

MIB RO/RW Description

3418.sysObjectID RO NE Object ID, which represents the NE Type.

3418.sysUpTime RO NE Time (in 1/100 seconds) since last restart.

rad.fileServerIP RW NMS IP Address

rad.fileName RW File names to which the NE transfers the data

rad.fileNameWithinProduct RW Requested data time or interval(s).

rad.fileTransCmd RW Should be set to stateUpLoad(5)

rad.tftpStatusChangeTrap Trap A trap sent by the NE whenever TFTP operation succeeds.

rad.tftpRetryTimeOut RW General Retransmission timeout (in seconds).



MIB RO/RW Description

rad.tftpTotalTimeOut RW Total Retransmission timeout (in seconds).

Statistics Collection Sequence

The collection process is performed as follows for each required NE:

1. The statistics application retrieves the NE ID (3418.sysObjectID), which represents the NE type, to avoid Device Type mismatch.

If collection data for the NE already exists in the NMS, the statistics application compares it to the NE Type stored in its database, and in case of NE Type mismatch:

The statistics application stops the process (no further steps are performed for this NE)

The NE icon in the GUI Tree is updated accordingly.

2. The statistics application retrieves the NE time (3418.sysUpTime) since the last restart (in 1/100 sec) in order to synchronize.

The statistics application determines which data to collect from the NE, based on:

NMS Time

NE time (3418.sysUpTime)

Time (or Interval number) of last data sample in the NMS for this type of data (e.g., bundle).

3. The statistics application sends an SNMP request for collecting statistics data to the NE that includes (see Table 5-1):

NMS IP address

File name to which the NE transfers the data

Requested data time or interval(s) according to the following table:

Data Type Format of Requested Data Time or Interval(s) Example

Running <FromTime>–<ToTime> in seconds, where:

<FromTime>= time of last data sample missing in the NMS

database, which cannot exceed Agent Max Interval.

<ToTime> = NE time since last restart * 100 (sec)

“10001 - 10900” (15 min)

“10001 - 13600” (an hour)

Intervals <FromInt>–<ToInt> where:

<FromInt>= 1

<ToInt> = No. of last interval missing in the NMS database,

which cannot exceed Agent Max Interval

“1 - 4” (an hour)

“1 - 96” (a day)

rad.fileTransCmd (set to stateUpLoad(5))

After the first collection:



Whenever the interval period is passed for a certain activated NE, the statistics application sends SNMP request for collecting the new statistics data (starting with the oldest statistics data that still does not exist in the NMS database).

In case of a new NE (just added to the collection requests list), the statistics application sends SNMP requests for collecting the Agent Max Interval data available in this NE (similarly to what is performed when the statistics application is opened for the first time).

4. NE prepares data and sends file(s) to the NMS.

Whenever an NE receives an SNMP request from the NMS, it performs the following:

Collects the statistics data

Creates binary file(s) with all relevant data (one or more, according to what is agreed with the NMS and as much as necessary)

Sends these files to the NMS via TFTP

Deletes these files from its database.

In case all requested files are successfully uploaded, NE performs the following:

Sends SNMP trap rad.tftpStatusChangeTrap to the NMS

Continues to the next SNMP request.

5. The statistics application receives file(s) and converts them to ASCII files stored in the NMS.

Whenever the NMS receives the rad.tftpStatusChangeTrap trap, the statistics application converts the received binary files to ASCII files stored in the NMS (for more information see Managing Statistics Data).

In case TFTP fails to upload one of the files, the statistics application performs the following for each NE:

Attempts to send it again (total of three attempts)

If all three attempts fail, the statistics application terminates the operation.

When the Server application is started for the first time, the statistics application performs the Collection Process to ALL activated NEs for collecting Agent Max Interval data available in the NEs.

Starting the Statistics Collection Application

To start the statistics application:

• Select All Programs> Network Manager > General > Performance Monitoring.

The main window opens (see Figure 5-1).

Note



Figure 5-1. Performance Monitoring Window

The following areas exist in the main window:

• Tree Navigator – in the left side of the window

Tree Navigator data is loaded from the map, having the same objects hierarchy, but including only nodes with OIDs supported by the application server). In addition to the data loaded from the map, the Tree Navigator includes:

A read-only check box next to each NE, indicating whether or not the NE belongs to the currently loaded Group Descriptor.

Another hierarchy level – Bundle, which is directly under the NE level

Bundles data is loaded from the NMS database (0…N bundles for each NE)

Any object (in any hierarchy) in the Tree Navigator is selectable.

• Group Descriptor list – in the right side of the window (for Group Descriptor details – see also Viewing Group Descriptors and Performing Operations)

The list (in the main window) displays only the Group Descriptor Name.

List rows are selectable.

Load GD – click a Group Descriptor row in the list.

Change GD – double-click a Group Descriptor row in the list (or via the respective Group Descriptor dialog boxes).

• Status bar – Displays the current Collection Process status (running or stopped) in the following format:

“Collection Process is running” (highlighted in green)

Or

“Collection Process is stopped” (highlighted in red)

You can start/stop the server using commands outside this application.

• ToolTip (NE level only)

Name: value is taken from the map

IP Address: value is taken from the map

Note



Device Type: based on 3418.sysObjectID

Configuring Statistics Collection

From the main window (see Figure 5-1), select Configuration. The following dropdown menu opens:

Figure 5-2. Configuration Dropdown Menu

• Reload from Map – reloading the Tree hierarchy. In addition, the statistics application also reloads SNMP properties (i.e., Read & Write Communities, Retries, Timeout) of each relevant NE and updates it in NMS database accordingly (if update is needed).

This operation is also performed each time the statistics application is opened.

• Group Descriptors… – see Viewing Group Descriptors and Performing Operations.

• Collection Process – see Starting/Stopping Statistics Collection Process.

• Exit – exiting the Configuration.

Viewing Group Descriptors and Performing Operations

To view Group Descriptors details and perform operations:

• From the main window, select Configuration > Group Descriptor.

The Group Descriptors dialog box (Figure 5-3) opens.

Note



Figure 5-3. Group Descriptors Dialog Box

Table 5-2. Group Descriptors Parameters

Parameter Name Function

Group Descriptor See Adding a Group Descriptor

Description See Adding a Group Descriptor

Collection Activation See Adding a Group Descriptor

Collection Period (days) See Adding a Group Descriptor

• Click <Add…> to add a Group Descriptor (see Adding a Group Descriptor).

• Click <Change…> to change a Group Descriptor (see Changing a Group Descriptor). This button is disabled when no Group Descriptor is selected.

• Click <Rename…> to rename a Group Descriptor (see Renaming a Group Descriptor). This button is disabled when no Group Descriptor is selected.

• Click <Remove> to remove a Group Descriptor.

The following dialog box appears:

Figure 5-4. Remove Group Descriptor Dialog Box



Click <OK> to perform the following operations for each NE in the selected Group Descriptor:

Stop the Collecting process if Collection Activation = Enable

Delete related data from NMS database

In addition:

Delete selected Group Descriptor from NMS database

Remove selected Group Descriptor from the list.

Or:

Click <Cancel> to cancel the operation.

Adding a Group Descriptor

To add a Group Descriptor to NMS database:

1. From the main window, select Configuration > Group Descriptor.

2. Click <Add>.

The following dialog box appears:

Figure 5-5. Add Group Descriptor Dialog Box

3. Set the parameters according to Table 5-2.



Table 5-3. Add Parameters

Parameter Name Values Notes

Group Descriptor Name 40-char string

Blank

Description 200-char string

Blank

Select From Tree Generic “Tree Navigator”

behavior

A map of devices in tree navigator is displayed:

• Device Type (e.g., Vmux-400) is displayed in

brackets next to NE name

• You can select the devices to be included in the

new current group (multiple selection is possible)

• When an object (e.g., submap) is selected, all

objects (e.g., NEs) under it in the tree are also

selected

• Upon entry, all devices are unchecked.

Collection Activation Disable

Enable

Collection Period (days) 1…99

30

three digits max

4. Click <Save> to add the Group Descriptor to the NMS database.

Upon the Save operation, the statistics application checks for each selected NE whether the Group Descriptor name already exists in NMS database. If it does, the following error message appears in the status bar (the save operation is not performed): Group Descriptor already exists

If at least one NE is found, the following dialog box appears:

Figure 5-6. Move NEs from another Group Descriptor Dialog Box



Table 5-4. Move NEs from another Group Descriptor List

Name Values MIB

Name Taken from the map

IP Address IP Address format

Device Type Taken from the map 3418.sysObjectID

Old Type Taken from NMS database

Old Group Descriptor Name Taken from NMS database

Type mismatch: NE that already exists in NMS database but with a different Device Type (e.g., real NE type = X and NMS database type = Y, where X ≠ Y). Such a row is marked in red. Afterwards, the following text is displayed: “NE(s) already exist/s in another Group Descriptor. Move to current Group Descriptor?”

• Click <OK> to perform the following:

a. For each NE Type mismatched – delete the NE data from NMS database.

b. Each (moved) NE is moved from the old Group Descriptor to the current Group Descriptor.

The collecting process of each NE is handled according to the following tables:

Collection Activation (Current Value)

New NE (nonexistent in any Group Descriptor before added to this Group Descriptor)

Enable Initiate process

Disable –

Collection Activation (Old Group Descriptor → Current Group Descriptor)

Moved NE (from old Group Descriptor to current Group Descriptor)

Enable → Enable –

Disable → Disable –

Enable → Disable Stop process

Disable → Enable Initiate process

Changing a Group Descriptor

To change a Group Descriptor in NMS database:


2. Click <Change>.

The following dialog box opens:

Note



Figure 5-7. Change Group Descriptor Dialog Box

3. Set the parameters according to Table 5-4.

Table 5-5. Change Group Descriptor Parameters


Group Descriptor Name Selected value

Description 200-char string

Blank

Select From Tree Generic “Tree Navigator”

behavior

A map of devices in tree navigation is displayed:

• Device Type (e.g., Vmux-400) is displayed in

brackets next to NE name

• You can select the devices to be included in the

new current group (multiple selection is possible)

• When an object (e.g., submap) is selected, all

objects (e.g., NEs) under it in the tree are also

selected

• Upon entry, all devices are unchecked.

Collection Activation Disable

Enable




Collection Period (days) 1…99

30

3 digits max

4. Click <Save> to add Group Descriptor to NMS database.

Upon the Save operation, the statistics application checks for each selected NE whether it corresponds to another Group Descriptor. If at least one such node is found, the dialog box shown in Figure 5-6 appears:

Table 5-6. Move NEs from another Group Descriptor List

Name Values Notes

Name Taken from the map

IP Address IP Address format

Device Type Taken from the map

Old Type Taken from NMS database

Old Group Descriptor Name Taken from NMS database

Type mismatch: NE that already exists in NMS database but with a different Device Type (e.g., real NE type = X and NMS database type = Y, where X ≠ Y). Such a row is marked in red. Afterwards, the following text is displayed: “NE(s) already exist/s in another Group Descriptor. Move to current Group Descriptor?”

5. Click <OK> to perform the following:

a. For each NE Type mismatched – delete the NE data from NMS database.

b. Each (moved) NE is moved from the old Group Descriptor to the current Group Descriptor.

c. Check whether at least one NE is removed (unchecked) from the Group Descriptor, in which case the statistics application displays the following dialog box:

Figure 5-8. Removing NE(s) from Group Descriptor Dialog Box

d. Click <OK>.

The collecting process of each NE is handled according to the following tables:

Note



Collection Activation (Current Value)

New NE (nonexistent in any Group Descriptor before added to this Group Descriptor)

Enable Initiate process

Disable –

Collection Activation (Old Group Descriptor → Current Group Descriptor)

Moved NE (from old Group Descriptor to current Group Descriptor)





Collection Activation (Old value → New value)

Removed NE (NE that is removed from current Group Descriptor)

Enable → Any Stop process

Disable → Any –

Collection Activation (Old value → New value)

Remained NE (NE that remains in current Group Descriptor)





In addition:

• The statistics application deletes all data related to NEs removed from the NMS database.

• All other configurations are saved in the NMS database.

Renaming a Group Descriptor

To rename a Group Descriptor in the NMS database:


2. Click <Rename>.

The following dialog box opens:



Figure 5-9. Rename Group Descriptor Dialog Box

3. Type a new name for the Group Descriptor.

Table 5-7. Rename Group Descriptor Parameters


Original Name 40-char string Read-only

New name 40-char string

original name

4. Click <Save> to add the Group Descriptor new name to NMS database.

Upon the Save operation, the statistics application checks whether the Group Descriptor name already exists in NMS database and if so, NMS displays an error message in the status bar (the save operation is not performed):

Group Descriptor already exists

Otherwise the statistics application renames the selected Group Descriptor.

Starting/Stopping Statistics Collection Process

To start the Statistics Collection Process:

1. From the main window, select Configuration > Collection Process.

2. Click <Start> to start the Collection Process.

A dialog box appears.

Click <OK> to start the process.

Or:

Click <Cancel> to close the dialog box.

To stop the Statistics Collection Process:

• Click <Stop> to stop the Collection Process.

A dialog box appears.

Click <OK> to start the process.

Or:

Click <Cancel> to close the dialog box.



Viewing the Navigation Tree

From the main window (see Figure 5-1), select View. The following dropdown menu opens:

Figure 5-10. View Dropdown Menu

Finding a Node

This command is used for finding a node by name, IP address, or according to history.

To find a Node:

1. From the View dropdown menu, select Find.

The Find dialog box opens.

Figure 5-11. Find Dialog Box

2. Select By Node Name, or By IP Address, or History radio button according to the category by which to find the node (see Table 5-7).

3. If By Node Name or By IP Address is selected, type the node name or the node IP address in the corresponding combo box (see Table 5-7).

4. Click <Find> (see Table 5-7).

Table 5-8. Fields in the Find Dialog Box

Field Name Function

By Node Name Combo-box: enabled only if its radio button is selected.

By IP Address Combo-box: enabled only if its radio button is selected.



Field Name Function

History Combo-box: enabled only if its radio button is selected.

Displays a list of the last 20 searched names/IP addresses. If a

node/IP address that appears in the list does not exist

anymore in the tree, and you select it, a message appears in

the status bar: “The search item was not found”, and the

[Find] button is disabled.

[Find] Click to locate and select the node on the tree. If the tree is

collapsed or if the view shows only the selected NEs (“Show All

Map” is not checked), the view changes to the “Show All Map”

view.

While the Find operation is in progress, the following message

is displayed in the status bar: “Working…”.

If an item is not found the following message is displayed in

the status bar:

“The search item was not found”. When the item is found, the

“Working…” message is replaced by a “Ready” message, and

the found item is highlighted in the Main Window.

Note: Find is not case sensitive. The scope for searching is always the entire tree.

[Close] Click to close

Collapsing the Navigation Tree

The Collapse All command collapses all subtrees in the navigation tree.

To collapse the Navigation Tree:

• From the View dropdown menu, select Collapse All.

The tree displays only the root node with or without the first level of submaps.

Expanding the Navigation Tree

To expand the Navigation Tree:

• From the View dropdown menu, select Expand All, or click the matching toolbar icon.

The navigation tree expands to all subtrees, displaying all parts in the navigation tree.

Displaying/Hiding the Navigation Tree

The Navigation Tree toggle command is used to show/hide the navigation tree.

The Navigation Tree is displayed by default, and a √ sign appears to the left of the command in the dropdown menu.

To hide the Navigation Tree:

• From the View dropdown menu, select Navigation Tree.



The Navigation Tree is hidden, the list (if exists) is displayed on the entire screen width, and the √ sign disappears from the View dropdown menu.

To display the Navigation Tree:

• From the View dropdown menu, select Navigation Tree again.

The Navigation Tree is displayed at its width before hiding it, the list is displayed at its width before hiding the tree, and the √ sign is displayed in the View dropdown menu.

Displaying the Map

To display the entire map:

• From the View dropdown menu, select Show All Map.

The entire map is displayed, and the √ sign is displayed in the View dropdown menu.

To display only selected Nodes:

• From the View dropdown menu, select Show All Map again.

Only the selected Nodes of the currently loaded Group Descriptor are displayed, and the √ sign disappears from the View dropdown menu.

Viewing the Statistics Chart

This option allows viewing statistics chart of a bundle. Show Chart is enabled only when a single bundle is in focus (main window tree).

To view the statistics chart:

1. From the main window, select View > Show Chart.

The following dropdown menu opens:

Figure 5-12. Show Chart Dropdown Menu

2. Select Trend to view areas within the chart (see Trend View).

Or

Select Detailed to view points within the chart (see Detailed View).

Trend View

Selecting Trend opens the Trend chart.



Figure 5-13. Trend Chart

Table 5-9. Trend View Parameters

Parameter Name

Values Notes

Data Period

From Date, current date

(YYYY-MM-DD)

You cannot select a date later than the date selected in

To.

To Date, current date

(YYYY-MM-DD)

You cannot select a date earlier than the date selected

in From.

Period Graph Displaying data in the time

period selected in Data

Period

Drag the mouse to select areas within the graph. Such

selection affects only Zoom Graph display.

Data is taken from NMS database, but as there is too

much data to be filled in this graph, the statistics

application performs a compression algorithm preserving

the graph behavior so that line tendency is not affected

(note that extremum points might not be displayed, due

to data compression.



Parameter Name

Values Notes

Zoom Graph Displays data in time period

for area selected within

Period Graph

The time period of this graph can be modified as follows:

• Selecting a subperiod within Period Graph.

• Selecting a subperiod (of displayed subperiod) within

this graph.

Data is taken from Period Graph after the statistics

application performs the compression algorithm and not

from NMS database.

[Update Period

Graph]

Click to update the Period Graph according to the

selection in Data Period

[Reset Zoom] Click to reset the graph zoom to the lowest resolution


Detailed View

Selecting Detailed opens the detailed chart.

Figure 5-14. Detailed Chart

Table 5-10. Detailed View Parameters

Parameter Name

Values Notes

Data Period

From Date, current date

(YYYY-MM-DD)

You cannot select a date later than the date selected in

To.



Parameter Name

Values Notes

To Date, current date

(YYYY-MM-DD)

You cannot select a date earlier than the date selected

in From.

Period Graph Displaying data in the time

period selected in Data

Period

You can select points within the graph. Such selection

affects only Zoom Graph display.

Data is taken from NMS database, but as there is too

much data to be filled in this graph, the statistics

application performs a compression algorithm preserving

the graph behavior so that line tendency is not affected

(note that extremum points might not be displayed, due

to the “smoothing action”algorithm).

Zoom Graph Displays data in time period

for point selected within

Period Graph

Time period of this graph can be changed in the

following ways:

• Selecting points within Period Graph.

• Clicking [< Previous] or [Next >].

Displays data that is taken from NMS database (again).

This data is “real” (uncompressed). Therefore the

amount of data points that can be displayed in the graph

is very limited. Thus, the statistics application divides this

data into Time Windows displaying a time period. You

can “browse” these windows by using [< Previous] and

[Next >] buttons.

A scenario for example:

• Time Window with time period of five hours

• Period Graph – you can select a point with time of

12:34.

• Zoom Graph displays time window of 12:00-17:00.

• Clicking [< Previous] changes the displayed data

period to 07:00-12:00

• Clicking [Next >] changes the displayed data period to

17:00-22:00

[Update Period

Graph]

Click to update the Period Graph according to the

selection in Data Period

[Reset Zoom] Click to reset the graph zoom to the lowest resolution


[< Previous] Click to move to the previous time window

[Next >] Click to move to the next time window

Both period and zoom graphs represent “accident” points by drawing vertical red lines through such points. An “accident” point is defined as a point that has exceeded a “critical” level and has a certain amount of adjacent successors that have also exceeded this level.

RADview-HPOV/Lite Ver. 1.7 Administering Users in the HPOV Environment 6-1

Chapter 6

Security Management

6.1 Overview

This chapter describes the following:

• Managing users

• Defining user security access.

6.2 Administering Users in the HPOV Environment

HPOV advanced security features allow users to be defined with varying security access to network elements and functions. The following sections describe how to create users and define their security access.

Adding Users

Administrators can add users by following this procedure:

To add a new user:

1. From the submap screen select Misc> RADview/OV > General> Security > Capabilities.

The Security Capabilities dialog box appears.

2. Click <Add>.

The Add User dialog box appears.

Chapter 6 Security Management Installation and Operation Manual

6-2 Administering Users in the HPOV Environment RADview-HPOV/Lite Ver. 1.7

Figure 6-1. Security Capabilities Dialog Box

Installation and Operation Manual Chapter 6 Security Management


Figure 6-2. Add User Dialog Box

3. Fill in the User Name, Password, and Verify Password fields for the intended new user.

4. For each Network Element from the list, define the access level of the new user.

Changing User Password

To change a user password:

1. From the submap screen select Misc > RADview/OV > Login.




2. Click <Change Password>.

The Change Password screen appears.

Figure 6-3. Change Password Dialog Box

3. Type your old password into the Old Password field.

4. Type your new password into the New Password field.

5. Type your new password into the Verify New Password field to confirm your new password.

6. Click <OK>.

Defining User Security Access Levels

The following are the user security access levels:

• Administrator: An Administrator can configure path management, including adding and removing elements form the map hierarchy. An administrator can view and configure all aspects of RADview-HPOV/Lite including all the map levels, agent, and edit configuration. The administrator can add, change, and remove users in the system and define their access privileges. An administrator can view the security log to see all Login and Logout attempts.

• Operator: Has full Write mode and access to all except for User/System Administration (Read-only)

• Technician: Has limited access to configuration operations

• Monitor: Has read-only mode for configuration operations, and no access to other applications

If a user attempts to carry out a restricted action, an Access Denied dialog box appears.

Note



Table 6-1. Access Level Definitions

Access Level Defining Users

Map Level

Applications

Zoom: Agent

Configuration

Zoom: Testing &

Alarms Clear

Zoom: Statistics

Administrator + + + + +

Operator – – + + +

Technician – – – + +

Monitor – – – – +

To define a user as an Administrator:

A user defined as an administrator has administrator privileges for all network elements and cannot be defined as an operator, technician, or monitor for individual elements (see Table 6-1).

1. Click <Administrator> in the Access field so that the field is filled in.

1. Click <OK>.

To define the access level of a user for each network element:

The left side of the Add User or Change User dialog box contains a list called All that contains all network elements (by selection name) currently on the map.


To set the access level for a network element currently on the map, select a network element in the All list by clicking it.

To set the access level for a network element not currently on the map, type the network element in the empty field below the All list

2. Use the arrow buttons in the middle of the screen to move the network element to a User Access level (Operator, Technician, Monitor).

The network element appears under the appropriate User Access Level category.

3. Repeat this process for each network element to be assigned.

4. Click <OK>.

Changing User Security Capabilities

To change user security capabilities:

1. In the Security Capabilities dialog box, select the name of the user to be changed and click Change.

The Change User dialog box appears.



Figure 6-4. Change User Dialog Box

2. Select a network element by clicking it in the All list, or for a network element not in the All list, type the network element in the empty field below the All list.

3. Add the network element to a user level or remove it from a user level by using the appropriate arrow in the center column.

4. Click <OK>.



To copy user security capabilities:

1. In the Security Capabilities dialog box, select the name of the user to be copied and click <Copy>.

The Copy User dialog box appears.

Figure 6-5. Copy User Dialog Box

2. Fill in the User Name, Password, and Verify Password fields for the user that you are copying.



Removing Users

To remove a user:

1. In the Security Capabilities dialog box select the name of the user to be removed.

2. Click <Remove>.

The Remove User dialog box appears.

Figure 6-6. Remove User Dialog Box

3. Click <OK>.

Viewing User Security Access Privileges

Users can view their own access levels for each network element. Administrators can view a list of all users and their access levels.

To view user access level privileges:

• From the submap screen select Misc > RADview/OV > General> Security > Capabilities.

The Security Capabilities dialog box appears.

From the Security Capabilities dialog box, Administrators can change, add, or remove users.

Displaying the Security Log

An administrator can display a log of all RADview-HPOV/Lite login and logout attempts, including failed attempts.

To display Security Log:

1. From the submap screen select Misc > RADview/OV > General > Security > View Security Log.

The Security Log appears.



Figure 6-7. Security Log Dialog Box

Security Log Status can be OK, Fail, or By System. OK: Login / Logout successful. Fail: Unspecified user or unspecified password. By System: If a user neglects to log out and closes HP Open View, the system will register this as a logout By System upon subsequent login.

2. To save the Security Log to a file, click <Save to File> and then enter the file name and location.

3. To print the Security Log, click <Print>.

4. To clear the Security Log, click <Clear>.

5. Click <Close> to exit the Security Log.

RADview-HPOV/Lite Ver. 1.7 Testing the Unix User Environment 7-1

Chapter 7

Fault Management

7.1 Managing Alarms

In RADview-HPOV/Lite, alarms are SNMP traps (or events) that are generated by agents, or system events generated by the EMS server that communicate with the agent. The All Alarms Browser displays these events and traps.

Figure 7-1 shows a sample of the All Alarms Browser. Each trap appears on a separate line

Figure 7-1. All Alarms Browser

7.2 Testing the Unix User Environment

If you need to test the Unix user environment, for example because the RADview-HPOV/Lite application does not function properly, or upon request from RAD Technical Support, you can use the RADview User Environment Tool or you can test the environment with commands.

Testing with User Environment Tool

You can use the RADview Post-installation User Environment Tool to test the following in the Unix user environment and installation:

• HPOV NNM process statuses

• Informix variables

Chapter 7 Fault Management Installation and Operation Manual

7-2 Testing the Unix User Environment RADview-HPOV/Lite Ver. 1.7

• Informix database online status

• ODBC variables

• ODBC driver

• RADview application path (MNG164__APP_PATH)

• Dynamic Libraries variable (LD_LIBRARY_PATH)

• CDE Language Variable (LANG)

• SHELL variables

• Informix disk space capacity.

To test the user environment with the user environment tool:

1. Log in as the user that you wish to test.

2. Type: /opt/MNG/MNGVIEWHP/bin/user_env.csh

As the script executes, it shows pass/fail messages on the screen, and writes the test results into the file user_env.log in the user home directory.

***************************************************************

* RADview User Environment *

* *

* This script should run only on a Unix server, that is *

* a dedicated RADview-HPOV installation. *

* *

* This script sets the User Environment variables for a *

* newly created user and performs User Environment tests *

* for an existing user. *

* *

* Run this script as RADview user and not as root. *

* *

* This script must run under csh environment only. *

* *

* User Environment variables are written into the *

* logfile user_env.log in the users home directory. *

**************************************************************

Running user environment tests for an existing user.

Checking HPOV NNM processes status...

HPOV NNM processes are running.

Installation and Operation Manual Chapter 7 Fault Management


Checking Informix Installation...

Informix Database Installed.

Checking ODBC...

ODBC installation and home directories are defined.

Checking application path...

Application path defined.

Checking Informix status...

Informix database is up

Checking LD_LIBRARY_PATH Environment Variable...

LD_LIBRARY_PATH defined.

Checking CDE Language variable...

*** WARNING: CDE Language variable is not set correctly. ***

Logout and modify the CDE language.

In the DTE login Dialog choose options > Language > c to en_GB.ISO8859-15> C-POSIX

Checking user shell...

User shell set to csh.

Checking ODBC Driver...

ODBC driver installed.

Checking that Informix disk capacity is below 90%

Informix Disk Space OK.

---------------------------------------------------------------

| RADview User Environment script done. Found 1 problem(s). |

| If you cannot correct the problem, send the file |

| /export/home/g7/user_env.log to RAD Technical Support. |

---------------------------------------------------------------

Figure 7-2. Testing RADview User Environment – Existing User

In the example above, the script found one error:

*** WARNING: CDE Language variable is not set correctly. ***

Logout and modify the CDE language.


7-4 Testing the Unix User Environment RADview-HPOV/Lite Ver. 1.7

In the DTE login Dialog choose options > Language > c to en_GB.ISO8859-15> C-POSIX

Figure 7-3 illustrates how to correct the error.

Figure 7-3. Correcting the Informix LANG variable

If you cannot correct the problem, send the file /export/home/g7/user_env.log to RAD Technical Support.

Testing with Commands

You can execute the commands in Table 7-1 to verify that the Unix user environment is set correctly.

Table 7-1. Testing the User Environment

Environment Test Result Note

1 To check Informix installation

directory, type:

cat /etc/passwd | grep informix

informix:x:101:100::<INF_HOME>:/bin/sh

Example

If the Informix installation directory is

/opt/informix, result is:

informix:x:101:100::/opt/informix:/bin/sh




2 To verify Informix installation

directory, server, and SQL

Hosts file are defined, type:

env | grep INF

INFORMIXDIR=<INF_HOME>

INFORMIXSERVER=mng164

INFORMIXSQLHOSTS=<INF_HOME>/etc/sqlhosts

Example



INFORMIXDIR=/opt/informix

INFORMIXSQLHOSTS=/opt/informix/etc/sqlhosts

Else

Verify user's .cshrc file was edited

correctly, and logout / login was

performed

3 To verify ODBC installation

and home directories are

defined, type:

env | grep ODBC

ODBCDIR=<INF_HOME>/ odbc

ODBCHOME=<INF_HOME>/ cli/cli

Example



ODBCDIR=/opt/informix/odbc

ODBCHOME=/opt/informix /cli/cli

Else

Verify user's .cshrc file was edited

correctly, and logout / login was

performed

4 To verify MNG164_APP_PATH

(RADview-HPOV/Lite home

directory) is defined, type:

echo $MNG164_APP_PATH

/opt/MNG/MNGVIEWHP Else

Verify the mng164_setenv.sh script was

executed by the user, and logout/login

was performed

5 To verify the

LD_LIBRARY_PATH variable

exists and points to the

Informix installation

directory, type:

env | grep LD_LIB

LD_LIBRARY_PATH=/opt/informix/odbc/lib:/opt/informix/odbc/drivers:/usr/lib:/opt/informix/odbc/lib:/opt/informix/odbc/drivers:/usr/lib:

/opt/informix/odbc/lib:/opt/informix/odbc/drivers:/usr/lib:/opt/OV/lib:/opt/informix/cli/lib:/opt/informix/cli/lib/esql:/opt/informix/cli/cli/dlls::/opt/OV/lib::/opt/informix/cli/lib:/opt/

Example



LD_LIBRARY_PATH=/opt/informix/odbc/lib=/opt/informix /odbc/drivers:/usr/lib

Else

Verify the mng164_setenv.sh script was

executed by the user, and logout/login

was performed.

6 To verify the CDE Language

variable is set correctly, type:

echo $LANG

(see Figure 7-3)

C Else

Modify the CDE language as follows: In

the CDE login dialog choose options >

language > c to en_GB.ISO8859-15 >

c-posix

7 To verify the user's shell is

csh, type:

echo $SHELL

/bin/csh Else

Change user shell to csh via admintool


7-6 Frequently Asked Questions RADview-HPOV/Lite Ver. 1.7


8 To verify Informix database is

online, type:

onstat –

INFORMIX-OnLine Version 7.20.UC2 -- On-Line -- Up 11 days 22:33:56 -- 12272 Kbytes

Else

Unless Informix is reported to be online,

database is down

9 To verify the user's home

directory includes .odnb.ini

file, pointing to an ODBC

driver located under the

Informix installation

directory, type:

cat /<USER_HOME_DIR>/.odbc.ini|grep vsifmx7.so.1

Driver=<INF_HOME>/odbc/drivers/vsifmx7.so.1

Replace <USER_HOME_DIR> with the

user’s home directory.

In case the above commands do not solve the problem, or return unexpected results, contact RAD Technical Support and send the output of all the above commands. In addition, send the Unix user’s .dtprofile and .cshrc files.

7.3 Frequently Asked Questions

This section contains commonly asked questions about RADview-HPOV/Lite.

Q. My /opt partition doesn’t have enough space for installation of RADview-HPOV/Lite. How can I install RADview-HPOV/Lite in a different partition?

A. By default, the RADview-HPOV/Lite installation script attempts to perform the installation in the /opt partition. If the /opt partition lacks sufficient disk space, the installation script stops and indicates the minimum disk space needed to install the selected components.

If the /opt partition doesn’t have enough space for installation, you can either free the required disk space or create a symbolic link to another location on the disk thathas sufficient disk space.

For example, to create a symbolic link between /opt and /export/home, use the following procedure:

1. Create a new directory named /export/home/MNG

2. Type: ln -s /export/home/MNG /opt/MNG

Q. How does the RADview-HPOV/Lite installation influence the HPOV platform?

A. During installation, RADview-HPOV/Lite places the following files inside HPOV (this is normal when integrating with HPOV):

• Registration files (including menu entries and application registration)

• Symbol registration files

• Field registration files.


RADview-HPOV/Lite Ver. 1.7 Technical Support 7-7

Use xnm events to load definitions of RAD's traps. MIB files are not installed anymore in HPOV. The files may be installed from the CD if necessary.

We follow the rules dictated by HPOV to perform integration. We do not influence the daemon intercommunication.

Q. After I install RADview-HPOV/Lite, how do I know for which IP/MAC address or host ID to request the license?

A.

You must have License Manager Version 2.02 (All installation setup from 2005 and above).

The host identifier for Unix is the host ID.

To determine the host identifier for the License Manager,, open a terminal and type the command: hostid.

If you encounter difficulties installing the license, you should provide the output of the above procedures to RAD Technical Support.

Q. How can I integrate RADview-HPOV/Lite or RAD devices with Netcool?

A. NetCool Omnibus (Cisco Info Center = CIC) can interface with RAD in three ways:

1. Interface with SNMP traps coming from RAD devices. For this you need SNMP Traps probe (mttrapd probe). Therefore you have to compile the RAD MIB file so that NetCool can understand the traps coming from RAD devices.

2. Interface with HPOV NNM (RADview works on top of HPOV). For this you need an HPOV NNM Probe. Compile the trapd.conf file so that NetCool can understand the events coming from HPOV. In this solution HPOV (and RADview-HPOV/Lite) are installed on one station and Netcool on another station.

3. Interface with RADview-HPOV/Liteand HPOV NNM. Same as option 2 above, but in addition, the user can launch RADview Zoom application directly from the Netcool Alarm Log. This integration can only be done by an engineer from RAD (including all the costs involved).

7.4 Technical Support

Technical support for RADview-HPOV/Lite can be obtained from the local distributor from whom it was purchased.

For further information, please contact the nearest RAD distributor or one of RAD's offices worldwide. This information can be found at RAD's Web site: http://www.rad.com/ (for office locations, click About RAD > Worldwide Offices; for distributors location, click Where to Buy > End Users).

Notes

Note

http://www.rad.com/�


7-8 Technical Support RADview-HPOV/Lite Ver. 1.7

RADview-HPOV/Lite Ver. 1.7 Checking the Installed Software A-1

Appendix A

Migration Guide

A.1 Introduction

This guide explains the required migration process to upgrade to the newer RADview version that is supported only by HPOV NNM Ver. 7.5 and Solaris 10.

RADview users must upgrade their systems when:

1. A new network element requires the newer RADview that in turn requires NNM 7.5

2. The server is replaced according to the scalability and hardware performance guidelines.

3. Both of the above.

There are two scenarios when upgrading RADview:

• Upgrade – Upgrading an existing RADview Station (Solaris, NNM, RADview) on the same hardware

• Migration – Migrating RADview to new hardware, while keeping the database of the existing system.

A.2 Checking the Installed Software

Before starting the migration process, verify the current system configuration of the following components: RADview, HPOV, and Solaris.

To verify the current HPOV version:

1. Launch RADview (open a terminal and type: ovw)

2. From the HPOV NNM menu bar select Help > About HP OpenView…

The About HP OpenView window displays:

Appendix A Migration Guide User's Manual

A-2 Checking the Installed Software RADview-HPOV/Lite Ver. 1.7

Figure A-1. About HP OpenView

3. The HPOV version appears on the first line.

To verify the RADview version:

1. From the About HP OpenView window (Figure A-1), click <Applications>.

The Application Index window opens:

Figure A-2. Application Index

2. Scroll down to the RADview entries. Highlighting each RADview entry displays the version on the right side of the window.

To verify the Solaris version:

1. Open a Sun terminal window.

2. Type uname -a and press <Enter>.

The Solaris version is displayed.

Figure A-3. Solaris Version

User's Manual Appendix A Migration Guide

RADview-HPOV/Lite Ver. 1.7 Migration Procedure Overview A-3

A.3 Upgrade Procedure Overview

When upgrading an existing RADview station, the HPOV and RADview databases on the server are preserved. The server is not formatted, only upgraded. However, before upgrading or migrating RADview it is strongly recommended that you backup your systems (refer to the Backup and Restore Tool in Chapter 4).

To upgrade an existing RADview station:

1. Backup your system using the RADview Backup and Restore tool.

2. Upgrade RADview to the required version according to the instructions appearing in Chapter 2 of the User Manual.

3. Upgrade HPOV NNM according to the procedures mentioned in section A.5.

4. Upgrade Solaris 8 to Solaris 10 according to the procedures mentioned in A.6.

5. Adjust Informix and TFTP setting according to the procedures mentioned in A.8.

6. Backup your system once more to keep an up-to-date backup file.

A.4 Migration Procedure Overview

Before migrating RADview, HPOV and RADview must be upgraded, before restoring the system and database to the new hardware from scratch.

To migrate RADview to new hardware:

1. Upgrade your existing RADview to the one that will be used after upgrading HPOV NNM and Solaris (before upgrading HPOV NNM or Solaris).

2. Backup your system with the RADview Backup and Restore tool (see Chapter 4).

3. Install Solaris 10 on the new hardware as specified in A.6.

4. Install HPOV NNM 7.51 as specified in A.7.

5. Install RADview according to the installation procedures in Chapter 2 of the RADview User Manual.

6. Use the backed-up file from your old RADview station and perform restore as described in the RADview User Manual (see Chapter 4).


A-4 Upgrading HPOV NNM 6.31/6.40/6.41 RADview-HPOV/Lite Ver. 1.7

A.5 Upgrading HPOV NNM 6.31/6.40/6.41

Since Solaris 10 requires NNM version 7.50 or later, customers migrating from Solaris 8 to Solaris 10 must migrate to NNM 7.50. However, software migration to NNM 7.50 cannot be performed directly from NNM 6.31.

• Migrate NNM 6.31 first to NNM 6.41, and only then to NNM 7.50, followed by NNM 7.51 (NNM 7.51 is optional).

• Migrate NNM 6.40 first to NNM 6.41, before upgrading to NNM 7.50/7.51.

Once the migration to NNM 7.50/7.51 is complete, you can upgrade Solaris 8 to Solaris 10.

• Direct migration to NNM 7.50 is supported only from NNM versions 6.2, 6.41 and 7.01

• It is the user’s responsibility to upgrade HPOV according to the official instructions of HP (refer to http://support.openview.hp.com/selfsolve/manuals). The included HPOV NNM upgrade procedures are given only as a recommendation.

Upgrading NNM 6.31/6.40 to NNM 6.41

If you are using NNM version 6.31 or 6.40, upgrade first to version 6.41.

To migrate from NNM 6.31/6.40 to NNM 6.41:

1. Log in with root privileges and verify that all HP OpenView process that are currently running, by typing:

# tcsh

# cd /opt/OV/bin/

# ./ovstatus -c

2. Stop all HP OpenView processes by typing: # /opt/OV/bin/ovstop

3. Recheck that all processes have stopped, by typing:

# /opt/OV/bin/ovstatus –c

If all processes are down, you should receive the message:

“ovstatus : ovspmd is not running”

4. Insert the NNM 6.41 installation CD into the CD-ROM drive.

5. Type:

# cd /cdrom/cdrom0/

# ./install

The following message appears: “Do you want Network Node Manager to discover your network automatically after the instillation? (y/n)”

Note

http://support.openview.hp.com/selfsolve/manuals�


RADview-HPOV/Lite Ver. 1.7 Upgrading HPOV NNM 6.31/6.40/6.41 A-5

6. Type n (No).

The following message appears: “Do you want the Network Node Manager user interface to be displayed after the installation? (y/n)”

7. Type n (No).

The following message appears: “Please enter the full path in your Web Browser or press “s” to skip”

8. Type s to skip.

The following message appears: “Do you to continue with this instillation? (y/n)”

9. Type y (Yes).

NNM 6.41 is installed on your system. Once installed, you can verify the installation by typing: # /opt/OV/bin/ovversion .

Upgrading NNM 6.41 to NNM 7.50

Migration to NNM version 7.50 is possible only from NNM version 6.41.

To migrate from NNM 6.41 to NNM 7.50:

1. Log in with root privileges and verify that all HP OpenView process that are currently running, by typing:

# tcsh

# cd /opt/OV/bin/

# ./ ovstatus -c

2. Stop all HP OpenView processes by typing: # /opt/OV/bin/ovstop

3. Recheck that all processes have stopped, by typing:

# /opt/OV/bin/ovstatus –c

If all processes are down, you should receive the message:

“ovstatus : ovspmd is not running”

4. Insert the NNM 7.50 installation CD No. 1 into the CD-ROM drive.

5. Type:

# cd /cdrom/cdrom0/

# ./install


6. Type n (No).

The following message appears: “Do you want the Network Node Manager user interface to be displayed after the installation? (y/n)”

7. Type n (No).


Note


A-6 Installing/Upgrading to Solaris 10 RADview-HPOV/Lite Ver. 1.7

8. Type s to skip.


9. Type y (Yes).

NNM 7.50 is installed from CD 1.

10. Once the installation from CD 1 completes, type:

# cd /

# eject cdrom

11. Remove CD No. 1 and insert the NNM 7.50 installation CD No. 2 into the CD-ROM drive.

12. Type:

# cd /cdrom/cdrom0/

# ./install

The following message appears: “Do you want to continue with this instillation? (y/n)”

13. Type y (Yes).

NNM 7.50 is installed from CD 2. When the installation completes, the following message appears: ”Network Node Manager Installation complete”. You can verify the installation by typing: # /opt/OV/bin/ovversion .

HP defines the upgrade from a NNM version 7.50 to version 7.51 as a regular upgrade, rather than a migration process. If you would like to install NNM 7.51, use the NNM 7.51 upgrade CD.

A.6 Installing/Upgrading to Solaris 10

Installation Notes

This section provides important information on the requirements, possible problems and troubleshooting in the upgrade process.

Required Media

The Solaris 10 installation procedure includes several stages. Before you begin, make sure that:

a. You have all five installation CDs, or the DVD that contains the entire installation package

Note


RADview-HPOV/Lite Ver. 1.7 Installing/Upgrading to Solaris 10 A-7

b. Your CD-ROM drive can fully access and read each CD. Insert each CD into the drive and verify that the computer recognizes the media (for example, by browsing through the different directories). This check is important since you may not be able to resolve media problems during the installation, and this may cause your system to remain in corrupt state.

Required Information

During installation you will be asked to provide general information on your system (networked system):

Host name of the system that you are installing

Language and locales that you intend to use on the system

Host IP address

Subnet mask

Type of name service (for example: DNS, NIS, or NIS+)

Domain name

Host name of the name server

Host IP address of the name server

Root password.

Possible Installation Methods

The installation can be performed either by:

A. Upgrading a system running with Solaris 8 (if exists) to Solaris 10;

or –

B. Installing Solaris 10 from scratch, installing HPOV and RADview, and then performing system restore.

In both methods, you must first perform backup and then save the backup files on a different station (or more).

For option A, you only need to install Solaris 10 in Upgrade mode over Solaris 8. The upgrade, however, may involve an initialization error, as explained in the next section (Possible Failures During Upgrade).

For option B, skip to Installing Solaris 10.

Possible Failures During Upgrade

In the upgrade procedure, only the Solaris operating system is upgraded, while the other already installed applications are left intact.

During the installation, however, the Solaris 10 Upgrade dialog box may fail to appear, and only the initial installation option may be available (not allowing to upgrade, leaving you only with the option to format the hard disk and loose all information stored on it).



Checking the Upgrade Availability

You can check the availability of the upgrade option without performing the full installation.

To check for the upgrade availability:

1. Reboot and run the Solaris 10 installation CD.

2. Proceed with the installation steps until you reach the License Agreement stage. This may take a few minutes since the system gathers information before reaching the License Agreement stage.

3. Once the License Agreement step is displayed, click Next.

A dialog box should appear and display the caption: “Select upgrade or initial install”. In this dialog box you should have the option to choose an initial installation or an upgrade.

If the dialog box displays only the Default installation and Custom installation options, it means that the installer runs in initial installation mode. If this is the case, you should exit the installer by clicking Exit.

Attaining Upgrade Availability

If the upgrade option is not automatically available, you can attain it manually.

To make the upgrade option available:

1. Reboot your Solaris 8 system regularly.

2. Open the /etc/vfstab file.

3. Type: vi /etc/vfstab

4. Remove the following lines/references in the /etc/vfstab file:

All mounts, swap files and disk parts that are not being upgraded

Swap files that are no longer present

Any unused swap parts.

Leave only the c0t0d0sX mounts:

Figure A-4. Modified Mounts

5. After applying the changes, type: reboot cdrom, and restart the installation.

The upgrade option should now be available.

Note


RADview-HPOV/Lite Ver. 1.7 Installing/Upgrading to Solaris 10 A-9

Installing Solaris 10

If you are upgrading to Solaris 10 from Solaris 8, refer to Steps Prior to Upgrading below.

If you are installing from scratch, skip to Installation Procedure.

Steps Prior to Upgrading

Before installing Solaris 10 over Solaris 8:

1. Stop all HP OpenView processes: /opt/OV/bin/ovstop

2. Stop the EMS server process: //etc/rc3.d/S98RvEmsServer stop

3. Enter CD No. 1 or the DVD of the Solaris 10 installation in the CD-ROM/DVD drive.

4. Type: init 0

5. Reboot your system: boot cdrom

Installation Procedure

The following table summarizes the required actions in each step/window of the installation process.

Table A-1. Solaris 10 Installation Summary

Window Name Option to Choose / Info to Provide

Button to Click

1. Welcome Next

2. Network Connectivity Networked Next

3. DHCP for eri0 No Next

4. Host Name for eri0 xxx Next

5. IP address for eri0 xxx.xxx.xxx.xxx Next

6. Net mask for eri0 255.255.255.000 Next

7. IP v6 for eri0 No Next

8. Set the default route for eri0 Specify one Next

9. Set the default route for eri0 Specify one Next

10. Kerberos No Next

11. Name Service None Next

12. Time Zone Geographic

continent/country/region

Next

13. Continent and country Select Country Next

14. Date and time Set the date and time Next

15. Root password Enter your root password Next

16. Enabling remote services Yes Next




Button to Click

17. Confirm Information Yes

18. Wait.. Next

19. Welcome Next

20. Installer options Reboot automatically after software

installation (Yes);

Eject CD/DVD automatically after

software installation (Yes)

Next

21. Specify media CD/DVD Next

22. Initializing…

23. License Accept Next

24. If the system detected a

previously installed Solaris:

Select upgrade or initial install

Otherwise:

Select initial install

Upgrade

or

Initial install

Next

25. Select installation type Custome Next

26. Select software localizations Skip – do not select Next

27. Select system locale POSIX English (POSIX C) Next

28. Select products Skip – do not select Next

29. Additional products None Next

30. Gathering information…

31. Select Solaris Software group Entire group

Select default package

Next

32. Disk choosing Choose c1t1do (bootdisk) Next

33. Preserve data No Next

34. Gathering information…

35. Lay out file system Choose C1t1d0 Modify


RADview-HPOV/Lite Ver. 1.7 Installing HPOV 7.5 A-11


Button to Click

36. Sile system slice sizes:

Slice File system Size in MB

0 / Rest of HD

1 Swap 2xRAM size

2

3

4

5

6

7

Set the swap size

Set / to slices

Apply (several times)

OK

37. Ready to install Install Now

38. Installing …

39. White screen:

Loading smf(5) service

descriptions xx/97 Until xx=97

Do you need to override the

system’s default NFS version 4

domain name? (yes/no)

No

40. Specify media CD/DVD Next

41. Insert disc Insert disc #2 Next

42. Ready to install Install Now

43. Continue as requested with CD

#3,4,5

44. Complete

At the end of the process, add users as explained in Chapter 2.

A.7 Installing HPOV 7.5

This section is relevant only for installations from scratch. The HPOV NNM installation procedures are given only as a recommendation. Refer to the HP official procedures at http://support.openview.hp.com/selfsolve/manuals.

After formatting the station and installing Solaris 10, perform the following preliminary steps:

1. Reboot the station.

2. Once the reboot is complete, log in as a non-root user.

3. Insert the NNM 7.50 installation CD No. 1 into the CD-ROM drive.

Note

http://support.openview.hp.com/selfsolve/manuals�


A-12 Installing HPOV 7.5 RADview-HPOV/Lite Ver. 1.7

4. In the terminal portal, log in with root privileges.

5. Type:

# cd /cdrom/cdrom0/

# ./install


6. Type n (No).

The following message appears: “Do you want the Dynamic Views Browser to be displayed after the installation? (y/n)”

7. Type n (No).


8. Type s to skip.


9. Type y (Yes).

NNM 7.50 is installed from CD 1.


# cd /

# eject cdrom

11. Remove CD No. 1 and insert the NNM 7.50 installation CD No. 2 into the CD-ROM drive.

12. Type:

# cd /cdrom/cdrom0/

# ./install

The following message appears: “Do you want to continue with this instillation? (y/n)”

13. Type y (Yes).

14. NNM 7.50 is installed from CD 2.

When the installation completes, the following message appears: ”Network Node Manager Installation complete”. You can verify the installation by typing: # /opt/OV/bin/ovversion .


# cd /

# eject cdrom

# reboot

The installation CD is ejected and the station reboots itself. The station is now ready for the HPOV 7.5 installation.


RADview-HPOV/Lite Ver. 1.7 Post-upgrade Procedures A-13

16. It is recommended to upgrade to 7.51 (please follow HP user manual for these procedures)

A.8 Post-upgrade Procedures

Adjusting TFTP Server in Solaris 10

Configure the TFTP server functionality for compatibility with Solaris 10.

To configure the TFTP server in the Solaris 10 environment:

1. Type: mkdir –p <directory name> (for example: mkdir –p /export/home/tftp)

2. Type: chmod –R 777 < directory name> (for example: chmod –R 777 /export/home/tftp)

3. Edit the /etc/inetd.conf file as follows:

Find the line starting with #tftp dgram udp6

Remove the # character

Remove the 6 from udp6 (should be just udp)

At the end of the line, you see –s <tftp_boot>. Change the <tftp_boot> to the directory you have just created. E.g., -s /export/home/tftp.

Figure A-5. TFTP Settings

4. Type: sync

5. Type: init 6

The system reboots.

6. After the restart, type: svcs |grep tftp.

No output should be displayed. If you receive the final configuration message (see Figure A-6), your configuration is already set.

7. Type: inetconv

All entries from /etc/inetd.conf are converted to SMF entries.

8. Type: svcs |grep tftp .

The final configuration message is displayed.

Figure A-6. Final Configuration Message


A-14 Post-upgrade Procedures RADview-HPOV/Lite Ver. 1.7

Adjusting Informix

To adjust Informix:

1. Login as root user.

2. Type: vi /etc/services

3. Add the following line to the file: sqlturbo 1526 /tcp (the location inside the list is not important).

Figure A-7. Adjusting Services File for Informix

4. Reboot the system.

5. Make sure Informix is running by typing: <Informix home directory>/bin/onstat –

The following confirmation message should be displayed:

Figure A-8. Informix Confirmation Message

RADview-HPOV/Lite Ver. 1.7 I-1

Index

—A—

ACU help, 4-41 status messages, 4-30

ACU Automatic Configuration Upload, 4-15 client, closing, 4-42 client, opening, 4-18 immediate upload, 4-28 profiles, 4-22

activating, 4-28 adding, 4-23 deactivating, 4-28 editing, 4-24 nodes, selecting, 4-26 removing, 4-27

report table, 4-30 clearing, 4-40 filtering, 4-32 printing, 4-39 refreshing, 4-37 saving, 4-37

tasks, summary, 4-21 TFTP server, configuring, 4-15 TFTP settings, configuring, 4-21

Add User, 6-1

Administrator, 6-4 Agent

Creating, 3-9 monitoring, 3-14

Agent SNMP parameters, 3-11 Alarm Categories, 3-14 Alarms, 7-1

display categories, 3-14 Autodiscovery

HPOV, 4-1 Automatic deletion of nodes

Disable, 4-2

—B—

Backup, 4-43 configuring, 4-44 database, 4-43 license, 4-43 requirements, 4-43 running, 4-47 RV, 4-43

Bundled license, 4-5

—C—

Changing agent attributes, 3-13

Changing the password, 6-3 Changing user security capabilities, 6-5 ConfiguRAD, 1-2 Configuration Management, 1-2 Creating an agent, 3-9

—D—

Date and time Auto mode, 4-84 net, 4-83

Deleting an Agent, 3-13 Diagnostics, 1-2 Disable Delete Nodes, 4-2 Display

alarm categories, 3-14

—E—

ENW, 4-4 Equivalent Node Weights, 4-4

—F—

Fault Management, 1-1 Features, 1-1 Functions supported, 1-2

—G—

Get Community, 3-12

—H—

Hardware requirements, 1-5 HP OpenView session

Ending, 3-14 Starting, 3-2

HPOV Autodiscovery, 4-1 Autodiscovery, disabling, 4-1 map status color propagation, 4-1 Map Status Color Propagation, 4-1 screen display, 3-4 Screen display, 3-4

HPOV session sEnding, 3-14 Starting, 3-2

—I—

Informix uninstalling, 2-11

Installation Hardware requirements, 1-5 Software requirements, 1-5

Index User's Manual

I-2 RADview-HPOV/Lite Ver. 1.7

Installing license, 2-9

—L—

License Add, 4-10 Calculating Points, 4-5 installing, 2-9 Points, 4-5 Remove, 4-11

License Calculator, 4-6 License service manager, 4-6

Add license, 4-10 Managed element list, 4-8 Opening, 4-6 Remove license, 4-11

License Service Manager Client Configuration, 4-14 Server Configuration, 4-13

License,bundled, 4-5 Licenses installed

viewing, 4-6 Licensing

Network size, 4-4 Licensing, 4-3

Terms, 4-4

—M—

Managed element list, license service manager, 4-8 Map

Moving objects, 3-6 Map application rules, 3-5 Map windows, moving between, 3-6 Monitor, 6-4 Monitoring

agent, 3-14 Moving objects on map, 3-6

—N—

Net creating, 3-7

Net hierarchy, 3-8 Net inventory, 4-78

editing entity, 4-82 filtering display, 4-80

Network topology, 3-8 Node names, 3-8

—O—

Operator, 6-4 OVbackup, 4-48

—P—

Password HPOV, 3-2 new, 6-3

Poll Intervals, 4-2 Poll Retries, 4-2 Products supported, 1-2

—R—

Remove

user, 6-8 Removing Users, 6-8 Requirements

Hardware, 1-5 Software, 1-5

Restore, 4-43 configuring, 4-44 requirements, 4-43 running, 4-48

Retry Count, 3-13 Root level rules, 3-5 Root map, 3-4 Rules

Map application, 3-5 root level, 3-5 WAN root map level, 3-5 WAN submap level, 3-6

—S—

Security log, 6-8 Selection name, 3-10 Set Community, 3-12 Setting

HPOV Autodiscovery, 4-1 Setting Polling Interval, 4-2 Setup

Hardware requirements, 1-5 Software requirements, 1-5

SNMP configuration, 4-2

SNMP platform, 1-1 Software requirements, 1-5 Status Polling, 3-13

—T—

Technician, 6-4 TFTP file transfer, 4-50 TFTP file transfer

Opening, 4-51 TFTP file transfer

default settings, 4-53 TFTP file transfer

default settings, 4-53 TFTP file transfer

Edit database, 4-54 TFTP file transfer

product profile adding, 4-54

TFTP file transfer options, 4-59

TFTP file transfer selecting nodes, 4-64

TFTP file transfer add agent from map, 4-66

TFTP file transfer remove agents, 4-67

TFTP file transfer transferring files, 4-67

TFTP file transfer reports, 4-74

TFTP file transfer report status messages, 4-76

TFTP file transfer save database, 4-77

User's Manual Index

RADview-HPOV/Lite Ver. 1.7 I-3

TFTP file transfer Help menu, 4-77

TFTP File Transfer adding agents, 4-66 download file, selecting, 4-61 editing product data, 4-61

TFTP server configuring, 4-50

Time Outs, 4-2 Timeout, 3-13

—U—

Uninstalling Informix, 2-11 Uninstalling RADview-HPOV/Lite, 2-11 Unix user

Creating, 2-6 Unix user environment

Defining, 2-8 Testing, 7-1 Testing with commands, 7-4 Testing with User Environment Tool, 7-1

User Adding, 6-1 administrator, 6-4 monitor, 6-4 operator, 6-4 removing, 6-8 Security Access, 6-4 technician, 6-4 View security access, 6-8

User, Unix Creating, 2-6

Using the GUI, 3-3

—W—

WAN Map terminology, 3-4

WAN Maps, 3-3 WAN root map level rules, 3-5 WAN submap, 3-4 WAN Submap Level Rules, 3-6

Index User's Manual

I-4 RADview-HPOV/Lite Ver. 1.7

24 Raoul Wallenberg Street, Tel Aviv 69719, Israel

Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250

E-mail: [email protected], Web site: http://www.rad.com

Customer Response Form

RAD Data Communications would like your help in improving its product documentation. Please complete and return this form by mail or by fax or send us an e-mail with your comments.

Thank you for your assistance!

Manual Name: RADview-HPOV/Lite Ver. 1.7

Publication Number: 217-210-05/08

Please grade the manual according to the following factors:

Excellent Good Fair Poor Very Poor

Installation instructions

Operating instructions

Manual organization

Illustrations

The manual as a whole

What did you like about the manual?


http://www.rad.com/�

Error Report

Type of error(s) or problem(s):

Incompatibility with product

Difficulty in understanding text

Regulatory information (Safety, Compliance, Warnings, etc.)

Difficulty in finding needed information

Missing information

Illogical flow of information

Style (spelling, grammar, references, etc.)

Appearance

Other

Please list the exact page numbers with the error(s), detail the errors you found (information missing, unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.

Please add any comments or suggestions you may have.

You are: Distributor

End user

VAR

Other

Who is your distributor?

Your name and company:

Job title:

Address:

Direct telephone number and extension:

Fax number:

E-mail:

Publication No. 217-210-05/08

International Headquarters 24 Raoul Wallenberg Street

Tel Aviv 69719, Israel

Tel. 972-3-6458181

Fax 972-3-6498250, 6474436

E-mail [email protected]

North America Headquarters 900 Corporate Drive

Mahwah, NJ 07430, USA

Tel. 201-5291100 Toll free 1-800-4447234

Fax 201-5295777

E-mail [email protected]

www.rad.com The Access Company

unix-based element management system · 2019-02-18 · radview-hpov/lite unix-based element...

Documents