radview-ems/ngn (unix) · solutions are client-server based systems that include “system”...

RADview-EMS/NGN (Unix)

Unix-Based Element Management System for NGN Applications

Version 1.8

USER

'S M

AN

UA

L

The Access Company

RADview-EMS/NGN (Unix) Unix-Based Element Management System for NGN

Applications

Version 1.8

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

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

© 1994–2008 RAD Data Communications Ltd. Publication No. 357-635-08/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/NGN (Unix) shall not exceed the sum paid to RAD for the purchase of the RADview-EMS/NGN (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.

Foreword

RADview, RAD’s network management software is a portfolio of integrated software suites that allows management of heterogeneous networks from a single console. The PC and Unix-based solutions are Client-Server based systems that include “System” software application that’s integrated with several “Agent” applications that enable management of individual elements within the network.

RADview-EMS/NGN (Unix) is a PC-based Element Management System (EMS) providing configuration, fault and performance management over SNMP. The modular Element Management System (EMS) implements the first three layers of the industry standard TMN model:

• Network element layer

• Element management layer

• Network management layer

The RADview solutions conform to ITU-T Telecommunication Management Network (TMN) recommendations for SNMP management systems, known as the FCAPS model:

• Fault management – detects and correlates fault in network devices, isolates faults and initiates recovery actions.

• Configuration management – tracks configuration changes, configures, installs and distributes software and configuration files across the network.

• Accounting management – collects accounting data and generates network usage reports.

• Performance management – continuously monitors network performance (QoS, CoS) and resource allocation.

• Security management – controls and restricts access to network resources.

In addition to this system manual, RAD provides separate user manuals for each of the SNMP agents supported by the RADview-EMS/NGN (Unix) system.

The table below details the FCAPS management functions.

Fault Configuration Accounting Performance Security

Alarm handling Map status color propagation

Viewing bundle statistics

Adding a new user

Viewing history log

Configuring Auto-discovery

Viewing Ethernet statistics

Changing users

Masking traps Configuring Status Polling

Viewing port statistics

Removing users

Viewing self-test results

Configuring Poll Intervals

Displaying the security log

Running loopbacks

Configuring SNMP parameters

Configuring Server Maps

Configuring Services

Creating a Net Hierarchy

Creating an agent for the RAD device

Adding a connection

Configuring Mesh Service

Configuring Normal Service

Adding sites

Adding Managed Elements

RADview-EMS/NGN (Unix) Ver. 1.8 i

Contents

Chapter 1. Introduction

1.1 Overview.................................................................................................................... 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-4 Territorial Distribution ........................................................................................ 1-5 Master/Slave Server Functions ............................................................................ 1-6

1.2 System Requirements ................................................................................................ 1-7 Hardware Requirements.......................................................................................... 1-7 Software Requirements .......................................................................................... 1-7

Chapter 2. Installation and Setup

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

Installing the Informix Database .............................................................................. 2-2 Installing the RADview-EMS Package ........................................................................ 2-3

Starting with the Initial Components ................................................................... 2-3 Continuing with RADview-EMS/NGN Installation .................................................. 2-7

Installing Additional PC Clients (Optional) .............................................................. 2-19 Creating Unix User ................................................................................................ 2-30 Defining the Unix User Environment ...................................................................... 2-31 Installing Licenses ................................................................................................. 2-33

2.3 Uninstalling the RADview Package ............................................................................ 2-34 Uninstalling RADview-EMS ..................................................................................... 2-34 Uninstalling the Informix Database ........................................................................ 2-35

Chapter 3. Operation

3.1 Running the HPOV Platform ........................................................................................ 3-1 Starting an HPOV Session........................................................................................ 3-2 Changing the HPOV Password ................................................................................. 3-2 Compiling Private RAD MIB ...................................................................................... 3-3 Ending the HPOV Session ........................................................................................ 3-4

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

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

Creating an Agent for a RAD Device ........................................................................ 3-9 Setting Selection Name and Selection Name Format ......................................... 3-11

Table of Contents User's Manual

ii RADview-EMS/NGN (Unix) Ver. 1.8

Setting Agent SNMP Parameters ....................................................................... 3-12 Deleting an Agent ............................................................................................ 3-14 Changing Agent Attributes................................................................................ 3-14

Monitoring Agents ................................................................................................ 3-15 Displaying Alarm Categories .................................................................................. 3-15

3.3 Running the EMS Application .................................................................................... 3-16 Starting/Stopping the EMS Server from the Command Line .................................... 3-18 Logging Into RADview-EMS .................................................................................... 3-18 Changing the EMS Password.................................................................................. 3-19 Logging Out of RADview-EMS ................................................................................ 3-20

3.4 Using the EMS GUI .................................................................................................... 3-20 Using the LaunchDesk Toolbar .............................................................................. 3-20 Using the EMS Consoles ........................................................................................ 3-21 Working with Network Elements ........................................................................... 3-24

Performing Hierarchy and Node Operations ...................................................... 3-25 Performing Agent Level Operations .................................................................. 3-34 Importing Nodes to the Network Element Browser ........................................... 3-41

Chapter 4. Configuration Management

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

4.2 Setting the EMS System Parameters ........................................................................... 4-4 Configuring Synchronization .................................................................................... 4-4 Configuring the NER Elements ................................................................................. 4-6

Adding an Entry ............................................................................................... 4-11 Renaming an Entry ........................................................................................... 4-11 Removing an Entry ........................................................................................... 4-11 Adding an Attribute .......................................................................................... 4-12 Modifying an Attribute ..................................................................................... 4-13 Removing an Attribute ..................................................................................... 4-13 Viewing Applied Changes .................................................................................. 4-14

4.3 Using Additional Applications ................................................................................... 4-15 Performing Backup and Restore ............................................................................ 4-15

Backup and Restore Requirements ................................................................... 4-15 Configuring Backup and Restore ....................................................................... 4-16 Configuring Backup and Restore Files ............................................................... 4-17 Backing Up System Components ....................................................................... 4-19 Restoring System Components ......................................................................... 4-20

Transferring Files Using TFTP ................................................................................. 4-22 Configuring the TFTP Server .............................................................................. 4-23 Opening the TFTP File Transfer Application ....................................................... 4-24 Changing the TFTP Default Settings .................................................................. 4-26 Editing the TFTP Database ................................................................................ 4-27 Selecting Nodes for TFTP .................................................................................. 4-37 Transferring Files Using TFTP ............................................................................ 4-40 Viewing TFTP File Transfer Reports ................................................................... 4-49 Saving the TFTP Database ................................................................................ 4-51 Using Help ....................................................................................................... 4-51 Exiting the Application ...................................................................................... 4-51

Performing Automatic Configuration Upload (ACU) ................................................ 4-52

User's Manual Table of Contents

RADview-EMS/NGN (Unix) Ver. 1.8 iii

Configuring the TFTP Server for ACU ................................................................. 4-52 Manually Starting or Stopping the ACU Server ................................................... 4-54 Launching the ACU Client Application ................................................................ 4-54 Summary of ACU Tasks ..................................................................................... 4-57 Configuring ACU TFTP Settings .......................................................................... 4-57 Configuring ACU Profiles ................................................................................... 4-58 Performing Immediate Configuration Upload ..................................................... 4-64 Working with the ACU Report Table .................................................................. 4-66 Accessing Help ................................................................................................. 4-77 Closing the ACU Client Application .................................................................... 4-78

Viewing the Net Inventory ..................................................................................... 4-78 Opening the Application ................................................................................... 4-78 Filtering the Display ......................................................................................... 4-81 Editing an Entity ............................................................................................... 4-82 Expanding/Collapsing Sublevels ......................................................................... 4-83

Licensing .............................................................................................................. 4-83 Network Size .................................................................................................... 4-84 Equivalent Node Weights (ENW) ....................................................................... 4-84 Bundled License Points ..................................................................................... 4-85 Calculating License Points ................................................................................. 4-85 Managing and Modifying Licenses ..................................................................... 4-86

Setting Net Date and Time .................................................................................... 4-94 Setting Net Date and Time ............................................................................... 4-95 Setting Automatic Update of Date and Time ..................................................... 4-96

Chapter 5. Performance Management

5.1 Monitoring Services and Processes ............................................................................. 5-2 Viewing EMS Server Process Information ................................................................. 5-5 Stopping/Starting a Service ..................................................................................... 5-7 Viewing the Server Tracing Configuration ................................................................ 5-9 Viewing the Java Name and Directory Service ........................................................ 5-12 Viewing the Informix Database Details .................................................................. 5-13 Viewing the CORBA Name Service .......................................................................... 5-15 Viewing the CORBA Event Service .......................................................................... 5-15 Viewing the EMS Log Service ................................................................................. 5-17 Viewing the EMS Element Network Repository ....................................................... 5-18 Viewing the EMS License Service ........................................................................... 5-19 Viewing the EMS Trap Listener .............................................................................. 5-19 Viewing the EMS Fault Management (Back End) ..................................................... 5-21 Viewing the EMS Fault Management (Front End) .................................................... 5-23 Viewing the EMS Polling Service ............................................................................. 5-24 Viewing the EMS Configuration Management ......................................................... 5-25 Viewing the EMS Security Service .......................................................................... 5-26 Viewing the EMS Discovery Service ........................................................................ 5-26 Viewing the EMS OSS Heartbeat Service ................................................................ 5-28

5.2 Additional Monitoring Options .................................................................................. 5-29 Viewing the RADview Package Contents ................................................................ 5-29 Monitoring SNMP Performance .............................................................................. 5-31

Filtering SNMP Requests and Traps ................................................................... 5-32 Reconnecting ................................................................................................... 5-34

Tracing Log Events ................................................................................................ 5-34

Chapter 6. Security Management


iv RADview-EMS/NGN (Unix) Ver. 1.8

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

Managing Security Profiles ...................................................................................... 6-2 Basic Permissions ............................................................................................... 6-4 Manually Loading Security Profiles ...................................................................... 6-9 Adding a New Profile ........................................................................................ 6-10 Using a Base Profile ......................................................................................... 6-12 Adding a Profile with No Base Profile ................................................................ 6-13 Working with Permissions ................................................................................. 6-14 Adding a Profile with No base Profile ................................................................ 6-22 Editing a Profile ................................................................................................ 6-25 Removing a Profile ........................................................................................... 6-25

Managing EMS Users ............................................................................................. 6-26 Adding a User .................................................................................................. 6-26 Editing a User ................................................................................................... 6-27 Changing a User’s Password ............................................................................. 6-28 Removing a User .............................................................................................. 6-29

Administering Login Names ................................................................................... 6-29 Defining the Active Login Names ...................................................................... 6-29 Performing Administrator Logout of User ......................................................... 6-30

Configuring Security Options ................................................................................. 6-31 Setting Password Policies ................................................................................. 6-31 Setting Account Policies ................................................................................... 6-33 Setting Audit Policies ........................................................................................ 6-34

Chapter 7. Fault Management

7.1 Handling EMS Device Events ....................................................................................... 7-1 Configuring the Event Browser ................................................................................ 7-1 Setting Parameters for the Event Browser Log ........................................................ 7-3

Setting Event Policies ......................................................................................... 7-5 Defining SNMP Trap Forwarding Destinations ................................................... 7-23 Defining Fault Clearance Procedures ................................................................. 7-25

Viewing EMS Device Events ................................................................................... 7-29 Terminology ..................................................................................................... 7-30 Toolbar Icons ................................................................................................... 7-32 Working with Filters ......................................................................................... 7-32 Refreshing Event Display .................................................................................. 7-34 Selecting Events ............................................................................................... 7-35 Acknowledging and Rejecting Events ................................................................ 7-35 Viewing Event Details ....................................................................................... 7-36 Entering Event Notes........................................................................................ 7-37 Filtering Events ................................................................................................ 7-40

7.2 Handling RADview-EMS Events ................................................................................. 7-52 Configuring the EMS Log Service ........................................................................... 7-52 Viewing RADview-EMS Events ................................................................................ 7-53

Setting the Log Display .................................................................................... 7-54 Saving, Printing, or Deleting Logs ..................................................................... 7-56

7.3 Testing the Unix User Environment ........................................................................... 7-58 Testing with User Environment Tool ...................................................................... 7-58 Testing with Commands ........................................................................................ 7-61

7.4 Frequently Asked Questions ..................................................................................... 7-63 7.5 Technical Support .................................................................................................... 7-67

User's Manual Table of Contents

RADview-EMS/NGN (Unix) Ver. 1.8 v

Appendix A. Migration Guide

Index


vi RADview-EMS/NGN (Unix) Ver. 1.8

RADview-EMS/NGN (Unix) Ver. 1.8 Overview 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/NGN (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/NGN (Unix) system is dedicated for managing products installed in next-generation network (NGN) environments.

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.

Table 1-1. RADview-EMS Management Functions

Fault Configuration Accounting Performance Security

Alarm handling Provisioning Not implemented Real-time statistics

presentation

Control NE access

Chapter 1 Introduction User’s Manual

1-2 Overview RADview-EMS/NGN (Unix) Ver. 1.8

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/NGN (Unix) package includes agents for the following products:

• ACE-201

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

• ACE-52

• ETX-102

• ETX-201

• ETX-202

• ETX-202A

• IPmux-2L

• LA-104

• LA-110

User’s Manual Chapter 1 Introduction


• LA-130

• LA-210

• RICi-16

• Vmux-4x5 – Vmux-405 and Vmux-425.

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.

Note



Client/Server Distribution

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

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 – the client and server are installed either in standalone mode or over the same copy of SNMPc.

• Distributed system – the client and server are installed on separate computers.

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

Note



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

Territorial Distribution

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



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

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

Distribution.

Each Slave server runs its own set of services.


RADview-EMS/NGN (Unix) Ver. 1.8 System Requirements 1-7

1.2 System Requirements

RADview-EMS/NGN (Unix) package version 1.8 can be installed on a Unix platform that is compatible with HP OpenView, according to the following hardware and software requirements.

Hardware Requirements

The following are the hardware requirements for networks containing up to 300 managed elements:

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

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

• Hard drive with at least 600 MB free for Informix (in any partition)

• 2 GB RAM

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

• For each four additional simultaneous users via X-session, add 1 GB RAM and 1 CPU

If you are using the EMS client on a different workstation than the RADview system, you do not need to add RAM or CPU.

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

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

• DVD drive.

For larger networks containing more than 300 managed elements, see FAQ 1168 at the RAD Technical Support website.

Software Requirements

The following software is required:

• SUN Solaris Version 10, Nov 2006 or later

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

• CDE 1.4 or higher

• HP OpenView NNM Version 7.5 or later

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

Note

Note

Note


1-8 System Requirements RADview-EMS/NGN (Unix) Ver. 1.8

RADview-EMS/NGN (Unix) supports only Solaris Version 10 (released in November 2006). Previous versions are no longer supported. For example, Versions 2.5.1, 2.6, 2.7, and 2.8 are not supported.

Note

RADview-EMS/NGN (Unix) Ver. 1.8 Installation 2-1

Chapter 2

Installation and Setup RADview-EMS/NGN (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/NGN (Unix) package includes the following items:

• RADview-EMS/NGN (Unix) Installation DVD

• RADview-HPOV database (Informix) CD

• RADview-EMS PC Client Installation CD

• Installation guide

• Technical documentation CD.

2.2 Installation

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

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

1. Installing the Informix Database

2. Installing the RADview-EMS

3. Installing Additional PC Clients (Optional).

Notes

Note

Chapter 2 Installation and Setup User’s Manual

2-2 Installation RADview-EMS/NGN (Unix) Ver. 1.8

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

Installing the Informix Database

RADview-EMS/NGN (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/DVD drive.

4. Type: cd /cdrom/cdrom0/informix

5. Type: ./informix.install

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

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

7. When prompted, confirm the system reboot.

Figure 2-1. Informix Installation, Starting

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

9. Type: csh

10. Type: cd /cdrom/cdrom0/informix

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

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

Note

Note

User’s Manual Chapter 2 Installation and Setup


Figure 2-2. Informix Installation, Completing

Installing the RADview-EMS Package

Once the Informix database has been 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/NGN (Unix) Installation DVD into the DVD drive.

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

5. Verify that Informix is running by typing:

onstat –

If Informix is online the following message appears:

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

Note



6. Type: ./install_gui.rad

A warning to not interrupt the installation is displayed, with the RADview Installation Product List behind it.

Figure 2-3. RADview Installation Warning

Figure 2-4. RADview Installation Product List

7. In the warning dialog box, click <OK>.

The warning dialog box closes.



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

The bullets next to the products that you selected are colored green, and the Informix installation directory confirmation dialog box is displayed.

Figure 2-5. RADview Installation Confirmation

9. Perform one of the following:

If the displayed Informix installation directory is correct, click <Yes> and skip to step 11.

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

A dialog box prompts you for the correct Informix Installation path.

Figure 2-6. Informix Path Dialog Box

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

If the path is correct, the installation continues; skip to step 11.

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 in the Informix Path Dialog Box.

Figure 2-7. Incorrect Informix Installation Directory Dialog Box



11. Once the Informix installation directory has been confirmed, the initial EMS product components are installed and an installation message appears in the Installation Data window of the RADview Installation Product List.


If this is an upgrade of an existing installation, a message box appears that prompts for 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-9. RADview Installation – Upgrade Dialog Box

Note



Continuing with RADview-EMS/NGN Installation

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

Figure 2-10. EMS Setup – Welcome Dialog Box

To continue with the RADview-EMS NGN installation:

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

The Select Installation Type dialog box is displayed.



Figure 2-11. EMS Setup – Select Installation Type

2. Select Server and Client.

• Server Only is an option for 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-19.

3. Click <Next>.

The Select Installation Method dialog box is displayed.

Note



Figure 2-12. EMS Setup – Select Installation Method

4. Choose the installation type:

Typical – for installation with the default settings.

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

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

5. Click <Next>.

The General Information dialog box is displayed.

Note



Figure 2-13. 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>.

Once the OS international information is loaded:

If this is an Advanced installation, the International Settings dialog box is displayed (Figure 2-14).

If this is a Typical installation and the EMS server is not yet installed on this station, the Database Settings dialog box is displayed (Figure 2-17), and you should skip to step 13 of this procedure.

If this is a Typical installation and the EMS Server is already installed on this station, the Install Summary dialog box is displayed (Figure 2-19) and you should skip to step 15 of this procedure.



Figure 2-14. 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 correct 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 Database Selection dialog box is displayed.

Note



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

10. Select one of the following target database servers:

Oracle Database Server

IBM Informix Server.

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

11. Click <Next>.

The Connecting to Database screen is displayed.

Note



Figure 2-16. Connecting to the Database

After the connection to the database is established, the Database Settings dialog box is displayed.



Figure 2-17. 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>.

Notes



If a new Database is created, a warning message is displayed that your Database Information will be lost if you continue.

Figure 2-18. Warning Message

14. Click <OK>.

The Installation Summary dialog box is displayed.

Figure 2-19. Installation Summary Dialog Box

15. Click <Next>.

The Installation Progression dialog box is displayed.



Figure 2-20. Installation in Progress

16. When installation completes, the Installation Completed dialog box is displayed.



Figure 2-21. Installation Completed

17. Click <Finish>.

In the RADview Installation Product List, Installation Done appears in green in the middle of the RADview-EMS/NGN (Unix) Installation dialog box and Success appears at the bottom of the dialog box.




18. Type: init 6 to reboot the system.

RADview-EMS is fully installed and ready for use.



Installing Additional PC Clients (Optional)

If 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. You do not need to install RADview Shell on the client, only RADview-EMS NGN.

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

To install the client on the PC station:

1. Insert the RADview-EMS/NGN (PC) Installation CD into the CD/DVD drive.

The RADview-EMS NGN Setup window is displayed.

Figure 2-23. RADview-EMS NGN Setup Window

2. In the RADview-EMS NGN Setup Dialog Box, click RADview-EMS NGN.

The Welcome dialog box is displayed.

Note



Figure 2-24. EMS Setup – Welcome Dialog Box

3. Click <Next>.

The Select Installation Type dialog box is displayed.



Figure 2-25. EMS Setup – Select Installation Type

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

The SNMPc Configuration Warning dialog box is displayed.



Figure 2-26. SNMPc Configuration Warning – Select MIB Option

5. Select Overwrite current MIBs and event policies to let the new MIBs replace your current MIBs.

6. Click <Next>.

The Select Products dialog box is displayed.



Figure 2-27. EMS Setup – Select Products

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

The Select Installation Method dialog box is displayed.



Figure 2-28. EMS Setup – Select Installation Method

8. Select the installation type:

Typical – for installation with the default settings

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

9. Click <Next>.

The General Information dialog box is displayed.



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

10. Enter the following:

Zone Name: Type the zone name for the client station, or leave blank.

Area Name: Type the area name for the client station, or leave blank.

Station Name: Type the Host Name of the Client Station.

Master Server Address: Type the IP address of the Master Server Unix Station.

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

11. Click <Next>.

One of the following occurs:

If this is an Advanced installation, the International Settings dialog box is displayed (Figure 2-30).

If this is a Typical installation, the Installation Summary dialog box is displayed (Figure 2-31) and you should skip to step 13 of this procedure.

Note



Figure 2-30. International Settings Dialog Box

12. 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 RAD cannot guarantee its correct 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 Installation Summary dialog box is displayed.

Note



Figure 2-31. EMS Setup – Installation Summary

13. Click <Next>.

The installation starts, and the Installation Progression dialog box is displayed.



Figure 2-32. Installation in Progress

14. When the installation completes, the Installation Complete dialog box is displayed.



Figure 2-33. EMS Installation Complete

15. Click <Finish>.

16. A message is displayed informing you that RADview License Manager will be installed, and asking whether you want to install RADview License Server too.

Figure 2-34. Autorun Message Box

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

18. Return to the RADview-EMS NGN Setup dialog box (Figure 2-23) and click <Exit>.

19. The Restart Confirmation dialog box appears stating that you must restart your computer for the installation to take effect.



Figure 2-35. Restart Confirmation

20. , Click <Restart> to restart your computer.

Once the restart is completed, RADview-EMS NGN is fully installed and ready for use on the PC client.

Creating Unix User

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

To create a Unix 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.

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-36. Reviewing the New User Details

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

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

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

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

14. Log in as the newly created user.

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

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

17. Save the .cshrc file.

Defining the Unix User Environment

The RADview post-installation user environment tool automates all post-installation procedures and completes the installation of RADview



UNIX-based products. The script is written in csh. It can be used by both a new user and an existing user to test the user environment.

To set the user environment for a new user:

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

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

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

* RADview User Environment *

* *

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

* a dedicated RADview-HPOV installation. *

* *

* This script sets the User Environment variables for a *

* newly created user and performs User Environment tests *

* for an existing user. *

* *

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

* *

* This script must run under csh environment only. *

* *

* User Environment variables are written into the *

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

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

Setting User Environment for a new RADview user...

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

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

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

Installing Licenses

Each RADview license is associated with a single management station. This station is identified by its host ID for UNIX-based stations or its IP/MAC address for Windows-based stations. If you do not know for which host ID to obtain the license, refer to Frequently Asked Questions in Chapter 7, or to FAQ 6171 at the RAD Technical Support website.

If you need a RADview license for your RADview package, you can activate it at the RAD Value Point website (via MyRAD or the Customer Information application). You can also add license points at the RAD Value Point website. For details on using RAD Value Point, refer to FAQ 4828 at the RAD Technical Support website.

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

To install a license:

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

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

The HPOV Root window appears.

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

The Login dialog box appears.

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

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

6. Select File > Add License.

The Open License File dialog box appears.


2-34 Uninstalling the RADview Package RADview-EMS/NGN (Unix) Ver. 1.8

Figure 2-38. Open License File Dialog Box

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

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

2.3 Uninstalling the RADview Package

Uninstalling RADview-EMS

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.

Note


RADview-EMS/NGN (Unix) Ver. 1.8 Uninstalling the RADview Package 2-35

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 Informix Database

To uninstall the Informix database:

1. Log in as su

2. Type: csh

3. Type: setenv INFORMIXDIR <informix home directory> where <informix home directory> is the Informix home directory, e.g. /export/home/Informix.

4. Type: <informix home directory>/i_uninstall

5. Type y in the three consecutive confirmation messages that appear.

6. Remove the directory <informix home directory>.

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


2-36 Uninstalling the RADview Package RADview-EMS/NGN (Unix) Ver. 1.8

RADview-EMS/NGN (Unix) Ver. 1.8 Running the HPOV Platform 3-1

Chapter 3

Operation This chapter describes the following activities:

• Running the HPOV Platform

• Using the HPOV GUI

• Running the EMS Application

• Logging Out of RADview-EMS

• Ending the HPOV Session.

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 working with the HPOV environment:

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

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

The HPOV Root window appears.

Figure 3-1. HPOV Root Window

Chapter 3 Operation User’s Manual

3-2 Running the HPOV Platform RADview-EMS/NGN (Unix) Ver. 1.8

Starting an HPOV Session

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

To log in to the HPOV environment:

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


Figure 3-2. Login Dialog Box

2. Type your User Name and Password.

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

3. Click <OK>.

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

Figure 3-3. Access Denied Dialog Box

Changing the HPOV Password

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

To change the HPOV user password:

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


2. Click <Change Password>.

User’s Manual Chapter 3 Operation

RADview-EMS/NGN (Unix) Ver. 1.8 Running the HPOV Platform 3-3

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

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

2. Insert the RADview-EMS/NGN (Unix) installation DVD into the DVD drive.

3. Type: cd /cdrom/cdrom0

4. Open a separate terminal window and 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, click <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.


3-4 Using the HPOV GUI RADview-EMS/NGN (Unix) Ver. 1.8

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.

Ending the HPOV Session

Once you have logged out of RADview-EMS (see Logging 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-5. HPOV Logout Dialog Box

2. Click <OK>.

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

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

Note


RADview-EMS/NGN (Unix) Ver. 1.8 Using the HPOV GUI 3-5

•

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

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, that can be accessed by right-clicking the mouse.

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

An alarm window is used to display traps and event messages that arrive from active network elements. The following possible event lists are available: Error Alarms, Threshold Alarms, Status Alarms, Configuration Alarms, Application Alert Alarms, Problem Diagnostics Alarms and 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 in the Root map. Double-clicking this icon displays the top level of the WAN map hierarchy.

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

• WAN Submap icon – Icon in 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.

Note



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

Map Application Rules

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

• General WAN Application level

• Root level

• WAN Root Map level

• WAN Submap level

• Connection level.

General WAN Application Rules

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

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

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

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

Root Level Rules

The following rules apply to the HPOV root map:

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

• You cannot delete the WAN root submap icon.

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

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

Note



• 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-6. Network Object Palette

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

Creating an Agent for a RAD Device

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

To define an object for a RAD device:

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

2. From the Edit menu, select Add Object .

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

Figure 3-7. Connector Palette for the Device Agent (ACE Family)



Figure 3-8. Connector Palette for the Device Agent (ETX and LA Family)

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

4. Hold down the 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-9. 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 RADview-HPOV.

Setting Selection Name and Selection Name Format

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

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

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

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



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.

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

To access the SNMP Configuration screen as root user:


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

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

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

To access the SNMP Configuration screen as regular user:

• From the Options menu, select SNMP Configuration.


Note



Figure 3-10. 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.

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

A delete confirmation dialog box appears.

Figure 3-11. Confirm Delete

3. Click <OK> to confirm the deletion.

Changing Agent Attributes

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

To modify a map object:

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

2. Select Object Properties > General Attributes.



The Symbol Description dialog box 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 Alarm 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-12).

Figure 3-12. Alarm Categories Dialog Box

To display the alarm list:

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

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


3-16 Running the EMS Application RADview-EMS/NGN (Unix) Ver. 1.8

Figure 3-13. All Alarms Browser

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-NGN/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) 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/S98RvEmsServer start

The EMS features become available.

3. Type exit to exit superuser mode.

4. In the terminal window, type ovw&

The HPOV Map, EMS LaunchDesk, and EMS Login appear.

Note


RADview-EMS/NGN (Unix) Ver. 1.8 Running the EMS Application 3-17

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

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

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

If you encounter any problems with the HPOV colors when opening windows using the EMS icons (LaunchDesk), change the graphics card’s screen resolution depending on your hardware. For example:

1. Log in as: su

2. Type: m64config –res 1152x900 –depth 24

3. Exit and re-enter the CDE session.

Note


3-18 Running the EMS Application RADview-EMS/NGN (Unix) Ver. 1.8

Figure 3-15. Application Manager Window

Starting/Stopping the 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. Type /etc/rc3.d/S98RvEmsServer start to start the server,

Or –

Type /etc/rc3.d/S98RvEmsServer stop to stop the server.

Logging Into RADview-EMS

To login from LaunchDesk:

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

The RADview-EMS LaunchDesk toolbar appears.

Figure 3-16. RADview EMS LaunchDesk Toolbar

2. Click in the EMS LaunchDesk toolbar.

The EMS Login dialog box appears.

Figure 3-17. EMS Login Dialog Box


RADview-EMS/NGN (Unix) Ver. 1.8 Running the EMS Application 3-19

The following points apply to EMS login:

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

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

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

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

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

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

Figure 3-18. EMS LaunchDesk after Login

4. Select any function in the LaunchDesk toolbar.

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

The new password takes effect immediately.

Notes


3-20 Using the EMS GUI RADview-EMS/NGN (Unix) Ver. 1.8

•

The password must be between four and eight characters. Only letters and numbers are valid characters. At least two characters must be letters and at least two characters must be numbers.

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 message is displayed in the LaunchDesk status bar).

To manually log out:

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

The LaunchDesk displays the Logged Out status.

Figure 3-20. Launch Desk Toolbar after Logout

3.4 Using the EMS GUI

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.

Note


RADview-EMS/NGN (Unix) Ver. 1.8 Using the EMS GUI 3-21

Figure 3-21. 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.

Using the EMS Consoles

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

• NER Explorer (refer to Chapter 4 for details)

• Security Service (refer to Chapter 6 for details)

• Log Admin (refer to Chapter 7 for details)

• Fault Service (refer to Chapter 7 for details).

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:

1. In the LaunchDesk toolbar, click the Admin Console icon .

The EMS Admin Console is displayed showing the NMS station name.

Note



Figure 3-22. EMS Admin Console Opening Window

2. Click the expansion icon next to the NMS station name to expand the Admin Console.

The list of EMS consoles is displayed.



Figure 3-23. EMS Admin Console Opening Window after Expanding

Figure 3-24. Admin Console – File Menu

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.



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.

Working with Network Elements

The Network Element Browser shows the hierarchies (submaps) and nodes (network elements) in the EMS network.

To open the Network Element Browser:

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

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

Figure 3-25. Network Element Browser

Each node has an icon with a symbol and color that indicate the most severe status of the nodes under that hierarchy.

Table 3-1. Network Element Browser Status Icons

Icon Color Status

Green Normal

Blue Warning

Yellow Minor

Orange Major

Note



Icon Color Status

Red Critical

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

non-existing IP address)

Performing Hierarchy and Node Operations

The following operations can be performed on hierarchies:

• Properties – Configure the properties of the current hierarchy and, if desired, all subordinate hierarchies and nodes

• Add Node – Add a node to the current hierarchy

• Add Nodes – Add range of IP addresses as nodes to the current hierarchy. You can add only nodes that are connected, and/or only RAD devices, or add the range without any connectivity checks.

• Add Hierarchy – Add a hierarchy under the current hierarchy

• Remove – Remove the current hierarchy and all subordinate hierarchies (this option is not available at the highest hierarchy)

• Refresh – Update the hierarchy with the latest configuration.

To configure the hierarchy properties in the Network Element Browser:

1. Right-click the selected hierarchy and choose Properties.

The Hierarchy Properties dialog box is displayed (see Figure 3-26 to Figure 3-29). It contains the following tabs:

General tab – Defines the hierarchy’s name and the default double-click action for nodes in the hierarchy. Refer to Figure 3-26 and Table 3-2 for a description of the parameters.

SNMP tab – Specifies the SNMP parameters of the hierarchy and, if desired, all subordinate hierarchies and nodes. Refer to Figure 3-27 and Table 3-3 for a description of the parameters.

SNMPv3 tab – Specifies the SNMPv3 parameters of the hierarchy and, if desired, all subordinate hierarchies and nodes. Refer to Figure 3-28 and Table 3-4 for a description of the parameters.

External Tools tab – Defines default command parameters for external tools for nodes in the hierarchy. Refer to Figure 3-29 and Table 3-5 for a description of the parameters.

2. Click <Set>.

The hierarchy and, if selected, all subordinate hierarchies and nodes, are configured with the new properties.



Figure 3-26. Hierarchy Properties Dialog Box – General Tab

Figure 3-27. Hierarchy Properties Dialog Box – SNMP Tab

Figure 3-28. Hierarchy Properties Dialog Box – SNMPv3Tab

Figure 3-29. Hierarchy Properties Dialog Box – External Tools Tab

Table 3-2. Hierarchy General Parameters

Parameter Function Possible Values

Hierarchy Name Name of hierarchy

Default double-click

action

Specifies default double-click action,

used for default node properties when

new nodes are added to the hierarchy

Zoom: Open zoom

application

Web Browser: Connect to

node via Web browser

Telnet: Connect to node

via Telnet.



Table 3-3. Hierarchy SNMP Parameters

Parameter Function

Read Community SNMP Read request community

Write Community SNMP Write request community

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

Retries The SNMP number of retries for the hierarchy

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

Apply changes to subnodes

and subhierarchies

Select to apply the same changes to all hierarchies

and nodes subordinate to this hierarchy

Note: This parameter is available only in the Hierarchy Properties dialog box.

Table 3-4. Hierarchy SNMPv3 Parameters


Access Mode SNMP version used for hierarchy

Note: If V1 is selected, the rest of the SNMPv3 parameters are not available.

V1 – SNMPv1

USM – SNMPv3 (User

Security Model)

User Name SNMPv3 user

Authentication

Protocol

Authentication protocol to use

No Authentication – No

authentication is performed

MD5 – The authentication

protocol MD5 is used

SHA – The authentication

protocol SHA is used

Authentication

Password

Authentication password

Note: This parameter is available only if Authentication Protocol is not set to No Authentication.

Privacy Protocol Privacy (encryption) protocol to use

No Privacy – No encryption

is performed

DES – The privacy protocol

DES is used

Privacy Password Privacy (encryption) password

Note: This parameter is available only if Privacy Protocol is not set to No Privacy.

Context String that identifies the SNMPv3

information



Table 3-5. Hierarchy External Tool Parameters


Menu Option Specifies for which external tool

to define the command

parameters

Ping – Define the command line

and parameters for sending ping

to node

Trace Route – Define the

command line and parameters for

tracing route to node

Command Line Defines the command line for the

external tool, used for default

node properties when new nodes

are added to the hierarchy

Note: This parameter is read-only.

Command

Parameters

Defines the command parameters

for the external tool, used for

default node properties when

new nodes are added to the

hierarchy

To add a hierarchy to the Network Element Browser:

1. Right-click the selected hierarchy in the Network Element Browser and choose Add Hierarchy.

The Add Hierarchy dialog box is displayed (see Figure 3-30 to Figure 3-33). It contains the following tabs:

General tab – Defines the hierarchy’s name and the default double-click action for nodes in the hierarchy. Refer to Figure 3-30 and Table 3-2 for a description of the parameters.

SNMP tab – Defines the SNMP parameters of the hierarchy and, if desired, all subordinate hierarchies and nodes. Refer to Figure 3-31 and Table 3-3 for a description of the parameters.

SNMPv3 tab – Defines the SNMPv3 parameters of the hierarchy and, if desired, all subordinate hierarchies and nodes. Refer to Figure 3-32 and Table 3-4 for a description of the parameters.

External Tools tab – Defines default command parameters for external tools for nodes in the hierarchy. Refer to Figure 3-33 and Table 3-5 for a description of the parameters.

2. Click <Set>.

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



Figure 3-30. Add Hierarchy Dialog Box – General Tab Figure 3-31. Add Hierarchy Dialog Box – SNMP Tab

Figure 3-32. Add Hierarchy Dialog Box – SNMPv3Tab Figure 3-33. Add Hierarchy Dialog Box – External ToolsTab

To remove a hierarchy from the Network Element Browser:

• Right-click the selected hierarchy in the Network Element Browser and choose Remove.

The hierarchy, and all subordinate hierarchies and nodes, are removed from the Network Element Browser.

To refresh a hierarchy in the Network Element Browser:

• Right-click the selected hierarchy in the Network Element Browser and choose Refresh.

The hierarchy, and all subordinate hierarchies and nodes, are refreshed with the latest configuration.



To add a node to a hierarchy in the Network Element Browser:

1. Right-click the selected hierarchy and choose Add Node.

The Add Node dialog box is displayed (see Figure 3-34 to Figure 3-37). It contains the following tabs:

General tab – Defines general node parameters. Refer to Figure 3-34 and Table 3-6 for a description of the parameters.

SNMP tab – Defines the SNMP parameters of the node. Refer to Figure 3-35 and Table 3-7 for a description of the parameters.

SNMPv3 tab – Defines the SNMPv3 parameters of the node. Refer to Figure 3-36 and Table 3-8 for a description of the parameters.

External Tools tab – Defines default command parameters for external tools. Refer to Figure 3-37 and Table 3-9 for a description of the parameters.

2. Click <Set>.

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

Figure 3-34. Add Node Dialog Box – General Tab Figure 3-35. Add Node Dialog Box – SNMP Tab



Figure 3-36. Add Node Dialog Box – SNMPv3 Tab Figure 3-37. Add Node Dialog Box – External Tools Tab

Table 3-6. Node General Parameters


Node Name Name of node

IP Address IP address of node


action

Specifies action to take when node is

double-clicked. The default is the

action that was defined for the

hierarchy, but you can specify a

different action for the node if you

wish.

Zoom: Open zoom

application




via Telnet.

Table 3-7. Node SNMP Parameters

Parameter Function

Read Community SNMP Read request community

Write Community SNMP Write request community

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

Retries The SNMP number of retries for the node(s)

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

Table 3-8. Node SNMPv3 Parameters


Access Mode SNMP version used for node

Note: If V1 is selected, the rest of the SNMPv3 parameters are not available.

V1 – SNMPv1

USM – SNMPv3 (User

Security Model)

User Name SNMPv3 user

Authentication

Protocol

Authentication protocol to use

No Authentication – No

authentication is performed

MD5 – The authentication

protocol MD5 is used

SHA – The authentication

protocol SHA is used

Authentication

Password

Authentication password

Note: This parameter is available only if Authentication Protocol is not set to No Authentication.

Privacy Protocol Privacy (encryption) protocol to use

No Privacy – No encryption

is performed

DES – The privacy protocol

DES is used




Privacy Password Privacy (encryption) password

Note: This parameter is available only if Privacy Protocol is not set to No Privacy.

Context String that identifies the SNMPv3

information

Table 3-9. Node External Tool Parameters


Menu Option Specifies for which external tool

to define the command

parameters

Ping – Define the command line

and parameters for sending ping

to node

Trace Route – Define the

command line and parameters for

tracing route to node

Command Line Defines the command line for the

external tool

Note: This parameter is read-only.

Command

Parameters

Defines the command parameters

for the external tool

To add a range of nodes to a hierarchy in the Network Element Browser:

1. Right-click the selected hierarchy and choose Add Nodes.

The Add Nodes dialog box is displayed (see Figure 3-38 to Figure 3-41). It contains the following tabs:




External Tools tab – Defines default command parameters for external tools. Refer to Figure 3-41 and Table 3-9 for a description of the parameters.

2. Click <Set>.

The range of nodes is configured with the new properties and added to the selected hierarchy.



Figure 3-38. Add Nodes Dialog Box – General Tab Figure 3-39. Add Nodes Dialog Box – SNMP Tab

Figure 3-40. Add Nodes Dialog Box – SNMPv3 Tab Figure 3-41. Add Nodes Dialog Box – External Tools Tab



Table 3-10. Add Nodes General Parameters


From Specifies starting IP address for

range of nodes to add

To Specifies ending IP address for

range of nodes to add


action

Specifies action to take when

node is double-clicked. The

default is the action that was

defined for the hierarchy, but you

can specify a different action for

the range of nodes if you wish.

Zoom: Open zoom

application




via Telnet.

Add only connected

devices

If selected, only devices that

respond to SNMP request for OID

are added

Selected or cleared

Add only RAD devices If selected, only devices whose

OIDs identify them as RAD devices

are added

Note: This option can be selected only if the option Add only connected devices is selected.

Selected or cleared

Ping Timeout Specifies timeout value for ping in

milliseconds

Note: This parameter is relevant only if the option Add only connected devices is selected. It is recommended to set it to a value between 100 and 500.

1– 4,294,967,296

Performing Agent Level Operations

The Network Element Browser - Node menu offers the following operations (see Figure 3-42):

• Properties – Configures the properties of the node

• Zoom – Opens the agent zoom application

• Web Browser –Connects to agent via Web browser

• Telnet – Connects to agent via Telnet

• External Tools –Opens a submenu for sending ping to agent or tracing route to agent

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



Figure 3-42. Network Element Browser – Node Menu

To configure the node properties in the Network Element Browser:

1. Right-click the selected node in the Network Element Browser and choose Properties.

The Properties dialog box is displayed (see Figure 3-43 to Figure 3-47). It contains the following tabs:




External Tools tab – Defines default command parameters for external tools. Refer to Figure 3-46 and Table 3-9 for a description of the parameters

Details tab – Displays the details of the node as configured in the agent device. Refer to Figure 3-47 and Table 3-11 for a description of the node details.

2. Click <Set>.

The node is configured with the new properties.



Figure 3-43. Node Properties Dialog Box – General Tab Figure 3-44. Node Properties Dialog Box – SNMP Tab

Figure 3-45. Node Properties Dialog Box – SNMPv3 Tab Figure 3-46. Node Properties Dialog Box – External Tools Tab



Figure 3-47. Node Properties Dialog Box – Details Tab

Table 3-11. Node Details

Parameter Function

Name Displays name configured in agent device

Description Displays agent description from agent device

Contact Displays contact information configured in agent device

Location Displays location information configured in agent device

To connect to node device via zoom application:

• Right-click the node in the Network Element Browser and choose Zoom, or double-click the node (if the node default double-click action is set to Zoom).

If there is not already a zoom application open for the agent, the agent zoom application appears (see Figure 3-48). For more information about a device-specific zoom application, refer to the specific RADview agent (device/module) user's manual (bundled with this system user manual).



Figure 3-48. Agent Zoom Application

If there is a zoom application already open for the device, you are given the choice of opening the zoom application in read-only mode or in read-write mode, or of cancelling the open, since only one user at a time can have the zoom application open in read-write mode.

Figure 3-49. Agent Application Already Open

If you choose to open the zoom application in read-write mode, the user that has it already opened receives a warning message that you have taken read-write access. The other user now has read-only access.

Figure 3-50. Warning That Other User Has Taken Read-Write Access

To connect to node device via Web browser:

• Right-click the node in the Network Element Browser and choose Web Browser, or double-click the node (if the node default double-click action is set to Web Browser).



A Web browser login window appears for the agent (see Figure 3-51). For more information about configuring a particular device via Web browser, refer to the device Installation and Operation manual.

Figure 3-51. Web Browser Connection to Agent

To connect to node device via Telnet:

• Right-click the node in the Network Element Browser and choose Telnet, or double-click the node (if the node default double-click action is set to Telnet).

A Telnet login window appears for the agent (see Figure 3-51). For more information about configuring a particular device via Telnet, refer to the device Installation and Operation manual.



Figure 3-52. Telnet Connection to Agent

You can quickly view system information and alarm status for an agent by positioning the mouse over the node in the Network Element Browser, until a tooltip appears that displays the device information (see Figure 3-53).

Figure 3-53. Tooltip for Node

To poll a node in the Network Element Browser:

• Right-click the selected node in the Network Element Browser and choose Poll.

The node’s device is polled.

To synchronize a node in the Network Element Browser:

• Right-click the selected node in the Network Element Browser and choose Synchronize.

The node’s HPOV map details are updated.

To remove a node from the Network Element Browser:

• Right-click the selected node in the Network Element Browser and choose Remove.

The node is removed from the Network Element Browser.

Note



To refresh a node in the Network Element Browser:

• Right-click the selected node in the Network Element Browser and choose 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:

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

The Import Nodes menu is displayed.

Figure 3-54. Import Nodes menu

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

1. From the Import Nodes menu (see Figure 3-54), click Import nodes.

The Import Nodes from HP OpenView dialog box is displayed.

Figure 3-55. 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 3-54), click Import All nodes.

