radview-ems/tdm (unix) · radview-ems/tdm (unix) element management system for tdm applications...

RADview-EMS/TDM (Unix) Element Management System for TDM Applications

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-EMS/TDM (Unix) 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-EMS/TDM (Unix). 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-EMS/TDM (Unix), based on or derived in any way from the RADview-EMS/TDM (Unix). Your undertaking in this paragraph shall survive the termination of this Agreement.

This Agreement is effective upon your opening of the RADview-EMS/TDM (Unix) 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-EMS/TDM (Unix) 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: mailto:[email protected]

© 1994–2008 RAD Data Communications Publication No. 357-279-02/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-EMS/TDM (Unix) shall not exceed the sum paid to RAD for the purchase of the RADview-EMS/TDM (Unix). 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-EMS/TDM (Unix) Element Management System for TDM Applications

Version 1.7

System © 1994–2008 RAD Data Communications Publication 02/08

RADview-EMS/TDM (Unix) Ver. 1.7 i

Contents

Chapter 1. Introduction 1.1 Overview....................................................................................................................1-1 1.2 System Features ........................................................................................................1-1

Compliance with FCAPS ...........................................................................................1-1 Graphical User Interface (GUI) .................................................................................1-2 Bundled Agents (Products Managed by this Package) ..............................................1-2 Backup and Restore................................................................................................1-3 Scalability of Distribution ........................................................................................1-3

Client/Server Distribution....................................................................................1-3 Territorial Distribution ........................................................................................1-7

Master/Slave Server Functions.................................................................................1-7 1.3 System Requirements ................................................................................................1-8

Hardware Requirements..........................................................................................1-8 Software Requirements ..........................................................................................1-8

Chapter 2. Installation and Setup 2.1 Package Contents ......................................................................................................2-1 2.2 Installation.................................................................................................................2-2

Installation Sequence..............................................................................................2-2 Installing the Informix Database ..............................................................................2-2 Installing the RADview-EMS Package........................................................................2-4

Starting with the Initial Components...................................................................2-4 Continuing with RADview-EMS/TDM ....................................................................2-7

Installing Additional PC Clients (Optional) ..............................................................2-19 Installing RADview Shell on the PC Client...........................................................2-19 Installing RADview-EMS/TDM on the PC Client ...................................................2-24

Installation Notes .................................................................................................2-34 Changing the RADview-HPOV Installation Directory ...........................................2-34

2.3 Post-Installation Steps .............................................................................................2-34 Creating a User .....................................................................................................2-34 Defining the User Environment .............................................................................2-36

2.4 Frequently Asked Questions on Installation ..............................................................2-37 2.5 Uninstalling the RADview Package ............................................................................2-39

Uninstalling RADview ............................................................................................2-39 Uninstalling the Database .....................................................................................2-39

Chapter 3. Operation 3.1 Running the HPOV Platform........................................................................................3-1

Starting an HPOV Session........................................................................................3-2 Installing Licenses...................................................................................................3-3

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

WAN Map Terminology .......................................................................................3-5 Map Application Rules ........................................................................................3-6 Moving Between Map Windows ..........................................................................3-7 Moving Objects on the Map ................................................................................3-7 Setting Polling Interval........................................................................................3-7

Table of Contents User's Manual

ii RADview-EMS/TDM (Unix) Ver. 1.7

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

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

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

Monitoring Agents ................................................................................................3-15 Displaying Alarms Categories ............................................................................3-15 Moving Objects on the Map ..............................................................................3-16

Using the Java Zoom Applications..........................................................................3-16 3.3 Running the EMS Application ....................................................................................3-17

Starting/Stopping EMS Server from the Command Line ..........................................3-19 Logging Into RADview-EMS....................................................................................3-19 Changing the EMS Password..................................................................................3-20 Using the LaunchDesk Toolbar ..............................................................................3-21 Using the Zoom Applications.................................................................................3-22

3.4 Logging Out of RADview-EMS ...................................................................................3-22 3.5 Ending the HPOV Session .........................................................................................3-23

Chapter 4. Configuration Management 4.1 Setting the HPOV System Parameters.........................................................................4-1

Propagating the HPOV Map Status Color..................................................................4-1 Disabling Auto-Discovery ........................................................................................4-2 Disabling Automatic Deletion ..................................................................................4-2 Setting the Polling Interval, Timeouts and Retries ....................................................4-2

4.2 Setting the EMS System Parameters ...........................................................................4-3 Configuring Synchronization....................................................................................4-4 Browsing the System Elements ...............................................................................4-7

Performing Node Level Operations .....................................................................4-9 Performing Agent Level Operations ..................................................................4-14 Importing Nodes to the Network Element Browser ...........................................4-18

Configuring the EMS Consoles ...............................................................................4-20 Stopping and Restarting Consoles ....................................................................4-20 Setting the Required Log Functions ..................................................................4-21 Setting the Trap and Alarm Characteristics........................................................4-23 Setting Event Policies .......................................................................................4-25

Configuring the NER Elements...............................................................................4-39 Adding an Entry ...............................................................................................4-40 Renaming an Entry ...........................................................................................4-41 Removing an Entry ...........................................................................................4-41 Adding an Attribute..........................................................................................4-41 Modifying an Attribute .....................................................................................4-42 Removing an Attribute .....................................................................................4-43 Viewing Applied Changes..................................................................................4-43

4.3 Licensing .................................................................................................................4-43 Product-Specific Considerations ............................................................................4-44 Equivalent Node Weights (ENW)............................................................................4-44 Bundled License Points .........................................................................................4-45 License Size Calculations.......................................................................................4-45

User's Manual Table of Contents

RADview-EMS/TDM (Unix) Ver. 1.7 iii

Managing and Modifying Licenses .........................................................................4-46 Checking the Currently Installed License Points .................................................4-46 Checking the Managed Elements ......................................................................4-48 Adding a License ..............................................................................................4-50 Removing a License..........................................................................................4-52 Refreshing the License Display .........................................................................4-52 Starting and Stopping the License Service.........................................................4-52 Configuring the Server Side License Ports .........................................................4-53 Configuring the Client Side License Ports ..........................................................4-54

4.4 Additional Tasks and Options ...................................................................................4-55 Performing Automatic Configuration Upload (ACU) ................................................4-55

Setting up the TFTP Server in a Unix Workstation..............................................4-56 Launching the ACU Application .........................................................................4-57 Summary of ACU Configuration Operations.......................................................4-59 Setting the ACU TFTP Parameters .....................................................................4-60 Configuring ACU Profiles...................................................................................4-61 Performing Immediate Configuration Upload.....................................................4-63 Working with the ACU Report Table ..................................................................4-64 Closing the ACU Application..............................................................................4-71

Performing Backup and Restore ............................................................................4-73 System Requirements.......................................................................................4-73 Installing the Backup and Restore Tool .............................................................4-74 Configuring the Backup & Restore Parameters..................................................4-74 Running Backup ...............................................................................................4-77 Running Restore ..............................................................................................4-78

Transferring Files Using TFTP.................................................................................4-80 Configuring TFTP Server....................................................................................4-80 Opening TFTP File Transfer Application .............................................................4-81 Configuring TFTP File Transfer Application.........................................................4-83 Using the Operation Tab ..................................................................................4-93 Viewing TFTP File Transfer Reports .................................................................4-102 Saving the TFTP Database ..............................................................................4-105

Exiting the Application ........................................................................................4-105 Viewing the Net Inventory...................................................................................4-106

Opening the Application .................................................................................4-106 Using Filters for the Display............................................................................4-108 Editing an Entity.............................................................................................4-110 Expanding/Collapsing Sublevels.......................................................................4-110

Setting the Net Date and Time............................................................................4-111

Chapter 5. Performance Management 5.1 Browsing and Handling System Events........................................................................5-1

Terminology............................................................................................................5-1 Toolbar Icons..........................................................................................................5-4 Opening and Saving Filters......................................................................................5-4 Selecting Events......................................................................................................5-5 Refreshing the Events Display .................................................................................5-6 Acknowledging and Rejecting Events .......................................................................5-6 Entering Event Notes ..............................................................................................5-7 Viewing Event Details..............................................................................................5-9 Filtering Events .....................................................................................................5-10

5.2 Monitoring Services and Processes ...........................................................................5-21 Stopping/Starting a Service ...................................................................................5-22


iv RADview-EMS/TDM (Unix) Ver. 1.7

Viewing the Server Tracing Configuration ..............................................................5-23 Viewing the Java Name and Directory Service ........................................................5-27 Viewing the Informix Database Details ..................................................................5-27 Viewing the CORBA Name Service..........................................................................5-29 Viewing the CORBA Event Service ..........................................................................5-30 Viewing the EMS Log Service .................................................................................5-30 Viewing the EMS Element Network Repository.......................................................5-32 Viewing the EMS License Service ...........................................................................5-33 Viewing the EMS Trap Listener ..............................................................................5-34 Viewing the EMS Fault Management (Back End).....................................................5-35 Viewing the EMS Fault Management (Front End)....................................................5-36 Viewing the EMS Polling Service.............................................................................5-37 Viewing the EMS Configuration Management.........................................................5-38 Viewing the EMS Security Service ..........................................................................5-39

5.3 Additional Monitoring Options..................................................................................5-40 Viewing the RADview Package Contents ................................................................5-40 Monitoring SNMP Performance..............................................................................5-42

Filtering SNMP Requests and Traps...................................................................5-42 Reconnecting ...................................................................................................5-44

Tracing Log Events................................................................................................5-44

Chapter 6. Security Management 6.1 Administering Users in the HPOV Environment............................................................6-1 6.2 Administering Users in the EMS Environment ..............................................................6-3

Managing Security Profiles ......................................................................................6-4 Loading a Security Profile ...................................................................................6-6 Adding a Profile..................................................................................................6-7 Using a Base Profile ...........................................................................................6-9 Working with Permissions.................................................................................6-10 Adding a No-Base Profile..................................................................................6-16 Editing a Profile................................................................................................6-19 Removing a Profile ...........................................................................................6-20

Managing EMS Users .............................................................................................6-21 Adding a User ..................................................................................................6-21 Editing a User...................................................................................................6-22 Removing a User ..............................................................................................6-24

Administrating Login Names..................................................................................6-24 Active Login Table ............................................................................................6-24 Administrator Logout .......................................................................................6-25

Changing Security Policies .....................................................................................6-26

Chapter 7. Fault Management 7.1 Detecting Faults.........................................................................................................7-1 7.2 Viewing Logs..............................................................................................................7-2

Setting the Log Display ...........................................................................................7-3 Saving, Printing or Deleting Logs .............................................................................7-5

7.3 Testing the System ....................................................................................................7-6 Testing the HPOV Environment................................................................................7-6 Testing the User Environment .................................................................................7-9

7.4 Frequently Asked Questions.....................................................................................7-11 7.5 Technical Support ....................................................................................................7-12

User's Manual Table of Contents

RADview-EMS/TDM (Unix) Ver. 1.7 v

Appendix A. Migration Guide


vi RADview-EMS/TDM (Unix) Ver. 1.7

RADview-EMS/TDM (Unix) Ver. 1.7 System Features 1-1

Chapter 1

Introduction

1.1 Overview

RADview-EMS is a modular, client-server, scalable element management system (EMS), providing configuration, fault, performance and security management capabilities. Advanced management functions allow a wide span of control and command features, along with modular installation and flexible management of devices over heterogeneous networks.

RADview-EMS/TDM (Unix) is a Unix (HPOV)-based system, which is backwards compatible with other RADview-HPOV modules. The CORBA-based northbound interface of RADview-EMS enables easy integration into the customer’s umbrella NMS (Unix-based).

RADview-EMS can be used in a distributed network topology or in a single-station configuration. It can be installed on a Unix-based workstation with Solaris 10, and it supports distribution of servers into manageable areas.

The system is bundled with agent components, each dedicated for controlling a specific RAD product on the network. The RADview-EMS/TDM (Unix) system is dedicated for managing products installed in next-generation network (NGN) environments.

1.2 System Features

Compliance with FCAPS

Management functions provided by RADview-EMS are divided into four different categories, which comply with the FCAPS model (excluding the Accounting element):

• Fault – alarm and trap handling, test and acceptance, polling service

• Configuration (provisioning) –configuration of Network Elements (NE) via user-friendly and intuitive GUI zoom applications

• Performance – real-time statistics and system monitoring

• Security – controls NE access, enables NE functions and accesses logs.

Table 1-1 summarizes the RADview management functions according to the FCAPS model.

Chapter 1 Introduction User’s Manual

1-2 System Features RADview-EMS/TDM (Unix) Ver. 1.7

Table 1-1. RADview-EMS Management Functions

Fault Configuration Accounting Performance Security

Alarm handling Provisioning Not implemented Real-time statistics

presentation

Control NE access

Trap handling Not implemented Enable NE functions

Test and

acceptance

Not implemented Access logs

Polling service Not implemented

Graphical User Interface (GUI)

The system provides an open, detailed and user-friendly GUI, enabling easy integration of a wide range of management capabilities via the customer’s Unix-based NMS.

The EMS LaunchDesk toolbar provides easy access to all the EMS functions:

• Log in / log out

• Zoom applications

• Event Browser

• Admin Console – Security Service, Fault Service, NER Explorer

• Log Viewer

• EMS System Console for monitoring currently active services

• Trace Monitor, Version Browser, SNMP SPY.

The EMS Security Admin Console allows users to:

• View and manage the EMS Users’ security profiles in a powerful and user-friendly way

• Create and edit security profiles

• Manage user accounts.

Bundled Agents (Products Managed by this Package)

The RADview-EMS/TDM (Unix) package includes agents for the following products:

ASMi-52 FCD-155E Megaplex -2104

ASMi-52L IMX-4E1/4T1 Megaplex -2104H

DXC-10A LRS-52 Megaplex -2200F/B

DXC-30 Megaplex-104 Megaplex -4100

DXC-30E Megaplex -204 Optimux-1551

DXC-8R Megaplex -2100 Optimux-1553

FCD-155 Megaplex -2100H

User’s Manual Chapter 1 Introduction


Note: Each RAD product is assigned an Equivalent Node Weight (EMW) according to the product's complexity. This weight determines the license points required for operating the product via RADview-EMS. For more information, see Licensing in Chapter 4.

To learn about the management of a specific product, refer to its agent’s user manual, complemented with this system manual.

Backup and Restore

Command line backup allows faster recovery of a network management station in case of failure. The backup script can be integrated into any Unix-based scheduling mechanism in order to automate network topology and configuration backup.

Scalability of Distribution

RADview-EMS provides scalability by balancing the load among a number of servers (for economy in infrastructure) and distributing the management tasks (in a flexible map) between client and server, and master and slave servers as follows:

• Several clients working opposite a group of servers, managing together several groups/domains of network elements

• Several clients working opposite a single server, managing a single group of network elements

• Server and client on separate computers, managing a single group of network elements

• Server and client on a single computer, managing a group of network elements

This scalability enables:

• Load balancing among a number of servers (economy in infrastructure)

• Distributed polling (improved system performance)

Enhanced network management resilience (server redundancy).

There are two kinds of system services:

• Core Services – maintain EMS Services (Naming, Event Services, etc.)

• EMS Services – implement the FCAPS model.

• All services have a CORBA northbound interface.

Client/Server Distribution

The flexible distribution capability of RADview-EMS enables running management tasks in a wide variety of client/server configurations. The system can consist of any number of clients working with any number of servers. Typical system examples are shown in Figure 1-1, Figure 1-2, Figure 1-3, and Figure 1-4.

Note



The RADview workstation element port must be connected to a switch or hub and not directly to the equipment. The workstation network connection must be active all the time.

The following options are supported:

• Single station – client and server installed either in Standalone mode or over the same copy of SNMPc/same computer

• Distributed system – client and server are installed on separate computers. Both client and server are installed either in a Standalone application or over different copies of SNMPc/different computers.

Server/Client

IMXi-4E1/T1MP-104MP-204

IP

Figure 1-1. Single Server and Single Client Running on the Same Station Managing Single Group of Network Elements

ClientServer

IP


Figure 1-2. Single Client and Single Server Running on Different Stations Managing Single Group of Network Elements

Note



IP

Master Server

Client YClient X Client Z

IP


Figure 1-3. Single Server and Several Clients Managing Single Group of Network Elements



IP

Server 2

Slave

Server 1

Master

Server 3

Slave

Client ZClient X Client Y

IP IP IP

MP-204 IMXi-4E1/T1MP-104 MP-204 IMXi-4E1/T1MP-104 MP-204 IMXi-4E1/T1MP-104

Figure 1-4. Group of Servers and Several Clients Managing Single Groups/Domains of Network Elements



Territorial Distribution

EMS supports groupings of servers called Areas. Areas can also be grouped into Zones. Thus, the system can be distributed through territorial units.

CORBABus

CORBABus

USA Zone

New York Area

Server 2

Server 3

Server 1

Los Angeles Area

Server 2

Server 3

Server 1

Server 2

Server 1

Master Server

Tel Aviv Area

Israel Zone

Server 2

Server 3

Server 1

Jerusalem Area

Figure 1-5. Territorial Distribution on CORBA Bus

Master/Slave Server Functions

The RADview-EMS Master server provides basic system services, such as:

• CORBA Name Service

• Centralized information.

Both master and slave servers provide:

• FCAPS services

• Manageable administrative services:

Health

Configuration

Administration


1-8 System Requirements RADview-EMS/TDM (Unix) Ver. 1.7

Distribution.

Each Slave server runs its own set of services.

1.3 System Requirements

RADview-HPOV for TDM Applications version 5.9 can only be installed over the Solaris™ 10 Operating System, according to the following minimum hardware and software requirements.

Hardware Requirements

For networks consisting of up to 300 managed elements:

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

• 2GB RAM or higher

• Swap file should be twice RAM size

• Hard disk with at least 2 GB free disk space under /opt partition

• Hard disk with at least 600 MB for Informix directory

• 1152x900 display resolution or higher with depth 24.

• For each 3 additional simultaneous users via X-session add 1 GB RAM and 1 CPU. (When using EMS client on a different workstation there is no need to add RAM or CPU)

• For each additional simultaneous open zoom application add 75MB RAM (via X-session only)

• For larger networks, consisting of more than 300 managed elements, see Table 1-2.

Table 1-2. HW Scaling Guideline – Solaris

Managed Elements System No. of CPUs RAM

Up to 300 Sun Fire V215 or Sun Ultra 25 1 2 GB

300 to 1000 Sun Fire V215 2 2 GB

1000 to 2000 Sun Fire V490/V890 4 4 GB

2000 to 5000 Sun Fire V890 4 8 GB

Software Requirements

• Solaris 10, Nov 2006 or later

• During installation choose “Select to include Solaris 64 Bit Support”

• CDE 1.4 or higher

• HP Open View NNM 7.50 or later

Note


RADview-EMS/TDM (Unix) Ver. 1.7 System Requirements 1-9

• Up to 250 nodes HPOV NNM Starter Edition can be used, however, for more than 250 nodes contact HPOV local distributor.

All the requirements and Table 1 apply to a single-user scenario. If several users use RADview simultaneously, additional resources may be required to maintain satisfactory performance as indicated above.

No other Solaris versions are supported (for example, versions 2.5.1, 2.6, 2.7 are not supported).

A license server is integrated into RADview. The license server protects the SW by restricting the installation of the RADview package onto a single host/computer, and restricting the number of network elements that can be managed by the system (according to the installed RADview license details).

In case you install this RADview version as an upgrade to an existing system, you will be required to install a license. Refer to Chapter 4 for additional details.

Note

Note

Note


1-10 System Requirements RADview-EMS/TDM (Unix) Ver. 1.7

RADview-EMS/TDM (Unix) Ver. 1.7 Package Contents 2-1

Chapter 2

Installation and Setup RADview-EMS/TDM (Unix) is typically installed on a single station, which acts as a server from which all management functions are initiated.

• To perform an installation on a distributed system consisting of several servers, please consult with Technical Support, since your system may require a tailored procedure based on the current server architecture.

• 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 running the following commands:

ifconfig hme0:1 <new_IP> plumb

ifconfig hme0:1 <new_IP> up

hme0 is the Ethernet interface that can be seen by typing ifconfig –a.

2.1 Package Contents

The RADview-EMS/TDM (Unix) package includes the following items:

• RADview-EMS/TDM (Unix) Installation CD

• RADview-HPOV database (Informix) CD

• RADview-EMS PC Client Installation CD

• Installation guide

• Technical Documentation CD.

Notes

Chapter 2 Installation and Setup User’s Manual

2-2 Installation RADview-EMS/TDM (Unix) Ver. 1.7

2.2 Installation

Installation Sequence

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