All nodes are added to the Network Element Browser.

To stop importing nodes to the Network Element Browser:

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

Note

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

Chapter 4

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

• Setting the HPOV System Parameters (see Section 4.1)

• Setting the EMS System Parameters (see Section 4.2)

• Using Additional Applications, which include:

Performing Backup and Restore

Transferring Files Using TFTP

Performing Automatic Configuration Upload (ACU)

Viewing the Net Inventory

Licensing

Setting Net Date and Time.

4.1 Setting the HPOV System Parameters

Setting the HPOV system parameters includes the following.

• Propagating the HPOV Map Status Color

• Disabling AutoDiscovery

• Disabling Automatic Deletion

• Setting Polling Interval, Timeouts, and Retries.

Propagating the HPOV Map Status Color

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

To set HPOV Map status color propagation:

1. From the HPOV Map menu, click Properties.

2. In Compound Status, select Propagate Most Critical.

Chapter 4 Configuration Management User’s Manual

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

Disabling AutoDiscovery

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

To disable autodiscovery :

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

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

Disabling Automatic Deletion of Nodes

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

To disable the delete nodes option:

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

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

Setting 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. Set the desired polling interval. The default polling interval is five minutes

3. Click <Set>.

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

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

To access the SNMP Configuration screen as root user:



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


Note

User’s Manual Chapter 4 Configuration Management

RADview-EMS/NGN (Unix) Ver. 1.8 Setting the HPOV System Parameters 4-3

To access the SNMP Configuration screen as regular user:

• Select SNMP Configuration from the Options menu.


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

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

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

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

4. In the Timeout field, type 10.0.

5. In the Retry count field, type 2.

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

Figure 4-1. SNMP Configuration Window


4-4 Setting the EMS System Parameters RADview-EMS/NGN (Unix) Ver. 1.8

4.2 Setting the EMS System Parameters

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

Configuring Synchronization

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


RADview-EMS/NGN (Unix) Ver. 1.8 Setting the EMS System Parameters 4-5

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 option is functional only in the PC-based (Windows) version of RADview-EMS.

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

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

Parameter Function

Context The directory of NER tree nodes related to LaunchDesk

actions, such as Zoom and Synchronization (see

Figure 4-6)

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

HPOV map are updated

Note



Parameter Function

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-5. Settings Dialog Box – Regional and Language Tab

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

Parameter Function

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

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.



To open the NER Explorer:

1. In the LaunchDesk toolbar, click the Admin Console icon .

The EMS Admin Console is displayed showing the NMS station name.


2. Click the expansion icon next to the NMS station name to expand the Admin Console.

The list of EMS consoles is displayed.




3. Select NER Explorer in the list of consoles.

The NER Explorer is displayed showing the NMS station name.

Figure 4-8. NER Explorer Opening Window

4. Click the the expansion icon next to the NMS station name to expand the NER Explorer.

The list of submaps is displayed.



Figure 4-9. NER Explorer Opening Window after Expanding

5. Click the expansion icon next to the submap for which you wish to view the nodes.

The list of nodes is displayed.

Figure 4-10. NER Explorer Opening Window after Expanding Submap

You can view an object’s attributes by selecting it (see Figure 4-11).



Figure 4-11. NER Explorer – with Attributes

The NER Explorer window 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.

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

Figure 4-12. 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 in the NER Explorer:

1. In the NER Explorer toolbar, select Edit > Add Entry...

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

2. Enter the entry name.

3. 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-13. NER Explorer – Add Entry

Renaming an Entry

To rename an entry:

1. In the NER Explorer, select an object in the hierarchy tree (network element in the middle pane).

2. In the NER Explorer toolbar, select Edit > Rename Entry…

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

3. Enter the new entry name.

4. Click <Apply>.

Figure 4-14. NER Explorer – Rename Entry

Removing an Entry

To remove an entry:

1. In the NER Explorer, select an object in the hierarchy tree (network element in the middle pane).



2. In the NER Explorer toolbar, select Edit > Remove Entry.

A confirmation dialog box is displayed.

Figure 4-15. Remove Entry Confirmation

3. Confirm the removal of the selected 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:

1. In the NER Explorer, select a node in the hierarchy tree (network element in the middle pane).

2. In the NER Explorer toolbar, select Edit > Add Attribute.

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

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

Table 4-3. Add Attribute Parameters

Parameter Function

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-17. NER Explorer – Add Attribute (Custom Attribute) Dialog Box

Modifying an Attribute

To modify an attribute:

1. In the NER Explorer, 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).

2. In the NER Explorer toolbar, select Edit > Modify Attribute…

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

3. Enter a new Attribute Value.

4. Click <Apply>.

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

Removing an Attribute

To remove an attribute:

1. In the NER Explorer, 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).

2. In the NER Explorer toolbar, select Edit > Remove Attribute.

A confirmation dialog box is displayed.



Figure 4-19. Remove Attribute Confirmation

3. Confirm the removal of the attribute.

The attribute is removed from the object.

Viewing Applied Changes

Figure 4-20. 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.


RADview-EMS/NGN (Unix) Ver. 1.8 Using Additional Applications 4-15

4.3 Using Additional Applications

This section describes the following activities:

• Performing Backup and Restore

• Transferring Files Using TFTP

• Performing Automatic Configuration Upload (ACU)

• Viewing the Net Inventory

• Licensing

• Setting Net Date and Time.

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 HPOV security files.

• 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: Defining Backup/Restore for Additional Files below.

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

Backup and Restore Requirements

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

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

Note

Note


4-16 Using Additional Applications RADview-EMS/NGN (Unix) Ver. 1.8

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

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

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

Configuring Backup and Restore

Configuring Backup and Restore Scripts Manually

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

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

1. Log in as a RADview user.

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

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

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

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

The Backup and Restore scripts are ready for use.

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

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

– Or –

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

Note

Note



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

No operations.

Configuring Backup and Restore Files

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

• mng164_backup.xml file. This file includes:

Information about the backup/restore version

Configuration parameters for the backup and restore process

Parts of the RADview-EMS/NGN (Unix) system to be backed up/restored

Backup destination directory in which to create backup files

Restore source directory from which to take restored files.

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

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

Setting Parameters in the mng164_backup.xml File

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

Defining the Database Type

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

To define the database type:

• Set the values for the following parameters:

Oracle Database Parameter Value

<dbtype_oracle> true

<dbtype_informix> false

Informix Database Parameter Value

<dbtype_oracle> false

<dbtype_informix> true

Defining Full or Partial Backup/Restore

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

To define a full backup/restore:

1. Open the mng164_backup.xml file.

Note



2. Set the full_backup/full_restore value to true.

To define a partial backup/restore:


2. Set the full_backup/full_restore value to false.

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

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


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

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


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

Defining the Backup/Restore Location

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

Defining Backup/Restore Mode

There are two modes for backup:

• Simple backup

• DateTime backup – based on date and time.

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

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

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

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

To define the required backup mode as simple or dateTime:

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



Defining Backup/Restore for Additional Files

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

To enable backup/restore of additional files:

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

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

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

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

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

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

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

/export/home/testing/.cshrc

/export/home/testing/832474bf.lic

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

Do not include the following:

• Non-existent files

• Asterisks

• Blank rows.

Backing Up System Components

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

You can run the backup 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

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

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

Note

Note

Note



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

To run the backup process:

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

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

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

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

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

• The backup can be performed when RADview-EMS/NGN (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).

Restoring System Components

Before running the restore script, check that:

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

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

Notes

Note



To run the restore process:

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

2. Close HPOV and stop any existing EMS server if it is running on the station. To stop the EMS server, log in as superuser and then type: /etc/rc3.d/S98RvEmsServer stop.

You can verify that the EMS server has been stopped by typing: ps –ef | grep ems If no output is received, then no EMS server is running.

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

You do not need to stop the ACU server, as the restore script automatically stops it.

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

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

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

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

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

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

8. Type y to continue.

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

While the restore process runs, the following types of messages are displayed:

Input configuration file is /opt/MNG/MNGVIEWHP/bin/mng164_backup.xml. Restore started...

Log file is created. Look at /opt/MNG/MNGVIEWHP/BACKUP/CURRENT/mng164_restore.log

48 blocks

Restore has been completed

Note

Caution

Note

Note



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

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

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

Start the EMS Server (and ACU server) manually:

a. Open a terminal, type su and when prompted type the root password.

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

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

d. After the EMS Server is running, start the ACU server by typing: /etc/rc3.d/S99AcuServer start

It is highly recommended to use 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 and EMS) and restoring it on another host, perform the following steps before starting to work with RADview:

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

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

To restore a backed-up file on another computer:

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

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

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


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

• TFTP protocol is used for file transfer

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

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

Note



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

Configuring the TFTP Server

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

To configure the TFTP server:

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

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

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

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

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

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

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

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

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

d. Click Update.

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

f. Click OK.

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

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

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

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

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

8. Perform the following steps after the reboot:

Note



a. Type: svcs |grep tftp.

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

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

c. Type: svcs |grep tftp.

The following is displayed:

Figure 4-21. Adjusting the TFTP Server

Opening the TFTP File Transfer Application

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

To start the TFTP application:

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

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

3. Login to RADview-EMS/NGN (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

c. Click <OK>.

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

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

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

Figure 4-22. Opening TFTP File Transfer Menu

Note



Figure 4-23. TFTP File Transfer – Opening Window

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

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

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

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

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

The following table gives an overview of the TFTP operations that can be performed on agents. For specific details on how a particular product performs TFTP operations, refer to the product’s Installation and Operation manual.

Table 4-4. TFTP Operations

Operation Description

S/W Download Only Download software to the agent. The agent stores the software, and only

loads it after the next reset. This operation can be used when you want to

download new operating software to the agent to be stored for use at a

later time.

S/W Download & Reboot Download software to the agent and then reset the agent. This operation

causes the agent to load the software immediately after the reboot.



Operation Description

Config Download Only Download a file of configuration data to the agent, to be stored for later use

Config Download & Reboot Download a file of configuration data to the agent and then reset the agent.

This operation causes the agent to load the configuration file immediately

after the reboot.

Additional S/W Download

Only

Download additional software to the agent, to be stored for later use

Additional S/W Download &

Reboot

Download additional software to the agent and then reset the agent. This

operation causes the agent to load the software immediately after the

reboot.

User Download Only Download a special user file to the agent. For details on user file download,

refer to the product’s Installation and Operation manual.

S/W Upload Upload software from the agent to the TFTP server

Config Upload Upload a file of configuration data from the agent to the TFTP server

Statistics Upload Upload statistics from the agent to the TFTP server

User Upload Upload a special user file from the agent to the TFTP server

Reset Only Reset the agent

SW Download to Backup Download software to the agent, to be stored in its backup memory

SW Upload from Backup Upload the software stored in the agent’s backup memory to the TFTP server

Swap Main and Backup S/W Send command to agent to swap its main software with the software stored

in its backup memory. After the next reset, the swapped-in backup software

is then used.

License Download Send license file to agent to activate features that require a license

Changing the TFTP Default Settings

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

To change the TFTP default settings:

1. From the Configuration menu select Default Settings.

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

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

3. Click <Set>.



Figure 4-24. Default Settings Dialog Box

Table 4-5. TFTP Default Parameters

Parameters Function

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

object

Exclude TFTP Directory Path Selected, Cleared

Default Value: Selected

Reboot Timeout (sec)

(10–4000 seconds)

The reboot timeout setting for the selected object.

The TFTP File Transfer application waits for this period

for the Cold Start trap after performing a reboot.

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-18) allows you to add, modify, or remove products. The displayed information is taken from the OIDs (Object IDs) of the product types stored in the TFTP database.

Adding a Product Profile

To add a new product:

1. From the Configuration menu select Edit Database.

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

2. Click <Add>.

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

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



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

4. Follow the procedure in Selecting the File to Download.

5. Click <Set>.

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

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

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



Figure 4-26. Add Product Dialog Box

Table 4-6. Add/Edit Product Parameters

Parameter Function

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

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

subsystems needed for download

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

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



Parameter Function

All the following fields except the last three fields can be set to a file path

and name for the TFTP operation corresponding to the field, therefore the

fields are enabled only if the selected product supports the TFTP operation.

The <Browse> button opens the Select File dialog box for locating the TFTP

File Transfer file (see Selecting the File to Download).

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

product.

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

product.

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

selected product.

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

selected product.

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

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

the selected product.

Note: This parameter is not relevant for all products

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

selected product.


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

selected product.


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

selected product.


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.

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: You must enter the file name

License Download File License file location

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

time has passed. See Table 4-7 for the default value for the selected

product.

Retry Timeout (sec) Retry between the specified number of attempts. See Table 4-7 for the

default value for the selected product.



Parameter Function

Cancel SNMP Retries for

Reset Operation

If the Set Response for the Reset command is not received by NMS (lost),

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

redundant card as well, causing services to stop for a period of time. In order

to avoid loss of service, the user can cancel the retries (this is the default

setting for the devices with this problem).

Default: Cleared

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

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



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

Product

Name

Reboot

Timeout

(sec)

SW

Downld

Config

Downld

Config

Upld

Additional

SW Downld

Statistics

Upld

User

Downld

User

Upld

File

Name

Within

Product

Timeout

(sec)

SW

Upld

SW

Downld

to Bkp &

Swap

Main and

Bkp SW

SW

Upload

from

Bkp

License

Downld

Subsys

Downld

ACE-52 300 + + + – – – – – 300 – + – – –

ACE-201 300 + + + – – – – – 300 – + – – –

ACE-3100 300 + + + – – + – + 300 – + – + –