The RADview-EMS/TDM (Unix) package must be installed in the following sequence:

1. Install the Informix Database

2. Install RADview-HPOV/TDM (optional, see note)

Install RADview-HPOV/TDM before installing RADview-EMS/TDM only if you need to manage devices that are managed by the RADview-HPOV/TDM package. For installation instructions, see the RADview-HPOV/TDM User Manual.

3. Install RADview-EMS/TDM

4. Install Additional PC Clients (Optional).

All installations must be performed on one computer station, and in the order specified above.

Installing the Informix Database

RADview-EMS/TDM (Unix) uses the Informix database, which must be installed prior to installing the RADview-EMS package.

Before initiating the Informix installation, close all running applications.

To perform the Informix database 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.

Note

Note

Note

Note

User’s Manual Chapter 2 Installation and Setup

RADview-EMS/TDM (Unix) Ver. 1.7 Installation 2-3

Figure 2-1. Informix Installation, Starting

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

9. Type: csh

10. Type: cd /cdrom/cdrom0/informix

11. Type: ./informix.install

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

Figure 2-2. Informix Installation, Completing



Installing the RADview-EMS Package

Once Informix database is installed, install the RADview-EMS package.

Starting with the Initial Components

To install the RADview-EMS components:

1. Log in as root.

2. Type:

csh cd /tmp source /<INFORMIXDIR>/.mng164_inf.csh.

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

3. Insert the RADview-EMS/TDM (Unix) Installation CD into the CD-ROM drive.

4. Type: cd /cdrom/cdrom0/radview.

5. Verify that Informix is running by typing:

onstat –

If Informix is online the following message should appear:

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

6. Type: ./install_gui.rad.

The RADview Installation warning appears.

Figure 2-3. RADview Installation Dialog Box

7. Click <OK>.

The RADview Installation Product List appears:

Note



Figure 2-4. RADview Installation Product List

8. Select the product(s) to be installed or select all and click <Install>.

A confirmation dialog box is displayed.

Figure 2-5. RADview Installation Confirmation

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

The installation continues to the EMS/TDM Setup Wizard stage. Skip to Continuing with RADview-EMS/TDM.

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

A dialog box requests you to type the correct Informix Installation path (see Figure 2-6).



Figure 2-6. Informix Path Dialog Box

11. In the Installation Path dialog box, type the Informix installation path and click <OK>.

If the path is correct, the installation continues to the EMS/TDM Setup Wizard stage; skip to Continuing with RADview-EMS/TDM.

If the path 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.

Figure 2-7. Incorrect Informix Installation Directory Dialog Box

If this is an upgrade of an existing installation, a confirmation message box appears and requires your confirmation to overwrite the contents of the existing database directory. Click <Overwrite> to overwrite and complete the installation. To cancel the installation without overwriting, click <Quit>.

Figure 2-8. RADview Installation – Upgrade Dialog Box

Note



Continuing with RADview-EMS/TDM

Once the initial EMS components are installed, the RADview-EMS/TDM Setup Wizard is automatically displayed.

Figure 2-9. EMS Setup – Welcome Dialog Box

To continue with the RADview-EMS/TDM installation:

1. In the Welcome dialog box, click <Next>.

The Select Installation Type dialog box is displayed.



Figure 2-10. EMS Setup – Select Installation Type

2. Select Server and Client.

• Server Only is an option for the distributed system installation. For more information, consult with Technical Support.

• Client Only is an option to be used only when setting up a PC-based client (not valid for Unix installations). For more information, see Installing Additional PC Clients (Optional) on page 2-20.

3. Click <Next>.

The Select Installation Method dialog box is displayed:

Note



Figure 2-11. EMS Setup – Select Installation Method

4. Choose the installation type:

Typical – for installation with the default settings.

Advanced – includes the International Settings (Figure 2-13) and the Database Settings (Figure 2-16) dialog boxes.

If you choose Typical and this is the first time you are installing RADview-EMS, the Database Settings dialog box will display. Otherwise, if you are performing an upgrade and you choose Typical, the Database Settings dialog box will not display.

5. Click <Next>.

The General Information dialog box is displayed.

Note



Figure 2-12. General Information Dialog Box

6. Select Master Server, and enter your Zone Name and Area Name (e.g., Zone = England, Area = London). These names determine the hierarchy levels in future topologies of multiple servers. Write down the names you selected and save them for later use. Check that you are using the correct station host name, and that it is listed as Station Name.

7. Click <Next>.

The International Settings Dialog Box dialog box is displayed.



Figure 2-13. International Settings Dialog Box (in Advanced Installation Only)

8. Select the Language, Country, and Time Zone for your station.

The default values are taken from the operating system.

• RADview applications use only English language text. It is recommended to use English as the default language setting for RADview. You can select a different Language, which allows you to input text in languages other than English. RADview has been tested only with English as its default language and RAD cannot guarantee its proper operation in other languages.

• Select the Country according to the Language you selected.

• Select the appropriate Time Zone so that the time that is displayed in Current Time Test matches the correct time in your country and area.

9. Click <Next>.

The Select Target Database Server dialog box is displayed.

Note



Figure 2-14. EMS Setup – Select Target Database Server

10. Select one of the following target database server:

Oracle Database Server

IBM Informix Server.

Make sure that the database service (Oracle or Informix) is running.

11. Click <Next>.

Connecting to Database screen is displayed.

Note



Figure 2-15. Connecting to the Database

After connection to the database is established, the Database Settings dialog box is displayed (Figure 2-16).



Figure 2-16. Database Settings Dialog Box

12. In the Database Settings dialog box, change DbSpace Name to rootdbs, User to root and Password to <root password>. For all the other parameters, leave the default values.

• If this is the first installation of the EMS package on your workstation and you want to use the Informix user instead of the Root user, perform the following steps:

1. Open a Terminal window.

2. Log in as su (superuser).

3. Type passwd informix and set the password that you want to use as an Informix user. Retype the password to confirm.

4. Use this user and password in the Database Settings dialog box.

• If a previous EMS server version was installed on your system with User = Informix and Password = Informix, you must use these settings again.

13. For first-time installation on the station (skip this step if not relevant):

Select New Database = Yes.

Verify that the values displayed are correct and click <Next>.

If a new Database is created, a warning message is displayed saying that the existing Database Information will be lost (Figure 2-17).

Note



Figure 2-17. Warning Message

14. Click <OK>.

The Install Summary dialog box is displayed.

Figure 2-18. Install Summary Dialog Box

15. Click <Next>.

The Installation Progression dialog box is displayed:



Figure 2-19. Installation in Progress

When it completes, the Installation Summary dialog box is displayed:



Figure 2-20. Installation Completed

16. Click <Finish>.

17. Type: init 6 to reboot the system.

The Installation Done Window appears:



Figure 2-21. Installation Done Window

RADview-EMS is fully installed and ready for use.



Installing Additional PC Clients (Optional)

In needed, additional PC-based clients can be installed on separate non-Unix stations. Additional client stations enable scalability of distribution, as explained in Chapter 1.

To install the Client Station on the PC station:

1. Insert the RADview-EMS/TDM (PC) Installation CD into the CD-ROM drive.

The RADview-EMS/TDM Setup window is displayed.

Figure 2-22. RADview-EMS/TDM Setup Window

2. Install the following components:

RADview Shell – only if this is a new installation

RADview-EMS/TDM (Client Only).

Installing RADview Shell on the PC Client

If this is an upgrade installation, do not install the RADview shell.

Note



To install the RADview Shell:

1. On the RADview-EMS/TDM Setup Dialog Box (Figure 2-22), click RADview Shell.

The Welcome dialog box is displayed:

Figure 2-23. RADview Shell Setup – Welcome Dialog Box

2. Click <Next>.

The Choose Destination Location dialog box is displayed.



Figure 2-24. RADview Shell Setup – Choose Destination Location

3. Use the default folder or click <Browse> to select the folder where RADview Shell will be installed. All further components of RADview-EMS installation will be installed in this folder. Click <Next>.

The Select Program Folder dialog box is displayed (Figure 2-25).



Figure 2-25. RADview Shell Setup – Select Program Folder

4. Click <Next>.

The RADview Platform Selection dialog box is displayed (Figure 2-26).

Figure 2-26. RADview Shell Setup – Platform Selection

5. Select Standalone Application, and click <Next>.



The Start Copying Files dialog box is displayed.

Figure 2-27. RADview Shell – Start Copying Files

6. Click <Next>.

The Setup Complete dialog box is displayed.



Figure 2-28. RADview Shell Setup Completed

7. Click <Finish>.

Installing RADview-EMS/TDM on the PC Client

If a RADview-EMS package is already installed on your workstation, delete the 'vpd.properties' file from the root directory before performing the RADview-EMS/TDM installation.

To install the RADview-EMS/TDM on the PC client:

1. On the RADview-EMS/TDM Setup Dialog Box (Figure 2-22), click on RADview-EMS/TDM.

The Welcome dialog box is displayed.

Note



Figure 2-29. EMS Setup – Welcome Dialog Box

2. Click <Next>.

The Select Installation Type dialog box is displayed:



Figure 2-30. EMS Setup – Select Installation Type – Client Only

3. Select the Client Only installation type, and click <Next>.

The following SNMPc warning dialog box opens:



Figure 2-31. EMS Setup –SNMPc Configuration Warning

4. Select whether to keep or overwrite the current MIBs and event policies, and click <Next>.

The Select Products dialog box is displayed.



Figure 2-32. EMS Setup – Select Products

5. Select the product(s) you would like to install, and click <Next>.

The Select Installation Method dialog box is displayed.



Figure 2-33. EMS Setup – Select Installation Method

6. Select the setup type:

Typical – for installation with the default settings

Advanced – includes the International Settings dialog box (Figure 2-35).

7. Click <Next>.

The General Information dialog box is displayed (Figure 2-34).



Figure 2-34. EMS Setup – General Information Dialog Box

8. Enter the Zone Name and Area Name for the Client Station. Enter the Host Name of the Client Station for Station Name. Enter the IP address of the Master Server Unix Station for Master Server Address. Click <Next>.

For a single-station installation, any string of characters without a space can be used for Zone/Area names.

The International Settings dialog box is displayed (Figure 2-35) only if this is an Advanced installation (see step 6). If this is a Typical installation, the Install Summary dialog box is displayed (Figure 2-36). Continue with step 10.

Note



Figure 2-35. International Settings Dialog Box

9. Select the Language, Country, and Time Zone for your station, and click <Next>. The default values are taken from the operating system.

• RADview applications use only English language text. It is recommended to use English as the default language setting for RADview. You can select a different Language, which allows you to input text in languages other than English. RADview has been tested only with English as its default language and we cannot guarantee its proper operation in other languages.

• Select the Country according to the Language you selected.

• Select the appropriate Time Zone so that the time that is displayed in Current Time Test matches the correct time in your country and area.

The Install Summary dialog box is displayed.

Note



Figure 2-36. EMS Setup – Installation Summary

10. Click <Next>.

The Installation Progression dialog box is displayed.



Figure 2-37. Installation in Progress

When it completes, the Installation Summary dialog box is displayed.



Figure 2-38. EMS Installation Complete

11. Click <Finish>.

12. After the RADview-EMS/TDM installation has completed, the following message box is displayed:

Figure 2-39. Autorun Message Box

13. Click <No> since you are using the License Server that has already been installed with the EMS Server.

14. Return to the RADview-EMS/TDM Setup dialog box (Figure 2-22), click <Exit>, and then click <Restart> in the Setup Complete dialog box.


2-36 Post-Installation Steps RADview-EMS/TDM (Unix) Ver. 1.7

Figure 2-40. Setup Complete Dialog Box

RADview-EMS/TDM is fully installed and ready for use on the PC client.

Installation Notes

Changing the RADview-HPOV Installation Directory

By default, the RADview-HPOV installation script tries to install into the /opt partition. If your /opt partition lacks sufficient disk space, the installation script stops and indicates the minimum disk space needed to install the selected components.

In such a case, you can either free the required disk space or create a symbolic link to another location on the disk, which has sufficient disk space.

For example, if you would like 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

2.3 Post-Installation Steps

Before opening RADview-EMS/TDM (Unix), you must create a user, and then set the user environment to include the variables needed for RADview-EMS/TDM (Unix), HPOV, and Informix. It is recommended that you select C as the user's SHELL. For more information on user management, refer to Chapter 6.

Creating a User

To create a user:

1. Log in as root user.

2. Type: smc

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.


RADview-EMS/TDM (Unix) Ver. 1.7 Post-Installation Steps 2-37

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-41. 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.


2-38 Post-Installation Steps RADview-EMS/TDM (Unix) Ver. 1.7

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 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-EMS/TDM (Unix) Ver. 1.7 Frequently Asked Questions on Installation 2-39

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-42. RADview User Environment Tool – New User

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

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

2.4 Frequently Asked Questions on Installation

Q I forgot my RADview user's password. How can I recover it? Also, is there a default user name and password that I can use?

A The default user name and password for accessing RADview-EMS (via the LaunchDesk) are "root" for the user name and "root" for the password. However, if the default password of the root user has changed since the initial installation, then it is necessary to reset the password for your specific user name.

To reset the password:

1. Stop the EMS server.

2. In the /opt/MNG/MNGVIEWHP/ems/conf/sec/ directory, backup the file svcsec.xml (copy svcsec.xml to svcsec.old.xml).

3. Edit the file svcsec.xml as follows: find the <database> section in the syntax and add/change the following line: <admin><administrator>root</administrator></admin>.

4. Restart EMS server.

5. Log in to the server and add a new administrator user via the Security Admin console.


2-40 Frequently Asked Questions on Installation RADview-EMS/TDM (Unix) Ver. 1.7

6. Stop the EMS server again.

7. Access the svcsec.xml file again and remove the previously added line: <admin><administrator>root</administrator></admin>.

The password is now reset.

Q How can I change the Unix station's password without conflicting with the EMS server password?

A When the EMS server is installed and running, changing the Unix station's password may conflict with the EMS server application.

To change the Unix station's password without conflicting with the EMS server installation

1. Copy the ems.sql file to the Informix database directory.

2. Log in as a RADview user (not as super user).

3. Start the EMS Server.

4. Verify that Informix is online by typing /<informixdir>/bin/onstat where <informixdir> is the Informix home directory.

The following message (or a similar one) is displayed:

Informix Dynamic Server Version 7.31.UD1 -- On-Line -- Up 4 days 22:45:47 --

5. After verifying that Informix is online, type: $INFORMIXDIR/bin/dbaccess -e - ems.sql

Make sure that no errors are reported.

The following syntax is displayed:

******************************************************* # $INFORMIXDIR/bin/dbaccess -e - ems.sql -- This file should be executed using -- $INFORMIXDIR/bin/dbaccess -e - ems.sql DATABASE ems; Database selected. GRANT CONNECT TO PUBLIC; Permission granted. GRANT RESOURCE TO PUBLIC; Permission granted. GRANT ALL ON ems.fm_event_v TO PUBLIC AS ems Permission granted. Database closed. **********************************************************

6. Open the EMS LaunchDesk and click the RADview-EMS system console button (green button).


RADview-EMS/TDM (Unix) Ver. 1.7 Uninstalling the RADview Package 2-41

7. Select the Datasource repository service (under process1).

8. Change the username to mng164 and the password to mng164.

9. Click set for setting the entered username and password.

10. Close all GUI dialog boxes and consoles.

11. Stop the EMS server.

12. Restart the EMS server.

From this point onwards, the server operates with the username mng164 and the password mng164.

2.5 Uninstalling the RADview Package

Uninstalling RADview

To uninstall the RADview-EMS system:

1. Log in as superuser: su.

2. Type:/opt/MNG/MNGVIEWHP/ems/uninstall/uninstall.

3. In the dialog box that is displayed, select the products that you want to uninstall.

4. Delete the 'EMS' directory.

5. In the root (' / ') directory, search for the 'vpd.properties' file and then delete this file.

To uninstall the RADview shell:

1. Access the user’s home directory.

2. Type: csh.

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

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

5. Type: cd /opt/

6. Type: rm -r MNG

7. Type: cd/etc/opt/OV/share/registration/C

8. Type: rm mng164* <Enter>

9. Type: init 6.

Uninstalling the Database

To uninstall the Informix database:

1. Log in as su

2. Type: csh


2-42 Uninstalling the RADview Package RADview-EMS/TDM (Unix) Ver. 1.7

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-43).

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-43. Uninstalling Informix

RADview-EMS/TDM (Unix) Ver. 1.7 Running the HPOV Platform 3-1

Chapter 3

Operation This chapter describe 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 by the HPOV graphic user interface (GUI). These options include:

Using the RADview-HPOV WAN Maps

Working in the HPOV Window

Creating an Agent for a RAD Device

Monitoring Agents

Using the Java Zoom Applications.

• Running the EMS Application – starting to work with the RADview-EMS environment.

3.1 Running the HPOV Platform

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

To start the HPOV environment:

• In the terminal window, type ovw &. The HPOV Root window appears:

The HPOV root window appears

Chapter 3 Operation User’s Manual

3-2 Running the HPOV Platform RADview-EMS/TDM (Unix) Ver. 1.7

Figure 3-1. HPOV Root Window

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 (Figure 3-1), select Misc > RADview/OV > Login.

The Login dialog box appears.

Figure 3-2. Login Dialog Box

2. Type your User Name and Password.

If this is the first time the system is being used or users have not yet been programmed into the system, enter the system under the User Name "root" with the User Password "root".

Once user names and passwords have been created, it is advisable to change the root password. Refer to Chapter 6 for a description of how to change user passwords.

3. Click <OK>.

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

Note

User’s Manual Chapter 3 Operation

RADview-EMS/TDM (Unix) Ver. 1.7 Running the HPOV Platform 3-3

Figure 3-3. Access Denied Dialog Box

To change a user password:

1. From the HPOV Root window, select Misc > RADview/OV > Login.

The Login dialog box appears.

2. Click <Change Password>.

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>.

Installing Licenses

You must install a license before you can start to work with the RADview-EMS/TDM (Unix) maps.

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.


3-4 Using the HPOV GUI RADview-EMS/TDM (Unix) Ver. 1.7

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.

To install a license:

7. Select Misc > RADview OV > License Service Manager.

8. Select File > Add License.

A browsing dialog box appears.

9. Select the desired license file, and click <Save>.

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

3.2 Using the HPOV GUI This section briefly explains the HP OpenView (HPOV) features which allow you to create and monitor nets and agents. •

• When a node appears in more than one HPOV map, and you delete it from one map, it is also deleted from the NER Explorer. There is no way to zoom to the node from the other HPOV maps. Workaround –- add the node again, in any map, so that it reappears in the NER Explorer; then it can be zoomed again.

• While the HPOV map is open and you want to open a new HPOV map (different from the current one), close the RADview EMS LaunchDesk manually. Use this procedure so that you can manage the RADview EMS applications correctly. RADview EMS LaunchDesk opens automatically after a few seconds.

Using the RADview-HPOV WAN Maps

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

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

RADview-HPOV 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 the first time the system is started up

• Double-clicking on the WAN hierarchy opens 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 the units.

Note

Note

Note




RADview-EMS/TDM (Unix) Ver. 1.7 Using the HPOV GUI 3-5

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 dark gray box surrounds the selected agent. 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 reveal 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 the following entries in its menu bar: Map, Edit, View, Performance, Fault, Tools, Options, Window, Misc, and Help. In addition to these menus, each object on the map has an object-specific menu, called a symbol menu, which can be accessed by clicking the right mouse button.

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. Six possible 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 system. For more detailed information about HPOV operation, refer to the HPOV Windows User's Guide.

WAN Map Terminology

Understanding the following terms is important for working with the WAN maps.

• WAN Root Submap icon – icon on 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 on 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-OV 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 main 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.

Setting Polling Interval

RADview-HPOV periodically polls network objects, and relay the information by updating the map and displaying messages dynamically.

To change the polling interval:

1. Make sure that no map symbol is selected. From the Misc menu, select RADview-HPOV > General > Status Polling...

The Status Polling Interval dialog box is displayed.

Caution



2. Select the desired polling interval in Days, Hours and Minutes, and click Set. The default polling interval is five minutes.

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 certain RAD device if no RADview is installed in the system.

To install RAD MIB on HPOV:

1. Log in as a super user.

2. Insert the RADview-EMS/TDM (Unix) application CD into the CD drive.

3. Type: cd /cdrom/cdrom0

4. 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 is displayed.

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

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

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

9. Locate the /cdrom/cdrom0/ filtered 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 relevant devices connected by communication links that can be configured as a group. A single stand-alone unit is a special type of net. Using RADview-HPOV, you can define nets, plan WAN agent connections, and configure nets as desired.