ACE-3105 300 + + + – – + – + 300 – + – + –

ACE-3200 300 + + + – – + – + 300 – + – + –

ACE-3205 300 + + + – – + – + 300 – + – + –

ACE-3400 300 + + + – – + – + 300 – + – + –

ACE-3402 300 + + + – – + – + 300 – + – + –

ACE-3600 300 + + + – – + – + 300 – + – + –

ETX-102 300 + + + – – – – – 300 + + – – –

ETX-201 300 + + + – – – – – 300 + + – – –

ETX-202 300 + + + – – – – – 300 + + – – –

ETX-202A 300 + + + - – – – – 300 + + – – –

IPmux-2L 300 + + + - – – – – 300 + – – – –

LA-104 300 + + + – – – – – 300 – – – – –

LA-110 300 + + + – – – – – 300 – – – – –

LA-130 300 + + + – – – – – 300 – – – – –

LA-210 300 + + + – – – – – 300 + – – – –



Product

Name

Reboot

Timeout

(sec)

SW

Downld

Config

Downld

Config

Upld

Additional

SW Downld

Statistics

Upld

User

Downld

User

Upld

File

Name

Within

Product

Timeout

(sec)

SW

Upld

SW

Downld

to Bkp &

Swap

Main and

Bkp SW

SW

Upload

from

Bkp

License

Downld

Subsys

Downld

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

Vmux-405 300 + + + – – + – + 300 – + – + –

Vmux-425 300 + + + – – + – + 300 – + – + –

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

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

Note



Selecting the File to Download

To select the file to download:

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

The Select File dialog box appears (see Figure 4-20).

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

3. Select the folder name and file name.

4. Click <Select File>.

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

Figure 4-27. Select File Dialog Box

Editing Product Data

To edit product data:



2. Select the product that you want to edit.

3. Click <Edit>.

Note



The Edit Product dialog box appears (see Figure 4-22).

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

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

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

Or

Follow the procedure in Selecting the File to Download.

6. Click <Set>.

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

Figure 4-28. Edit Database Dialog Box



Figure 4-29. Edit Product Dialog Box

To remove a product from the product 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.

Selecting Nodes for TFTP

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

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

Figure 4-30. Operation Tab

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

Table 4-8. TFTP File Transfer Parameters in Operation Tab

Parameter Function

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

displayed

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

node is displayed

Product Name Product names of the selected nodes

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

database

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

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

application

Note

Note



Parameter Function

Last Operation Last selected operation for each node:

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

Config. Download & Reboot, Additional SW Download Only,

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

Config. Upload, Statistics Upload, User Upload, Reset Only,

SW Download to Backup, SW Upload from Backup,

Swap Main and Backup S/W, License Download

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

SW Upload The name of the file to upload

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

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

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

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

Table 4-12. The row displaying the last TFTP status of each node has a

color-coded background as detailed in Table 4-12. The column is empty

before clicking the <Set> button and/or confirming all messages prompting

for confirmation related to the [All Nodes Operation…] or [Selected Nodes

Operation…] Dboxes. After clicking the <Set> button, the column is

automatically filled in for the selected nodes according to the tftpStatus

MIB object received directly by NMS upon request or received with the

tftpStatusChangeTrap each time the status changes. The column displays

the last status only so the last status received always overwrites the

previous status.

Schedule The date and time a TFTP file transfer is scheduled to occur.

[All Nodes Operation...] Performs operation for all nodes in list

[Selected Nodes Operation...] Opens a selection list box to choose operation for selected nodes

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

[Remove] Removes an agent

In order to upgrade an agent’s software, you must reboot (reset) the agent after downloading the software. In some cases, you may want to reboot the device later at a specific time. Therefore, when required, you can select an operation that includes Download Only for file download only, an operation that includes Reset Only for rebooting at a specific time after successfully downloading the software, or an operation that includes Download & Reboot for complete software upgrade.

Adding Agents for TFTP Operations

You can add agents directly from the HPOV map to the agent list in the Operation tab.

Note



To add agents from the map:

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

The Add Agent from Map dialog box appears (see Figure 4-24). As RADview-EMS/NGN (Unix) polls all the agents, it lists in the dialog box the agents that are in the TFTP database and are on the map. When it finishes, the status bar at the bottom of the screen displays Ready.

2. Select the node(s) to be added.

3. Click <Set>.

The node(s) are added to the list in the Operation tab.

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

Figure 4-31. Add Agents from Map Dialog Box

To remove an agent from the Operation tab:

1. Select a node from the list displayed in the Operation tab.

2. Click <Remove>.

The node is removed from the list in the Operation tab.

Note




This section explains how to transfer files using TFTP File Transfer.

Figure 4-32. TFTP File Transfer – Operation Tab

To perform TFTP File Transfer operations:


Select the specific nodes on which you want to perform Software Download from the list (hold down <Shift> while dragging the mouse to select several nodes) and then click <Selected Nodes Operation>. This can be used in case of unsuccessful TFTP transfer. Select only those nodes where the transfer of new software was not successful, according to the Last Status column, and reinitialize the TFTP session.

The Selected Nodes Operation dialog box appears (see Figure 4-27).

Click <All Nodes Operation…> to perform the TFTP file transfer for all the nodes in the list.

The All Nodes Operation dialog box appears (see Figure 4-36)

2. Select the desired S/W and Configuration Transfer operation. Only options that are supported by all nodes of the list are selectable (see Figure 4-28).

3. To schedule the TFTP operation for a later date/time, select Enable and define a date and time for the TFTP operation.



Figure 4-33. Selected Nodes Operation Dialog Box, Scheduling Enabled



Figure 4-34. Selected Nodes Operation Dialog Box, Scheduling Not Enabled



Figure 4-35. All Nodes Operation Dialog Box, Scheduling Enabled



Figure 4-36. All Nodes Operation Dialog Box, Scheduling Not Enabled



Figure 4-37. Selected Nodes Operation Dialog Box – Selection

4. Configure the parameters as specified in Table 4-9.

5. Click <Set>.

A confirmation message appears.

Figure 4-38. Selected Nodes Operation Dialog Box – Confirmation



Figure 4-39. All Nodes Operation Dialog Box – Confirmation

6. Click <OK>.

The Last Operation column in the Operation tab shows the selected TFTP operation. If scheduling was not enabled for the operation, it starts immediately. If scheduling was enabled, the Last Status and Schedule columns show the operation has been scheduled.

Figure 4–40. TFTP File Transfer – Scheduled operation

7. After allowing time for the operation to finish, or after the scheduled time if scheduled operation was performed, check the status reported in the Last Status column (see Figure 4–31) to determine whether the operation was successful. Additional information is available via the Report Tab (see Viewing TFTP File Transfer Reports).



Figure 4–41. TFTP Dialog Box – Operation Tab, Successful Transfer

In order to upgrade an agent’s software, you must reboot (reset) the agent after downloading the software. In some cases, you may want to reboot the device later at a specific time. Therefore, when required, you can select an operation that includes Download Only for file download only, an operation that includes Reset Only for rebooting at a specific time after successfully downloading the software, or an operation that includes Download & Reboot for complete software upgrade.

Table 4-9. All Nodes and Selected Nodes Parameters

Parameter Function

Operation Select any TFTP file transfer operation.

Values: S/W Download Only, S/W Download & Reboot, Config. Download Only, Config. Download & Reboot, Additional SW Download Only, Additional SW Download & Reboot, User Download Only, SW Upload, Config. Upload, Statistics Upload, User Upload, Reset Only, SW Download to Backup, SW Upload from Backup, Swap Main and Backup S/W, License Download

Default: SW Download Only

Note: Only options that are supported by all selected nodes can be chosen.

File Name As Selected per Product: The file name is taken from the TFTP product database.

Specifically Defined for Current Session: Use this option if you want to define a file name for this TFTP session, rather than use the file name defined in the TFTP product database. If this option is selected, a Browse button is available to select the file name, as well as a text box where you can type the file name.

Default: As Selected per Product

Note: This field is enabled for all operations selected in the Operation field except for Reset Only and Swap Main and Backup SW, because they don’t require a file.

Note



Parameter Function

File Name Format This parameter is used to specify a format for file names. You can use it for operations involving multiple files or multiple agents, as it is then necessary to be able to distinguish the different files.

Values:

As Selected per Product: The file name alone is used

As Selected per Product + Host Name: The file name + host name is used. Use this option when uploading files from multiple products.

As Selected Per Product + Host Name + Time Stamp: The file name + host name + time stamp is used. Use this option when uploading multiple files.

Note: This field is enabled only for Upload operations, and if the File Name parameter is set to As Selected per Product.

Schedule

Enable Select to enable scheduling of the operation.

Date Select the date for the scheduled operation.

Time Select the time for the scheduled operation.

When the operation selected in the Operation tab, [All Nodes Operation...] or [Selected Nodes Operation...] includes Download & Reboot, the NMS performs the operations shown in Table 4-10.

Table 4-10. Download & Reboot NMS Operations

Product Name Operation

ACE-52, ACE-201, RICi-16 A

LA-104, LA-110, LA-130,

LA-210, IPmux-2L

B

ACE-3100, ACE-3105,

ACE-3200, ACE-3205,

ACE-3600, ETX-102,

ETX-201, ETX-202,

ETX-202A, Vmux-405,

Vmux-425

A, when software download is performed

B, when configuration download is performed

Legend:

A = Same as Download Only + Reset. Same as Download Only (above) + upon successful completion, activate the Reset process.

B = Same as Download Only. For these products, no additional operation is needed, because these products automatically perform a reboot after receiving TFTP download.

If you select SW Download & 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.

Warning



Viewing TFTP File Transfer Reports

The Report tab (see Figure 4-32) 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-11. Messages are listed in Table 4-12.

Only agents for which Download/Upload is currently in process are displayed in this tab. A new row is added each time tftpStatusChangeTrap is received..

Reports are based on traps from the agent. In order to receive traps, the workstation running the TFTP file transfer application must be registered as a manager in the agent.

Figure 4-42. Report Tab

Table 4-11. TFTP File Transfer- Report Tab Parameters

Parameter Function

Date Local date at the NMS when the message was registered

Time Local time at the NMS when the message was registered

Host Name Name of the relevant agent

IP Address IP address of the relevant agent

Product Name Name of product for which file transfer process is being

reported

Status Status of the download process (see Table 4-12)

Table 4-12. Status Messages

Message (Standard TFTP messages) Color

Connecting… Yellow

Connected. Transferring Data Yellow

Note



Giving up. Server does not respond Red

File successfully transferred Green

File not found Red

Illegal TFTP operation Red

Unknown transfer ID Red

Server overflow Red

No available UDP port Red

No available resources Red

Illegal file mode Red

Illegal PDU size Red

Rebooting... Yellow

Device successfully upgraded Green

Device successfully rebooted Green

No SNMP connectivity Red

Device not responding after expiration of reboot

timer

Red

Incorrect File Red

IP Address format of the node is not valid Red

Unknown sysObjectID Red

Agent is busy with another TFTP session.

Operation will not be performed

Red

SNMP request failed Red

Access violation Red

Disk full or allocation exceeded Red

File already exists Red

No such user Red

TFTP server does not exist Red

Wrong license format Red

License ID already used Red

Scheduled Yellow

<Operation selected> scheduled for

<yyyy:mm:dd hh:mm:ss >

Executing scheduled operation

Scheduled operation has been canceled

To remove messages from the Report tab:



• In the Report tab, select a row and click <Remove>, or click <Remove All> to clear all messages from the list.

Saving the TFTP Database

If you keep the TFTP application open for a long time you should save the database periodically to avoid losing parameter data in the event of a power failure.

To save the database:

• From the Configuration menu, select Save Database.

Using Help

You can access the online user manual and information about the TFTP application via the Help menu.

To access the user manual:

• From the Help menu, select Help > User’s Manual.

To access information about the TFTP application:

• From the Help menu, select Help > About Application.

Exiting the Application

When you select Configuration > Exit to exit TFTP:

• If there is at least one scheduled entry that was not performed, the following dialog box is displayed:

Figure 4-43. Exit Dialog Box (Scheduled Operation Exists)

• Else, the following dialog box is displayed:

Figure 4-44. Exiting Application Dialog Box (No Scheduled Operation)



Click <OK> in both cases, to exit the application.

Performing Automatic Configuration Upload (ACU)

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

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

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

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

The Client can configure the following Server parameters:

• Date and Time to start the upload

• Time interval for the upload sessions

• Location of the uploaded files

• TFTP parameters

• Nodes in the agent list.

Configuring the TFTP Server for ACU

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

To set up the TFTP server:

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

2. Login as root.

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

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

Note



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

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

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

b. From the File menu select Open.

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

d. Click <Update>.

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

f. Click <OK>.

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

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

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

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

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

Note



Figure 4-45. File Edit for the TFTP Server

Manually Starting or Stopping the ACU Server

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

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

To start the ACU server:



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

To stop the ACU server:



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

Launching the ACU Client Application

Before starting the ACU client application, ensure that RADview HPOV and a TFTP server are running. If the TFTP Server is not running when the ACU application tries to initiate an upload session, the error message shown in Figure 4-36

Note



appears. This message appears for any activity that requires the TFTP server to be running.

Figure 4-46. TFTP Disabled Error Message

To log in:

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

2. Type ovw & in the terminal window.

HP OpenView is launched.

3. Log in to RADview:

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

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

c. Click <OK>.

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

To launch the ACU client application:

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

Figure 4-47. Launching the ACU Client Application

If the ACU server is running, the ACU main window appears (see Figure 4-39), containing the Report Table. If the ACU Server is not

Note



running, an error message is displayed (see Figure 4-38) and the ACU client does not start.

Figure 4-48. ACU Server Disabled Error Message

Figure 4-49. ACU Client main window

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

For each ACU profile, the Report Table shows:

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

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

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

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

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

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



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

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

Summary of ACU Tasks

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

Table 4-13. ACU Tasks

Task Dialog Box and Parameter Location

Path

Configuring ACU

TFTP Settings

ACU TFTP Settings dialog box

(Figure 4-40)

Options

General TFTP Settings

Configuring profiles

(Use this option to

schedule uploads.)

ACU Profiles window

(Figure 4-41)

Options

Profile

Uploading configuration

immediately

Upload Configuration

Confirmation dialog box

(Figure 4-47)

Configuration

Upload Now

Filtering report Report Table Filter dialog box

(Figure 4-50)

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

Configuration

Report

Save As…

Printing report Print Report dialog box

(Figure 4-61)

Configuration

Report

Print

Clearing report Clear Report dialog box

(Figure 4-62)

Configuration

Report

Clear

Exiting ACU application Exit ACU dialog box (Figure 4-66) 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-40). Table 4-14 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-50. TFTP Settings

Table 4-14. 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-41).

Figure 4-51. 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-42).

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

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

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

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



Figure 4-53. Edit Profile Dialog Box

Table 4-15. Profile Parameters

Parameter Function

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

Default value: current date

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

00:20 – 23:20

Default value = 00:20

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

Time Intervals Time period for periodical upload sessions

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

1 Week, 10 Days, 2 Weeks, 30 Days

Default value = 1 Day

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

3–1000

Default value = 30

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

Activity Specifies whether this profile is Active or Not Active

Next Session Time

(Read only)

Date and nearest time of next upload

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



Parameter Function

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-14) 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-44). To open the Object Selection dialog box, select the profile in the ACU Profiles window, and click Object Selection.

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

• Black – the node was selected from the active map

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

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

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

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

To add node objects to a profile:

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

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

Note



To remove node objects from a profile:

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

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

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

Figure 4-54. 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-45).

2. Click OK.

The profile does not appear in the list of profiles.



Figure 4-55. Remove Profile Confirmation

Deactivating a Profile

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

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

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

Activating a Profile

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

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

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

Refreshing the List of Profiles

• In the ACU Profiles window, click Refresh.

The list of profiles is refreshed.

Performing Immediate Configuration Upload

To upload a configuration immediately:

1. From the Configuration menu, select Upload Now.

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



Figure 4-56. Upload Now Dialog Box

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

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

Figure 4-57. Upload Now Confirmation Dialog Box

3. Click OK.

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

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

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

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

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

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

Note



Working with the ACU Report Table

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

Figure 4-58. ACU Report Table

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

Table 4–16. ACU Status Messages

Message (Standard TFTP messages) Color

Connecting… White

Connected. Transferring Data White

Giving up. Server does not respond Red

File successfully transferred Green

File not found Red

Illegal TFTP operation Red

Unknown transfer ID Red

Server overflow Red

No available UDP port Red

No available connection Red

Illegal file mode Red

Illegal PDU size Red

Rebooting... Red

Device successfully upgraded Red



Device successfully rebooted Red

No SNMP connectivity Red

Connection with agent is lost. No Indication for

End-of-TFTP Process

Red

Unknown sysObjectID Red

Access violation Red

File already exists Red

No such user Red

TFTP server does not exist Red

Wrong license format Red

License ID already used Red

Created new directory White

Directory removed Yellow

TFTP Server not in service Red

TFTP Root does not exist Red

Unable to create Upload directory Red

Unable to create Upload file Red

Agent reject request to Upload file Red

Unknown error Red

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

Can’t remove Directory Red

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



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

Figure 4-60. 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-51):

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

Figure 4-61. Report Level Filtering

Figure 4-62. ACU Report Table – Profiles Only

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



Figure 4-64. 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-55).

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-65. 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-56).

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-66. Edit Filtered Profiles

To filter the number of sessions displayed:

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

2. Click Set to save your changes

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



Figure 4-67. ACU Report Table – Maximum of One Session 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-58).

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



Figure 4-68. Save Dialog Box

Figure 4-69. ACU Report in CSV Format



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

2. Enter the Print parameters.

3. Click Print.

The report is printed.



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

2. Press <OK>.

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

Figure 4-72. Clearing Report Dialog Box



Figure 4-73. Report Table, Cleared

Accessing Help

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

Figure 4-74. Help Menu

To access the user manual:

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

The user manual is displayed.

To display details about the application:

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

Details about the application are displayed.



Figure 4-75. ACU Details Window

Closing the ACU Client Application

To exit the ACU client application:

1. From the Configuration menu select Exit.

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

2. Press <OK>.

The ACU client application closes.

Figure 4-76. Exit ACU Dialog Box

Viewing the Net Inventory

The Net Inventory application allows you to display an Inventory Table (see Figure 4-68) for all products that support the Entity MIB.

The LA-104 agent does not support the Net Inventory application.

The HPOV map should be open when activating Net Inventory for the first time. When you start the Net Inventory application, it reads information from all nodes representing agents on the map that support Entity MIB.

Opening the Application

To open the Net Inventory application:

• In the HPOV Map select Misc>RADview/OV> General> Net Inventory.

Note



Figure 4-77. 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-68).

Figure 4-78. Net Inventory 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-17. Inventory Table Parameters

Parameter Function

Entity Unique value that identifies the physical entity

Desc. Description of the entity

Note

Note



Parameter Function

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

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 Identification information added to the entity. It can be used to

indicate the Configuration Status Letter (CSL) of the unit component.

[Filter…] Opens a dialog box to filter the entity

[Edit…] Opens a dialog box to edit the parameters of the selected row

[Close] Closes the application

[Print…] Prints all selected rows

[Save to File…] Saves all selected rows

[Expand All] Expands all entities to display all subordinates down to the lowest

level

[Collapse All] Closes all tree entries to display node level only

[Help] Displays Help file

About Displays info about the program, such as version and licensing

information

[Refresh] Opens the following submenu:

Synchronize All Refreshes information for all displayed entities