At the net level, the following information is displayed:

• The net topology

• The communication status of each WAN agent with the management station

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



• The status of operation of the links connecting WAN agents.

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

• The operational status of the agent

• The operational status of each card, including its ports

• The 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 unique Internet address and host name for each node. The Internet name must be a valid IP address written in dot notation, in which no single value exceeds 255 (for example, 125.4.254.11). Host names can be written with normal characters (for example, "bridge1"). Refer to the TCP/IP protocol software documentation for details of how to assign Internet addresses and to 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 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. Select Add Object from the Edit menu.

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

To define the object for the RAD device:

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

2. Select Add Object from the Edit menu.

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

Figure 3-6. Connector Palette for the Device Agent

3. Click the Connector icon (from the choices in Symbol Class) to display the Class Net Device objects.



4. Click the middle 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 Dialog Box

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 of the RADview-HPOV program.

Setting Selection Name and Selection Name Format

HP OpenView identifies objects by their selection name. 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 of the names that have been set for 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 text is provided, HP OpenView uses the name entered in the Label field as the selection name of the object.

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

Selection Name Format

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 (for example, "New York")

• Enter the host name and IP address, by typing them in. Click <OK>.

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 screen.

To access the SNMP Configuration screen:

Perform the following three steps only if you are working with HPOV version 7.51 before continuing to the numbered steps below:

• Open a Terminal Window.

• To grant root permissions, type: su.

• To launch HPOV SNMP Configuration from cmd line as root, run the following command: "/opt/OV/bin/xnmsnmpconf"

1. Select SNMP Configuration from the Options menu.

Note



Figure 3-8. SNMP Configuration Dialog Box

The SNMP Configuration screen consists of two main sections:

• The top portion of the screen contains three selection lists with the current SNMP configuration parameters for the selected node or group of nodes. One list contains the configuration for individual nodes, one for a group of nodes (according to a wildcard IP address) and one contains the default SNMP settings

• The bottom portion of the screen contains data entry fields for modifying existing parameters or entering a new configuration.

The following SNMP parameters can be modified using this screen:

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

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

Time-out The amount of time that RADview-HPOV waits for a response before attempting to retry an SNMP request to the agent.



Retry Count The maximum number of retries that RADview-HPOV attempts before concluding that an agent is unreachable.

Status Polling The frequency that the application queries the agent status. This field is not relevant; polling is done by the configuration made in Misc. > RADview/OV > Status Polling screen.

To add a new configuration:

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> or <OK> to save the changes.

To modify an existing configuration:

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.

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

Deleting an Agent

To delete a WAN agent:

1. Select the agent that you want to delete.

2. Select either Delete from this Submap or Delete from all Submaps from the Edit menu.

Figure 3-9. Confirm Delete

3. 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 is displayed.

3. Modify the Label as desired.

4. Click <OK>.

You are prompted for confirmation of the modifications before saving. The Symbol Description 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 polls the agents itself, maintaining its own database for RAD agents in the system. Newly created agents are automatically added to the RAD database. The agents are monitored for the presence of active alarms and tests.

Displaying Alarms Categories

In the RADview-HPOV 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 Dialog Box

To display the alarms list:

• In the Alarm Categories window, select the required type of alarm list.

Figure 3-11 shows a sample of the All Alarms Browser. Each trap appears on a separate line.



Figure 3-11. All Alarms Browser

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 the Delete option with caution. If the selected node is a hierarchy node, all information pertaining to its children is erased from the database.

Using the Java Zoom Applications

Multiple Java (Java is a trademark of Sun Microsystems) zoom applications can be launched on the same node (of the same agent) on Java-based products. Java does not recognize applications that were previously opened, and it does not direct to a session that is already open.

For more information about a device-specific zoom application, refer to the specific RADview agent (device/module) user's manual.

Note


RADview-EMS/TDM (Unix) Ver. 1.7 Running the EMS Application 3-17

3.3 Running the EMS Application

The RADview-EMS application allows you to control, manage and monitor various devices over the network, via a dedicated user interface.

•

• After installing RADview-EMS-TDM/Unix, it is necessary to restart the workstation and wait at least 2–3 minutes before starting to work with the EMS system. This is required for the Informix database to initialize its tables and for the EMS Server Service to start, before first using the system.

• The Server starts automatically, so there is no need to run it manually.

• You can use the log file in the /opt/MNG/MNGVIEWHP/ems/log directory to view Server messages (Errors & Info).

• If this is an upgraded EMS installation, you must Import (via the Launch Desk) of all the nodes already in the HPOV map, to ensure error-free management.

To run the element management system (EMS):

1. Log in as a superuser.

2. Type /etc/rc3.d/S98radViewEmsServer –start

The EMS features become available.

3. In the terminal window, type ovw&

The HPOV Map, EMS LaunchDesk and EMS Login appear.

Note


3-18 Running the EMS Application RADview-EMS/TDM (Unix) Ver. 1.7

Figure 3-12. HPOV Map, EMS LaunchDesk and EMS Login Dialogs

4. In the EMS Login, enter the valid user name (root) and password (root).

5. Activate one of the RV-EMS applications (Admin_Console, Event Browser, LaunchDesk, Application Manager or Version Browser) via the Application Manager (right-click on desktop> Applications > Application Manager > Network Manager > RADview-EMS).



Figure 3-13. Application Manager Window

Starting/Stopping EMS Server from the Command Line

To start or stop EMS Server from the command line:

1. Open a terminal window and then log in as a superuser.

2. To start the server, type: /etc/rc3.d/S98RvEmsServer start

Or –

To stop the server, type /etc/rc3.d/S98RvEmsServer stop.

Logging Into RADview-EMS

To login from LaunchDesk:

1. From the Application Manager window (Figure 3-13), select LaunchDesk.

The RADview-EMS LaunchDesk toolbar appears.

Figure 3-14. RADview EMS LaunchDesk Toolbar

2. Click on the EMS LaunchDesk toolbar.

The EMS Login dialog box appears.

Figure 3-15. EMS Login Dialog Box

Note


3-20 Running the EMS Application RADview-EMS/TDM (Unix) Ver. 1.7

•

• You can change your password or another user’s password. Refer to Changing the EMS Password for instructions.

• Multi-user Unix station users can be logged in simultaneously.

• The same user can have many open sessions (logged in from different sessions/terminals).

• For the very first login (before users are defined) use the default user: Username=root, Password=root.

3. Enter Username and Password and click <OK>.

The login icon on the EMS LaunchDesk toolbar is now disabled.

Figure 3-16. EMS LaunchDesk After Login

4. Select any function on the LaunchDesk toolbar.

•

If you select a function on the LaunchDesk toolbar without being logged in, the EMS Login dialog box is displayed and you are required to log in.

Changing the EMS Password

You can change your user password or another user’s password at any time. For security reasons, it is recommended to change the password periodically.

To change a password:

1. In the EMS Login dialog box click <Change Password>.

The Replace Password dialog box appears.

Figure 3-17. Replace Password Dialog Box

2. Enter the Username and the Old Password (current password) of the user whose password you are changing.

3. Enter the user’s new password in the New Password and Verify fields.

4. Click <OK>.

Note



The new password takes effect immediately.

•

The password must be between 4 and 8 characters. Only letters and numbers are valid characters. At least 2 characters must be letters and at least 2 characters must be numbers.

Using the LaunchDesk Toolbar

The LaunchDesk toolbar provides access to all the EMS functions, which are:

• Login

• Logout

• Settings

• Network Element Browser

• Import Nodes

• Stop Import

• System Console

• Admin Console

• Log Viewer

• Event Browser

• Tools

• Help.

To open LaunchDesk:

• From the Solaris desktop, right click and select Applications> Application Manager> Network Manager> RADview EMS> LaunchDesk.

The LaunchDesk toolbar is displayed.

Figure 3-18. Launch Desk Toolbar

The EMS Server, which manages the EMS system, is started when the station is up. After rebooting the station, wait three to four minutes before starting to work with the EMS application.

In addtion, if this is an EMS installation upgrade, you have to perform Import (via the LaunchDesk) to all the nodes already in the SNMPc map to ensure problem-free management.

Note

Note


3-22 Logging Out of RADview-EMS RADview-EMS/TDM (Unix) Ver. 1.7

Using the Zoom Applications

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

For more information about a device-specific zoom application, refer to Browsing the Network Elements in Chapter 4, and to the specific RADview agent (device/module) user's manual (bundled with this system user's manual).

3.4 Logging Out of RADview-EMS

In addition to manual log out, the server automatically logs you out after a specified time if for some reason the connection with the server is lost, or if all applications are closed without proper logout (a proper message is displayed on the LaunchDesk status bar).

To manually log out:

• On the LaunchDesk toolbar, click . Perform logout only through LaunchDesk.

The LaunchDesk displays the Logged Out status.

Figure 3-19. Launch Desk Toolbar after Logout


RADview-EMS/TDM (Unix) Ver. 1.7 Ending the HPOV Session 3-23

3.5 Ending the HPOV Session

Once you have logged out of RADview-EMS, you can end the HPOV session to log out completely.

To end the HPOV session:

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

The Logout dialog box appears.

Figure 3-20. HPOV Logout Dialog Box

2. Click <OK>.


3-24 Ending the HPOV Session RADview-EMS/TDM (Unix) Ver. 1.7

RADview-EMS/TDM (Unix) Ver. 1.7 Setting the HPOV System Parameters 4-1

Chapter 4

Configuration Management This chapter describes in detail the following configuration activities:

• Setting the HPOV System Parameters

• Setting the EMS System Parameters

• Additional Monitoring Options

• Additional Tasks and Options – which include:

Using the Backup and Restore Tool

Transferring Files via TFTP

Displaying the Net Inventory

Licensing

Setting the Date and Time.

4.1 Setting the HPOV System Parameters

The system parameters of the HPOV platform are configured by:

• Propagating the HPOV Map Status Color

• Disabling Auto-Discovery

• Disabling Automatic Deletion

• Setting the Polling Interval, Timeouts and Retries.

Propagating the HPOV Map Status Color

By default, the network node manager (NNM) does not propagate alarms. This means that a mismatch may occur between the hierarchy and the underling nodes.

To set HPOV Map status color propagation:

1. From the HPOV Map menu, click Properties.

2. In Compound Status, check the Propagate Most Critical checkbox.

Chapter 4 Configuration Management User’s Manual

4-2 Setting the HPOV System Parameters RADview-EMS/TDM (Unix) Ver. 1.7

Disabling Auto-Discovery

It is recommended to disable the Auto-discovery To avoid detection of irrelevant network elements, and to prevent overloading of the management station.

To disable Auto-discovery :

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

It is recommended to disable the option of automatically deleting nodes from the HPOV map. Otherwise there can be problems managing the devices and the global NMS applications (for example, TFTP file transfer).

To disable the delete nodes option:

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

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

Setting the Polling Interval, Timeouts and Retries

RADview-HPOV automatically polls network nodes periodically.

To set the polling interval time:

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

2. Select 5 min, and click <Set>.

Each SNMP request (for example an SNMP poll) has a time-out. A retry can be defined to compensate for the connectionless nature of the SNMP protocol.

To define the polling timeouts and retries:

Only if you are installing HPOV 7.51, perform steps 1 through 3. Otherwise, skip to step 4.

1. Open a Terminal window.

2. Grant root permissions by typing su in the command line.

3. To launch HPOV SNMP Configuration from the command line as root, run the command: /opt/OV/bin/xnmsnmpcconf

4. From the Options menu, select SNMP configuration.

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

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

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

Note

User’s Manual Chapter 4 Configuration Management

RADview-EMS/TDM (Unix) Ver. 1.7 Setting the EMS System Parameters 4-3

8. In the Timeout field, type 10.0.

9. In the Retry count field, type 2.

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

Figure 4-1. SNMP Configuration Window

4.2 Setting the EMS System Parameters

The EMS system configuration includes various activities, each affecting different aspects of the system. This includes:

• Configuring Synchronization

• Browsing the System Elements

• Configuring the EMS Consoles

• Configuring the NER Elements.


4-4 Setting the EMS System Parameters RADview-EMS/TDM (Unix) Ver. 1.7

Configuring Synchronization

Synchronization occurs between NER Explorer and HPOV maps (if they exist; see Figure 4-2), where nodes represent RAD live agents.

To use Synchronization operations, the station containing the EMS should also run RADview in HPOV.

Figure 4-2. HPOV Map

To configure synchronization:

• Click the Synchronization Settings icon on the LaunchDesk toolbar.

The Settings dialog box is displayed (see Figure 4-3). The General tab defines the system’s appearance and the Master Server Address. The Network Element Repository tab sets parameters for interaction with the

Note



NER tree. The Regional and Language tab defines the system’s time, country, and language.

Figure 4-3. Settings Dialog Box – General Tab

The Always on top option is not functional in the Unix environment. This check box is functional only in the PC-based (Windows) version of RADview-EMS.

Figure 4-4. Settings Dialog Box – Look and Feel Selection

Note



Figure 4-5. Settings Dialog Box – Network Element Repository Tab

Table 4-1. Settings Dialog Box – Network Element Repository Tab Parameters

Parameter Possible Values / Remarks

Context The directory of NER tree nodes related to LaunchDesk

actions, such as Zoom and Synchronization (see

Figure 4-44)

Map Context The directory of NER tree nodes where changes in the

HPOV map are updated

Allow Duplicated Net

Addresses

Check box selected – a node with the same IP address

(but with different name) as a node already stored in

the NER can be imported into the repository

Check box cleared – a node with IP address that is

already stored in NER cannot be imported into the

repository



Figure 4-6. Settings Dialog Box – Regional and Language Tab

Table 4-2. Settings Dialog Box – Regional and Language Tab Parameters


Language The system’s language

Country The system’s host country

Time Zone The system’s time zone

Current Time Test The date and time of the test

Browsing the System Elements

The Network Element Browser shows the levels (sub-maps) and nodes (network elements) in the EMS network.

To open the Network Element Browser:

• On the LaunchDesk toolbar, click the Network Element Browser Icon .

The Network Element Browser is displayed, displaying the levels and nodes in the network.



Figure 4-7. Network Element Browser

Each node has an icon indicating its severity. For each level, the color of the icon indicates the status of the nodes under that level.

Table 4-3. Network Element Browser Status Icons

Icon Color Status

Green Normal

Blue Warning

Yellow Minor

Orange Major

Red Critical

Gray Unknown (e.g., a non-EMS node or

non-existing IP address)



Performing Node Level Operations

Figure 4-8. Network Element Browser – Level Menu

The Network Element Browser – Level menu offers the following operations:

• Properties – Configures the properties of the current level and, if desired, all subordinate levels and nodes

• Add Node – Adds a node under the current level

• Add Level– Adds a level under the current level

• Remove – Removes the current level and all subordinate levels (this option is not available at the highest level)

• Refresh – Updates the level with the latest configuration

To configure the level properties on the Network Element Browser:

1. Right-click the selected level on the Network Element Browser.

A pop-up menu is displayed (see Figure 4-8).

2. Click Properties.

The Properties dialog box is displayed (see Figure 4-9). The General tab defines the level’s name. The SNMP tab sets the SNMP parameters of the level and, if desired, all subordinate levels and nodes.

Figure 4-9. Properties – General Tab



Figure 4-10. Properties – SNMP Tab

Table 4-4. Properties – SNMP Tab Parameters


Read Community SNMP Read request community

Write Community SNMP Write request community

Timeout (msec) The SNMP timeout for the level, in milliseconds

Retries The SNMP number of retries for the level

Polling Interval (sec) The SNMP polling interval for the level, in seconds

Apply changes to subnodes and

sublevels

Select to apply the same changes to all levels and

nodes subordinate to this level

3. Click <Set>.

The level and, if selected, all subordinate levels and nodes, are configured with the new properties.

To add a node to the Network Element Browser:



2. Click Add Node.

The Add Node dialog box is displayed (see Figure 4-11). The General tab defines the node’s name and IP Address. The SNMP tab sets the SNMP parameters of the node.



Figure 4-11. Add Node – General Tab

Figure 4-12. Add Node – SNMP Tab

Table 4-5. Add Node – SNMP Tab Parameters







3. Click <Set>.

The node is configured with the new properties and added under the selected level.



To add a level to the Network Element Browser:



2. Click Add Level.

The Add Level dialog box is displayed (see Figure 4-13). The General tab defines the level’s name. The SNMP tab sets the SNMP parameters of the level.

Figure 4-13. Add Level – General Tab

Figure 4-14. Add Level – SNMP Tab



Table 4-6. Add Level – SNMP Tab Parameters







3. Click <Set>.

The level is configured with the new properties and added under the selected level.

To remove a level from the Network Element Browser:



2. Click Remove.

The level, and all subordinate levels and nodes, are removed from the Network Element Browser.

To refresh a level on the Network Element Browser:



2. Click Refresh.

The level, and all subordinate levels and nodes, are refreshed with the latest configuration.



Performing Agent Level Operations

Figure 4-15. Network Element Browser – Node Menu

The Network Element Browser - Node menu offers the following operations:

• Properties – Configures the properties of the node

• Zoom – Opens the agent zoom application

• Poll – Polls the node device

• Synchronize – Updates the node’s HPOV map details

• Remove – Removes the node from the Network Element Browser

• Refresh – Updates the node with the latest configuration.

To configure the node properties on the Network Element Browser:

1. Right-click the selected node on the Network Element Browser.


2. Click Properties.

The Properties dialog box is displayed (see Figure 4-16). The General tab defines the node’s name and IP address. The SNMP tab sets the SNMP parameters of the node. The Details tab shows the details for the node.



Figure 4-16. Properties – General Tab

Figure 4-17. Properties – SNMP Tab

Table 4-7. Properties – SNMP Tab Parameters









Figure 4-18. Properties – Details Tab

3. Click <Set>.

The node is configured with the new properties.

To view the node (agent) device:



2. Click Zoom.

The agent zoom application is displayed (see Figure 4-19).

You can only open one agent zoom application for each device. If you try to open the same device again, you receive the message: “Zoom application already running for [device IP address]”.

Note



Figure 4-19. Agent Zoom Application

To poll a node on the Network Element Browser:



2. Click Poll.

The node’s device is polled.

To synchronize a node on the Network Element Browser:



2. Click Synchronize.

The node’s HPOV map details are updated.

To remove a node from the Network Element Browser:





2. Click Remove.

The node is removed from the Network Element Browser.

To refresh a node on the Network Element Browser:



2. Click Refresh.

The device is refreshed with the latest configuration.

Importing Nodes to the Network Element Browser

The Network Element Browser shows the levels and nodes in the EMS network. You can import nodes from the HPOV map to the Network Element Browser.

To import nodes to the Network Element Browser:

• On the LaunchDesk toolbar, click the Import Nodes Icon .

The Import Nodes menu is displayed.

Figure 4-20. Import Nodes menu

To import one or more nodes to the Network Element Browser:

1. From the Import Nodes menu (see Figure 4-20), click Import nodes.

The Import Nodes from HP OpenView dialog box is displayed.



Figure 4-21. Import Nodes from HP OpenView

2. Select the node or nodes to import.

To select multiple nodes, use <Ctrl> or <Shift>.

3. Click <Select>.

The selected node(s) is added to the Network Element Browser.

To import all nodes to the Network Element Browser:

• From the Import Nodes menu (see Figure 4-20), click Import All nodes.

All nodes are added to the Network Element Browser.

To stop importing nodes to the Network Element Browser:

• On the LaunchDesk toolbar, click the Stop Import Nodes Icon .

Note



Configuring the EMS Consoles

The Admin Console includes four EMS administration tools, also called consoles:

• Security Service

• Log Admin

• Fault Service

• NER Explorer.

All consoles share the File and Help menus; any console can be stopped/restarted, or all consoles can be stopped/restarted by Stop All/Restart All.

To open the Admin Console:

• On the LaunchDesk toolbar, click the Admin Console icon .

The EMS Admin Console is displayed (see Figure 4-23).

Stopping and Restarting Consoles

Figure 4-22. Admin Console – File Menu

The Admin Console File menu view varies depending on the console selected. When no console is in focus, the main menu only displays the ‘File’ and ‘Help’ options.

The Admin Console File menu offers the following operations:

• Restart Console – Starts the communication between the EMS Admin Console and the relevant service that is running in the background (i.e. – Security Service, Fault Service, or NER Explorer)

• Stop Console – Stops the communication between the EMS Admin Console and the relevant service that is running in the background (i.e. – Security Service, Fault Service, or NER Explorer)

• Restart All – Starts the communication between the EMS Admin Console and all the services that are running in the background (i.e. – Security Service, Fault Service, or NER Explorer)

• Stop All - Stops the communication between the EMS Admin Console and all the services that are running in the background (i.e. – Security Service, Fault Service, or NER Explorer)

• Exit.

Note



Figure 4-23. EMS Admin Console Window

Setting the Required Log Functions

The EMS Log Administrator (see Figure 4-24) defines the behavior of the RADview-EMS Log Service. The Log Service is designed to be consistent with ITU-T X.735 and Telecom Log service.



Figure 4-24. EMS Log Administrator

To configure the Log Service:

1. In the EMS Admin Console dialog box, select Log Admin.

The EMS Log Administrator dialog box is displayed.

2. From the Action menu, select Configuration.

The Log Admin Configuration dialog box is displayed (see Figure 4-25).

Table 4-8 lists the values for the Configuration dialog box.



Figure 4-25. Log Admin Configuration Dialog Box

Table 4-8. Log Admin Configuration Parameters


Admin Status Locked – Actions are not logged

Unlocked – Actions are logged

Log Full Action Halt – No more entries are logged

Wrap – The oldest entries are deleted

Wrap by Severity – Entries with the lowest severity are deleted

(enabled only when Wrap is selected)

Max. Size Maximum size of the log. This can be any positive number.

Record Life Time (Days) Number of days that the entries are saved in the log. This can

be any non-negative integer. Zero means unlimited.

Quality Of Service None – No quality is guaranteed

Efficiency (Flush) – Records that should be logged are

buffered, and eventually flushed into the log. This gives the

best performance.

Reliability – Records logged immediately. This QoS provides the

most reliable behavior, and is recommended for Security Log.

Setting the Trap and Alarm Characteristics

The Log Management, which controls the traps and alarms that appear in the Event Browser can be configured for:

• Cycles

• Maximum number of log records

• Procedure when log reaches the maximum size.



Figure 4-26. Fault Service Configuration Menu

To manage the log settings:

1. From the Fault Administration window, select Configuration, > Log Management.

The Log Management dialog box is displayed (see Figure 4-27).

2. Move the marker to indicate Maximum No. of Log Records in Events Browser log.

3. Select Cyclic Log to define the procedure when the log reaches the maximum size. If the Cyclic Log check box is cleared, any new Events are lost once the log is full.

4. Select Alerts and indicate the percentage of log events that trigger an event (which appears in the Event Browser).

5. Click <Set>.

Figure 4-27. Log Management Dialog Box



Table 4-9. Log Management Parameters

Parameters Possible Values / Remarks

Max No. of Log

Records

(slider)

Allows you to specify the maximum number of Log Records possible in the Event

Browser

10,000 – 1,000,000

Cyclic

Cyclic Log If selected, allows you to specify what to do when the Event Browser reaches the

maximum number of log records.

Selected – Allows you to specify the percentage of log records to be removed when

log reaches the maximum size

Cleared – No additional events are displayed when log reaches the maximum size

Old Records Remove Percentage of old log records to be removed when log reaches the maximum size

Alerts When reaching a certain percentage of the log maximum size, an Alert can be

produced by the server and sent (as an Event) to the user

Major If selected, allows you to specify the percentage of the maximum size of the log

before a Major Alert is generated

Critical If selected, allows you to specify the percentage of the maximum size of the log

before a Critical Alert is generated

Setting Event Policies

Event policies can be handled via the Event Policy menu.

Figure 4-28. Fault Administrator Events Menu

Adding an Event Policy

To add an Event policy:

Policies with old (prior version) event classes are not replaced. You must define new policies using the new event classes.

1. From the Fault Administrator window, select Event Policy > Add…

The Add Event Policy dialog box is displayed (see Figure 4-29).

2. For Event Class, Source, Instance click […] or leave as Any (see Figure 4-29 and

3. Figure 4-30). Any means that the policy applies to ALL Sources, ALL Instances, or ALL Event Classes.

Note



4. Click <Continue>.

The Add Event dialog box with Policy tabs is displayed (see Figure 4-32). You can specify the following policies for the event:

Mask (see Masking an Event)

Severity (see Setting the Severity)

Duplication (see Duplicating Events)

Forwarding (see Forwarding)

Threshold (see Setting the Threshold)

Clearing (see Clearing Traps)

Formatting (see Formatting).

Figure 4-29. Add Event Policy Dialog Box

Table 4-10. Add Event Parameters


Event Class Any

… – Opens a list to select a specific Class

Description Description of the selected Event (Read-only)

Source Any

… – Opens a list to select a specific Source

Instance Instance on the device where the Event occurred (e.g. –

Slot2, Port3). Possible values vary as to the device that

generates the Event. For values other than ANY, refer to the

Installation and Operation Manual of the specific device.



Figure 4-30. Select Event Dialog Box

Figure 4-31. Select Event – Expanded



Figure 4-32. Add Event Dialog Box with Policy Tabs

Masking an Event

To mask an event:

1. Click the Mask tab (see Figure 4-32).

2. Select Mask if you want to mask the Event.

3. Enter the Description of the Mask (only enabled when Mask is selected).

4. Click <Apply>.



Figure 4-33. Add Event Dialog Box – Mask Tab

Setting the Severity

To set the severity:

1. Click the Severity tab (see Figure 4-34).

2. Select Severity Policy if you want to specify severity of the Event.

3. Perform the following steps only if Severity Policy is selected.

Enter the Description of the Severity.

Select the level of Severity from list.

4. Click <Apply>.



Figure 4-34. Add Event Policy Dialog Box– Severity Tab

Duplicating Events

Duplication allows multiple appearances of the same event in a specific interval of time. You can configure the option of only one event appearance in the database and in the Browser, when the interval between two identical events is shorter than a defined interval of time.

To configure Duplication:

1. Click the Duplication tab (see Figure 4-35).

2. If you want to specify duplication of the event, select Duplication Policy.

3. Perform the following steps only if Duplication Policy is selected.

Enter the Description of the Duplication.

Move the slider to select the interval of time.

4. Click <Apply>.



The event is recorded and displayed only once if the next event occurs before the interval ends.

Figure 4-35. Add Event Policy Dialog Box – Duplication Tab

Forwarding

The Forwarding tab allows you to determine where to send notification of an event (trap or system alarm) when it occurs.

To set the forwarding:

1. Click the Forwarding tab (see Figure 4-36).

2. Select Forwarding Policy.

3. Perform the following:

In the Description box, enter a description for the forwarding (only enabled when Forwarding Policy is selected).

Perform one or more of the following:



Select E-Mail and enter one or more email addresses (separated by commas)

Select Event Channel and enter one or more Event Channel destinations separated by commas (any CORBA application listening to the specified event channels will receive the events).

Select SNMP Traps to create SNMP traps when receiving a certain event or trap and send them to another station (PC or Unix). These traps/events will be displayed in the SNMPc/HPOV maps.

Figure 4-36. Add Event Policy Dialog Box – Forwarding Tab

4. Click <Apply>.

To edit the SNMP traps:

1. Click <Edit>.

2. Fill-in the four boxes in the Trap Header group:

Description



Object ID of the trap (the Object ID should be known and unmasked)

Host (the IP address of the station to which the traps will be sent).

Port – leave the default value.

3. Click <Add>.

4. If you want the trap to include a variable, enter the required Object ID and Value of the variable you want the trap to include (according to the MIB), and then click <Add>. Repeat this procedure for each variable that you want to add to the Trap Variables table (see Figure 4-37).

Figure 4-37. SNMP Traps Dialog Box

5. Click <Set>.

Setting the Threshold

Threshold defines a different Event to be generated when this Event occurs more than a specified number of times in a specified time interval.

To set the threshold:

1. Click the Threshold tab (see Figure 4-38).

2. If you want to specify threshold of the event, select Threshold Policy.

3. Perform the following steps only if Threshold Policy is selected.

Enter Description of the Threshold.

Set the number of seconds in Interval.

Select the Events per Interval value (number of times an Event can occur in an Interval).



Select an event to be generated when the threshold is exceeded. Click […] to display a selection of Event Types (see Figure 4-39).

In the Select Event dialog box, click an event in the Event Class Tree.

The Event Class appears on the bottom of the dialog box (see Figure 4-39).

Click <Set>.

The Event Type appears on the Add Event dialog box (see Figure 4-38).

4. Click <Apply>.

Figure 4-38. Add Event Policy Dialog Box – Threshold Tab



Figure 4-39. Select Event Dialog Box

Clearing Traps

You can set the clearing policy by clearing traps.

To clear a trap when it arrives:

1. Click the Clearing tab.

2. Select Clearing Policy.

3. Perform the following steps only if Clearing Policy is selected.

Enter the Description of the Clearing.

Select Event to Clear. Click Browse […] to display a selection of Event Types.

In the Select Event dialog box, click an Event in the Event Class Tree.

The Event Class appears on the bottom of the dialog box.

Click <Set>.

The Event Type appears in the Add Event Policy dialog box (see Figure 4-40)

4. Click <Apply>.



Figure 4-40. Add Event Dialog Box – Clearing Tab



Figure 4-41. Select Event for Clearing

Formatting

Formatting determines the string to be sent.

To set the format of the trap/event:

1. Click the Formatting tab.

2. If you want to specify formatting to the event, select Formatting Policy.

3. Perform the following steps only if Formatting Policy is selected.

Enter the Description of the format.

Enter the string that is displayed in the Event Browser if this trap/event occurs.

4. Click <Apply>.



Figure 4-42. Add Event – Formatting Dialog Box

To complete configuration for the Add Event dialog box:

• Click <Set> after you have configured all the Policy Tabs.

The Event Policy appears on the upper right part of the Fault Administrator dialog box.

To edit an existing event policy:

1. Select the event policy to be edited from the list of policies.

2. Edit the Policy tabs, i.e. – Mask, Severity, Duplication, Forwarding, and so on.

3. Click <Apply>.



Removing an Event Policy

To remove an event policy:

1. Select the Event Policy, to be removed from the list of policies.

2. Click <Remove>.

The Remove Event confirmation dialog box is displayed.

Figure 4-43. Remove Event – Confirmation Dialog Box

3. Click <OK>.

The Event Policy is removed from the Event Class table.

Configuring the NER Elements

The Network Element Repository (NER) is a hierarchical tree storage of the network elements and their set of attributes. NER supports inheritance of attributes. All lower-layer elements take the attributes of the higher-level elements (if the attribute is not overridden).

The NER explorer allows you to:

• Create, edit, and remove nodes in NER

• Create, edit, and remove the attributes of NER nodes

• View changes in nodes’ attributes that result from polling.

The NER Explorer window (see Figure 4-44) is a split pane.

The tree of NER objects is displayed in the left pane, and the right pane presents a table of selected object’s attributes. The tree represents the hierarchy of NER objects. Objects that have subordinates are represented with a folder icon, and objects that do not have subordinates (leaf objects) are displayed with a leaf icon.

The Attributes table on the far right has two columns:

• Name – Indicates the attribute name

• Value – Indicates the attribute value.

Attributes inherited from a parent are displayed in blue color. Other attributes are displayed in black color.



Figure 4-44. NER Explorer – Open Window with Attributes

The NER Explorer's Edit menu allows you to modify entries of the network elements, and their attributes.

Figure 4-45. NER Explorer– Edit Menu

Adding an Entry

This operation is enabled when you select an entry in the hierarchy tree. The selected node is the parent of the new entry.



To add an entry:

1. On the EMS Admin Console select NER Explorer (see Figure 4-44).

2. On the NER Explorer toolbar, select Edit > Add Entry...

The Add Entry dialog box is displayed (see Figure 4-46).

3. Enter the entry name.

4. Click <Apply>.

The new entry is created with same set of attributes as its parent (i.e. – inherited attributes). The attributes are displayed in blue.

Figure 4-46. NER Explorer – Add Entry

Renaming an Entry

To rename an entry:


2. Select an object in the hierarchy tree (network element in the middle pane).

3. On the NER Explorer toolbar, select Edit > Rename Entry…

The Rename Entry dialog box is displayed (see Figure 4-46).

4. Enter the new entry name.

5. Click <Apply>.

Figure 4-47. NER Explorer – Rename Entry

Removing an Entry

To remove an entry:


2. Select an object in the hierarchy tree (network element in the middle pane).

3. On the NER Explorer toolbar, select Edit > Remove Entry.



The selected object together with all its subordinates (if it has any) is removed from the NER Explorer.

Adding an Attribute

To add an attribute:


2. Select a node in the hierarchy tree (network element in the middle pane).

3. On the NER Explorer toolbar, select Edit > Add Attribute.

The Add Attribute dialog box is displayed (see Figure 4-48).

Figure 4-48. NER Explorer – Add Attribute Dialog Box

Table 4-11. Add Attribute Parameters


Attribute Name Net Address, Poller Name, Read Community, Write Community, Trap

Community, Timeout, Retries, Custom

Note: If this field is set to Custom, the Custom Attribute Name field is enabled.

Custom Attribute Name Enabled if Attribute Name is set to Custom

Attribute Value Freeform text or number

Figure 4-49. NER Explorer – Add Attribute (Custom Attribute) Dialog Box


RADview-EMS/TDM (Unix) Ver. 1.7 Licensing 4-43

Modifying an Attribute

To modify an attribute:


2. Select a black row in the Attributes table (if the respective row is blue, i.e. – derived from the parent, it must be modified via Add Attribute).

3. On the NER Explorer toolbar, select Edit > Modify Attribute…

The Modify Attribute dialog box is displayed (see Figure 4-50).

4. Enter a new Attribute Value.

5. Click <Apply>.

Figure 4-50. NER Explorer – Modify Attribute Dialog Box

Removing an Attribute

To remove an attribute:


2. Select a black row in the Attributes table (if the respective row is colored in blue, i.e. – attribute derived from the parent object, it cannot be removed).

3. On the NER Explorer toolbar, select Edit > Remove Attribute.

Viewing Applied Changes

Figure 4-51. NER Explorer – View Menu

Refresh in the View menu updates a subtree in the tree view starting with a selected node (e.g. – a selected node with all its subordinates). If no node is selected, refresh is performed for the parent node.

4.3 Licensing

The RADview-EMS/TDM (Unix) 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


4-44 Licensing RADview-EMS/TDM (Unix) Ver. 1.7

optimal correlation between the types of managed devices and size of the network, and the price of the management system.

The licensing mechanism does not restrict or limit simultaneous usage by different users in client-server applications, or in Unix-based systems that are accessed simultaneously by several users via X-terminals (RADview-HPOV).

For full licensing terms, see the RADview-EMS/TDM (Unix) license agreement included in the RADview-EMS/TDM (Unix) package.

Product-Specific Considerations

Each RAD product managed by RADview 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, modules within an ACE-3400 chassis do not require a license. Only the ACE-3400 node itself requires and consumes a RADview license. Standalone units like ACE-201, ACE-52 and ACE-3200 are subject to a license.

Equivalent Node Weights (ENW)

Each RAD manageable device (product) is assigned an Equivalent Node Weight (ENW). Different devices are assigned different ENW values according to their level of 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 higher number of license points.

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

Table 4-12 lists the different RAD devices and their respective ENW.

Table 4-12. Equivalent Node Weights

Device ENW Device ENW

Default 500 LRS-52 40

ASMi-52 5 MP-104 5

ASMi-52L 4 MP-204 15

DXC-10A 50 MP-2100 60

DXC-30 65 MP-2100H 60

DXC-30E 90 MP-2104 40

DXC-8R 50 MP-2104H 40

FCD-155 30 MP-2200F/B 60

FCD-155E 40 MP-4100 250

FCD-155ES/APS 40 Optimux-1551 70

FCD-155EW/APS2PDH 40 Optimux-1553 30

Note



Device ENW Device ENW

IMXi-4 20



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-13 lists the RADview packages and their bundled license points.

Table 4-13. Bundled Licenses

Platform Bundled License Points (Free of Charge)

RADview-EMS (PC) NGN/TDM 300

RADview-EMS (Unix) NGN/TDM 400

License Size Calculations

To determine the license size required to manage a given network:

1. Multiply the ENW licence points of each device (see Table 4-12) by the quantity of the device (see the example in Table 4-14.)

2. Sum the device totals to calculate the total network license points required.

3. Subtract the number of license points included with the bundled license.

4. Order the remainder of points from RAD.

Table 4-14. Licence Calculation Example

Device Quantity ENW Total

DXC-8R 2 50 100

FCD-155 4 30 120

FCD-155E 2 40 80

Total network points 300

RADview-PC/TDM bundled -200

Points to be ordered 100

To simplify the calculations for larger networks, that contain many different products, use the RADview License Calculator, available online at RAD's Web site.

To simplify the calculations for larger networks that contain many different products, use the RADview License Calculator.



Managing and Modifying Licenses

The License Service Manager application is a tool for RADview managed elements that are used to configure the License Server.

The License Service Manager can:

• 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.

For Unix stations, you must log into the system before opening the license service manager application.

To start the License Service Manager:

• Select: Misc > RADview OV > License Service Manager.

Checking the Currently Installed License Points

The General tab 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.

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

Each entry in the table describes either a license for License Points or a license for a specific product (or feature), for example – SC-TDM product.

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

Note



Figure 4-52. General Tab

Figure 4-53. General Tab (Cont.)



Table 4-15. License Status

Parameter Possible Values / Notes

Total installed license points Total License Points to which the user is entitled (for

all valid licenses that have not expired)

Consumed license points License Points that the user has already used (for

RADview managed elements)

ID Unique identifier given by RAD to a certain existing

license file

License points/Products License points included in the specific license file

When “Products” is relevant, no license points will

counted, but only “Products”

Exp. Date Expiration Date of a temporary license. If the license

is permanent, it is indicated as “permanent”.

Host Identifier For Windows – IP Address, MAC Address or Any Host

For UNIX – HOST ID, MAC Address or Any Host

Platform Platform for which the license was generated

(Windows or UNIX)

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

Figure 4-54. License Expiration Warning

Checking the Managed Elements

The Managed Element List tab displays all the devices that are managed by RADview.



Figure 4-55. Managed Element List

Figure 4-56. Managed Element List (Cont.)



Table 4-16. Managed Element List


IP Address IP Address of managed element

Name Selection Name of managed element

Type Type of managed element

ENW Equivalent Node Weight of a specific managed element

Last Host IP IP Address of the last host management station that used a

specific managed element

Last Time Used Last Date and Time that a specific managed element was used

• You can manage one agent from different RADview maps on the same station without requiring an additional license. The RADview license service makes sure that different logical representations of single network elements 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).

• The display is ordered by IP address. You can sort the list by clicking on any column.

Adding a License

To add a license file:

1. Click the General tab to display the license service manager.

2. Select: File > Add License.

3. Select a license file.

4. Click <Save>.

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

5. 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.

Note

Note



Figure 4-57. Open License Dialog Box

Figure 4-58. License Added



Removing a License

To remove a license file:

1. Click the General tab to display 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 does not cause the Total Installed License Points value to be less than the Consumed License Points, it is removed from the General tab list.

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

Figure 4-59. Remove License Warning

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

The row is removed from the General tab list. Management Services does not work anymore (until another valid License is added).

Refreshing the License Display

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

Starting and Stopping the License Service

Figure 4-60. Action Menu

The Service Console allows the user to manage the License Server.

To start the License Server:

1. Select Action > Service Console.

2. In the Service Action field select Start.



To stop the License Server:

1. Select Action > Service Console.

2. In the Service Action field select Stop.

A message is displayed: “Stopping License Server operation.”

Figure 4-61. Service Console

Configuring the Server Side License Ports

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

To configure the Server Side:

1. Select Options > Server Side Configuration.

2. Enter the Socket Port and INS Port numbers.

3. Click <Set>.

Figure 4-62. Server Side Configuration

Table 4-17. Server Side Configuration


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.

The Client Side Configuration dialog box appears.

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

3. Click <Set>.

Figure 4-63. Client Side Configuration Dialog Box

Table 4-18. Client Side Configuration Parameters


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


4-56 Additional Tasks and Options RADview-EMS/TDM (Unix) Ver. 1.7

4.4 Additional Tasks and Options

This section describes the following activities:

• Performing Automatic Configuration Upload (ACU)

• Performing Backup and Restore

• Transferring Files Using TFTP

• Setting the Net Date and Time .

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 the following products:

• ACE-201 and ACE-201/622

• ACE-3xxx – ACE-3100, ACE-3200, ACE-3400, ACE-3402 and ACE-3600

• ACE-52

• LA-104

• LA-110

• LA-130.

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.


RADview-EMS/TDM (Unix) Ver. 1.7 Additional Tasks and Options 4-57

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:

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

5. Login as root.

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

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

8. 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).

9. 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 on 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-64 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.

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

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

Note

Note



Figure 4-64. File Edit for the TFTP Server