Refresh Selected Refreshes information for selected entities

Remove Selected Removes selected entities from net inventory

table.

Add New Nodes

from Map

Adds new entities to inventory table, containing

data of nodes that were added to map

Last Refresh NMS time when the last refresh was performed



Filtering the Display

You can display only nodes that you wish to view.

To filter the display:

1. In the Inventory Table, select Filter> Filter.

The Inventory List Filter dialog box appears (see Figure 4-69).

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 that have entities matching all the filter criteria are displayed.

• Filtering is not case-sensitive.

• The only wild card character that can be used in the Edit boxes is *.

Figure 4-79. Inventory List Filter Dialog Box

Note

Note



Table 4-18. 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. In the Inventory Table, select an entity (row) and click <Edit>.

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

2. Modify the desired parameters.

3. Click <Set>.

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

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

Figure 4-81. Inventory Table Dialog Box – Entities Expanded

Licensing

The RADview-EMS/NGN (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 optimal correlation between the types of managed devices and size of the network, and the price of the management system.

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

For full licensing terms, see the RADview-EMS/NGN (Unix) license agreement included in the RADview-EMS/NGN (Unix) package. If you need a RADview license for your RADview package, you can activate it at the RAD value point website (via MyRAD or the Customer Information link.)



Network Size

Each RAD product managed by RADview-EMS/NGN (Unix) 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 the NMS does not have the correct community name) is assigned a default value of 500.

Table 4-19 lists the equivalent node weights for RAD devices supported by RADview-EMS/NGN (Unix).

Table 4-19. Equivalent Node Weights (ENW)

Device ENW

Default 500

ACE-201 45

ACE-3100 30

ACE-3105 17

ACE-3200 55

ACE-3205 35

ACE-3400 150

ACE-3402 150

ACE-3600 150

ACE-52 45

ETX-102 8

ETX-201 7

ETX-202 15

ETX-202A 15

IPmux-2L 6

LA-104 15

LA-110 5

LA-130 15

LA-210 5

RICi-16 22

Vmux-405 45

Note



Device ENW

Vmux-425 100

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–20 lists the RADview EMS/NGN packages and their bundled license points.

Table 4–20. Bundled License Points

Platform Bundled License Points (Free of Charge)

RADview-EMS/NGN (Unix) 400

RADview-EMS/NGN(PC) 300

Calculating License Points

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

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

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

However, since a particular number of license points is bundled within every RADview-EMS/NGN (Unix) package, the actual number of license points required can be calculated as follows:

Required license points = Total Number of License points (for all types) − RADview-EMS/NGN (Unix) package bundled license points

The following is an example of calculating license points for a network to be managed by RADview-EMS/NGN (Unix), with the following elements:

• Eight ETX-202 units

• Twenty LA-130 units

• Four ACE-3600 units.

Referring to the equivalent node weights in Table 4-19, we find that:

• ETX-202 = 15 ENW

• LA-130 = 15 ENW

• ACE-3600 = 150 ENW

Considering the bundled license points table (see Table 4–20), we find that:

• The RADview-EMS/NGN (Unix) package includes a 400-point free-of-charge bundled license.



Thus, the license you need to order = ⎨[(8x15)+(20x15)+(4x150)]–(400)⎬ = 620.

Explanation: since the actual license size that is needed to manage the given network is 1020, and 400 points are bundled free-of-charge within the RADview package, you only need to order 620 license points.

To simplify the calculations for larger networks that contain many different products, use the RADview License Calculator, available on RAD’s website.

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.

To open the License Service Manager:

• Select: Misc > RADview OV > License Service Manager

The License Service Manager opens.

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

Viewing the Installed License Points

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

http://www.rad.com/RADCnt/MediaServer/8085_RADview_License_Calculator_v1.01.xls�



Figure 4-82. General Tab

Figure 4-83. General Tab (Cont.)

Table 4-21. License Status

Parameter Function

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)



Parameter Function

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 six hours subsequently (see Figure 4-74).

Figure 4-84. License Expiration Warning

Viewing the Managed Element List

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

Figure 4-85. Managed Element List, Left Side



Figure 4-86. Managed Element List, Right Side

Figure 4-87. Managed Element List (Cont.), Left Side



Figure 4-88. Managed Element List (Cont.), Right Side

Table 4-22. Managed Element List Parameters

Parameter Function

IP Address IP Address of managed element

Name Selection Name of managed element

Type Type of managed element

ENW Equivalent Node Weight of 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 at 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.

Note



Adding a License

To add a license file:

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

2. Select: File > Add License.

The Open License File dialog box is displayed (see Figure 4-77).

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

The Open License File dialog box closes, and the data of the new file is added as a new row in the General tab.

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

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

Figure 4-89. Open License File Dialog Box

Removing a License

To remove a license file:

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

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

Note



3. Select: File > Remove License.

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

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

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

Figure 4-90. Remove License Warning

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

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

Starting and Stopping the License Service

Figure 4-91. Action Menu

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

To start the License Server:

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

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

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

To stop the License Server:

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

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

A message is displayed: Stopping License Server operation.

3. Click <OK> to confirm.



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

Figure 4-92. Service Console

Configuring the Server Side License Ports

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

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

To configure the Server Side:

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

2. Enter Socket Port and INS Port.

3. Click <Set>.

Figure 4-93. Server Side Configuration

Table 4-23. Server Side Configuration

Parameter Function

Socket Port Socket Port of the Server

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

INS Port INS Port of the Server


Note



Configuring the Client Side License Ports

To configure the Client Side:

1. Select Options > Client Side Configuration.

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-94. Client Side Configuration Dialog Box

Table 4-24. Client Side Configuration Parameters

Parameter Function

Server CORBA Mode For future use

Socket Port Socket Port of the Server


INS Port INS Port of the Server


Server IP Address Server IP Address

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

Setting Net Date and Time

RADview-EMS/NGN (Unix) has two date and time functions:

• Set the date and time for managed units via a single screen

• Automatically update date and time parameters of agents according to NMS clock.

Note



Setting Net Date and Time

RADview-EMS/NGN (Unix) allows you to set the date and time for all managed units via a single screen.

To set net date and time:

1. From the Misc. menu, select RADview-OV> General> Net Date and Time.

The Net Date and Time dialog appears (see Figure 4-83).

2. Select the required device from the Remaining Products list and move it to the Selected Products list.

3. Select the time format from one of the following options:

User Time – allows you to configure date and time

NMS time – This automatically sets the date and time according to the NMS clock.

4. Enter the Date and Time parameters if you selected User Time:

Date – Day/Month/Year

Time – Hour/Minute/Second

5. Click <Set> to implement the changes.



Figure 4-95. Net Date and Time Dialog Box

Setting Automatic Update of Date and Time

RADview-EMS/NGN (Unix) can automatically update date and time parameters for the ACE agents.

• Closing HP OpenView does not affect the automatic update.

• If the automatic update was activated and the station reboots, the update is still performed with the same settings.

To set the parameters for automatic update of date and time:

1. From the Misc. menu, select RADview/OV > General> Date and Time Auto Mode. Do not click an agent icon on the WAN map.

The Date and Time Auto Mode dialog box appears.



2. Select the required device from the Remaining Products list and move it to the Selected Products list.

3. Set the update period and update time.

4. Click <Set> to implement the changes.

Figure 4-96. Date and Time Auto Mode Dialog Box

RADview-EMS/NGN (Unix) Ver. 1.8 Monitoring Services and Processes 5-1

Chapter 5

Performance Management Once RADview-EMS/NGN (Unix) is installed, configured and operating, you can start monitoring the system's performance. This includes:

• Monitoring Services and Processes (see Section 5.1)

• Additional Monitoring Options (see Section 5.2), which include:

Viewing the RADview Package Contents

Monitoring SNMP Performance

Filtering SNMP Requests and Traps

Tracing Log Events.

Chapter 5 Performance Management User's Manual

5-2 Monitoring Services and Processes RADview-EMS/NGN (Unix) Ver. 1.8

5.1 Monitoring Services and Processes

The system console allows you to monitor the EMS server process and services. This includes the following activities:

• Viewing EMS Server Process Information

• 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 Configuration Management

• Viewing the EMS Security Service

• Viewing the EMS Discovery Service

• Viewing the EMS OSS Heartbeat Service.

To open the System Console Window:

1. In the LaunchDesk toolbar, click System Console .

The System Console Opening Window is displayed showing the NMS station name (see Figure 5-4).

2. Click the expansion icon next to the NMS station name to show the process manager and processes.

The process manager and processes are displayed (see Figure 5-2).

3. Click the expansion icon next to Process 1 to show the services.

The list of services is displayed (see Figure 5-3).

User's Manual Chapter 5 Performance Management


Figure 5-1. System Console Opening Window

Figure 5-2. System Console Opening Window, Expanded



Figure 5-3. System Console Opening Window, Services Expanded

You can view the following elements in the System Console window:

• Servers on Stations with EMS

• EMS server process information

• Services that can be monitored

• Services that can be configured

• Status of Services (see Table 5-1).

Table 5-1. Status of Service

Color Status

Green OK

Yellow Trying to connect or restart

Red Service is down



Figure 5-4. 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-9, Figure 5-12, and Figure 5-19.

Viewing EMS Server Process Information

You can view and refresh the following information for the EMS server process:

• Memory information

• Resolved host/IP address pairs (used for trap forwarding).

The EMS server can be distributed to several processes on deployment. However, in a standard setup there is only one EMS server process, named Process 1.

To view and refresh the EMS server process memory information:

1. In the System Console, select Process 1 (or the name of your EMS server process) in the left pane and click the General tab.

The EMS server process memory information is displayed as shown in Figure 5-5. See Table 5-2 for parameter details.

2. Click <Poll> next to any of the memory fields to refresh the information.

The <Poll> button appears pressed, and the memory status is polled every few seconds and refreshed in the memory field, until you click <Poll> again to stop the polling.



It is recommended to not run the polling indefinitely, as it increases the load on the EMS server process.

Figure 5-5. EMS Server Process General Tab

Table 5-2. EMS Server Process Parameters – General Tab

Parameter Description

Info

Description The name of the EMS server process

Maximum memory Maximum amount of memory that is available to be allocated to the EMS

server process

Total memory The amount of memory that has been allocated to the EMS server process

Free memory The amount of free memory available, from of the total memory allocated to

the EMS server process

To view the EMS server process Host/IP address pairs:

1. In the System Console, select Process 1 (or the name of your EMS server process) in the left pane and click the Advanced tab.

The Advanced tab is displayed as shown in Figure 5-6.

2. Click <Get> to fill the information in the Hosts/IPs field with the resolved host/IP addresses that have been used in trap forwarding.

3. Click <Update> to update the cache, for example if the IP address of a workstation used in trap forwarding has changed.

Note



Figure 5-6. EMS Server Process Advanced Tab

Stopping/Starting a Service

To stop/start a service:

• In the System Console, right-click a service or management item and select Start or Stop (see Figure 5-7).

The service that you selected starts/stops.



Figure 5-7. Service Start/Stop Dialog Box

To manage all services:

• In the System Console, right-click Process Manager and select one of the following options (see Figure 5-8):

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.



Figure 5-8. Process Manager – for ALL Services

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-9) sets the parameters to enable Trace Monitor and SNMP SPY (see Table 5-3).

To enter new information:

1. In the System Console, select one of the server names that appear below the 'Servers' root (see Figure 5-9) and then click the General tab.

2. In the Tracing dialog box, enter information for any of the parameters (see Table 5-3).

3. Click <Set>.

To retrieve the current value, click <Get>.

Note



Figure 5-9. Server Tracing Configuration Dialog Box – General Tab

Table 5-3. Server Tracing Configuration Parameters – General Tab


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 selected, it allows viewing traced messages

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 selected, it enables monitoring SNMP SPY messages

SNMP SPY Hosts The port for SNMP SPY communications. It is recommended to leave this as

the default value.



Figure 5-10. Server Tracing Configuration Dialog Box – Advanced Tab

Table 5-3. 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 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-11).

Figure 5-11. Java Name and Directory Service



Table 5-4. 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-12).

3. Click <Set>.

To retrieve the current value, click <Get>.

Figure 5-12. Datasource Repository Configuration

Note



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

EMS Datasource (Oracle

database server)

User The name of the EMS Datasource Oracle Database server user

Password*** The user’s password used to gain access to the EMS Datasource



Viewing the CORBA Name Service

The CORBA name service allows server applications to advertise object references using logical names.

Figure 5-13. CORBA Name Service

Table 5-5. 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-14).



Figure 5-14. CORBA Event Service

Table 5-6. 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-15. EMS Log Service

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

No. 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, e.g. – 50




Log Browsing Performance

No. of Records Retrieved

per Request

The number of records that can be retrieved for every request, e.g. – 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-16. EMS Network Element Repository

Table 5-7. 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-17). 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-17. EMS License Service Configuration

Table 5-8. 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-18. EMS Trap Listener

Table 5-9. 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-19) 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-19. EMS Fault Management (Back End)

Table 5-10. EMS Fault Management Parameters (Back End)



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 Every 60 minutes, EMS checks the tree to determine if it is

synchronized with the map

Selected = Enabled

Cleared = Disabled

Traps Buffering and Retransmission Traps defined as forwarded with retransmission are buffered (see

the 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-20. EMS Fault Management (Front End)

Table 5-11. EMS Fault Management Parameters (Front End)



Read-only


Read-only



Viewing the EMS Polling Service

You can set the Polling Service parameters (see Figure 5-21 and Table 5-12).

Figure 5-21. EMS Polling Service Configuration

Table 5-12. 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-22. EMS Configuration Management

Table 5-13. 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-23. EMS Security Service

Table 5-14. 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 profile storage Enables/disables using the file system to store files

Viewing the EMS Discovery Service

When the EMS Discovery Service is enabled, the RADview EMS server listens to coldStart and warmStart standard SNMP traps.

When traps are received, a new node is automatically added to the NER under a pre-configured tree node if the following conditions are met:

• The node is a RAD node

• The node does not exist in the NER.



Figure 5-24. EMS Discovery Service

Table 5-15. EMS Discovery Service Parameters


Info


Read-only


Read-only

Discovery settings

Discovery Enabled Selected = Yes

Cleared = No

Ner Context Name of NER tree node level where discovered nodes will be

added

Read Community One or more communities to use when accesing the device

via SNMP in this service

Note: When entering multiple communities, separate them using a semicolon (;)

Timeout (msec) SNMP timeout when accessing the device via SNMP in this

service

Retries SNMP retries when accessing the device via SNMP in this

service



Viewing the EMS OSS Heartbeat Service

When EMS OSS Heartbeat Services is enabled, the RADview EMS server periodically checks connectivity (using TCP/IP Ping) with the OSS stations configured. When disconnectivity is detected, the service monitors the connection until connectivity returns and then sends an SNMP trap to the OSS with details on the period of disconnectivity.

Figure 5-25. EMS OSS Heartbeat Service

Table 5-16. EMS OSS Heartbeat Service Parameters


Info


Read-only


Read-only

OSS Heartbeat Settings

OSS Heartbeat Enabled Selected = Yes

Cleared = No

OSSes IP-Addresses IP Address of all OSSes for which the heartbeat check should

be performed by this service

Note: When entering multiple IP Addresses, separate them using a semicolon (;)

Time Interval (sec) Time interval of the periodic check

OSS Heartbeat Timeout (sec) Ping timeout, which determines after how much time OSS is

considered to be disconnected


RADview-EMS/NGN (Unix) Ver. 1.8 Additional Monitoring Options 5-29

5.2 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 tools:

• Click in the LaunchDesk toolbar.

A dropdown menu appears (see Figure 5-26).

Figure 5-26. LaunchDesk Toolbar with Tools Dropdown 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 in 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):

1. From the LaunchDesk Tools menu (see Figure 5-26), select Version Browser.

The Version Browser window appears and displays the RADview contents tree.


5-30 Additional Monitoring Options RADview-EMS/NGN (Unix) Ver. 1.8

Figure 5-27. Version Browser Window

2. Click the expansion icons next to RADview EMS and NGN to view the RADview package contents.

The Version Browser window displays the RADview package contents.



Figure 5-28. Version Browser Window, Expanded

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 SNMP Spy Enabled.

2. In the Tools toolbar, click SNMP Spy.

The SNMP Spy window is displayed (see Figure 5-29).

3. Select Online to view messages as they arrive, otherwise you just see the number of messages (top left corner in Figure 5-29), until you click <Refresh>.

4. Select Freeze to stop displaying new messages.



Figure 5-29. SNMP Spy Window

Filtering SNMP Requests and Traps

Description Filter

To set a filter by description:

• In the SNMP Spy Window, type in a string that you want to use as a filter.

Options Filter

To set filters by options:

• In the SNMP Spy Window, click <Options>.

The Options dialog box is displayed, with two tabs: General (see Figure 5-30) and Filter (see Figure 5-31). Filter selects agents for which SNMP requests/responses are displayed.



Figure 5-30. Options General Tab

Figure 5-31. Options Filter Tab

Table 5-17. Options Filter Parameters


Host Address Address of EMS Server

Port Port for Spy communication. It is recommended to leave



this as the default value.

Maximum Rows Maximum rows in SNMP Spy display

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.

To enable the Trace Monitor:

1. In the LaunchDesk toolbar, click to open the System Console.

2. Select the main server to view the General tab (see Figure 5-4 on page 5-5).

3. Set Global Level to any value other than OFF, and click <Set> to apply the change.

4. Set Trace Monitor Level to any value other than OFF, and click <Set> to apply the change.

To display messages using the Trace Monitor:

1. From the Tools menu, click Trace Monitor .

The Trace Monitor window is displayed (see Figure 5-32).

2. Click Options (see Figure 5-33).

3. Select Level.

4. In Maximum Log Lines field, enter the maximum number of messages that can be displayed in Trace Monitor for the selected level. Additional messages are not displayed.

5. You can stop Trace Monitor by selecting Freeze in the Trace Monitor window.



Figure 5-32. Trace Monitor Window

Figure 5-33. Options Dialog Box

RADview-EMS/NGN (Unix) Ver. 1.8 Administering Users in the EMS Environment 6-1

Chapter 6

Security Management This chapter describes the following:

• Managing users

• Using the Security Administrator

• Creating security profiles

• Working with administrator options.

6.1 Administering Users in the HPOV Environment

In RADview-EMS/NGN (Unix), you normally work with EMS users, therefore you can use the default HPOV user (root). You do not need to create additional HPOV users.

6.2 Administering Users in the EMS Environment

The EMS 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. EMS user management is performed via the EMS Security Administrator.

The EMS Security Administrator 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 Administrator.

To start the Security Administrator:

• In the EMS Admin Console, click Security Service.

The main application window (see Figure 6-1) 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.

Chapter 6 Security Management User’s Manual

6-2 Administering Users in the EMS Environment RADview-EMS/NGN (Unix) Ver. 1.8

Figure 6-1. 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 zoom applications (see Figure 6-2).

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-2 shows the available permissions that have been uploaded from the permission file (‘perm’ file) in 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

User’s Manual Chapter 6 Security Management


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

Basic Permissions

Figure 6-3 shows the basic permissions displayed in the right pane of the Security Administrator:

• global_perm – Group of labels for global functions

• audit_perm – Group of labels for audit functions

• config – Tree of labels for general configuration functions including SC-TDM and device-specific functions. Each device tree contains labels for device-specific functions, grouped for technician, monitor, and operator profiles (see Figure 6-4).

• fault – Tree of labels for Event Browser functions (see Figure 6-5)

• admin – Tree of labels for Admin Console functions (see Figure 6-5)

• ner – Tree of labels for NER Explorer functions (see Figure 6-5)

• log – Tree of labels for Log Viewer functions (see Figure 6-5)

• launchdesk – Labels for LaunchDesk functions (see Figure 6-5).

For details on the function labels, refer to Table 6-1.

Note



Figure 6-3. Basic Permissions



Figure 6-4. Basic Permissions, Expanded Config



Figure 6-5. Basic Permissions, Expanded Fault, Admin, Ner, Log, Launchdesk

Table 6-1. Security Profile Function Labels

Function Label Functionality Controlled

Group: global_perm General permissions

ADMIN_GrabRWMode Grabbing read-write mode when launching a device zoom

application. When two or more users try to work with the same

device, only one user can have read-write access. Additional

users have read-only access. When the second user launches

the zoom application, he gets an indication that another user

has already launched the zoom application for this device and

currently has read-write access. The second user has the option

to grab the read-write access from the first user, if the setting

of this function label is Write.

ElaborateTable_SaveCommonSettings Pressing the SaveCommonSettings in table dialogs where

applicable.

ElaborateTable_RemoveCommonSettings Pressing the RemoveCommonSettings in table dialogs where

applicable.

ElaborateTable_RemoveDialogSettings Pressing the RemoveDialogSettings in table dialogs where

applicable.




ElaborateTable_RemoveAllSettings Pressing the RemoveAllSettings in table dialogs where

applicable.

Group: audit_perm Audit permissions

Audit Currently unused

AUDIT_Operations Auditing for any Set operations

Group: SCTDM_perm SC-TDM permissions

PM_PathConfig Node access permission [i.e. Read, Write, Disable] configuration

for Service Center TDM.

Group: config_perm Configuration permissions

Zoom Launching device zoom application

All_Print Pressing <Print> in applications

All_SaveToFile Pressing <SaveToFile> in applications

Group: fault_perm Event Browser permissions

EVENT_clearEvents Clear events in the Event Browser

EVENT_remove Remove event/events in the Event Browser

EVENT_acknowledge Acknowledge an event in the Event Browser

EVENT_unacknowledge Unacknowledge an event in the Event Browser

EVENT_clear Clear an event in the Event Browser

EVENT_unclear Unclear an event in the Event Browser

EVENT_noteCreate Create an event note in the Event Browser

EVENT_noteModify Modify an event note in the Event Browser

EVENT_noteRemove Remove an event note in the Event Browser

Group: ADMINperm Admin Console permissions

ADMIN_security Access to Security Administration Console.

ADMIN_fault Access to Fault Service console

ADMIN_ner Access to Ner Explorer console

ADMIN_log Access to Log Admin console

ADMIN_monitoring Access to Trace Monitoring

Group: tools_perm Application permissions

TOOLS_SystemConsole Opening the System Console

TOOLS_AdminConsole Opening the Admin Console

TOOLS_LogViewer Opening the Log Viewer

TOOLS_Inventory Opening the Net Inventory application

TOOLS_TftpFileTransfer Opening the TFTP File Transfer application




TOOLS_AutomaticConfigurationUpload Opening the Automatic Configuration Upload application

TOOLS_EventBrowser Opening the Event Browser

TOOLS_VersionBrowser Opening the Version Browser

TOOLS_SnmpSpy Opening the SnmpSpy

TOOLS_TraceMonitor Opening the TraceMonitor

Group: Ner_perm NER Explorer permissions

ENTRY_create Create/add an entry in the NER Explorer

ENTRY_rename Rename an entry in the NER Explorer

ENTRY_remove Remove an entry in the NER explorer

ATTRIBUTE _create Create an attribute in the NER explorer

ATTRIBUTE_modify Modify an attribute in the NER explorer

ATTRIBUTE_remove Remove an attribute in the NER explorer

Group: Log_perm Log permissions

LOG_delete Delete a log entry

Group: ld_perm. LaunchDesk or Radview MAP permissions

NODE_sync Performing Sync

NODE_import Importing nodes

NODE_poll Polling nodes

NODE_add Adding nodes

NODE_change Changing node properties

NODE_remove Removing nodes

Manually Loading Security Profiles

The EMS server automatically loads security profiles after performing a setup or upgrade. However, if you need to manually load a security profile, perform the following procedure.

To manually load a security profile (permissions):

1. From the EMS Security Administrator window (see Figure 6-1), select Profile > Load.

The Load Basic Profile dialog box appears (see Figure 6-6).

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.

<device name>_perm_monitor, <device name>_perm_technician & <device name>_perm_operator – Device-specific labels for zoom application functions.

3. Click <Load>.

Figure 6-6. 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 New Profile

The following are recommended when adding a new profile:

• Add a new profile using a base profile, and then make modifications.

• Leave user as root.

To add a new profile:

1. From the EMS Security Administrator window (see Figure 6-1), select Profile > Add.


Note

Note



2. Enter the Profile Name and Profile Description.


Select a category from Base Profile.

Or

Select None.

4. Click <Continue>.

The Add <New Profile Name> Profile dialog box appears (see Figure 6-8).

5. Make modifications (see Working with Permissions).

6. Click <Set>.

Figure 6-7. Add Profile Dialog Box

Table 6-2. Add Profile Parameters

Parameter Possible Values / Remarks

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

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-3). 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-12) 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

Note



Adding a Profile with No Base Profile

To add a profile with no base profile:

1. From the EMS Security Administrator window, select Profile > Add…

The Add Profile dialog box is displayed (see Figure 6-7).

2. Enter Profile Name and Profile Description.

3. Select None for Base Profile.

4. Click <Continue>.

The Add <New Profile Name> Profile dialog box is displayed with the left column empty (see Figure 6-10).

5. Drag the whole set of permissions from a folder or drag one permission at a time to the left column (see Figure 6-12).

6. Click <Set>.

Refer to Working with Permissions to change permissions.

Figure 6-9. Add Profile – Base Profile NONE



Figure 6-10. Add <New Profile Name> Profile (NONE) Dialog Box

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-3. 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-13) .

2. Click <Set>.

To change permission, i.e. – change from Read to Not Available:

1. Double-click the yellow icon (see Figure 6-13) .

2. Click <Set>.

To change permission, i.e. – change from Not Available to Write:

1. Double-click the red icon (see Figure 6-13) .

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.

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.

Note

Note



Figure 6-11. Add <New Profile Name> Profile Dialog Box – Possible Permissions



Figure 6-12. Add <New Profile Name> Profile Dialog Box – Selected Permissions



Figure 6-13. 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-14).

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

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

To add domain of permissions in a folder:



2. Click Add Domain to select permissions for a domain (see Figure 6-16).

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

To delete permissions:

1. Select a permission in the left pane.

2. Click (see Figure 6-12).

You cannot delete permissions from a Base Profile.

Note



Figure 6-14. Right Mouse Pop-Up Menu

Figure 6-15. Select Range Dialog Box



Figure 6-16. 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-17. Selecting IP Address Permissions

Adding a Profile with No base Profile

To add a profile with no base profile:

1. From the EMS Security Administrator window (see Figure 6-1), select Profile > Add.


2. Enter a Profile Name and a Profile Description.

3. Select a None for the Base Profile (see Figure 6-18).

The Add <NEW PROFILE NAME> Profile dialog box appears with the left column empty (see Figure 6-19).

4. Drag the whole set of permissions from a folder (see Figure 6-19) or drag one permission at a time to the left column (see Figure 6-20).

5. Click <Set>.

Refer to Working with Permissions to change permissions.



Figure 6-18. Add Profile – Base Profile NONE

Figure 6-19. Add <New Profile Name> Profile (NONE) Dialog Box



Figure 6-20. Dragging Permissions

When you add a profile based on an existing profile, you cannot double-click the

group permanent icon .

Note



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

2. Make any changes.

3. Click <Set>.

You cannot edit your own Profile properties.

Figure 6-21. Edit Profile

Removing a Profile

To remove a profile:

1. From the EMS Security Administrator window (see Figure 6-1), select Profile > Remove.

Note



The Confirm Profile Removal dialog box appears (see Figure 6-22).

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.

Figure 6-22. Confirm Profile Removal Dialog Box

Managing EMS Users

The EMS administrator can:

• Add users

• Edit users

• Remove users.

Figure 6-23. EMS Administrator User Menu

Adding a User

To add a user:

1. From the EMS Security Administrator window (see Figure 6-1), select User > Add.

The Add User dialog box appears (see Figure 6-24).

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

Note



Figure 6-24. 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-25).

2. If necessary, make changes to User Name, Description, Profile, or Lock.

You cannot edit your own User properties.

Note



Figure 6-25. 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-1), select User > Edit.

The Edit User dialog box appears (see Figure 6-25).

2. Click <Change Password>.

The Change Password dialog box appears (Figure 6-26).

3. Enter the new Password.

4. Enter the new password again to Confirm Password.

5. Click <Set>.

Note



Figure 6-26. 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-27).

2. Click <OK>.

Figure 6-27. Confirm User Removal Dialog Box

Administering Login Names

Figure 6-28. EMS Security Administrator Login Menu

Defining the Active Login Names

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-1), select Login > Active Login Table.

The Active Login Table dialog box appears.



Figure 6-29. Active Login Table Dialog Box

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

Performing Administrator Logout of User

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



Configuring Security Options

There are three tabs in the Configuration dialog box, accessible via Options > Configuration:

• Password

• Account

• Audit.

Figure 6-30. EMS Security Administrator Options Menu

Setting Password Policies

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-1), select Options > Configuration.

2. Click the Password tab (see Figure 6-31).

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-31. Configuration – Password Tab

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



Table 6-5. Configuration – Password Parameters (Cont.)


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 Account Policies

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

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-32. Configuration – Account Tab

Table 6-6. 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 Audit Policies

To configure a user’s audit policies:

1. From the EMS Security Administrator window (see Figure 6-1), select Options > Configuration.



2. Click the Audit tab (see Figure 6-33).

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-33. Configuration – Audit Tab

Table 6-7. 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/NGN (Unix) Ver. 1.8 Handling EMS Device Events 7-1

Chapter 7

Fault Management This chapter describes:

• Handling EMS Device Events – SNMP traps received from the network devices are converted by RADview-EMS/NGN (Unix) to events that you can view with the Event Browser (refer to Viewing EMS Device Events). You can use the Fault Administrator to configure the Event Browser (refer to Configuring the Event Browser).

• Handling RADview-EMS Events – Events received from the RADview-EMS system are recorded by the EMS Log Server. You can use the Log Viewer to view these events (refer to Viewing RADview-EMS Events). You can use the Log Administrator to configure log properties (refer to Configuring the EMS Log Service).

7.1 Handling EMS Device Events

Configuring the Event Browser

You can configure the following for the Event Browser, via the EMS Fault Administrator:

• Event Browser log parameters (refer to Setting Parameters for the Event Browser Log)

• SNMP trap forwarding destinations (refer to Defining SNMP Trap Forwarding Destinations)

• Fault clearance (refer to Defining Fault Clearance Procedures)

• Event Policies to manage the display and handling of events in the Event Browser (refer to Setting Event Policies).

To open the EMS Fault Administrator:

1. Open the EMS Admin Console window by clicking on the LaunchDesk toolbar.

The EMS Admin Console is displayed showing the NMS station name (see Figure 7-1).

2. Click the + to expand the Admin Console.

The list of EMS consoles is displayed (see Figure 7-2).

3. Select Fault Service in the list of consoles

The EMS Fault Administrator is displayed (see Figure 7-3and Figure 7-4).

Chapter 7 Fault Management User’s Manual

7-2 Handling EMS Device Events RADview-EMS/NGN (Unix) Ver. 1.8



User’s Manual Chapter 7 Fault Management


Figure 7-3. Fault Administrator – Left Side Columns

Figure 7-4. Fault Administrator – Right Side Columns

Setting Parameters for the Event Browser Log

You can configure the following Event Browser log parameters:

• Maximum number of log records

• Procedure when log reaches the maximum size

• Automatic event clearing.

Figure 7-5. 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 7-6). Refer to Table 7-1 for a description of the parameters.

2. Enter the Maximum No. of Log Records in Event Browser log.

3. Select Cyclic Log to define the procedure when the log reaches the maximum size, and enter the percentage of old records to remove when the log reaches its maximum size. If Cyclic Log is cleared, any new events are lost once the log is full.

4. Select Major/ Critical under Alerts and indicate the percentage of major/critical log events that trigger an event (which appears in the Event Browser).

5. Select Clear non-cleared events which are in the system for the last given days to configure automatic event clearing, and enter the time to check and the age of the events. The automatic event clearing procedure selects the



Cleared parameter for the event in the Event Browser, it does not remove the event.

6. Click <Set>.

Figure 7-6. Log Management Dialog Box

Table 7-1. Log Management Parameters

Parameters Function

Current No. of Log Records Indicates the current number Log Records

(read-only)

Max No. of Log Records The maximum number of Log Records in Event Browser

10,000 – 1,000,000

Cyclic

Cyclic Log 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



Parameters Function

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 Allows you to specify the percentage of the maximum size of the log before a

Major Alert is generated

Critical Allows you to specify the percentage of the maximum size of the log before a

Critical Alert is generated

Automatic Events Clearing

Clear non-cleared events

which are in the system for

the last given days

Select to configure automatic event clearing. The automatic event clearing

selects the Cleared parameter in the Event Browser (see Figure 7-38) for

events that meet the criteria for automatic event clearing, as defined by the

next two parameters.

Checking time once a day Time of day when to check for events to automatically clear, in hh:mm:ss

format

Clear events older than

(days)

Enter the number of days that events should be older than, to be

automatically cleared.

Setting Event Policies

You can define event policies to manage the way events are displayed in the Event Browser, and manage the behavior of the system upon receiving specific events and traps

You can add or remove policies via the Event Policy menu.

Figure 7-7. Fault Administrator Event Policy 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. In the Fault Administrator window, select Event Policy > Add…

The Add Event Policy dialog box is displayed (see Figure 7-8).

2. For Event Class, Source, and Instance, you can use the default value of Any to mean that the policy applies to all sources, all Instances, or all event classes, respectively. If you want to use Any for event class, skip to step 3. The following steps explain the procedure for selecting a specific event class:

a. In the Add Event Policy dialog box click Browse […] next to Event Class.

The Select Event dialog box is displayed (see Figure 7-9).

b. Double-click the desired event class group in the Select Event dialog box.

Note



The event class group is expanded in the Select Event dialog box (see Figure 7-10).

c. Select the desired event class from the expanded event class group.

The event class appears at the bottom of the Select Event dialog box (see Figure 7-11).

d. Click <Set>.

The event class appears in the Add Event Policy dialog box (see Figure 7-12).

3. If you want to use Any for source, skip to step 4. The following steps explain the procedure for selecting a specific source:

a. In the Add Event Policy dialog box click Browse […] next to Source.

The Select Node dialog box is displayed showing the NMS station name (see Figure 7-13).

b. Click the + next to the NMS station name to display the list of submaps, and then click the + next to the desired submap to display the list of nodes in the submap (see Figure 7-14).

c. Select the desired node and click <OK> to close the Select Node dialog box.

The node appears in the Add Event Policy dialog box (see Figure 7-15).

4. In the Add Event Policy dialog box click <Continue>.

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

Mask (see Masking an Event)

Severity (see Setting the Severity)

Duplication (see Duplicating Events Events)

Forwarding (see Forwarding)

Threshold (see Setting the Threshold)

Clearing (see Clearing )

Formatting (see Formatting).

Figure 7-8. Add Event Policy Dialog Box



Table 7-2. Add Event Parameters

Parameter Function

Event Class Browse button (…) – opens a list to select a specific Class.

You can set the event class only by using the Browse button.

Description Description of the selected event (Read-only)

Source Any

… – Opens a list to select a specific Source

Instance Instance in 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 7-9. Select Event Dialog Box



Figure 7-10. Select Event Dialog Box – Expanded Tree

Figure 7-11. Select Event Dialog Box – Event Class Selected

Figure 7-12. Add Event Policy Dialog Box after Event Class Selected



Figure 7-13. Select Node Dialog Box



Figure 7-14. Select Node Dialog Box, Expanded

Figure 7-15. Add Event Policy Dialog Box after Node Selected



Figure 7-16. Add Event Dialog Box with Policy Tabs

Masking an Event

To mask an event:

1. Click the Mask tab (see Figure 7-16).

2. Select Mask.

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

4. Select one of the following to specify when the event should be masked:

Always

Every Day –Specify the time and duration of the masking

On Date – Specify the date, time, and duration of the masking.

5. Click <Apply>.



Figure 7-17. Add Event Dialog Box – Mask Tab

Setting the Severity

To set the severity:

1. Click the Severity tab (see Figure 7-18).

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 7-18. Add Event Policy Dialog Box– Severity Tab

Duplicating Events Events

Duplication refers to 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 7-19).

2. If you want to configure 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 once if duplicate events occur within the specified interval.



Figure 7-19. Add Event Policy Dialog Box – Duplication Tab

Forwarding Events

The Forwarding tab allows you to specify where to send notification of an event when it occurs.

To set the forwarding:

1. Click the Forwarding tab (see Figure 7-20).

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 receives the events).



Select Generate SNMP Trap to create SNMP traps when receiving a certain event or trap. These traps/events are displayed in the SNMPc/HPOV maps when generated. Refer to Configuring Generated SNMP Traps for details on configuring the generated SNMP traps.

Select Forward SNMP Trap to send the SNMP traps to another station (PC or Unix). Before using this option, you must configure the SNMP trap forwarding destinations (refer to Defining SNMP Trap Forwarding Destinations). Refer to Configuring Forwarding SNMP Traps for details on configuring the forwarding of SNMP traps

4. Click <Apply>.

Figure 7-20. Add Event Policy Dialog Box – Forwarding Tab

Configuring Generated SNMP Traps

To add traps in the list of generated SNMP traps:

1. Click <Edit> next to Generate SNMP Trap.

The SNMP Traps dialog box is displayed (see Figure 7-21).

2. Fill-in the following in the Trap Header group:

Description –Text description of the trap



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

Community – Community for which to send the trap

SNMP version – Select V1, V2c, or V2c-inform

Host –IP address or host name of the station to which to send the traps

Port – Leave the default value.

3. Click <Add Trap> if you do not need to specify a variable for the trap.

The trap is displayed at the top of the dialog box.

4. If you want the trap to include variables:

a. Enter the required Object ID and Value of the variable you want the trap to include (according to the MIB). For Value, you can type in a value or select one of the following:

Device name – The host name of the device is used as the value

Device IP address – The IP address of the device is used as the value.

b. Click <Add Variable>.

The variable is shown in the Trap Variables table.

c. Repeat this procedure for each variable that you want to add to the Trap Variables table (see Figure 7-22).

d. Click <Add Trap>

The trap is displayed at the top of the dialog box.

5. When you have completed specifying traps and variables, click <Set>.

The SNMP Traps dialog box closes and your changes are applied.

To edit traps in the list of generated SNMP traps:



2. At the top of the dialog box, select the trap that you wish to edit

The Trap Header fields and Trap Variables table for the trap are displayed.

3. Edit the fields in the Trap Header if desired.

4. If you want to edit the trap variables:

To add a new variable, enter the Object ID and Value of the variable and click <Add Variable>.

To remove a variable, highlight the variable and click <Remove Variable>.

To update a variable, highlight it and enter your changes, then click <Update Variable>.