Launching the ACU Application

Before starting the ACU 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 in Figure 4-65 appears. This message appears for any activity that requires the TFTP server to be running.

Figure 4-65. 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 application:

1. Select: Misc > RADview/OV > General > Auto Config Upload > Start Server to start the ACU server.

Figure 4-66. Launching the ACU Application

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

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

Figure 4-67. ACU Server Disabled Error Message

Note



Figure 4-68. 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 ‘–––‘.

• 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 Operations

Table 4-18 lists the ACU application operations.

Table 4-19. ACU Operations

Tasks – Configuration Dialog Box and Parameter Location

Path

Configuring ACU

TFTP Settings

ACU TFTP Settings dialog box

(Figure 4-69)

Options

General TFTP Settings

Configuring profiles

(Use this option to

schedule uploads.)

ACU Profiles window

(Figure 4-70)

Options

Profile

Uploading configuration

immediately

Upload Configuration

Confirmation dialog box

(Figure 4-75)

Configuration

Upload Now

Filtering report Report Table Filter dialog box

(Figure 4-78)

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-86)

Configuration

Report

Save As…

Printing report Print Report dialog box

(Figure 4-89)

Configuration

Report

Print

Clearing report Clear Report dialog box

(Figure 4-90)

Configuration

Report

Clear

Exiting ACU application Exit ACU dialog box (Figure 4-92) 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-69). Table 4-19 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-69. TFTP Settings

Table 4-20. 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-70).



Figure 4-70. 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-71).

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

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-71. 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-72).

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

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



Figure 4-72. Edit Profile Dialog Box

Table 4-21. 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. This avoids overloading the processor.

Time Intervals Time period for periodical upload sessions

6 hrs, 8 hrs, 12 hrs, 1 day, 3 days, 7 days, 10 days, 15 days, 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 inactive



Parameter Function

Active

Not Active

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-20) 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-73). 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.

Note



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.

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-73. 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-74).

2. Click OK.

The profile does not appear in the list of profiles.



Figure 4-74. 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 Automatic Configuration Upload confirmation dialog box appears, prompting you to confirm immediate configuration upload for the specified number of profiles and nodes (see Figure 4-75).

Figure 4-75. Upload Now Confirmation Dialog Box



2. 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).

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-76. ACU Report Table

The color of each row indicates the session status:

• Green – indicates success

• Red – indicates failure

• Yellow – indicates that the directory has been removed

• Clear – indicates such statuses as “Connecting..”; ”Connected. Transferring Data”; “Created New Directory”.

The table can be sorted according to 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-77).

Note



Figure 4-77. 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-78), which appears when you select Configuration > Report > Report Table Filter.

Figure 4-78. 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-79):



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-80 through Figure 4-82 for examples of the different detail levels.

Figure 4-79. Report Level Filtering

Figure 4-80. ACU Report Table – Profiles Only

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



Figure 4-82. 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-83).

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-83. 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-84).

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-84. 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 profiles is displayed (see Figure 4-85 for an example of displaying maximum five profiles).



Figure 4-85. ACU Report Table – Maximum of Five Profiles 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-86).

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-87 and Figure 4-88 for examples of the report saved in CSV and PDF format, respectively.



Figure 4-86. Save Dialog Box

Figure 4-87. ACU Report in CSV Format



Figure 4-88. 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-89).

2. Enter the Print parameters.

3. Click Print.

The report is printed.



Figure 4-89. 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-90).

2. Press <OK>.

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

Figure 4-90. Clearing Report Dialog Box



Figure 4-91. Report Table, Cleared

Closing the ACU 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-92).

2. Press <OK>.

The ACU client application closes.

Figure 4-92. Exit Dialog Box

To stop the ACU server:

• Select: Misc > RADview/OV > General > Close Server.



Performing Backup and Restore

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

• Database backup – backs up the entire database. The database backup includes all EMS data (if any) and the NetDBS databases that are located in the station.

• RV backup – backs up the security files of the HPOV.

• EMS backup – backs up all the XML files needed for the EMS system and the EMS security profiles.

• License backup – backs up the existing RADview 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. In case you would like to backup also the TFTP files refer to section: Backing Up and Restoring Additional Files below.

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

For system requirements and instructions for manually installing the Backup and Restore scripts, see Chapter 2.

System Requirements

• The Backup & Restore tool requires Informix, version 7.3 or higher, or Oracle 10g.

• The same installations of RADview (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.

• In stations with EMS installations, the same structure of the EMS system in the source & destination stations is needed (Clients & Servers – Master, Slaves).

• 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 database version should be installed on the source and destination stations.

Note

Note

Note



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

If Oracle is used as a database import.sql, drop_ems.sql and drop_netdbs.sql are placed also.

Installing the Backup and Restore Tool

The RADview Backup & Restore tool should be installed as a part of the RADview setup.

To manually install 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.)

It this 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 your <INF_HOME>/etc directory, and then change the following three lines in it to the following values:

TAPEDEV /backup_destination

TAPEBLK 128

TAPESIZE 2000000

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

The Backup and Restore scripts are installed and 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 asked 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.

Configuring the Backup & Restore Parameters

Before backing up or restoring files, the backup configuration file mng164_backup.xml must be configured. The mng164_backup.xml is located in the opt/MNG/MNGVIEWHP/bin directory.

The mng164_backup.xml file includes:

• Information about the backup/restore tool version

Note

Note



• Configuration parameters for the backup and restore process

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

• The backup destination directory, in which the backup files will be created.

• The restore source directory, from which the restored files will be taken.

Configuring the mng164_backup.xml File

Configure parameters in the mng164_backup.xml file.

Database Type

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

Full or Partial Backup/Restore

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

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 an IP address on a station where a backup is performed:


2. Set the <used_ip_address_backup> to IP address of your station.

To define an IP address on a station where a restore is performed:


2. Set the <used_ip_address_resotre> to IP address of your station.



Backup Directory Location

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.

Simple and dateTime Backup

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 any error occurs.

To define the required backup mode (simple or dateTime):

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

Backing Up and Restoring Additional Files

The utility can be used to backup and restore additional files which do not belong to the RADview application and are not backed up by default. This is not required for the normal program operation.

To enable the option of additional files (listed in the mng164_backup_extra file) to be backed up/restored:

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

2. Configure the mng164_backup_extra file (see next section).

Configuring the mng164_backup_extra File

To add additional files to be backed up:

• Create the mng164_backup_extra file, and add it to the opt/MNG/MNGVIEWHP/bin directory.

The additional backed up files are compressed into the mng164_backup_extra.zip file. This file is then added to the rest of the backed up files in the mng164_backup.zip file.



To add directories and files:

• Include the full paths and file names, as such:

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

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

/export/home/testing/832474bf.lic

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

Do not include the following:

• Non-existent files

• Asterisks

• Blank rows.

Running Backup

In case SC-TDMoIP is installed and you want to backup 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 and restore scripts without an input argument, or with one input argument. The default value for running the scripts is:

/opt/MNG/MNGVIEWHP/bin/mng164_backup .

In case you have different required XML files (where each XML defines which components 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 required file; you should type the actual filename

The XML file must be a legal configuration file (with a correct syntax). Otherwise, the scripts may not work properly. To run the backup process:

To run the backup process:

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

2. If Informix database 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.

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

Note

Note



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.cpio.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-EMS/TDM (Unix) 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).

Running Restore

Before running the restore script, check that:

• The directory of the mng164_backup.cpio.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. Close HPOV and stop any existing EMS server if it is running on the station.

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

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

4. 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).

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

Note

Note



6. Click ‘Y’ to continue.

The restore process may take between 10 to 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.

While the restore process runs, the following messages may be displayed:

Input configuration file is /opt/MNG/MNGVIEWHP/bin/mng164_backup.xml. 62820 blocks

Restore started…

Log file is created. Look at /opt/MNG/MNGVIEWHP/BACKUP/Jul18-2006-09:03:46/mng16

7. 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 that all the selected parts were successfully restored.

• If RADview EMS Server is installed on your station, you have to start it after the Restore process ends. You can do so by one of the following:

Reboot the system.

- Or -

Open a terminal, type su and when asked type the root password. Then, type /etc/rc3.d/S98RvEmsServer start to start the server.

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

It is highly recommend using the same hostname for both (the primary and secondary) stations. If you do not follow this recommendation then after performing the backup of the EMS system (Database & EMS) and restoring it on another host, perform the following steps before starting to work with RADview:

8. Change both the NER Context and the Map Context of the second host to the first host’s NER and MAP contexts.

9. In the EMS Launch Desk, click<Import all Nodes>.

To restore a backed-up file on another computer:

1. Create a new directory and name it CURRENT under /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. From the /opt/MNG/MNGVIEWHP/bin/ folder configure the mng164_backup.xml file for the required type of the backup/restore operation.

Note

Caution

Notes



Transferring Files Using TFTP

TFTP File Transfer is a RADview-EMS/TDM (Unix) 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.

Perform the TFTP File Transfer procedures in the following order:

1. TFTP server setup, as explained in Configuring TFTP Server

2. Create profiles – TFTP File Transfer application definitions, and associating them to network elements, as explained in Editing the TFTP Database

3. Execute TFTP File Transfer functions (i.e. SW Download, Configuration Upload, etc.), as explained in Performing TFTP File Transfer Operations.

Configuring 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.

3. Create the directory in which to save the transferred file. 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 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:

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

2. From the File menu select Open.

The Text Editor is displayed.

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



4. Click Update.

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

6. Click OK.

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

8. 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.

9. 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. Type: svcs |grep tftp.

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

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

10. Type: svcs |grep tftp.

The following is displayed:

Figure 4-93. Adjusting the TFTP Server

Opening TFTP File Transfer Application

Before starting the TFTP File Transfer application, ensure that RADview-EMS/TDM (Unix) and a TFTP server are running.

To login:

1. Login to Solaris as a RADview-EMS/TDM (Unix) user.

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

3. Login to RADview-EMS/TDM (Unix):

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

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

Note



c. Click <OK>.

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

Once launched, the TFTP File Transfer window appears (see Figure 4-90).

Only RADview-EMS/TDM (Unix) administrators are allowed to use the TFTP File Transfer application.

Figure 4-94. Opening TFTP File Transfer Menu

Figure 4-95. TFTP File Transfer – Opening Window

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

• Configuring and editing the database (see Editing the TFTP Database).

• Reviewing the operation details in the Operation tab (see Using the Operation Tab).

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

Note



Configuring TFTP File Transfer Application

To configure the TFTP file transfer application, you use the configuration menu to define the default settings for the TFTP application, and configure the product data in the TFTP database.

Figure 4-96. Configuration Menu

Configuring the TFTP Default Settings

To configure the TFTP default settings:

1. From the Configuration menu select Default Settings.

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

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

3. Click <Set>.

Figure 4-97. TFTP Default Settings Dialog Box

Table 4-22. TFTP Default Parameters

Parameter Function

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

Exclude TFTP Directory Path 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-93) enables you to add, modify, or remove product profiles. The dialog box displays 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-93).

2. Click <Add>.

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

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

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>.

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

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



Figure 4-98. Edit Database Dialog Box



Figure 4-99. Add Product Dialog Box

Table 4-23. 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



Parameter Function

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

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 card Software Download file path and name on the

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


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

Default: 60 seconds

Retry Timeout (sec) Retry between the specified number of attempts

Default: 15 seconds

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. 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-24.

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 the following table for the TFTP File Transfer options and recommended TFTP values that are relevant for your product.



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

Option

ASM

i-5

2

ASM

i-5

2L

FCD

-155

FCD

-155

E

IMX

i-4

LRS-5

2

MP-1

04

MP-2

04

Op-1

551

Op-1

553

MP-4

10

0

1 Reboot Timeout

(sec)

300 300 300 300 300 300 300 300 300 300 300

2 SW Download + + + + + – + + + + –

3 Configuration

Download

+ + + + + – – – – – +

4 Configuration

Upload

+ + + + + – – – – – +

5 Additional SW

Download

– – – – – – – – – – –

6 Statistics Upload – – – – – – – – – – –

7 User Download – – – – – – – – – – –

8 User Upload – – – – – – – – – – –

9 File Name within

Product

– – – – – – – – – – –

10 Timeout [sec] 250 250 300 300 300 300 300 300 200 200 300

11 SW Upoad – – – – – – – – + + –

12 SW Download to

Backup

– – – – – – – – – – –

13 SW Download from

Backup

– – – – – – – – – – –

14 License Download – – – – – – – – – – –

15 Subsystem

Download

– – – – – – – – – – +

• UL means Upload, DL means Download

• (+) 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 Add Product dialog box.

• Config Download and Config Upload in FCD-155 are supported from version 3, and onward.

Note



Selecting the File to Download

To select the file to download:

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

The Select File to Download dialog box appears (see Figure 4–95).

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 to Download>.

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

Figure 4–100. Select File to Download Dialog Box

Editing Product Data

To edit product data:

1. From the Configuration menu select Edit Database.

Note




2. Select the product that you want to edit.

3. Click <Edit>.

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

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

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. On the Edit Database dialog box, click <Close>.



Figure 4–101. Edit Product Dialog Box

To remove a product from the product database:

1. From the Configuration menu select Edit Database


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.

Using the Operation Tab

The Operation tab (see Figure 4–97) allows you to select all agents or specific agents for TFTP file transfer operations (see Table 4–25).

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–102. Operation Tab

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

Table 4–25. 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

Note

Note



Parameter Function

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

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–30. The row displaying the last TFTP status of each node has a

color-coded background as detailed in Table 4–30. 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

[Cancel Schedule] Cancels the highlighted scheduled backup

[Add from Map] Opens a selection list box containing all nodes on map

[Add…] Opens a dialog box for adding a new agent (node)

[Remove] Removes an agent

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.

Associating Products to Nodes

You can add an agent to the agent list in the Operation tab by one of the following methods:

• Add Agent directly from HPOV map

• Add agent via Add Agent dialog box.

Note



The Add from Map method is preferable because the Community, Timeout, and Retries of the SNMP node are obtained automatically from the map. This is faster and more accurate since there is no need for you to define them.

To add an agent from the map:

1. In the Operation Tab, click <Add from Map>.

The Add Agent from Map dialog box appears (see Figure 4–98). As RADview-EMS/TDM (Unix) polls all the agents, it lists them on the dialog box. When it finishes, the status bar at the bottom of the screen displays Ready.

2. Select the node to be added.

3. Click <Apply>.

The node is added to the list in the Operation tab.

The selection names in the list in the Operation tab are not updated if the selection names are changed in the map after being added in the Operation tab.

Figure 4–103. Add Agents from Map Dialog Box

To add an agent via Add Agent dialog box:

1. In the Operation Tab, click <Add>.

The Add Agent dialog box appears (see Figure 4–99).

Note

Note



2. Type the IP address of the HPOV node to be added.

3. Enter the parameters as specified in Table 4–26.

4. Click <Apply>.

The node is added to the list in the Operation tab.

Figure 4–104. Add Agent Dialog Box

Table 4–26. Add Agent Parameters

Parameter Function

Host Name or IP Address Host name or IP address of the agent

Community (if agent not

found on Map)

Read Name of the read community

Write Name of the write community

Timeout (msec): The maximum period of time the NMS waits for

a Get/Set response from the agent

Default value: 4000

Retries Number of attempts the NMS makes when

sending a Get/Set command to the agent. The

NMS resends the command each time the

timeout period expires.

Default Value: 3

The added node may exist in the map with a different name. In this case, the Node Name you enter via this dialog box is the one that appears in the Operation tab list as Node Name.

Note



To set default values in the Add Agent dialog box

• Click <Default>.

The dialog box reverts to the default values listed in Table 4–26.

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.

Performing TFTP File Transfer Operations

This section explains how to perform TFTP File Transfer via the Operation tab.

Figure 4–105. TFTP File Transfer – Operation

To perform TFTP file transfer operations:

1. Perform one of the following:

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.

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–102).



Figure 4–106. Selected Nodes Operation Dialog Box



Figure 4–107. Selected Nodes Operation Dialog Box – Selection

3. Configure the parameters as specified in Table 4–27.

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–108. 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–109. 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–105) to determine whether the download was successful. Additional information is available via the Report Tab (see Viewing TFTP File Transfer Reports).



Figure 4–110. TFTP Dialog Box – Operation Tab, Successful Transfer

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–27. 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-28.

Note



Table 4-28. Download & Reboot NMS Operations

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–106) 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–29. Messages are listed in Table 4–30.

Product Name Operation

ASMi-52 B

ASMi-52L B

FCD-155 B - when the Operation is “SW Download & Reboot”

D - when the Operation is “Config. Download & Reboot”

FCD-155E B

D

FCD-155ES B

D

FCD-155EwAPS B

D

FCD-155 EwAPS2PDH B

D

IMXi-4 B

LRS-52 A - when the Operation is “SW Download & Reboot”

MP-104 C – when the Operation is “SW Download & Reboot”

MP-204 C

MP-4100 A - when the Operation is “SW Download & Reboot”

E - when the Operation is “Config. Download & Reboot”

Warning



Nodes are displayed in the Report tab only if download/upload is currently in process for them. A new row is added each time the tftpStatusChangeTrap is received.

Reports are based on traps from the agent. To receive traps, the workstation running the TFTP file transfer application must be registered as a manager in the agent.

Figure 4–111. TFTP File Transfer – Report Tab

Table 4–29. 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 whose file transfer process is reported

Status Status of the download process

Possible messages are listed in Table 4–30.

Note



Table 4–30. Status Messages

Message (Standard TFTP messages) Color

Connecting… Yellow

Connected. Transferring Data Yellow

Giving up. Server does not respond Red

File 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

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.

Exiting the Application

When the user selects this menu entry:

• If there is at least one scheduled entry that was not performed, the following dialog box is displayed:

Figure 4-112. TFTP Exit Dialog Box (Scheduled Operation Exists)

• Else, the following dialog box is displayed:

Figure 4-113. Exiting Application Dialog Box (No Scheduled Operation)

Click <OK> in both cases, to exit the application.



Viewing the Net Inventory

The Net Inventory application allows you to display an Inventory Table (see Figure 4–110) for all products that support 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:

• Select HPOV Map and then select Misc > RADview/OV > General > Net Inventory.

Figure 4–114. 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.

The Inventory Table window appears (see Figure 4–110).

Note

Note



Figure 4–115. 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–31. 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

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

Note



Parameter Function

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

Refreshing the Inventory Display

To refresh the net inventory:

• Click <Refresh> and choose the desired option (see Figure 4-111 and Table 4–31.)



Figure 4-116. Inventory Refresh Options

Using Filters for the Display

To filter display:

1. On the Inventory Table, click <Filter>.

The Inventory List Filter dialog box appears (see Figure 4–112).

2. Select whether you want to filter on:

All Map Nodes

Displayed Nodes Only.

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 with 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 *.

Note

Note



Figure 4–117. Inventory List Filter Dialog Box

Table 4–32. 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

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. On the Inventory Table, select an entity (row) and click <Edit>.

The Edit dialog box opens (see Figure 4–113).

2. Modify the desired parameters.

3. Click <Set>.

Figure 4–118. 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–114).

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–115).



Figure 4–119. Expand All

Setting the Net Date and Time

RADview enables you to set the date and time for all managed units via a single screen.

To set date and time:

1. From the Misc. menu, select RADview-OV> General> Net Date and Time.

The Net Date and Time dialog box is displayed.



Figure 4-120. Network Time and Date Configuration

2. Select the redundant device from the remaining products and move it to the selected products list.

3. Check the boxes next to the network devices, as required.



Date – Day/Month/Year according to the computer clock

Time – Hour/Minute/Second according to the computer clock.

4. Check the User Time/NMS Time box as follows:

User Time – allows you to configure the Date and Time as preferred.

NMS Time – disables all fields, and the Date and Time are taken from the workstation.

5. Enter the required date and time parameters.

6. Click <Set> to implement the changes.

Date and Time Auto Mode

The NMS can automatically update date and time parameters for the ACE agents according to the computer clock and a pre-set configuration.

• 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:

1. From the HPOV 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 is displayed.

Note



Figure 4-121. Date and Time Auto Mode Dialog Box

2. Select the redundant device from the Remaining Products list and move it to the Selected Products list.

3. Set the update period in days/hours.

4. Click Set to implement the changes.

RADview-EMS/TDM (Unix) Ver. 1.7 Browsing and Handling System Events 5-1

Chapter 5

Performance Management

Once RADview-EMS/TDM (Unix) is installed, configured and operating, you can start monitoring the system's performance. This includes:

• Browsing and Handling System Events

• Monitoring Services and Processes

• Additional Monitoring Options

5.1 Browsing and Handling System Events

The main goals of the Event Browser are to:

• Display a list of events

• Filter events in display (according to various attributes)

• Manage events (acknowledging, clearing, removing etc.)

• Print and save the log of events

• Provide all the above functions to any NMS (of any vendor).

You can open more than one Event Browser window simultaneously. Each opened window represents a filter with a selected filter applied to it.

To open the Event Browser:

• On the LaunchDesk toolbar, click the Event Browser icon .

The Event Browser window is displayed (see Figure 5-1).

Terminology

Some terms that appear on the Event Browser are described below:

• Event – A general name for all Alarms and Traps

• Ack = Acknowledge (an event) – Mark an event as noticed (the opposite action is UnAck)

Note

Chapter 5 Performance Management User's Manual

5-2 Browsing and Handling System Events RADview-EMS/TDM (Unix) Ver. 1.7

• Clear (an event) – Mark an event as currently irrelevant (the opposite action is Unclear). An event that is marked as Cleared indicates that the event was either:

Manually cleared by a user

Automatically cleared (according to the clearing policy) by one or more recent events.

• Filter – A collection of criteria for several attributes

A filter is applied on Events. A filtered Event is an Event that doesn’t fulfill at least one of the conditions.

The filter enables you to view only the Events you think are important, according to the following defined conditions.

• Forward Destination – The target address of forwarded events or log file

• Log – Storage of events in the Server, where all the incoming events (which were not filtered by the Server) are being managed

• Mask (a NE) – Mark a NE so that its initiated events won’t be added to the Server storage (the opposite action is Unmask)

• NE = Network Element – An agent on the Net. Same as Source

• Source – One of the following:

An agent on the Net (same as NE)

The Server (initiates traps/events).

User's Manual Chapter 5 Performance Management


Figure 5-1. Event Browser – Opening Window

There are some cases where several events are combined into one event. In these cases, an entry does not necessarily indicate one event.

The selected events are highlighted with colors according to the severity value of the event:

• Red – Critical

• Orange – Major

• Yellow – Minor

• Blue – Warning

• Green – Indeterminate, Normal.

Table 5-1. Event Browser


Count Counts event entries for each severity type (Critical, Major, Minor, and Warning)

UnAcked Counts Unacknowledged events (entries which are not currently Acknowledged), for each

Severity

Time The Date and Time of the Last arrival of the event to the Server

YYYY-MM-DD- hh:mm:ss

Type The type of the agent.

Source IP Address, Text

The NE that initiated the event. Can appear in one of the following formats:

• IP Address (of the NE)

• Text (the NE’s Name)

• “Server” (regarding the log state)

Note




Instance The object on the Source, where the event was initiated. This is specific to the individual

agent (see the specific product manual).

Description The Description of the event.

Cleared Selected (Yes), Cleared (No)

Clear status of event

Acked Selected (Yes), Cleared (No)

Acknowledge status of event

Toolbar Icons

Figure 5-2. Event Browser – Toolbar Icons

The Event Browser toolbar icons on the top left of the window are used for (from left to right):

• Details

• Notes

• Remove

• Save As

• Print

• Stop Refresh

• Refresh

• Pause

• Resume

• Edit Current Filter

• Acknowledge

• Unacknowledge.

Opening and Saving Filters

Figure 5-3. Event Browser File Menu



The File menu operations are:

• Open a Filter

• Save As – Saves the whole table as a PDF or HTML file

• Print – Prints the log

• Clear Events

• Exit.

To open a filter:

1. On the Event Browser window, select File > Open > Default Filter.

2. Choose a default filter (see Figure 5-4).

Figure 5-4. Event Browser File Menu

You can change the format of the Event Browser log.

• Move a column to a different place in the columns order by dragging and dropping the column’s header-bar.

Selecting Events

Figure 5-5. Event Browser Edit Menu

Choose Select All to perform Ack/Clear/Remove actions on all the Events in the Event Browser window.



Refreshing the Events Display

Figure 5-6. Event Browser View Menu

Select Refresh to view new Events that have occurred, or Events that have been modified (the log is re-read completely from the database).

Acknowledging and Rejecting Events

Figure 5-7. Event Browser Event Menu

You can perform two actions on recorded events:

• Acknowledge – Mark an event as noticed

• Clear – Mark an event as currently irrelevant

To acknowledge events:

1. On the Event Browser log, select the event(s) to acknowledge.

2. From the Edit menu, select Acknowledge.

A checkmark appears on the line of the selected (highlighted) Event to mark the event as noticed.

To un-acknowledge events:

1. On the Event Browser log, select the event(s) to be unacknowledged.

2. From the Edit menu, select UnAcknowledge.

The checkmark is removed from the line of the selected (highlighted) event.



To clear events:

1. On the Event Browser log, select the event(s) to be cleared.

2. From the Edit menu, select Clear.

A check appears in the Cleared checkbox (see Figure 5-4).

To unclear events:

1. On the Event Browser log, select the event(s) to be uncleared.

2. From the Edit menu, select Unclear.

The selection disappears from the Cleared checkbox (see Figure 5-4).

To remove events:

1. On the Event Browser log, select the event(s) to be removed.

2. From the Edit menu, select Remove.

The Remove Event confirmation dialog box is displayed (see Figure 5-8).

Figure 5-8. Remove Event – Confirmation Dialog Box

The events can also be handled by choosing an event, right-clicking it and selecting the required action (acknowledge, unacknowledge etc).

Entering Event Notes

If necessary, you can add a descriptive note to each event.

To enter notes:

1. On the Event Browser log, select an event.

2. From the Event menu, select Notes.

The Event Notes dialog box is displayed.

Note



Figure 5-9. Event Notes Dialog Box

You can add a note (see Figure 5-10), change a note (see Figure 5-11), or remove a note (see Figure 5-12).

Figure 5-10. Add Note Dialog Box



Figure 5-11. Change Note Dialog Box

Figure 5-12. Remove Event Note – Confirmation Dialog Box

Viewing Event Details

To view the details of an event:

1. In the Event Browser log, select an event.

2. From the Event menu, select Details.

The Details dialog box (see Figure 5-13) is displayed.



Figure 5-13. Details Dialog Box

Filtering Events

The filter enables you to determine which events to display in the Event Browser according to the rules you define. If the source list is empty, no source-based filtering is available. You can add one or more sources to filter upon. Each entry in the source list has two fields: Source and Instance. Source can be either a specific NER or a subnet. If the Instance field is empty, all events for this source are shown. Alternatively, you can filter events that occur on specific Instance in the device. Instance is a free text (you can see in the Event Browser Instance column the type of Instances that you can filter upon).

You can open more than one window simultaneously. Each opened window represents a filter. All opened windows have the same menus and format, but can include different information – according to the selected filter.

Note



Figure 5-14. Event Browser Filter Menu

The filter allows the user to specify criteria for which events are displayed (filtered). Select one of the following:

• Add filter

• Change filter

• Remove filter.

Figure 5-15. Filter List Dialog Box

To add a filter:

1. In the Filter List dialog box, click <Add>.

The Add Filter dialog box is displayed (see Figure 5-16 to filter by General criteria and Figure 5-17 to filter by Sources).

2. Complete the fields according to Table 5-2.

3. Click <Set>.



Figure 5-16. Add Filter Dialog Box – General Tab



Figure 5-17. Add Filter Dialog Box – Sources Tab



Figure 5-18. Add Filter Dialog Box – Event Classes Tab



Figure 5-19. Add Filter Dialog Box – Advanced Tab

Table 5-2. Add Filter / Change Filter Parameters

Tab Filter Name Possible Values / Remarks

General Tab Severity Enables the user to select severity levels

Critical, Major, Minor, Warning, Indeterminated,

Normal

Time Interval

Today Only displays Events received on the current day

Last, Days, Hours, Minutes Both edit-boxes can be filled only with integers



Tab Filter Name Possible Values / Remarks

Interval, From, To The values are available in ‘YYYY-MM-DD’ and

‘hh:mm:ss’ format and can be specified through

the drop-down boxes.

General Tab Cleared Events

All Displays all Events

Cleared Only displays Events that are marked as ‘Cleared’.

Not Cleared Only displays Events that are marked as ‘Not

Cleared’.

Acknowledged Events

All Displays all Events

Acknowledged Only displays Events that are marked as

‘Acknowledged’

Not Acknowledged Only displays Events that are marked as ‘Not

Acknowledged’

Sources Tab Source Selected Network Element

Note: An empty Source list means that this field is not relevant (i.e. – the filter won’t refer to this field as a part of its conditions).

Instance Only displays Events of a specific Instance

Event Classes

Tab

Event Class Only displays Events of a specific Event Class

Description Only displays Events according to a specific string

in the Events Description field

Advanced Tab Show short node names

only

Enables the user to display names in short nodes

only

To change a filter:

1. In the Filter List dialog box, click <Change>.

The Change Filter dialog box is displayed (see Figure 5-20).

2. Complete the fields according to Table 5-2.

3. Click <Set>.



Figure 5-20. Change Filter Dialog Box – General Tab



Figure 5-21. Change Filter Dialog Box – Sources Tab



Figure 5-22. Change Filter Dialog Box – Event Classes Tab



Figure 5-23. Change Filter Dialog Box – Advanced Tab

For details on the General, Sources and Advanced tabs, refer to Table 5-2.

To remove a filter:

1. In the Filter List dialog box, click <Remove>.

2. The Remove Filter confirmation dialog box is displayed (see Figure 5-24).

Note


RADview-EMS/TDM (Unix) Ver. 1.7 Monitoring Services and Processes 5-21

Figure 5-24. Remove Filter Question Box

5.2 Monitoring Services and Processes

The system console allows you to monitor the EMS services. This includes the following activities:

• Stopping/Starting a Service

• Viewing the Server Tracing Configuration

• Viewing the Java Name and Directory Service

• Viewing the Informix Database Details

• Viewing the CORBA Name Service

• Viewing the CORBA Event Service

• Viewing the EMS Log Service

• Viewing the EMS Element Network Repository

• Viewing the EMS License Service

• Viewing the EMS Trap Listener

• Viewing the EMS Fault Management (Back End)

• Viewing the EMS Fault Management (Front End)

• Viewing the EMS Polling Service

• Viewing the EMS Security Service

To open the System Console Window:

• On the LaunchDesk toolbar, click System Console .

The System Console Opening Window is displayed (see Figure 5-25).

You can view the following elements on the System Console window:

• Servers on Stations with EMS

• Services that can be monitored

• Services that can be configured

• Status of Services (see Table 5-3).


5-22 Monitoring Services and Processes RADview-EMS/TDM (Unix) Ver. 1.7

Table 5-3. Status of Service

Color Status

Green OK

Yellow Trying to connect or restart

Red Service is down

Figure 5-25. System Console General Tab

Each Service or Management has a unique configuration. Some are Read-only (e.g., CORBA Event Service) and some can be configured (e.g., EMS Polling Service). Examples are shown in Figure 5-27, Figure 5-30, and Figure 5-37.

Stopping/Starting a Service

To stop/start a service:

1. On the System Console, select a service or management item.

2. Right-click the item.


3. Select Start or Stop.

The service that you selected starts/stops.



Figure 5-26. Service Start/Stop Dialog Box

To manage all services:

1. On the System Console, select Process Manager.

2. Right-click.

A pop-up menu is displayed.

3. Select one of the following options:

Up – to activate the Process Manager

Down – to deactivate the Process Manager

Reboot – to reboot the System

Shutdown – to shut down the System, including the Server

Restart – to restart the System.

Viewing the Server Tracing Configuration

Server Tracing Configuration is allowed only when the root in the hierarchy is selected. You can configure Server Tracing for any of the servers. The General tab of the Server Tracing Configuration dialog box (see Figure 5-27) sets the parameters to enable Trace Monitor and SNMP SPY (see Table 5-4).



To enter new information:

1. In the System Console, select one of the server names that appear below the 'Servers' root (see Figure 5-27) and then click the General tab.

2. In the Tracing dialog box, enter information for any of the parameters (see Table 5-4).

3. Click <Set>.

To retrieve the current value, click <Get>.

Figure 5-27. Server Tracing Configuration Dialog Box – General Tab

Table 5-4. Server Tracing Configuration Parameters – General Tab

Parameter Description

Info

System Name The name of the server (root)

Tracing

Global Level Level of message that appears in the MAIN server tracing window, when the

Server is activated (i.e. – INFO)

Console Enabled When the checkbox is selected, it allows viewing traced messages

Note




Trace Monitor Level Level of messages to be displayed in Trace Monitor. This parameter can be

set to ON or OFF.

Trace Monitor Host Host on IP Address of the server you wish to trace

Trace Monitor Port Port for Trace Monitor communications. It is recommended to leave this as

the default value.

SNMP SPY Monitors all SNMP connections

SNMP SPY Enabled When the checkbox is selected, it enables monitoring SNMP SPY messages

SNMP SPY Port The port for SNMP SPY communications. It is recommended to leave this as

the default value.

Figure 5-28. Server Tracing Configuration Dialog Box – Advanced Tab



Table 5-4. Server Tracing Configuration Parameters – Advanced Tab


RMI

Host RMI Host on IP Address of Server. Read-only

Port Port for RMI communications. Read-only

JAVA Naming and Directory

Service Access

Initial Context Factory Accesses the real context implementation--the Context instance created by

the initial context factory class environment property. This factory class

implements the Initial Context Factory interface. Read-only

Provider URI The unique identifier for each service provider configured in a domain. Service

provider URIs are useful in that they allow a domain to distinguish between

two service providers that may share the same implementation (but not

configuration). Read-only

SMTP

Mail Domain Mail server, required for Event Forwarding by email

Host Host on IP Address of Server

Port The port for SMTP communications

User The name of the user

Password Internal password for tracing the server

Security Connection (SSL) Secure Sockets Layer, when enabled through the checkbox (selected),

ensures the security of data sent via the Internet by using encryption.

Security

Internal Password A password used for protecting access to the System Console. If the internal

password option is enabled, the user will be required to provide a password

when attempting to initiate the System Console.



Viewing Process Description

To view the process description:

• Highlight Process 1.

Figure 5-29. Process Description – Advanced Tab

Table 5-4. Server Tracing Configuration Parameters – Advanced Tab


Cache of Resolved Hosts An internal cache of hosts/IPs, used for trap forwarding

[Get] Displays all cached Host/IP pairs

[Update] Updates all cached pairs



Viewing the Java Name and Directory Service

The Java Name and Directory service is a Read-only service where only the description and version of the service are available for viewing (see Figure 5-29).

Figure 5-30. Java Name and Directory Service

Table 5-5. Java Name and Directory Service Parameters


Info

Description Describes the current service selected in the system console

Read-only

Version The version of the service

Read-only

Viewing the Informix Database Details

The Informix dialog box lists the location and name of the Informix server and database.

To enter new information:

1. Select the Datasource Repository service in the tree.