5. When you have completed the changes for the trap, click <Update Trap>.

6. When you have completed editing traps and variables, click <Set>.




To remove a trap from the list of generated SNMP traps:



2. At the top of the dialog box, select the trap that you wish to remove.

3. Click <Remove Trap>.

The trap is removed from the list.

4. Click <Set>.


Figure 7-21. SNMP Traps Dialog Box



Figure 7-22. SNMP Traps Dialog Box with Variables

Configuring Forwarding SNMP Traps

To specify forwarding SNMP traps:

1. Click <Edit> next to Forward SNMP Trap.

The SNMP Trap Forwarding dialog box is displayed (see Figure 7-23).

2. Click <Add> to display a dropdown list (see Figure 7-24) of the configured SNMP trap forwarding destinations, and select a destination.

The selected forwarding destination is shown in the SNMP Trap Forwarding dialog box (see Figure 7-25).

3. When you have completed specifying destinations, click <Set> in the SNMP Trap Forwarding dialog box to close it.

Figure 7-23. SNMP Trap Forwarding Dialog Box



Figure 7-24. SNMP Trap Forwarding Dialog Box – Select Destination

Figure 7-25. SNMP Trap Forwarding Dialog Box –Destination Selected

Setting the Threshold

The threshold defines a different event to be generated if the 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 7-26).

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

To select an event to be generated when the threshold is exceeded:

a. Click […] next to Event Type to display the Select Event dialog box (see Figure 7-9).

b. In the Select Event dialog box double-click the desired event class group to expand it, then select the desired event class from the expanded event class group (see Figure 7-10).


c. In the Select Event dialog box click <Set>.



The Select Event dialog box closes, and the selected event class appears in the Event Type parameter.

4. Click <Apply>.

Figure 7-26. Add Event Policy Dialog Box – Threshold Tab

Clearing Events

You can set the clearing policy for clearing events. Clearing the event means selecting the Cleared parameter in the Event Browser, it does not mean removing the event from the event log. This clearing procedure can be useful for example to clear the Link Down event if the Link Up event arrives.

To clear an event when it arrives:

1. Click the Clearing tab.

2. Select Clearing Policy.

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

a. Enter the Description of the Clearing.

b. Click […] next to Event to Clear to display the Select Event dialog box (see Figure 7-9).



c. In the Select Event dialog box double-click the desired event class group to expand it, then select the desired event class from the expanded event class group (see Figure 7-10).


d. In the Select Event dialog box click <Set>.

The Select Event dialog box closes, and the selected event class appears in the Event to Clear parameter.

4. Click <Apply>.

Figure 7-27. Add Event Dialog Box – Clearing Tab

Formatting Events

Formatting determines the string to be displayed in the Event Browser for the event.

To set the format of the trap/event:

1. Click the Formatting tab.

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



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

a. Enter the Description of the format

b. Enter the string to display in the Event Browser if this event occurs.

4. Click <Apply>.

Figure 7-28. 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 in the upper right part of the Fault Administrator dialog box.

To edit an existing event policy:

1. In the Fault Administrator window 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. In the Fault Administrator window select the event policy to be removed from the list of policies.

2. Click <Remove>.

The Remove Event confirmation dialog box is displayed.

Figure 7-29. Remove Event – Confirmation Dialog Box

3. Click <OK>.

The event policy is removed from the Event Class table.

Defining SNMP Trap Forwarding Destinations

You must define the destinations for SNMP trap forwarding if you want to specify SNMP trap forwarding in an event policy.

To define SNMP trap forwarding destinations:

1. In the Fault Administrator window, select Configuration > Forwarding Destinations.

The Forwarding Destinations dialog box is displayed (see Figure 7-30).

2. Click <Add>.

The Add Destination dialog box is displayed (see Figure 7-31).

3. Fill in the following:

Name –Name of the station to which to forward the traps

Host –IP address or host name of the station to which to forward the traps

Port – Leave the default value

SNMP version – Select V1, V2c, or V2c-inform

Source Address Variable – Object ID for source address

Source Community Variable – Object ID for source community

Retransmit – If selected, the trap is retransmitted

Forward Mode – Select how to forward the trap:

Original Trap – Forward the original trap sent by the agent device

EMS Event – Forward the EMS event as a trap



Original Trap + Severity – Forward the original trap sent by the agent device, with severity assigned by EMS.

4. In the Add Destination dialog box, click <Set>.

The Add Destination dialog box closes, and the forwarding destination is shown in the Forwarding Destinations dialog box (see Figure 7-30).

5. When you have completed specifying destinations, click <Close> in the Forwarding Destinations dialog box.

The Forwarding Destinations dialog box closes. You can use the defined destinations when configuring SNMP trap forwarding in an event policy (refer to Forwarding Events).

Figure 7-30. Forwarding Destinations Dialog Box



Figure 7-31. Add Destination Dialog Box

Defining Fault Clearance Procedures

You can define the probable cause and corrective actions for events. When the event occurs and is shown in the event browser, the defined probable cause and corrective actions can be viewed in the details of the event.

To configure fault clearance procedures:

1. In the Fault Administrator window, select Configuration > Fault Clearance.

The Fault Clearance Procedure dialog box is displayed (see Figure 7-32).

2. Click <Add>.

The Add Fault Clearance Event dialog box is displayed (see Figure 7-33).

3. For Event Class, Source, and Instance, you can use the default value of Any to mean that the policy applies to all sources, all Instances, or all event classes, respectively. If you want to use Any for event class, skip to step 4. The following steps explain the procedure for selecting a specific event class:

a. Click […] next to Event Class to display the Select Event dialog box (see Figure 7-9).

b. In the Select Event dialog box double-click the desired event class group to expand it, then select the desired event class from the expanded event class group (see Figure 7-10).


c. In the Select Event dialog box click <Set>.

The Select Event dialog box closes, and the selected event class appears in the Add Fault Clearance Event dialog box (see Figure 7-34).



4. If you want to use Any for source, skip to step 5. The following steps explain the procedure for selecting a specific source:

a. Click Browse […] next to Source.

The Select Node dialog box is displayed showing the NMS station name (see Figure 7-13).

b. Click the + next to the NMS station name to display the list of submaps, and then click the + next to the desired submap to display the list of nodes in the submap (see Figure 7-14).

c. Select the desired node and click <OK> to close the Select Node dialog box.

The node appears in the Add Fault Clearance Event dialog box (see Figure 7-35).

5. In the Add Fault Clearance Event dialog box, click <Set>.

The Add Fault Clearance Event dialog box closes, and the Fault Clearance Procedure dialog box displays the event, along with text boxes for the probable cause and corrective actions (see Figure 7-36).

6. If you wish to specify a probable cause, enter text describing the probable cause of the event in the Probable Cause text box.

7. If you wish to specify corrective measures, enter text describing corrective actions for the event in the Corrective Measures text box.

8. Click <Apply> to complete the fault clearance specification for the event.

If you entered probable cause and/or corrective actions, the Probable Cause and/or Correction options for the event are shown as selected (see Figure 7-37).

9. When you have completed specifying fault clearance procedures, click <Close> in the Fault Clearance Procedure dialog box.

The Fault Clearance Procedure dialog box closes. When an event occurs for which you have specified a fault clearance procedure, you can see the probable cause and corrective actions in the details of the event in the Event Browser.



Figure 7-32. Fault Clearance Procedure Dialog Box, Empty

Figure 7-33. Add Fault Clearance Event Dialog Box Figure 7-34. Add Fault Clearance Event Dialog Box – Event Class Selected

Figure 7-35. Add Fault Clearance Event Dialog Box – Node Selected



Figure 7-36. Fault Clearance Procedure Dialog Box, after Event Added



Figure 7-37. Fault Clearance Procedure Dialog Box, after Events Added with Probable Causes and Corrective Actions

Viewing EMS Device Events

SNMP traps received from the network devices are converted by RADview-EMS to events that you can view with the Event Browser.

The main functions 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:

• In the LaunchDesk toolbar, click the Event Browser icon .

The Event Browser window is displayed (see Figure 7-38).

Note



Terminology

Some terms that appear in 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)

• 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 allows 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 in the Net. Same as Source

• Source – One of the following:

An agent in the Net (same as NE)

The Server (initiates traps/events).



Figure 7-38. 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 – Normal

• White – Indeterminate. SNMP trap unrecognized, couldn’t be converted to event.

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

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

Note




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)

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

Severity Severity of event

Notes Indicates if notes exist for event

Selected (Yes), Cleared (No)

Toolbar Icons

Figure 7-39. Event Browser – Toolbar Icons

The Event Browser toolbar icons in the top left of the window are used for (from left to right):

• Details

• Notes

• Add Note

• Remove

• Save As

• Print

• Stop Refresh

• Refresh

• Pause

• Resume

• Edit Current Filter

• Acknowledge

• Unacknowledge

• Scroll Up

• Scroll Down.

Working with Filters

The File menu operations are:

• Open a Filter



• Save As – Saves the whole table as a PDF or HTML file

• Print – Prints the log

• Remove all events

• Export filter definition

• Import filter definition

• Exit.

To open a filter:

• In the Event Browser window, select File > Open > <filter_name>.

The filter is shown in orange at the bottom of the Event Browser window (see Figure 7-40).

Figure 7-40. Event Browser File Menu

To export filter definition:

• In the Event Browser window, select File > Export > <filter_name>.

A Save dialog box is displayed in which you can specify the location where to save the filter definition.



Figure 7-41. Save Filter Definition

To import filter definition:

• In the Event Browser window, select File > Import.

An Open dialog box is displayed in which you can specify the location of the filter definition.

Figure 7-42. Open Filter Definition

Refreshing Event Display

You can view new events that have occurred and events that have been modified.

To refresh the event display:

• Select View > Refresh.



Selecting Events

You can select Edit > Select All to perform Ack/Clear/Remove actions on all the events in the Event Browser window.

Figure 7-43. Event Browser Edit Menu

Acknowledging and Rejecting Events

You can perform the following actions on recorded events:

• Acknowledge – Mark an event as noticed

• Clear – Mark an event as currently irrelevant

To acknowledge events:

1. In the Event Browser log, select the event(s) to acknowledge.

2. From the Edit menu, select Acknowledge.

The Acked parameter in the line of the selected event is selected.

To un-acknowledge events:

1. In the Event Browser log, select the event(s) to be unacknowledged.

2. From the Edit menu, select UnAcknowledge.

The Acked parameter in the line of the selected event is cleared.

To clear events:

1. In the Event Browser log, select the event(s) to be cleared.

2. From the Edit menu, select Clear.

The Cleared parameter in the line of the selected event is selected.

To unclear events:

1. In the Event Browser log, select the event(s) to be uncleared.

2. From the Edit menu, select Unclear.



The Cleared parameter in the line of the selected event is cleared.

To remove events:

1. In 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 7-44).

Figure 7-44. Remove Event – 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 Edit menu, select Details.

The Details dialog box (see Figure 7-45) is displayed. If you defined probable cause and corrective actions in the EMS Fault Administrator for the event, they are displayed. Refer to Defining Fault Clearance Procedures for details on how to define probable cause and corrective actions for events.



Figure 7-45. Details Dialog Box

Entering Event Notes

You can add descriptive notes for events, change notes, and view the notes for an event. You can add a note to a single event or to multiple events.

To view notes for an event:

1. In the Event Browser log, select an event.

2. From the Edit menu, select Notes.

The Event Notes dialog box is displayed, showing any notes that exist for the event.



Figure 7-46. Event Notes Dialog Box

To add a note for the event:

1. In the Event Notes dialog box, click <Add>.

The Add Note dialog box is displayed (see Figure 7-47).

2. Enter the text of the note as desired.

3. Click <Set> in the Add Note dialog box.

The Add Note dialog box closes, and the note is shown in the Event Notes dialog box. In the Event Browser line where the event is shown, the Notes parameter is selected, to indicate that a note exists for the event.

To change an event note:

1. In the Event Notes dialog box, select the note that you wish to change, and click <Change>.

The Change Note dialog box is displayed (see Figure 7-48).

2. Change the text of the note as desired.

3. Click <Set> in the Change Note dialog box.

The Change Note dialog box closes, and the changed note is shown in the Event Notes dialog box.

To remove an event note:

1. In the Event Notes dialog box, select the note that you wish to remove, and click <Remove>.

The Remove Note confirmation dialog box is displayed (see Figure 7-49).

2. Click <OK> to confirm the removal.

The Remove Note dialog box closes, and the note no longer appears in the Event Notes dialog box. If the event no longer has any notes, then in the Event Browser line where the event is shown, the Notes parameter is cleared.



Figure 7-47. Add Note Dialog Box

Figure 7-48. Change Note Dialog Box

Figure 7-49. Remove Event Note – Confirmation Dialog Box



To add a note to one or more events:

1. In the Event Browser log, select one or more events.

2. From the Edit menu, select Add Note.

The Add Note dialog box is displayed (see Figure 7-47).

3. Enter the text of the note.

4. Click <Set>.

The note is added to the selected events, and the Add Note dialog box closes. In the Event Browser line where the events are shown, the Notes parameter is selected, to indicate that a note exists for the events.

Events can be handled by choosing one or more events, right-clicking and selecting the required action (Acknowledge, Unacknowledge, Notes, Add Note, Remove, Details).

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.

The filters allow you to specify criteria for which events are displayed (filtered). You can add, change, or remove filters from the Filter List dialog box (see Figure 7-50), which appears when you select View > Filter > Filter List.

Note

Note



Figure 7-50. 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 7-51 to filter by General criteria and Figure 7-52 to filter by Sources).

2. Complete the fields according to Table 7-4.

3. Click <Set>.



Figure 7-51. Add Filter Dialog Box – General Tab



Figure 7-52. Add Filter Dialog Box – Sources Tab



Figure 7-53. Add Filter Dialog Box – Event Classes Tab



Figure 7-54. Add Filter Dialog Box – Advanced Tab

Table 7-4. Add Filter Parameters / Change Filter Parameters

Parameters Possible Values / Remarks

Filter Name Name of filter

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

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.

Cleared Events



Parameters Possible Values / Remarks

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 event 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 7-55).

2. Complete the fields according to Table 7-4.

3. Click <Set>.



Figure 7-55. Change Filter Dialog Box – General Tab



Figure 7-56. Change Filter Dialog Box – Sources Tab



Figure 7-57. Change Filter Dialog Box – Event Classes Tab



Figure 7-58. Change Filter Dialog Box – Advanced Tab

For details on the General, Sources, Event Classes, and Advanced tabs, refer to Table 7-4.

To remove a filter:

1. In the Filter List dialog box, click <Remove>.

2. The Remove Filter confirmation dialog box is displayed (see Figure 7-59).

Note



Figure 7-59. Remove Filter Confirmation


7-52 Handling RADview-EMS Events RADview-EMS/NGN (Unix) Ver. 1.8

7.2 Handling RADview-EMS Events

RADview-EMS events are recorded in the following logs by the EMS Log Service:

• Security log – Displays events from the RADview-EMS security subsystem such as logins to EMS and audits

• System log –Displays events from the RADview-EMS system

• Application log – Displays events from the RADview-EMS management application.

Refer to Configuring the EMS Log Service for details on configuring the EMS Log Service. Refer to Viewing RADview-EMS Events for details on viewing the logs.

Configuring the EMS Log Service

The Log Service is designed to be consistent with ITU-T .735 and Telecom Log service. You can configure the properties of the RADview-EMS Log Service with the EMS Log Administrator

To open the EMS Log Administrator:

1. Open the EMS Admin Console window by clicking on the LaunchDesk toolbar.

The EMS Admin Console is displayed showing the NMS station name (see Figure 7-1).

2. Click the + to expand the Admin Console.

The list of EMS consoles is displayed (see Figure 7-2).

3. Select Log Admin in the list of consoles.

The EMS Log Administrator is displayed (see Figure 7-60). For each EMS log it shows the status, current size, and maximum size.

Figure 7-60. EMS Log Administrator


RADview-EMS/NGN (Unix) Ver. 1.8 Handling RADview-EMS Events 7-53

To configure the Log Service:

1. In the Log Administrator, select Action > Configuration.

The Log Admin Configuration dialog box is displayed (see Figure 7-61).

2. Configure the parameters according to Table 7-5.

Figure 7-61. Log Admin Configuration Dialog Box

Table 7-5. Log Admin Configuration Parameters

Parameter Function

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.

Viewing RADview-EMS Events

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

Setting the Log Display

Figure 7-63. 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, showing a list of active servers in the system that can be master or slave servers (see Figure 7-64).

If the dialog box does not display the list of EMS servers, click the EMS Servers parameter to expand the list.

Note



Figure 7-64. EMS Server Selection Dialog Box

2. Select the server and then click <Select>.

The selected server is used for the log service.

To filter the type of display:

1. From the Configuration menu, select Filter.

The Filter dialog box is displayed (see Figure 7-65).

2. Select the type of filter for the display, according to Table 7-6, and click <Set>.

Figure 7-65. Filter Dialog Box



Table 7-6. 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)

Saving, Printing, or Deleting Logs

You can save, print, or delete logs.

Figure 7-66. 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 apply only 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.

Note



To delete the whole log:


2. From the Action menu, select Delete > Log.

Delete Log applies only to the active tab.

Note


7-58 Testing the Unix User Environment RADview-EMS/NGN (Unix) Ver. 1.8

7.3 Testing the Unix User Environment

If you need to test the Unix user environment, for example because the RADview-EMS/NGN (Unix) application does not function properly, or upon request from RAD Technical Support, you can use the RADview User Environment Tool or you can test the environment with commands.

Testing with User Environment Tool

You can use the RADview Post Installation User Environment Tool to test the following in the user environment and installation:

• HPOV NNM process statuses

• 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 test the user environment with the user environment tool:

1. Log in as the user that you wish to test.

2. Type: /opt/MNG/MNGVIEWHP/bin/user_env.csh

As the script executes, it shows pass/fail messages on the screen, and writes the test results into the file user_env.log in the user home directory.

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

* RADview User Environment *

* *

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

* a dedicated RADview-HPOV installation. *

* *

* This script sets the User Environment variables for a *

* newly created user and performs User Environment tests *

* for an existing user. *

* *

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


RADview-EMS/NGN (Unix) Ver. 1.8 Testing the Unix User Environment 7-59

* *

* This script must run under csh environment only. *

* *

* User Environment variables are written into the *

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

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

Running user environment tests for an existing user.

Checking HPOV NNM processes status...

HPOV NNM processes are running.

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-67. Testing RADview User Environment – Existing User

In the example above, the script found one error:

*** WARNING: CDE Language variable is not set correctly. ***

Logout and modify the CDE language.

In the DTE login Dialog choose options > Language > c to en_GB.ISO8859-15> C-POSIX

Figure 7-68 illustrates how to correct the error.

Figure 7-68. Correcting the Informix LANG variable


RADview-EMS/NGN (Unix) Ver. 1.8 Testing the Unix User Environment 7-61

If you cannot correct the problem, send the file /export/home/g7/user_env.log to RAD Technical Support.

Testing with Commands

You can execute the commands in Table 7-7 to verify that the user environment is set correctly.

Table 7-7. Testing the User Environment

Environment Test Result Note

1 To check Informix installation

directory, type:

cat /etc/passwd | grep informix

informix:x:101:100::<INF_HOME>:/bin/sh

Example

If the Informix installation directory is

/opt/informix, result is:

informix:x:101:100::/opt/informix:/bin/sh

2 To verify Informix installation

directory, server, and SQL

Hosts file are defined, type:

env | grep INF

INFORMIXDIR=<INF_HOME>

INFORMIXSERVER=mng164

INFORMIXSQLHOSTS=<INF_HOME>/etc/sqlhosts

Example



INFORMIXDIR=/opt/informix

INFORMIXSQLHOSTS=/opt/informix/etc/sqlhosts

Else

Verify user's .cshrc file was edited

correctly, and logout / login was

performed

3 To verify ODBC installation

and home directories are

defined, type:

env | grep ODBC

ODBCDIR=<INF_HOME>/ odbc

ODBCHOME=<INF_HOME>/ cli/cli

Example



ODBCDIR=/opt/informix/odbc

ODBCHOME=/opt/informix /cli/cli

Else

Verify user's .cshrc file was edited

correctly, and logout / login was

performed

4 To verify MNG164_APP_PATH

(RADview-EMS/NGN (Unix)

home directory) is defined,

type:

echo $MNG164_APP_PATH

/opt/MNG/MNGVIEWHP Else

Verify the mng164_setenv.sh script was

executed by the user, and logout/login

was performed



Environment Test Result Note

5 To verify the

LD_LIBRARY_PATH variable

exists and points to the

Informix installation

directory, type:

env | grep LD_LIB

LD_LIBRARY_PATH=/opt/informix/odbc/lib:/opt/informix/odbc/drivers:/usr/lib:/opt/informix/odbc/lib:/opt/informix/odbc/drivers:/usr/lib:

/opt/informix/odbc/lib:/opt/informix/odbc/drivers:/usr/lib:/opt/OV/lib:/opt/informix/cli/lib:/opt/informix/cli/lib/esql:/opt/informix/cli/cli/dlls::/opt/OV/lib::/opt/informix/cli/lib:/opt/

Example



LD_LIBRARY_PATH=/opt/informix/odbc/lib=/opt/informix /odbc/drivers:/usr/lib

Else

Verify the mng164_setenv.sh script was

executed by the user, and logout/login

was performed.

6 To verify the CDE Language

variable is set correctly, type:

echo $LANG

(see Figure 7-68)

C Else

Modify the CDE language as follows: In

the CDE login dialog choose options >

language > c to en_GB.ISO8859-15 >

c-posix

7 To verify the user's shell is

csh, type:

echo $SHELL

/bin/csh Else

Change user shell to csh via admintool

8 To verify Informix database is

online, type:

onstat –

INFORMIX-OnLine Version 7.20.UC2 -- On-Line -- Up 11 days 22:33:56 -- 12272 Kbytes

Else

Unless Informix is reported to be online,

database is down

9 To verify the user's home

directory includes .odnb.ini

file, pointing to an ODBC

driver located under the

Informix installation

directory, type:

cat /<USER_HOME_DIR>/.odbc.ini|grep vsifmx7.so.1

Driver=<INF_HOME>/odbc/drivers/vsifmx7.so.1

Replace <USER_HOME_DIR> with the

user’s home directory.

In case the above commands do not solve the problem, or return unexpected results, contact RAD Technical Support and send the output of all the above commands. In addition, send the Unix user’s .dtprofile and .cshrc files.


RADview-EMS/NGN (Unix) Ver. 1.8 Frequently Asked Questions 7-63

7.4 Frequently Asked Questions

Q My /opt partition doesn’t have enough space for installation of RADview-EMS NGN. How can I install RADview-EMS NGN in a different partition?

A By default, the RADview-HPOV installation script attempts to perform the installation in the /opt partition. If the /opt partition lacks sufficient disk space, the installation script stops and indicates the minimum disk space needed to install the selected components.

If the /opt partition doesn’t have enough space for installation, you can either free the required disk space or create a symbolic link to another location on the disk that has sufficient disk space.

For example, to create a symbolic link between /opt and /export/home, use the following procedure:

1. Create a new directory named /export/home/MNG

2. Type: ln -s /export/home/MNG /opt/MNG

Q How can I change the size of the Informix database?

A By default, the installation script creates allocates 500 MB when it creates the Informix database. In addition, approximately 100 MB is used by Informix tools and ODBC drivers.

To change the default database size:

• Run the installation script with the -r<new size> option, where newsize specifies how many KB to allocate. An example is shown in the following command that allocates approximately 300 MB (refer to Chapter 2 for details on installing Informix):

./informix.install –r300,000

A ratio of 1 MB per managed node should be used to determine the database size. For example, if you plan to manage 200 network elements, then allocate 200 MB for the database plus an additional 100 MB for Informix tools and ODBC drivers.

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.

Note


7-64 Frequently Asked Questions RADview-EMS/NGN (Unix) Ver. 1.8

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

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

6. Stop the EMS server again.

7. Access svcsec.xml 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 file ems.sql to the Informix database directory.

2. Log in as RADview user (not as superuser).

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


RADview-EMS/NGN (Unix) Ver. 1.8 Frequently Asked Questions 7-65

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

Make sure that no errors are reported.

The following text 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. **********************************************************

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

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

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

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

8. Close all GUI dialog boxes and consoles.

9. Stop the EMS server.

10. Restart the EMS server.

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

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/NGN (Unix) systems require Solaris 10 and above, so your system may require a migration process. You


7-66 Frequently Asked Questions RADview-EMS/NGN (Unix) Ver. 1.8

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/NGN (Unix) package. In addition, each zoom application has a built-in Help application that displays the manual in a browser window.


RADview-EMS/NGN (Unix) Ver. 1.8 Technical Support 7-67

7.5 Technical Support

Technical support for RADview-EMS/NGN (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/�


7-68 Technical Support RADview-EMS/NGN (Unix) Ver. 1.8

RADview-EMS/NGN (Unix) Ver. 1.8 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/NGN (Unix) Ver. 1.8

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 the command: uname -a.

The Solaris version is displayed.

Figure A-3. Solaris Version

User's Manual Appendix A Migration Guide

RADview-EMS/NGN (Unix) Ver. 1.8 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 Performing Backup and Restore 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 section A.6.

5. Adjust Informix and TFTP setting according to the procedures mentioned in section 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 (refer to Chapter 4).

3. Install Solaris 10 on the new hardware as specified in section A.6.

4. Install HPOV NNM 7.51 as specified in section 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/NGN (Unix) Ver. 1.8

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 (for details refer to http://support.openview.hp.com/selfsolve/manuals). The included HPOV NNM upgrade procedures are provided only as recommendations.

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 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/DVD 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)

Notes

http://support.openview.hp.com/selfsolve/manuals�


RADview-EMS/NGN (Unix) Ver. 1.8 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 want 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 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/DVD 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/NGN (Unix) Ver. 1.8


8. Type s to skip.

The following message appears:Do you want to continue with this installation? (y/n)

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/DVD drive.

12. Type:

# cd /cdrom/cdrom0/

# ./install


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/NGN (Unix) Ver. 1.8 Installing/Upgrading to Solaris 10 A-7

b. Your CD 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/NGN (Unix) Ver. 1.8 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/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/NGN (Unix) Ver. 1.8 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 drive.

Note

http://support.openview.hp.com/selfsolve/manuals�


A-12 Installing HPOV 7.5 RADview-EMS/NGN (Unix) Ver. 1.8

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.

The following message appears: Do you to continue with this installation? (y/n)

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

12. Type:

# cd /cdrom/cdrom0/

# ./install


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/NGN (Unix) Ver. 1.8 Post-upgrade Procedures A-13

16. It is recommended to upgrade to 7.51 (please follow HP user manual for these procedures)

A.8 Post-upgrade Procedures

Adjusting TFTP Server in Solaris 10

Configure the TFTP server functionality for compatibility with Solaris 10.

To configure the TFTP server in the Solaris 10 environment:

1. Type: mkdir –p <directory name> (for example: mkdir –p /export/home/tftp)

2. Type: chmod –R 777 < directory name> (for example: chmod –R 777 /export/home/tftp)

3. Edit the /etc/inetd.conf file as follows:

Find the line starting with #tftp dgram udp6

Remove the # character

Remove the 6 from udp6 (should be just udp)

At the end of the line, you see –s <tftp_boot>. Change the <tftp_boot> to the directory you have just created, e.g., -s /export/home/tftp.

Figure A-5. TFTP Settings

4. Type: sync

5. Type: init 6

The system reboots.

6. After the restart, type: svcs |grep tftp.

No output should be displayed. If you receive the final configuration message (see Figure A-6), your configuration is already set.

7. Type: inetconv

All entries from /etc/inetd.conf are converted to SMF entries.

8. Type: svcs |grep tftp .

The final configuration message is displayed.

Figure A-6. Final Configuration Message


A-14 Post-upgrade Procedures RADview-EMS/NGN (Unix) Ver. 1.8

Adjusting Informix

To adjust Informix:

1. Login as root user.

2. Type: vi /etc/services

3. Add the following line to the file: sqlturbo 1526 /tcp (the location inside the list is not important).

Figure A-7. Adjusting Services File for Informix

4. Reboot the system.

5. Make sure Informix is running by typing: <Informix home directory>/bin/onstat –

The following confirmation message should be displayed:

Figure A-8. Informix Confirmation Message

RADview-EMS/NGN (Unix) Ver. 1.8 I-1

Index

—A—

Active login table, 6-29 ACU

help, 4-77 status messages, 4-66

ACU Automatic Configuration Upload, 4-52 client, closing, 4-78 client, opening, 4-54 immediate upload, 4-64 profiles, 4-58

activating, 4-64 adding, 4-59 deactivating, 4-64 editing, 4-60 nodes, selecting, 4-62 removing, 4-63

report table, 4-66 clearing, 4-76 filtering, 4-68 printing, 4-75 refreshing, 4-73 saving, 4-73

tasks, summary, 4-57 TFTP server, configuring, 4-52 TFTP settings, configuring, 4-57

Adding license, 4-91 security profile, 6-10 user, 6-26

Administrator login menu, 6-29 logout, 6-30

Agent change attributes, 3-14 creating, 3-9 deleting, 3-14 monitoring, 3-15 SNMP parameters, 3-12 Telnet, 3-40 Web Browser, 3-39 zoom application, 3-38

Alarms display categories, 3-15

Attributes change, 3-14 removing, 4-13

Autodiscovery HPOV, 4-2

Automatic deletion of nodes Disable, 4-2

—B—

Backup, 4-15 configuring, 4-17 database, 4-15 EMS, 4-15 license, 4-15 requirements, 4-15 running, 4-20 RV, 4-15

Backup and Restore, 4-15 Base profile

administrator, 6-11 montor, 6-11 operator, 6-11 selecting permissions, 6-12 technician, 6-11 using, 6-12

—C—

Changing agent attributes, 3-14 user password, 6-28

Client/Server distribution, 1-4

Community read, 3-27 write, 3-27

Configuration server tracing, 5-9

Console system, 5-2

Creating net hierarchy, 3-8 RAD device agent, 3-9

—D—

Date and time Auto mode, 4-96 net, 4-95

Default user, 3-19

Deleting agent, 3-14

Directory access, 5-11

Disable Delete Nodes, 4-2 Display

alarm categories, 3-15 Distribution

client, 1-4

Index User’s Manual

I-2 RADview-EMS/NGN (Unix) Ver. 1.8

server, 1-4 system, 1-4 territorial, 1-5

—E—

Edit profile, 6-25 user, 6-27

EMS admin console, opening, 3-21 admin console, using, 3-21 components installation, 2-3 fault management, 5-21 fault management, front end, 5-23 GUI, 3-20 license service, 5-19 logging in, 3-18 logging out, 3-20 opening, 3-16 running application, 3-16 starting server, 3-18 stopping server, 3-18

EMS user managing, 6-26

ENW, 4-84 Equivalent Node Weights, 4-84

—F—

FCAPS services, 1-6

File transfer TFTP, 4-22

Functions master/slave server, 1-6

—G—

GUI, 3-4

—H—

Hardware requirements, 1-7 Hierarchy

parameters, general, 3-26 Host

address, 5-33 HP OpenView session

Ending, 3-4 HPOV

autodiscovery, 4-2 Autodiscovery, disabling, 4-2 GUI, 3-4 map application rules, 3-6 map status color propagation, 4-1 screen display, 3-5

HPOV session sEnding, 3-4

—I—

Importing nodes, 3-41 Installation

Hardware requirements, 1-7 PC (client station), 2-19

RADview EMS NGN, 2-7 single station system, 2-3 Software requirements, 1-7

Installing license, 2-33

Internet addresses preparing, 3-8

—J—

Java naming, 5-11

—L—

LaunchDesk, 3-20 logging in, 3-18 synchronization, 4-4 toolbar, 5-29

License, 4-83 adding, 4-91 bundled, 4-85 Calculating Points, 4-85 installing, 2-33 Points, 4-85 removing, 4-91

License Calculator, 4-86 License service manager

Managed element list, 4-88 Opening, 4-86

License Service Manager Client Configuration, 4-94

Licenses installed viewing, 4-86

Licensing Terms, 4-83

Loading, manually security profile, 6-9

Logging in administrator, 6-29 EMS, 3-18

Logging out administrator, 6-30 EMS, 3-20

—M—

Managed element list, license service manager, 4-88

Maps moving objects, 3-7

—N—

NER explorer, 4-6 add entry, 4-11 adding attributes, 4-12 edit menu, 4-10 modifying attributes, 4-13 remove entry, 4-11 removing attributes, 4-13 rename entry, 4-11

Net creating, 3-7 hierarchy, creating, 3-8 network topology, 3-8

User’s Manual Index

RADview-EMS/NGN (Unix) Ver. 1.8 I-3

Net inventory, 4-78 editing entity, 4-82 filtering display, 4-81

Network element repository, 4-5 size, 4-84

Network element browser add hierarchy, 3-25 add node, 3-25 add nodes, 3-25 refresh, 3-25 remove, 3-25

Network element Browser add a hierarchy, 3-28 adding a node, 3-30 hierarchy menu, 3-25 importing nodes, 3-41, 3-42 node menu, 3-34 status icons, 3-24 stop importing nodes, 3-42

No base profile add profile, 6-13, 6-22

Node add, 3-30 add range, 3-32 details, 3-37 parameters, general, 3-31 view device via Telnet, 3-39 view device via Web browser, 3-38 view device via zoom, 3-37

Node names preparing, 3-8

Nodes importing, 3-41 network element Browser, 3-34

—O—

OVbackup, 4-20

—P—

Parameters agent SNMP, 3-12 EMS fault management, 5-21, 5-23 polling service, 5-24

Password, 3-19 EMS, 3-19 HPOV, changing, 3-2 policy, 6-31

PC client station installation, 2-19

Permissions access rights, 6-14 changing, 6-15 delete, 6-19 domain, 6-19 dragging, 6-24 folder, 6-18 hierarchy, 6-3 modify, 6-15 not available, 6-15 read, 6-15 write, 6-15

Poll Intervals, 4-2

Poll Retries, 4-2 Polling

service, 5-24 Profile

adding, 6-10 base, 6-12 editing, 6-25 manually loading, 6-9 no base, 6-13, 6-22 permissions, 6-14 removinge, 6-25 security, 6-2

—R—

Removing base profile, 6-25 license, 4-91 user, 6-29

Requirements Hardware, 1-7 Software, 1-7

Restore, 4-15 configuring, 4-17 requirements, 4-15 running, 4-21

RMI, 5-11, 5-14, 5-17 Running

EMS application, 3-16

—S—

Security, 5-12 adding profile, 6-10 manually loading profile, 6-9 no base profile, 6-13, 6-22 opening console, 6-1 profile, 6-2 service, 6-1

Selection name, 3-11 Server side

configuration, 4-93 Server tracing

configuration, 5-9 Services

CORBA event service, 5-15 CORBA name service, 5-15 EMS discovery, 5-26 EMS element network repository, 5-18 EMS log service, 5-17 EMS OSS Heartbeat, 5-28 EMS trap listener, 5-19, 5-25, 5-26 java name and directory service, 5-12

Setting HPOV autodiscovery, 4-2

Setting Polling Interval, 4-2 Setup

Hardware requirements, 1-7 Software requirements, 1-7

Single station, 1-4 Single station system

installation, 2-3 SMTP, 5-11 SNMP

configuration, 4-3

Index User’s Manual

I-4 RADview-EMS/NGN (Unix) Ver. 1.8

parameters, 3-12, 3-27 spy, 5-9, 5-10

SNMP spy, 5-31 description, 5-32 filters, 5-32 options, 5-32 reconnect, 5-34

Software requirements, 1-7 Starting

EMS server from command line, 3-18 service on system console, 5-7

Stopping EMS server from command line, 3-18 service on system console, 5-7

Sublevels collapsing, 4-83 expanding, 4-83

Synchronization settings, 4-4

System console EMS fault management, 5-21 EMS license service, 5-19 EMS server process, 5-5 open, 5-2 polling service, 5-24 starting service, 5-7 stopping service, 5-7

—T—

Terminology WAN maps, 3-5

TFTP file transfer, 4-22

TFTP file transfer add agent from map, 4-39 default settings, 4-26 default settings, 4-26 edit database, 4-27 Help menu, 4-51 Opening, 4-24 options, 4-32 product profile

adding, 4-27 remove agents, 4-39 report status messages, 4-49 reports, 4-49 Save database, 4-51 selecting nodes, 4-37 transferring files, 4-40

TFTP File Transfer adding agents, 4-38 download file, selecting, 4-34 editing product data, 4-34

TFTP server configuring, 4-23

Time Outs, 4-2 Trace monitor, 5-34 Tracing, 5-10

—U—

Uninstalling RADview, 2-34 Unix user

Creating, 2-30 Unix user environment

Defining, 2-31 User

account policy, 6-33 adding, 6-26 administering, 6-1 audit policy, 6-34 editing, 6-27 password policy, 6-31 remove, 6-29

User, Unix Creating, 2-30

Username, 3-19 Using

base profile, 6-12

—V—

Version browser, 5-29

—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 root map level rules, 3-6 submap level rules, 3-6 terminology, 3-5

WAN submap creating, 3-8

—Z—

Zone, 1-5

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/NGN (Unix) Ver. 1.8

Publication Number: 357-635-08/08

Please grade the manual according to the following factors:

Excellent Good Fair Poor Very Poor

Installation instructions � � � � �

Operating instructions � � � � �

Manual organization � � � � �

Illustrations � � � � �

The manual as a whole � � � � �

What did you like about the manual?


http://www.rad.com/�

Error Report

Type of error(s) or problem(s):

� Incompatibility with product

� Difficulty in understanding text

� Regulatory information (Safety, Compliance, Warnings, etc.)

� Difficulty in finding needed information

� Missing information

� Illogical flow of information

� Style (spelling, grammar, references, etc.)

� Appearance

� Other

Please list the exact page numbers with the error(s), detail the errors you found (information missing, unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.

Please add any comments or suggestions you may have.

You are: � Distributor

� End user

� VAR

� Other

Who is your distributor?

Your name and company:

Job title:

Address:

Direct telephone number and extension:

Fax number:

E-mail:

Publication No. 357-635-08/08

International Headquarters 24 Raoul Wallenberg Street

Tel Aviv 69719, Israel

Tel. 972-3-6458181

Fax 972-3-6498250, 6474436

E-mail [email protected]

North America Headquarters 900 Corporate Drive

Mahwah, NJ 07430, USA

Tel. 201-5291100 Toll free 1-800-4447234

Fax 201-5295777

E-mail [email protected]

www.rad.com The Access Company

radview-ems/ngn (unix) · solutions are client-server based systems that include “system”...

Documents