2. In the Datasource Repository dialog box, enter information for any of the parameters (see Figure 5-30.

3. Click <Set>.



To retrieve the current value, click <Get>.

Figure 5-31. Datasource Repository Configuration

Table 5-5. Datasource Repository Configuration Parameters


Info


Read-only

Version The version of the present service selected

Read-only

EMS Datasource (Informix)

User The name of the EMS Datasource Informix user

Password The user’s password used to gain access to the EMS Datasource

Host Host on IP Address of Server

Port The port for Informix communications

Server The name of the EMS Datasource Informix server

Database The name of the EMS Datasource Informix database

Note



Viewing the CORBA Name Service

The CORBA name service allows server applications to advertise object references using logical names.

Figure 5-32. CORBA Name Service

Table 5-6. CORBA Name Service Parameters


Info


Read-only


Read-only



Viewing the CORBA Event Service

The CORBA event service allows the application to send an event that will be received by any number of objects (see Figure 5-32).

Figure 5-33. CORBA Event Service

Table 5-7. CORBA Event Service Parameters


Info


Read-only


Read-only

Event Service Settings

Event Channels Event channel files containing the event service settings

Viewing the EMS Log Service

RADview has a log service that records all the events that occurred in the server. For example, it records every request made to the server.



Figure 5-34. EMS Log Service

Table 5-7. EMS Log Service Parameters


Info


Read Only

Version The version of the present service selected

Read Only

Log Service Configuration

Start Status Check Delay

(min)

The delay time (in minutes) until the status check is started

Read Only

Status Check Interval (min) The amount of idle time (in minutes) from the time the log service stops until

the time it will have to start again.

Number of Storage Threads The number of separately stored data to retain

The Batch Size to use in DB

Operations

The size of the batch specified for DB operations, i.e. – 50

Log Browsing Performance

No of Records Retrieved per

Request

The number of records that can be retrieved for very request, i.e. – 1000



Viewing the EMS Element Network Repository

The EMS Element Network Repository is a collection of common elements that can be shared and reused in different installation projects.

Figure 5-35. EMS Network Element Repository

Table 5-8. EMS Network Element Repository Parameters


Info


Read-only


Read-only



Viewing the EMS License Service

You can set the EMS License Service parameters (see Figure 5-35). This section is especially relevant if you have installed the License Server on a remote host other than the one where the License Service Manager is located.

Figure 5-36. EMS License Service Configuration

Table 5-9. EMS License Service Configuration Parameters


Info


Read-only


Read-only

License Service Settings

License Provider Host Host address of the license provider

License Provider Port The port number for the license provider’s internal server



Viewing the EMS Trap Listener

The EMS trap listener is configured in such a way that, if a particular trap is received, actions can be configured and alerts will be generated accordingly.

Figure 5-37. EMS Trap Listener

Table 5-10. EMS Trap Listener Parameters


Info


Read-only


Read-only

Adapter Java type used to get traps

Map Type Type of the map

Driver Software module used to pass traps from the underlying layer to

the Java application

Trap Driver Software module used to receive traps



Viewing the EMS Fault Management (Back End)

Event Log settings can be configured from EMS Fault Management (Back End) (see Figure 5-37) or from Fault Administrator > Configuration.

The back end server performs server-side fault management tasks. It identifies the process when the existence and nature of network faults are detected and the fault identification problems are explored.

Figure 5-38. EMS Fault Management (Back End)

Table 5-11. EMS Fault Management (Back End) Parameters



Read-only


Read-only

Fault Management Back End

Service settings

Log Full Alarm Timeout (sec) The amount of time before the log is selected to see if it has reached

the maximum size

Fault Status Propagation Enables/disables auto checking of the status of each element in

the NER tree (internal database)

Traps Buffering and Traps defined as forwarded with retransmission are buffered (see the




Retransmission forwarding policy configuration in the Admin Console.) Add the

destination of the forwarding to the OSS heartbeat service in order to

check if it is reachable using ping. If the destination becomes

unreachable for some period, then becomes reachable again, the

traps buffered during that period are retransmitted in groups.

Max Size of Traps Cache Size of traps cache in RAM (in traps). When cache size exceeds this

value, the oldest traps are removed from the RAM cache and stored

in the database.

Max Size of Traps Database Size of database storage for buffered traps (in traps). When database

size exceeds this value, the oldest traps are deleted.

Clear Database Delete all buffered traps, that are stored in database

Retransmission Group Size Number of traps sent without delay during retransmission

Retransmission Delay (ms)

Between Groups

Delay after every retransmitted group

Viewing the EMS Fault Management (Front End)

The EMS Fault Management (Front End) service is a Read-only service where only the description and version of the service are available for viewing.

Figure 5-39. EMS Fault Management (Front End)

Table 5-12. EMS Fault Management Parameters (Front End)


Description Describes the current service selected in the system console Read-only

Version The version of the service Read-only



Viewing the EMS Polling Service

You can set the Polling Service parameters (see Figure 5-39 and Table 5-13).

Figure 5-40. EMS Polling Service Configuration

Table 5-13. Polling Service Parameters



Read-only


Read-only

Polling Service Settings

Polling Enabled Selected = Yes

Cleared = No

Polling Threads Count Number of threads performing polling at once. This only affects the

polling duration.

NER Context Name of NER tree nodes level to be polled



Viewing the EMS Configuration Management

The EMS Configuration Management is a Read-only service where the description and version of the service appears.

Figure 5-41. EMS Configuration Management

Table 5-14. EMS Configuration Management Parameters


Info


Read-only


Read-only



Viewing the EMS Security Service

The EMS Security Service, when configured, provides the protection to the system.

Figure 5-42. EMS Security Service

Table 5-15. EMS Security Service Parameters


Info


Read-only


Read-only

Sec Service Configuration

Profiles Storage Directory The location of the directory where profiles are stored

Directory to Write Audits The location of the directory where audits can be written

Use file system for file storage Enables/disables using the file system to store files


RADview-EMS/TDM (Unix) Ver. 1.7 Additional Monitoring Options 5-41

5.3 Additional Monitoring Options

The EMS application includes tools that allow you to view and define monitoring parameters of the actual running services. These tools are accessed by the LaunchDesk toolbar, and include:

• Version Browser – The Version Browser displays the name, date, version, and description of all services and management. It is a non-editable window (read-only)

• SNMP Spy – for more information, see Monitoring SNMP

• Trace Monitor – for more information, see Tracing Log Events.

To access the support tools:

• Click on the LaunchDesk toolbar.

A drop down menu appears (see Figure 5-44).

Figure 5-43. LaunchDesk Toolbar

Figure 5-44. Tools Drop-Down Menu

Viewing the RADview Package Contents

The version browser allows you to view a tree that contains the entire contents of the RADview package(s) installed on the current computer. This includes the details of both the system and agent components.

To view the contents of the currently installed RADview package(s):

• From the LaunchDesk’s Tools menu, select Version Browser.


5-42 Additional Monitoring Options RADview-EMS/TDM (Unix) Ver. 1.7

Figure 5-45. Tools Drop-down Menu

The Version Browser window appears and displays the RADview contents tree.

Figure 5-46. Version Browser Window



Monitoring SNMP Performance

The SNMP Spy window displays various details regarding the SNMP performance and connectivity status.

To use SNMP Spy (RADview-EMS Spy):

1. In the System Console dialog box enable the SNMP Spy by selecting the SNMP Spy Enabled checkbox.

2. On the Tools toolbar, click SNMP Spy.

The SNMP Spy window is displayed (see Figure 5-46).

3. Select Online to view messages as they arrive, otherwise you just see the number of messages (top left corner in Figure 5-46), until you click <Refresh>.

4. Select Freeze to stop displaying new messages.

Figure 5-47. SNMP Spy Window

Filtering SNMP Requests and Traps

Description Filter

To set a filter by description:

• On the SNMP Spy Window, type in a string that you want to use as a filter.



Options Filter

To set filters by options:

• On the SNMP Spy Window, click <Options>.

The Options dialog box is displayed, with two tabs: General (see Figure 5-47) and Filter (see Figure 5-48). Filter selects agents for which SNMP requests/responses are displayed.

Figure 5-48. Options General Tab



Figure 5-49. Options Filter Tab

Table 5-16. Options Filter Parameters


General Tab

Maximum Rows Maximum rows in SNMP Spy display

Filter Tab

SNMP Agent IP Address of SNMP Agent

[Add] Add IP Address to list

[Update] Modify the selected IP Address

[Remove] Remove the selected IP Address

Reconnecting

Click <Reconnect> to restart the SNMP Spy process according to the new settings.

Tracing Log Events

You can monitor messages from all services and management operations with the Trace Monitor (see Figure 5-49).

To display messages using the Trace Monitor:

1. Click to open the System Console.



2. Highlight the main server to view the General tab.

3. Choose the appropriate trace monitor level, other than Off, from the drop-down list, and click <Set> to confirm your choice.

4. Set parameters in the Server Tracing Configuration dialog box.

5. From the Tools menu, click Trace Monitor .

The Trace Monitor window is displayed.

Figure 5-50. Trace Monitor Window

6. Click Options.

The Options Dialog box opens:

Figure 5-51. Options Dialog Box



7. In Maximum Log Size field, enter the maximum number of messages that can be displayed in Trace Monitor. Additional messages are not displayed.

8. You can stop Trace Monitor by checking Freeze in the Trace Monitor window.

RADview-EMS/TDM (Unix) Ver. 1.7 Administering Users in the HPOV Environment 6-1

Chapter 6

Security Management This chapter describes the following:

• Creating a RADview user and user environment

• Performing user environment tests

• Using the security console

• Creating security profiles

• Managing users

• Administrator options.

The RADview security features allow operation restrictions to be predefined for users. Users and their privileges can be set to define access to various network elements and functions. The following sections describe these various security management options.

6.1 Administering Users in the HPOV Environment

When you create a user in Solaris, you must set the environment to include the variables needed for RADview-EMS/TDM (Unix), HPOV, and Informix. It is recommended that you select C as the user's SHELL.

To create a user:

1. Log in as root user.

2. Type: smc

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.


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.

Chapter 6 Security Management User’s Manual

6-2 Administering Users in the HPOV Environment RADview-EMS/TDM (Unix) Ver. 1.7

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 6-1. 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.

User’s Manual Chapter 6 Security Management

RADview-EMS/TDM (Unix) Ver. 1.7 Administering Users in the EMS Environment 6-3

6.2 Administering Users in the EMS Environment

The EMS Security Console allows you to:

• View and manage the EMS Security profiles in a graphical interface

• Create and edit security profiles

• Manage user accounts.

Only users with administrative privileges can access the EMS Security Console.

To start the Security Console:

• In the EMS Admin Console, click Security Service.

The main application window (see Figure 6-2) is split into three parts:

Left upper side – A tree of the security profiles

Right upper side – A list of users that share the selected profile

Bottom – A list of all the users.

The operations specific to EMS Security Administrator are:

• Profile

• User

• Login

• Options.


6-4 Administering Users in the EMS Environment RADview-EMS/TDM (Unix) Ver. 1.7

Figure 6-2. EMS Admin Console – EMS Security Administrator

Managing Security Profiles

A security profile is a set of function labels that are organized in a hierarchical tree. Each function label represents one action in one of the EMS applications or in one of the different zoom applications (see Figure 6-3).

A function label can have different permission rights:

• Write (which includes Read)

• Read

• Not Available. •

The EMS server automatically loads all permission files after installation/upgrade. Therefore you do not need to load permission files before assigning permissions to a profile. •

Figure 6-3 shows the available permissions that have been uploaded from the permission file (‘perm’ file) on the right pane and the individual permissions that have been assigned to a profile on the left pane.

The types of profiles are:

• Mandatory – Administrator, Operator, Monitor, Technician

• User-defined – Can be created “from scratch” or derived from any existing profile.

Note



A user is assigned only one role (profile); however a role (profile) can be assigned to many users.

• The user cannot delete or edit any of the Mandatory profiles.

• It is recommended that you reserve user root for administrative tasks only. The first administrative task should be to create new profiles and users for all other tasks.

Figure 6-3. Permission Hierarchy

Function labels can be included in a profile in different ways:

• As a single label

• As a group, through an insertion of a basic profile

• Through the All function label that includes all groups and single permissions. It functions as a group. The All function is a special permission – any operation has the right to this level of permission. This includes subordinates. All can be overridden if the permissions are explicitly set below or on the subordinate sublevel.

Note



The benefit of including group permissions is that if you load an updated permission file in the future all existing profiles that are included in this group are updated automatically. Single labels that were included without their group label are not updated.

The hierarchical permissions tree in Figure 6-3 shows:

• Available basic permissions that have been loaded (on the right pane)

• Group permissions

• Individual permissions that have been assigned (and can be modified) for the new profile (on the left pane)

• Permissions that have been modified for a range of IP addresses (on the left pane)

• Permissions that have been modified for a specific slot or port instance (on the left pane).

Figure 6-4. Security Profile Menu

Manually Loading a Security Profile

The EMS server automatically loads security profiles after performing a setup or upgrade. However, if you need to manually load the security profiles, perform the following procedure.

To load a security profile (permissions):

1. From the EMS Security Administrator window (see Figure 6-2), select Profile > Load.

The Load Basic Profile dialog box appears (see Figure 6-5).

2. Select the permission file(s) that you want to load. If you want to choose more than one file, hold the <Ctrl> key and select the required files. Each of the files contains all the security labels of the category represented by its name:

admin_perm – Labels for Admin Console functions

config_perm – Labels for general configuration functions (i.e. – Zoom function)

fault_perm – Labels for Event Browser functions

ld_perm – Labels for LaunchDesk functions

log_perm – Labels for Log Viewer functions

ner_perm – Labels for NER Explorer functions.

Note



<device name>_perm_monitor, <device name>_perm_technician & <device name>_perm_operator – Device specific labels for functions inside the Zoom application.

3. Click <Load>.

Figure 6-5. Load Basic Profile Dialog Box

All permission files must be loaded before you perform the first Add/Edit Profile or Add/Edit User.

Adding a Profile

• It is recommended that you add a new Profile using a Base Profile, and then make modifications.

• Leave the user as root.

To add a new Profile:

1. From the EMS Security Administrator window (see Figure 6-2), select Profile > Add.


2. Enter the Profile Name and Profile Description.

3. Perform one of the following:

Select a category from Base Profile.

Or

Select None.

4. Click <Continue>.

Note

Note



The Add <New Profile Name> Profile dialog box appears (see Figure 6-7).

5. Make modifications (see Working with Permissions).

6. Click <Set>.

Figure 6-6. Add Profile Dialog Box

Table 6-1. Add Profile Parameters


Profile Name Profile Name

Profile Description Description of new Profile

Base Profile Profile to be used as a base for the new one

Administrator – Has unlimited access to all operations including User

Administration

Operator – Has full Write mode and access to all except for User/System

Administration (Read-only)

Technician – Has limited access to configuration operations, and Read-only mode

for Event Browser

Monitor – Read-only mode for configuration operations, and no access to other

applications

None

Note: Any existing Profile can be used as a base for a new Profile. The user can also select None to create a completely new Profile.

[Continue…] Opens a dialog box with the new name



Figure 6-7. Add <New Profile Name> Profile Dialog Box

Using a Base Profile

To select permissions using a Base Profile:

1. Click a profile folder on the left pane to view the possible permissions defined for the Base Profile that you have selected (see Figure 6-8).

The permissions and inserts are represented as subordinates in the profile tree. Each has a small icon that indicates the access rights (see Table 6-2). The profile name and profile description fields are Read/Write.

2. Select a permission group from the top right pane or a single permission from the bottom right pane (see Figure 6-9) and drag it to the profile tree (to either a specific place in the tree or an empty place on the left pane, where it is automatically added to the correct place in the tree).



If you drag a permission to an incorrect place, you receive the message: “The selected place is inconsistent”.

Working with Permissions

The access rights of a Permission are:

• Write

• Read

• Not Available.

You can change the access rights by double-clicking on the permission icon. This toggles from Write > Read > Not Available > Write.

Table 6-2. Permission Icons

Icon Permission

Write

Read

Not Available

Group Permission

Group Permission – from Base Profile

You cannot directly change a Group Permission that is derived from a Base Profile, see below.

To change permission, i.e. – change from Write to Read:

1. Double-click the green icon (see Figure 6-10) .

2. Click <Set>.

To change permission, i.e. – change from Read to Not Available:

1. Double-click the yellow icon (see Figure 6-10) .

2. Click <Set>.

To change permission, i.e. – change from Not Available to Write:

1. Double-click the red icon (see Figure 6-10) .

2. Click <Set>.

To modify a Group Permission that is derived from a Base Profile ( ):

1. Drag the icon from the right pane to the left pane.

Note

Note



The icon is removed.

2. Click the icon to modify it.

If you change the attribute of a group permission, all the individual permissions in the group change.

Figure 6-8. Add <New Profile Name> Profile Dialog Box – Possible Permissions

Note



Figure 6-9. Add <New Profile Name> Profile Dialog Box – Selected Permissions



Figure 6-10. Add <New Profile Name> Profile Dialog Box – Different Permissions

To add all permissions in a folder:

1. Right click the selected folder item.

A pop-up menu appears (see Figure 6-11).

2. Click Add All to add all permissions of this category.



3. Click <Set>.

An All permission, with Write access rights, is added directly below the selected tree node.

To add a range of permissions in a folder:



2. Click Add IP Range… to select permissions for a range of IP addresses (see Figure 6-12).

3. When selecting a Range, type the IP Addresses or click the <…> button to select the range of IP Addresses.

4. Click <Set>.

The range appears in the left pane.

5. Drag available permissions from the right pane to the range of addresses on the left pane (see Figure 6-3).

To add domain of permissions in a folder:



2. Click Add Domain to select permissions for a domain (see Figure 6-13).

3. When selecting a Domain, type the source IP Address or click the Browse <…> button to select the domain source IP Address.

4. Click <Set>.

The domain appears in the left pane.

5. Drag available permissions from the right pane to the domain on the left pane (see Figure 6-3).

To delete permissions:

1. Select a permission in the left pane.

2. Click (see Figure 6-9).

You cannot delete permissions from a Base Profile.

Note



Figure 6-11. Right Mouse Pop-Up Menu

Figure 6-12. Select Range Dialog Box

Figure 6-13. Select Domain Dialog Box



To assign permissions to a range of IP addresses:

1. Right click the selected range of IP Addresses in the left pane.


2. Select one of the following:

Add All – Add all permissions of the category under which the range has been placed (Admin, Fault, Config, etc)

Add Instance – Modify permissions for a certain instance on the nodes in this IP range (e.g. – Port1 or specify type of interface)

Move Up – Move up the order of priority, in relation to other range groups.

Move Down – Move down the order of priority, in relation to other range groups.

Figure 6-14. Selecting IP Address Permissions

Adding a No-Base Profile

To add a Profile with No Base Profile:

1. From the EMS Security Administrator window (see Figure 6-2), select Profile > Add.


2. Enter a Profile Name and a Profile Description.



3. Select a None for the Base Profile (see Figure 6-15).

The Add <NEW PROFILE NAME> Profile dialog box appears with the left column empty (see Figure 6-16).

4. Drag the whole set of permissions from a folder (see Figure 6-16) or drag one permission at a time to the left column (see Figure 6-17).

5. Click <Set>.

Refer to Working with Permissions to change permissions.

Figure 6-15. Add Profile – Base Profile NONE



Figure 6-16. Add <New Profile Name> Profile (NONE) Dialog Box



Figure 6-17. Dragging Permissions

When you add a profile based on an existing profile, you cannot double-click the

group permanent icon .

Editing a Profile

To edit a profile:

1. From the EMS Security Administrator toolbar, select Profile > Edit.

The Edit Profile dialog box appears (see Figure 6-18).

2. Make any changes.

3. Click <Set>.

You cannot edit your own Profile properties.

Note

Note



Figure 6-18. Edit Profile

Removing a Profile

To remove a profile:

1. From the EMS Security Administrator window (see Figure 6-2), select Profile > Remove.

The Confirm Profile Removal dialog box appears (see Figure 6-19).

2. Click <OK>.

This entry is enabled only when a profile is selected in the profiles tree, the profile is not mandatory, and the profile does not have any users attached.

Note



Figure 6-19. Confirm Profile Removal Dialog Box

Managing EMS Users

The EMS administrator can:

• Add users

• Edit users

• Remove users.

Figure 6-20. EMS Administrator User Menu

Adding a User

To add a user:

1. From the EMS Security Administrator window (see Figure 6-2), select User > Add.

The Add User dialog box appears (see Figure 6-21).

2. Enter the User Name and Description.

3. Select a Profile (from one of the existing profiles).

4. Enter the user’s Password.

5. Enter the user’s password again to Confirm Password.

6. Click <Set>.



Figure 6-21. Add User Dialog Box

Editing a User

To edit a user:

1. From the EMS Security Administrator window, select User > Edit.

The Edit User dialog box appears (see Figure 6-22).

2. If necessary, make changes to User Name, Description, Profile, or Lock.

You cannot edit your own User properties.

Note



Figure 6-22. Edit User Dialog Box

• This entry is enabled only when an entry on the Users Table is selected.

• When Admin Lock is selected, the User cannot use the system until the Administrator clears the check box.

Changing a User’s Password

To change a user’s password:

1. From the EMS Security Administrator window (see Figure 6-2), select User > Edit.

The Edit User dialog box appears (see Figure 6-22).

2. Click <Change Password>.

The Change Password dialog box appears (Figure 6-23).

3. Enter the new Password.

4. Enter the new password again to Confirm Password.

5. Click <Set>.

Note



Figure 6-23. Change Password Dialog Box

Removing a User

To remove a User:

1. From the EMS Security Administrator window, select User > Remove.

The Confirm User Removal dialog box appears (see Figure 6-24).

2. Click <OK>.

Figure 6-24. Confirm User Removal Dialog Box

Administrating Login Names

Figure 6-25. EMS Security Administrator Login Menu

Active Login Table

The Active Login Table is a list of all users who are currently logged in.

To view all Users who are currently logged in:

• From the EMS Security Administrator window (see Figure 6-2), select Login > Active Login Table.

The Active Login Table dialog box appears.



Figure 6-26. Active Login Table Dialog Box

Table 6-3. Active Login Table


User User’s name

Login ID User’s Login ID

Login Date Date and time of User login

Host User’s Host IP Address

Terminal User’s Terminal

Administrator Logout

An administrator can log out a user.

To logout a User:

1. Select a User in the table.

2. Click <Logout>.

A user must log out from the LaunchDesk. Only an administrator can log out a user from this menu.

Note



Changing Security Policies

There are three tabs in the Configuration dialog box, accessible via Options > Configuration:

• Password

• Account

• Audit.

Figure 6-27. EMS Security Administrator Options Menu

Setting a User’s Password Policy

The Administrator can define the following characteristics of a password:

• Combination of letters, numerals, spaces, and symbols that are allowed

• Maximum or minimum length of the password

• Whether the password is case-sensitive, i.e. – users must type the same capitalization as defined by the Administrator when they enter the password

• Enhanced security by requiring expiration of passwords and ensuring that old passwords are not reused.

To configure password policies:

1. From the EMS Security Administrator window (see Figure 6-2), select Options > Configuration.

2. Click the Password tab (see Figure 6-28).

3. Select Length Policy if you want to define the maximum or minimum length for a password and then enter the Minimum Length and Maximum Length.

4. Under Alphanumeric Policy, select Case Sensitive if you want users to type the same capitalization when they enter a password as the capitalization when the password was assigned. If you want to require a minimum number of letters or digits in the password, enter the Minimum No. of Letters and Minimum No. of Digits.

5. Select Expiration Policy if you want a password to expire after a specified number of days, and select the number of days.

6. Select History Policy to determine the number of unique passwords that must be associated with a User account before an old password can be used.

7. Under Password Storage, select Encryption Policy and select type of Encryption.

8. Click <Set>.



Figure 6-28. Configuration – Password Tab

Table 6-4. Configuration – Password Parameters


Length Policy

Length Policy Selected - Length Policy is on

Minimum Length 2–30

Enabled only when Length Policy is selected.

Maximum Length 4–30

Enabled only when Length Policy is selected.

Case Sensitive Selected - The password is case sensitive

Alphanumeric Policy

Alphanumeric Policy Selected - Alphanumeric Policy is on

Minimum No. of Letters 1–30

Enabled only when Alphanumeric Policy is selected.

Minimum No. of Digits 1–30

Enabled only when Alphanumeric Policy is selected.




Expiration Policy

Expiration Policy Selected - Expiration Policy is on

Expires In (days) 1–100

Enabled only when Expiration Policy is selected.

History Policy

History Policy Selected - History Policy is on

No. of Remembered Past

Passwords

0–10

Enabled only when History Policy is selected.

Password Storage

Encryption Policy Selected - the password is encrypted

Encryption Algorithm Encryption types: Open, SHA1, MD5

Enabled only when Encryption Policy is selected.

Setting a User’s Account Policy

The Administrator can configure whether a User is automatically locked out of the system if he does not enter the correct password, and if he is logged off after a period of non-activity.

To configure a user’s account policies:

1. From the EMS Security Administrator window, select Options > Configuration.

2. Click the Account tab (see Figure 6-29).

3. Select Auto Lockout Policy if you want to configure Lockout, and then configure the Number of Failed Logon Attempts Before Lockout.

4. Select Auto Logout Policy if you want to logout a User after a specified amount of non-activity time, and then configure the amount of time for Auto Logout.

5. Click <Set>.



Figure 6-29. Configuration – Account Tab

Table 6-5. Configuration – Account Parameters


Auto Lockout Policy

Auto Lockout Policy When selected: Auto lockout policy is on

No. of Failed Logon Attempts

Before Lockout

1–15

Enabled only when Auto Lockout Policy is selected.

Lockout Duration 0 minutes, 5 minutes, 10 minutes, 15 minutes, 30 minutes,

1 hour, 2 hours, 3 hours, 4 hours, 5 hours, 6 hours, 7 hours,

8 hours, 9 hours, 10 hours, 11 hours, 0.5 days, 1 day, 2 day

Enabled only when Auto Lockout Policy is selected.

Auto Logout Policy

Auto Logout Policy Selected - Auto Logout Policy is on

Auto Logout After (minutes) 3–60

Enabled only when Auto Logout Policy is selected.



Setting a User’s Audit Policy

To configure a user’s audit policies:

1. From the EMS Security Administrator window (see Figure 6-2), select Options > Configuration.

2. Click the Audit tab (see Figure 6-30).

3. Select Audit Policy if you want to configure Audit, and then complete Logon and Logoff parameters.

The Audit file is located under: <RADview Shell directory> > EMS > Conf> Sec> Audit.

Figure 6-30. Configuration – Audit Tab

Table 6-6. Configuration – Audit Parameters


Audit Policy When selected, the Audit Policy is on

Logon and Logoff Success When selected, a successful logon and logoff is

recorded in the log file.

Enabled only when Audit Policy is selected.

Logon and Logoff Failure When selected, a failure logon and logoff is recorded in

the log file.

Enabled only when Audit Policy is selected.

Note

RADview-EMS/TDM (Unix) Ver. 1.7 Detecting Faults 7-1

Chapter 7

Fault Management In RADview, fault management handles SNMP traps (or events) that are generated by agents, or system events generated by the EMS server that communicate with the agent. The Event Browser displays these events and traps.

The Fault Service component includes:

• Fault Administrator (see Detecting Faults).

• Event Browser (see Viewing Logs).

In addition, the system can be tested as explained in Testing the System.

7.1 Detecting Faults

The Fault Administrator allows you to:

• Manage the Event Log parameters

• Manage the way Events are displayed in the Event Browser

• Manage the behavior of the system upon receiving specific events and traps.

To launch the EMS Fault Administrator:

1. Go to the EMS Admin Console window (assuming it is already open).

2. From the left pane of the window, click Fault Service.

The EMS Fault Administrator is displayed.

Figure 7-1. Fault Administrator – Left Side Columns

Chapter 7 Fault Management Installation and Operation Manual

7-2 Viewing Logs RADview-EMS/TDM (Unix) Ver. 1.7

Figure 7-2. Fault Administrator – Right Side Columns

7.2 Viewing Logs

The Log Viewer displays events captured by the EMS Log Service.

To access the Log Viewer:

• On the LaunchDesk toolbar, click the Log Viewer Icon .

The Log Viewer window is displayed.

Figure 7-3. Log Viewer Window

There are three kinds of displays. Select one of the tabs:

• Security – displays security-related events

• System – displays system-related events

• Application – displays application-related events.

Installation and Operation Manual Chapter 7 Fault Management

RADview-EMS/TDM (Unix) Ver. 1.7 Viewing Logs 7-3

Setting the Log Display

Figure 7-4. Log Viewer Configuration Menu

To select the EMS server for displays:

1. From the Configuration menu, select EMS Server Selection.

The EMS Server Selection dialog box is displayed (see Figure 7-5). The list shows active servers in the system that can be master or slave servers.

Figure 7-5. EMS Server Selection Dialog Box

2. Select the server and then click <Select>.

The filter operation opens on the selected server (see next section).

To filter the type of display:

1. From the Configuration menu, select Filter…

The Filter dialog box is displayed (see Figure 7-6).

2. Select the type of filter for the display, according to Table 7-1, and click <Set>.


7-4 Viewing Logs RADview-EMS/TDM (Unix) Ver. 1.7

Figure 7-6. Filter Dialog Box

Table 7-1. Log Viewer Filter Parameters

Parameter Description / Possible Values

Date Filter display by beginning and end dates

Severity Critical

Major

Minor

Warning

Normal

Unknown

Source Filter display by Source IP Address

User Filter display by User Name

Category Filter display by Category

Sub Category Filter display by Sub Category

Description Filter display by Description (can also be part of a

description with ‘*’ instead of a prefix/suffix)


RADview-EMS/TDM (Unix) Ver. 1.7 Viewing Logs 7-5

Saving, Printing or Deleting Logs

You can save, print or delete logs.

Figure 7-7. Log Viewer Action Menu

To save a log:

1. Click a tab on the Log Viewer.

2. From the Action menu, select Save As.

To print a log:


2. From the Action menu, select Print.

Save and Print only apply to the active tab.

To delete selected entries:


2. Select the entries you want to delete.

3. From the Action menu, select Delete > Selected Entries.

To delete the whole log:


2. From the Action menu, select Delete > Log.

Delete Log only applies to the active tab.

Note

Note


7-6 Testing the System RADview-EMS/TDM (Unix) Ver. 1.7

7.3 Testing the System

Testing the HPOV Environment

The RADview Post Installation User Environment Tool automates all post-installation procedures and completes the installation of RADview Unix-based products.

When an existing user needs to perform User Environment Tests, such as when a RADview application does not function properly, or upon request from RAD Technical Support, the csh script performs the following User Environment and Installation tests:

• HPOV NNM processes status

• Informix variables

• 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 perform an environment tests:

1. Log in as a RADview user.

2. Type: /opt/MNG/MNGVIEWHP/bin/user_env.csh and press <Enter>.

The script shows pass/fail messages on the screen, and writes the test results into the file user_env.log in the user’s home directory.


RADview-EMS/TDM (Unix) Ver. 1.7 Testing the System 7-7

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

* 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...

Setting user files:

/export/home/radview/.login

/export/home/radview/.dtprofile

User Environment files set successfully.

Running user environment tests for an existing user.

Checking HPOV NNM processes status...

HPOV NNM processes are running.

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-8. RADview User Environment – Existing User

In the example above, the script found 1 error.

*** 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


RADview-EMS/TDM (Unix) Ver. 1.7 Testing the System 7-9

Figure 7-9. Correcting the Informix LANG Variable (Solaris 10)

Figure 7-9 illustrates how to correct the error in the Solaris 10 environment.

If you cannot correct the problem, send the file: /export/home/g7/user_env.log to Technical Support.

Testing the User Environment

Run the commands in Table 7-2 to verify that the user environment is set correctly. These procedures are optional.

Table 7-2. Setting the User Environment

No. 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 then:

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


/opt/informix then:

INFORMIXDIR=/opt/informix

INFORMIXSQLHOSTS=/opt/informix/etc/

sqlhosts

Else

Verify RADview user's .cshrc file was

edited correctly, and log-out / log-in

performed (see step 3)

3 To verify ODBC

installation and home

directories are defined,

type:

env | grep ODBC

ODBCDIR=<INF_HOME>/odbc

ODBCHOME=<INF_HOME>/cli/cli

Example


/opt/informix then:

ODBCDIR=/opt/informix/odbc

ODBCHOME=/opt/informix /cli/cli

Else

Verify RADview user's .cshrc file was

edited correctly, and log-out / log-in

performed (see step 3).

4 To verify

MNG164_APP_PATH

(RADview HPOV's home

directory) is defined,

type:

echo

$MNG164_APP_PATH

/opt/MNG/MNGVIEWHP Else

Verify the mng164_setenv.sh script

was executed by the RADview user,

and logout/login 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/o

dbc/lib:/opt/informix/odbc/drivers:

/usr/lib:/opt/informix/odbc/lib:/opt

/informix/odbc/drivers:/usr/lib:

/opt/informix/odbc/lib:/opt/inform

ix/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


/opt/informix then:

LD_LIBRARY_PATH=/opt/informix/odbc/l

ib=/opt/informix /odbc/drivers:/usr/lib

Else

Verify the mng164_setenv.sh script

was executed by the RADview user,

and logout/login performed.

6 To verify the CDE

Language variable is set

to the right, type:

echo $LANG

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

RADview-HPOV user's

Shell is csh, type:

echo $SHELL

/bin/csh Else

Change user shell to csh via admintool


RADview-EMS/TDM (Unix) Ver. 1.7 Frequently Asked Questions 7-11


8 To verify Informix

Database is On-Line,

type:

onstat –

INFORMIX-OnLine Version

7.31.UC2 -- On-Line -- Up 11

days 22:33:56 -- 12272 Kbytes

Else

Unless Informix is reported to be On-

Line, Database is down.

9 To verify the RADview-

HPOV user's home

directory includes a

.odnb.ini file, pointing

to an ODBC driver

located under the

Informix installation

directory, type:

cat

/<USER_HOME_DIR>/.od

bc.ini|grep vsifmx7.so.1

Driver=<INF_HOME>/odbc/drivers/

vsifmx7.so.1

Replace <USER_HOME_DIR>, with the

RADview-HPOV user’s home directory.

7.4 Frequently Asked Questions

Q My network requires the installation of additional RAD products. How can I find out whether my system has sufficient license points?

A Refer to the Licensing section in Chapter 4.

Q Does Solaris 10 require the Mozilla browser?

A No. Only previous versions of Solaris needed the Mozilla browser installation.

Q Is it possible to upgrade an existing HPOV/Solaris system to a newer one without losing all the data?

A Yes. Please note that newer RADview-EMS/TDM (Unix) systems require Solaris 10 and above, so your system may require a migration process. You will need to use the Backup and Restore tool and perform an upgrade procedure. For more information, refer to Appendix A and contact Technical Support.

Q Where can I obtain operating/monitoring instructions regarding a specific RAD product that is installed on the network?

A This system manual is complemented by individual agent manuals, each relating to a specific RAD product that is included in the RADview-EMS/TDM (Unix) package. In addition, each zoom application has a built-it help system that displays the manual in a browser window.


7-12 Technical Support RADview-EMS/TDM (Unix) Ver. 1.7

7.5 Technical Support

Technical support for RADview-EMS/TDM (Unix) can be obtained from the local distributor from whom it was purchased.

For further information, please contact the RAD distributor nearest you or one of RAD's offices worldwide. This information can be found at RAD's Web site: http://www.rad.com/ (for offices location, click About RAD > Worldwide Offices ; for distributors location, click Where to Buy > End Users).

http://www.rad.com/

RADview-EMS/TDM Ver. 1.7 Checking the Installed Software A-1

Appendix A

Migration Guide

A.1 Migration Guide 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.

To upgrade your system, check the installed software in section A.2, then follow the procedure in section A.3.

• Migration – Migrating RADview to new hardware, while keeping the database of the existing system.

To migrate to new hardware, check the installed software in section A.2, then follow the procedure in section A.4.

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-EMS/TDM 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-EMS/TDM Ver. 1.7 Migration Procedure A-3

A.3 Upgrade Procedure

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

When migrating RADview-HPOV you must: upgrade the old version of the HPOV on your present system, backup the database, and finally restore the database on the new system.

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-EMS/TDM 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 installation? (y/n)”

Note

http://support.openview.hp.com/selfsolve/manuals


RADview-EMS/TDM 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 installation? (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-EMS/TDM 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 installation? (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-EMS/TDM 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-EMS/TDM 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-EMS/TDM 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-EMS/TDM 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 installation? (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-EMS/TDM 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

Appendix B Migration Guide User's Manual

B-14 Post-upgrade Procedures RADview-EMS/TDM 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. Name of Figure

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

I-1

Index

—A—

Active login table, 6-24 Adding

events, 4-25 license, 4-50 security profile, 6-7 user, 6-21

Administrator login menu, 6-24 logout, 6-25

Agent change attributes, 3-14 creating, 3-10 deleting, 3-14 monitoring, 3-15 SNMP parameters, 3-12

Alarms display categories, 3-15

Alerts, 4-25 Application

log viewer, 7-2 Attributes

change, 3-14 removing, 4-43

Auto mode date, 4-113 time, 4-113

Autodiscovery HPOV, 4-2

—B—

Backup EMS, 4-73 license, 4-73 running, 4-77 RV, 4-73

Backup and Restore installation and setup, 4-74

Backup and Restore tool, 4-73 Base profile

selecting permissions, 6-9 using, 6-9

—C—

Changing agent attributes, 3-14 password, 3-20 user password, 6-23

Clearing traps, 4-35

Client/Server

distribution, 1-3 Community, 4-96 Configuration

TFTP server, 4-80 Configuration

Client side, 4-54 fault service, 4-23 management, 4-1 server side, 4-53 server tracing, 5-23

Console system, 5-21

Creating net hierarchy, 3-9 RAD device agent, 3-10

—D—

Date setting, 4-1, 4-111

Deleting agent, 3-14

Device type, 4-44

Directory access, 5-26

Display alarm categories, 3-15 filter, 7-3

Distribution client, 1-3 server, 1-3 system, 1-4 territorial, 1-7

Duplication configuration, 4-26, 4-30 policy, 4-30

—E—

Edit profile, 6-19 user, 6-22

Edit menu event browser, 5-5

EMS admin console, opening, 4-20 admin console, using, 4-20 components installation, 2-4 fault administrator, 7-1 fault management, 5-35 fault management, front end, 5-36 license service, 5-33 log service, 7-2

Index Installation and Operation Manual

I-2 RADview-EMS/TDM (Unix) Ver. 1.7

logging in, 3-19 logging out, 3-22 opening, 3-17 running application, 3-17 starting server, 3-19 stopping server, 3-19

Environment tests performing, 7-6

Event adding, 4-25 clear, 5-7 details, 5-9 editing policy, 4-38 handling policies, 4-25 masking, 4-28 notes, 5-7 remove, 5-7 removing policy, 4-39 unacknowledge, 5-6 unclear, 5-7

Event browser, 5-1, 5-3 edit menu, 5-5 event menu, 5-6 file menu, 5-4 filter menu, 5-10 icons, 5-4 notes, 5-7 terminology, 5-1 view menu, 5-6

—F—

Fault threshold, 4-33

Fault administrator, 7-1 Fault service

configuration, 4-23 formatting, 4-37

Fault severity setting, 4-29

FCAPS services, 1-7

File menu event browser, 5-4

Filter add, 5-11 change, 5-11 changing, 5-16 display, 7-3 event browser,menu, 5-10 list, 5-11 remove, 5-11 removing, 5-20

Format trap event, 4-37

Forwarding, 4-31 Functions

master/slave server, 1-7

—G—

GUI, 3-4

—H—

HP OpenView session

starting, 3-2 HPOV

autodiscovery, 4-2 GUI, 3-4 installation directory, changing, 2-34 map application rules, 3-6 map status color propagation, 4-1 running, 3-1 screen display, 3-5

—I—

Icons event browser, 5-4

Importing nodes, 4-18 Installation

PC (client station), 2-19 RADview EMS NGN, 2-7 RADview shell, 2-19 single station system, 2-4

Installing licenses, 3-3

Internet addresses preparing, 3-9

—J—

Java naming, 5-26 zoom applications, 3-16, 3-22

—L—

LaunchDesk logging in, 3-19 open, 3-21 toolbar, 3-21, 5-40, 7-2

License, 4-43 adding, 4-50 bundled, 4-45 installing, 3-3 removing, 4-52 size calculation, 4-45

Licensing Terms, 4-43

Loading security profile, 6-6

Log administrator, 4-21 configuration, 4-22 cyclic, 4-25 management parameters, 4-25 records, 4-25

Log viewer, 7-2 filter parameters, 7-4

Logging in administrator, 6-24 EMS, 3-19

Logging out administrator, 6-25 EMS, 3-22

—M—

Management configuration, 4-1 users, 6-21

Installation and Operation Manual Index

RADview-EMS/TDM (Unix) Ver. 1.7 I-3

Map Moving objects, 3-7

Maps moving objects, 3-16

Masking events, 4-28

Menu File, 4-20 options, 6-26

Monitoring agent, 3-15

Moving objects on map, 3-7

—N—

NER explorer, 4-39 add entry, 4-40 adding attributes, 4-41 edit menu, 4-40 modifying attributes, 4-42 remove entry, 4-41 removing attributes, 4-43 rename entry, 4-41

Net creating, 3-8 hierarchy, creating, 3-9 network topology, 3-9

Net inventory, 4-106 editing an entity, 4-110 Filtering display, 4-108 Opening, 4-106

Net Inventory Table parameters, 4-107

Network element repository, 4-6 size, 4-44

Network element Browser add a level, 4-12 adding a node, 4-10 importing nodes, 4-18, 4-19 level menu, 4-9 node menu, 4-14 status icons, 4-8 stop importing nodes, 4-19

No base profile, 6-16 Node names

preparing, 3-9 Nodes

adding, 4-10 importing, 4-18 network element Browser, 4-14

—O—

Opening security console, 6-3 TFTP file transfer, 4-81

Options menu, 6-26

OVbackup, 4-78

—P—

Parameters add events, 4-26 agent SNMP, 3-12

EMS fault management, 5-36 log admin, 4-23 polling service, 5-37

Password, 3-20 change, 3-3, 3-20 policy, 6-26

PC client station installation, 2-19

Performing TFTP file transfer, 4-97 Permissions

access rights, 6-10 changing, 6-10 delete, 6-14 domain, 6-14 dragging, 6-19 folder, 6-13 hierarchy, 6-5 modify, 6-10 not available, 6-10 read, 6-10 write, 6-10

Polling interval, setting, 3-7 service, 5-37 status, 4-2

Port installation user environment, 7-6

Profile adding, 6-7 base, 6-9 editing, 6-19 loading, 6-6 no base profile, 6-16 permissions, 6-10 removinge, 6-20 security, 6-4

—R—

Removing base profile, 6-20 event, 4-39 license, 4-52 user, 6-24

Report, TFTP file transfer Remove messages, 4-105 Status messages, 4-104

Reports TFTP file transfer, 4-102

Restore, 4-78 RMI, 5-26, 5-28, 5-31 Running

EMS application, 3-17

—S—

Security, 5-26 adding profile, 6-7 loading profile, 6-6 log viewer, 7-2 opening console, 6-3 profile, 6-4 start HP OpenView session, 3-2 starting console, 6-3

Selection setting format, 3-12



Server side configuration, 4-53

Server tracing configuration, 5-23

Services CORBA event service, 5-30 CORBA name service, 5-29 EMS element network repository, 5-32 EMS log service, 5-30 EMS trap listener, 5-34, 5-38, 5-39 java name and directory service, 5-27

Setting fault severity, 4-29 HPOV autodiscovery, 4-2 map status color propagation, 4-1

Severity, 5-15 Single station, 1-4 Single station system

installation, 2-4 SMTP, 5-26 SNMP

configuration, 4-2 editing traps, 4-32 parameters, 3-12, 4-10, 4-13 spy, 5-23, 5-25

SNMP spy, 5-42 description, 5-42 filters, 5-42 options, 5-43 reconnect, 5-44

Starting EMS server from command line, 3-19 service on system console, 5-22

Status polling, 4-2

Stopping EMS server from command line, 3-19 service on system console, 5-22

Synchronization, 4-4 settings, 4-4

System log viewer, 7-2

System console EMS fault management, 5-35 EMS license service, 5-33 open, 5-21 polling service, 5-37 starting service, 5-22 stopping service, 5-22

—T—

Terminology event browser, 5-1 WAN maps, 3-5

TFTP file transfer, 4-80 Report, remove messages, 4-105

TFTP file transfer Add agent from map, 4-95 Add agent with dialog box, 4-95 Agent default values, 4-97 Configuration, 4-83 default settings, 4-83 Default settings, 4-83 Edit database, 4-84

Opening, 4-81 Operation tab, 4-93 options, 4-89 perform, 4-97 Product profile

Add, 4-84 remove agents from map, 4-97 Report status mesages, 4-104 Reports, 4-102 Save database, 4-105 Select file to download, 4-90

TFTP File Transfer Associating device profile to network element,

4-94 Associating product to network element, 4-94 Associating product to node, 4-94 Editing product data, 4-90 Product data

Editing, 4-90 TFTP server

Configuration, 4-80 Threshold, 4-33

set, 4-33 Time

setting, 4-111 Toolbar

LaunchDesk, 3-21 Trace monitor, 5-44 Tracing, 5-24 Traps

clearing, 4-35

—U—

Uploading automatic configuration, 4-55

User account policy, 6-28 adding, 6-21 administering, 6-3 audit policy, 6-30 Creating, 2-34 editing, 6-22 environment tool, 7-6 managing, 6-21 password policy, 6-26 remove, 6-24

User environment Defining, 2-36 testing, 7-9

Username, 3-20 Using

base profile, 6-9

—V—

View menu event browser, 5-6

—W—

WAN maps, 3-4 application rules, 3-6 general application rules, 3-6 moving between map windows, 3-7 root level rules, 3-6

Installation and Operation Manual Index

RADview-EMS/TDM (Unix) Ver. 1.7 I-5

root map level rules, 3-6 submap level rules, 3-6 terminology, 3-5

WAN submap creating, 3-9

—Z—

Zone, 1-7 Zoom applications

Java, 3-16, 3-22

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-EMS/TDM (Unix) Ver. 1.7

Publication Number: 357-279-01/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

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

Type of error(s) or problem(s):

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.

Distributor

End user

VAR

You are:

Other

Who is your distributor?

Your name and company:

Job title:

Address:

Direct telephone number and extension:

Fax number:

E-mail:

Publication No. 357-279-01/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 Innovative Access Solutions



radview-ems/tdm (unix) · radview-ems/tdm (unix) element management system for tdm applications...

Documents