RADview-HPOV/ATM Ver. 5.2

RADview-HPOV/ATM
Unix-Based Element Management System for ATM
Applications
Version 5.2
User’s Manual
Notice
This manual contains information that is proprietary to RAD Data Communications Ltd. (“RAD”). No
part of this publication may be reproduced in any form whatsoever without prior written approval by
RAD.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other
intellectual property or other proprietary rights relating to this manual and to the RADview-HPOV/ATM
are proprietary products of RAD protected under international copyright law and shall be and remain
solely with RAD.
You shall not copy, reverse compile or reverse assemble all or any portion of the manual or the
RADview-HPOV/ATM. You are prohibited from, and shall not, directly or indirectly, develop, market,
distribute, license or sell any product that supports substantially similar functionality as the
RADview-HPOV/ATM, based on or derived in any way from the RADview-HPOV/ATM. Your
undertaking in this paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the RADview-HPOV/ATM package or to
downloading it and shall continue until terminated. RAD may terminate this Agreement upon the
breach by you of any term hereof. Upon such termination by RAD, you agree to return to RAD the
RADview-HPOV/ATM 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.
U.S. Headquarters
RAD Data Communications Inc.
24 Raoul Wallenberg St.
Tel Aviv 69719 Israel
Tel: 972-3-6458181
Fax: 972-3-6498250
E-mail: rad@rad.com
900 Corporate Drive
Mahwah, NJ 07430 USA
Tel: (201) 529-1100, Toll free: 1-800-444-7234
Fax: (201) 529-5777
E-mail: mailto:market@radusa.com
© 1994–2003 RAD Data Communications
Publication No. 357-250-02/04
License Terms
RAD hereby grants a non-exclusive, nontransferable worldwide license to the licensee of this software
product to use and install this RAD software product on one workstation only, in object code only for
the sole and internal purpose of configuring, monitoring and managing RAD’s hardware products.
Title. All claims to the contrary contained herein notwithstanding, title in and to this RAD software
product and documentation, including but not limited to, all copyright, patent, trade secret rights, and
intellectual property rights shall remain in and with RAD. The licensee of this software product shall
not copy, reverse compile or reverse assemble all or any portion of this software product.
Copies. This RAD software product and documentation shall not be copied, in whole or in part,
except as explicitly permitted by RAD or for internal backup or archival purposes.
Warranty
RAD does not warrant that this software product is free from errors and/or will run properly on all
computer hardware and/or operating systems. RAD does not warrant that this software product will
meet requirements of its licensee or operate in the combinations which may be selected for use by a
licensee or the end users or that the operation of this software product will be uninterrupted or error
free.
THE WARRANTIES ABOVE ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES, WHETHER
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE.
Limitation of Liability
RAD’s cumulative liability to you or any other party for any loss or damages resulting from any claims,
demands, or actions arising out of or relating to this Agreement and the RADview-HPOV/ATM shall not
exceed the sum paid to RAD for the purchase of the RADview-HPOV/ATM. In no event shall RAD be
liable for any indirect, incidental, consequential, special or exemplary damages or lost profits, even if
RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of Israel.
RADview-HPOV/ATM
Unix-Based Element Management System for ATM
Applications
Version 5.2
System
© 1994–2003 RAD Data Communications
Publication No.
02/04
Contents
Chapter 1. Introduction
1.1 RADview-HPOV for ATM Applications – Overview......................................... 1-1
Supported Products .................................................................................................1-1
Basic Features..........................................................................................................1-2
Alarms Monitoring ...................................................................................................1-2
Test Monitoring .......................................................................................................1-2
Viewing Active Events ..............................................................................................1-2
On-Line Help Support .............................................................................................1-2
Topology and Protocol.............................................................................................1-3
System Security........................................................................................................1-3
1.2
Basic Terminology........................................................................................... 1-4
Chapter 2. Installation
2.1 Installation Procedures.................................................................................... 2-1
Hardware Requirements ..........................................................................................2-1
Software Requirements ............................................................................................2-1
2.2
Installation ...................................................................................................... 2-2
Cluster Patches Installation.......................................................................................2-2
Informix Installation .................................................................................................2-3
RADview Installation................................................................................................2-4
2.3
Post Installation Steps...................................................................................... 2-8
Creating a User........................................................................................................2-8
User Environment Tests..........................................................................................2-12
2.4
License Installation........................................................................................ 2-15
Working With a Remote License Server .................................................................2-15
Loading the License File.........................................................................................2-15
2.5
Advanced Installation Options ...................................................................... 2-16
Informix Home Directory.......................................................................................2-16
Database Size ........................................................................................................2-16
RADview-HPOV Installation Directory ...................................................................2-17
2.6
Frequently Asked Questions ......................................................................... 2-18
FAQ 1419 .............................................................................................................2-18
FAQ 1391 .............................................................................................................2-18
FAQ 1070 .............................................................................................................2-18
FAQ 0837 .............................................................................................................2-19
FAQ 0988 .............................................................................................................2-19
FAQ 0887 .............................................................................................................2-20
FAQ 0803 .............................................................................................................2-20
FAQ 0830 .............................................................................................................2-21
FAQ 1302 .............................................................................................................2-21
2.7
2.8
Uninstalling RADview-HPOV........................................................................ 2-21
Uninstalling Informix..................................................................................... 2-22
Chapter 3. RADview-HPOV Startup
3.1 Getting Started................................................................................................ 3-1
HPOV Parameter Settings ........................................................................................3-2
3.2
3.3
RADview-HPOV‘s WAN Maps........................................................................ 3-4
HPOV Screen Display..................................................................................... 3-5
WAN Map Terminology...........................................................................................3-5
RADview-HPOV/ATM User’s Manual
i
Table of Contents
Map Application Rules .............................................................................................3-6
Moving Between Map Windows ..............................................................................3-7
Setting Polling Interval..............................................................................................3-8
3.4
Creating a Net ................................................................................................ 3-8
Net Functionality .....................................................................................................3-8
Preparing Node Names and Internet Addresses ........................................................3-8
Network Topology ...................................................................................................3-8
Creating a Net Hierarchy .........................................................................................3-9
3.5
Creating an Agent for the RAD Device .......................................................... 3-10
Selection Name .....................................................................................................3-12
Setting Agent SNMP Parameters.............................................................................3-13
Deleting an Agent ..................................................................................................3-15
Changing Agent Attributes......................................................................................3-15
3.6
Creating a Connection .................................................................................. 3-16
Changing Connection Attributes.............................................................................3-17
Viewing Multiple Connections ...............................................................................3-18
3.7
Agent Monitoring.......................................................................................... 3-19
Displaying Alarms Categories .................................................................................3-19
Moving Objects on the Map...................................................................................3-20
Chapter 4. RADview-HPOV System Functions
4.1 Backup, Restore and Undo Last Restore Utilities ............................................. 4-1
Backup ....................................................................................................................4-1
Restore ....................................................................................................................4-2
Undo Last Restore ...................................................................................................4-6
4.2
Security .......................................................................................................... 4-6
Starting an HP OpenView Session ............................................................................4-6
Viewing User Security Access Privileges ....................................................................4-8
Adding Users ...........................................................................................................4-9
Changing Users......................................................................................................4-12
Removing Users.....................................................................................................4-13
Security Log...........................................................................................................4-13
Logging Out of RADview........................................................................................4-14
4.3
4.4
4.5
Alarm List ..................................................................................................... 4-15
Setting Net Date and Time............................................................................ 4-16
TFTP File Transfer ......................................................................................... 4-17
Introduction...........................................................................................................4-17
Starting TFTP File Transfer......................................................................................4-19
Configuration.........................................................................................................4-20
Operation..............................................................................................................4-28
Reset .....................................................................................................................4-36
TFTP File Transfer Reports......................................................................................4-37
Save the Database .................................................................................................4-38
4.6
Net Inventory ............................................................................................... 4-39
Introduction...........................................................................................................4-39
Using the Net Inventory Table................................................................................4-40
Using Filters for the Display....................................................................................4-42
Editing an Entity.....................................................................................................4-44
Expanding/Collapsing Sublevels..............................................................................4-44
4.7
ii
Automatic Configuration Upload .................................................................. 4-45
Overview...............................................................................................................4-45
Setting up the TFTP Server in a Unix Workstation...................................................4-46
Opening the ACU Application ...............................................................................4-47
Closing the ACU Application..................................................................................4-50
RADview-HPOV/ATM User’s Manual
Table of Contents
4.8
ACU Configuration Operations ..............................................................................4-51
ACU Main Window – Reports Filter .......................................................................4-52
Configuration.........................................................................................................4-55
Options .................................................................................................................4-58
Net Statistics .................................................................................................. 4-67
Setting up the TFTP Server in a Unix Workstation...................................................4-67
Station's UDP Receive Buffer..................................................................................4-69
ACE-50/ACE-101 Statistics Collection .....................................................................4-71
ACE-202/ACE-2002 Statistics Collection .................................................................4-75
4.9 Date and Time Auto Mode ........................................................................... 4-78
4.10 RADview Licensing Function......................................................................... 4-79
Introduction...........................................................................................................4-79
License Service Manager ........................................................................................4-82
Chapter 5. RADview-HPOV for ATM
5.1 Introduction.................................................................................................... 5-1
RADview-HP OpenView for ATM on the SNMP Platform .........................................5-1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
ATM Functionality .......................................................................................... 5-2
The Port and Card Levels................................................................................ 5-3
Communication With the Agent ..................................................................... 5-5
Traps Monitoring ............................................................................................ 5-5
LED Indications .............................................................................................. 5-6
VPI/VCI Range for ACE-101 ............................................................................ 5-7
VPI/VCI Range for ACE-2002/2002E/202 ........................................................ 5-8
Appendix A. RADview User's Environment
RADview-HPOV/ATM User’s Manual
iii
Table of Contents
List of Figures
2-1. Informix Installation Terminal Screen......................................................................... 2-3
2-2. Informix Installation Terminal Screen (continued) ...................................................... 2-3
2-3. RADview Installation Dialog Box ............................................................................... 2-5
2-4. RADview Installation Product List .............................................................................. 2-5
2-5. Directory Confirmation Dialog Box............................................................................ 2-5
2-6. Informix Path Dialog Box........................................................................................... 2-6
2-7. Incorrect Directory Dialog Box .................................................................................. 2-6
2-8. Informix Not Running Dialog Box.............................................................................. 2-7
2-9. RADview Installation – Upgrade Dialog Box .............................................................. 2-7
2-10. Admintool: Users Screen ......................................................................................... 2-8
2-11. Admintool: Add User Screen ................................................................................... 2-9
2-12. Set User Password Screen...................................................................................... 2-10
2-13. RADview User Environment – New User ............................................................... 2-11
2-14. RADview User Environment – Existing User........................................................... 2-13
2-15. Correcting the Informix LANG variable (Solaris 8) .................................................. 2-14
2-16. Uninstalling Informix ............................................................................................. 2-22
3-1. Getting Started Screen............................................................................................... 3-1
3-2. Setting Time-out........................................................................................................ 3-3
3-3. Network Object Palette ............................................................................................. 3-9
3-4. Connector Palette for the Device Agent................................................................... 3-10
3-5. Add Object ............................................................................................................. 3-11
3-6. SNMP Configuration................................................................................................ 3-13
3-7. Confirm Delete ....................................................................................................... 3-15
3-8. Add Object ............................................................................................................. 3-16
3-9. Define Connection .................................................................................................. 3-17
3-10. Connection Information ........................................................................................ 3-17
3-11. Multiple Connections ............................................................................................ 3-18
3-12. Alarm Categories Window..................................................................................... 3-19
3-13. All Alarms Browser ................................................................................................ 3-19
4-1. Backup File ............................................................................................................... 4-2
4-2. Restore File ............................................................................................................... 4-3
4-3. Restore Dialog Box .................................................................................................... 4-4
4-4. Modifying in the Restore Dialog Box.......................................................................... 4-5
4-5. Login Dialog Box ....................................................................................................... 4-6
4-6. Access Denied Dialog Box......................................................................................... 4-7
4-7. Change Password Dialog Box .................................................................................... 4-7
4-8. Security Capabilities Dialog Box ................................................................................ 4-8
4-9. Add User Dialog Box................................................................................................. 4-9
4-10. Change User Dialog Box........................................................................................ 4-12
4-11. Remove User Dialog Box....................................................................................... 4-13
4-12. Security Log Dialog Box......................................................................................... 4-13
4-13. Logout Dialog Box................................................................................................. 4-14
4-14. ATM Active Alarm List Dialog Box ......................................................................... 4-15
4-15. Network Time & Date Configuration ..................................................................... 4-16
4-16. TFTP File Transfer – Opening Window .................................................................. 4-17
4-17. Opening TFTP File Transfer Application – HPOV................................................... 4-19
iv
RADview-HPOV/ATM User’s Manual
Table of Contents
4-18.
4-19.
4-20.
4-21.
4-22.
4-23.
4-24.
4-25.
4-26.
4-27.
4-28.
4-29.
4-30.
4-31.
4-32.
4-33.
4-34.
4-35.
4-36.
4-37.
4-38.
4-39.
4-40.
4-41.
4-42.
4-43.
4-44.
4-45.
4-46.
4-47.
4-48.
4-49.
4-50.
4-51.
4-52.
4-53.
4-54.
4-55.
4-56.
4-57.
4-58.
4-59.
4-60.
4-61.
4-62.
4-63.
4-64.
4-65.
4-66.
4-67.
Configuration Menu .............................................................................................. 4-20
Default Settings Dialog Box ................................................................................... 4-20
Edit Database Dialog Box ...................................................................................... 4-21
Add Product Dialog Box ........................................................................................ 4-22
Select File to Download Dialog Box – Unix ........................................................... 4-26
Select File to Download Dialog Box – PC .............................................................. 4-26
Edit Product Dialog Box ........................................................................................ 4-27
Operation Tab....................................................................................................... 4-28
Add Agents from Map Dialog Box.......................................................................... 4-30
Add Agent Dialog Box ........................................................................................... 4-31
TFTP File Transfer – Operation .............................................................................. 4-33
Selected Nodes Operation Dialog Box................................................................... 4-36
Selected Nodes Operation Dialog Box – Selection................................................. 4-36
Selected Nodes Operation Dialog Box – Confirmation .......................................... 4-36
Report Tab ............................................................................................................ 4-37
Net Inventory Opening Window ........................................................................... 4-39
Opening Unix Application..................................................................................... 4-40
Inventory List Filter ................................................................................................ 4-42
Edit Dialog Box...................................................................................................... 4-44
Expand All ............................................................................................................. 4-44
Edit inetd File ........................................................................................................ 4-47
Opening the ACU application ............................................................................... 4-48
Start Server Terminal Message ............................................................................... 4-49
ACU Server Disable Message................................................................................. 4-49
TFTP Disable Message ........................................................................................... 4-49
Close Server Confirmation Dialog Box ................................................................... 4-50
Close Server .......................................................................................................... 4-50
Report Filter – Final Status Only ............................................................................ 4-53
Report Filter – Showing Intermediate Reports ........................................................ 4-54
Save Report Dialog Box ......................................................................................... 4-55
Print Report Dialog Box......................................................................................... 4-56
Clearing Report Dialog Box ................................................................................... 4-56
Upload Now Confirmation Dialog Box .................................................................. 4-57
Exit Automatic Configuration Upload Confirmation Dialog Box ............................. 4-57
Schedule Start Time and Date Dialog Box ............................................................. 4-59
Schedule Date....................................................................................................... 4-59
Schedule Time ...................................................................................................... 4-59
Schedule Time Interval .......................................................................................... 4-60
IP Addresses in mng164_FileTransfer..................................................................... 4-61
TFTP Settings......................................................................................................... 4-62
Automatic Configuration Upload Nodes Selection Dialog Box ............................... 4-64
Nodes Selection Dialog Box– for Agent ................................................................. 4-65
All Agents Dialog Box – Status ............................................................................... 4-66
Edit inetd File ........................................................................................................ 4-69
Net Statistics Dialog Box........................................................................................ 4-70
Agent Selection Dialog Box ................................................................................... 4-70
Date & Time Auto Mode dialog Box...................................................................... 4-78
General Tab .......................................................................................................... 4-83
Managed Element List ........................................................................................... 4-84
Managed Element List – Continued ....................................................................... 4-84
RADview-HPOV/ATM User’s Manual
v
Table of Contents
4-68.
4-69.
4-70.
4-71.
4-72.
4-73.
4-74.
4-75.
File Menu.............................................................................................................. 4-85
Add License .......................................................................................................... 4-86
Remove License Warning ...................................................................................... 4-87
Action Menu ......................................................................................................... 4-88
Service Console..................................................................................................... 4-88
Options Menu....................................................................................................... 4-88
Server Side Configuration ...................................................................................... 4-89
Client Side Configuration....................................................................................... 4-90
5-1. ACE-101 Agent View ................................................................................................. 5-2
vi
RADview-HPOV/ATM User’s Manual
Table of Contents
List of Tables
4-1. Access Level Definitions .......................................................................................... 4-10
4-2. ATM Active Alarm List Parameters ........................................................................... 4-15
4-3. Configuring Default Parameters ............................................................................... 4-20
4-4. Add/Edit Product Parameters ................................................................................... 4-22
4-5. TFTP File Transfer Options – by Device ................................................................... 4-24
4-6. TFTP File Transfer Operation Parameters................................................................. 4-29
4-7. Add Agent Parameters ............................................................................................. 4-32
4-8. Download & Reboot NMS Operations .................................................................... 4-35
4-9. TFTP File Transfer - Report Tab Parameters ............................................................. 4-37
4-10. Status Messages ..................................................................................................... 4-38
4-11. Inventory Table Parameters ................................................................................... 4-40
4-12. Inventory List Filter Parameters .............................................................................. 4-43
4-13. ACU Management Options ................................................................................... 4-51
4-14. Schedule Parameters ............................................................................................. 4-60
4-15. TFTP Settings......................................................................................................... 4-62
4-16. Equivalent Node Weights ...................................................................................... 4-80
4-17. Bundled Licenses .................................................................................................. 4-81
4-18. License Status........................................................................................................ 4-83
4-19. Managed Element List ........................................................................................... 4-85
4-20. Server Side Configuration ...................................................................................... 4-89
4-21. Client Side Configuration....................................................................................... 4-90
5-1. ACE LED Indicators ................................................................................................... 5-6
5-2. VPC Ranges............................................................................................................... 5-7
5-3. VCC Ranges .............................................................................................................. 5-7
RADview-HPOV/ATM User’s Manual
vii
Table of Contents
viii
RADview-HPOV/ATM User’s Manual
Chapter 1
Introduction
This chapter provides a general introduction to RADview-HPOV for ATM
Applications, which is used for managing the ATM family of products.
1.1
RADview-HPOV for ATM Applications – Overview
Supported Products
RADview-HPOV for ATM Applications provides network management for ACE-50,
ACE-101, ACE-202 and ACE-2002/2002E.
ACE-50 is a manageable demarcation point between private and public
high-speed access lines.
ACE-101 can be used as an ATM NTU (Network Termination Unit) for native ATM
or as a Multiservice Access Concentrator (MSAC). Located at the customer
premises, it can be controlled by an ATM service provider, or it can be used as
part of a corporate ATM-based WAN.
ACE-202 is a Multiservice Access Concentrator and a Network Termination Unit
(NTU) for public and private ATM networks.
ACE-2002/2002E is a Multiservice Access Concentrator (MSAC) that can be used
as a carrier-owned demarcation device or as a corporate concentrator connected
to the public ATM network.
RADview-HPOV for ATM Applications – Overview
1-1
Chapter 1 Introduction
RADview-HPOV/ATM User’s Manual
Basic Features
RADview-HPOV provides a flexible, reliable environment for planning and
preparing network configurations for ATM agents, while complying with standard
management protocols for monitoring, control and diagnostics.
Using RADview-HPOV, you can define nets, plan the required connections
between ATM agents within a given net, and configure the nets to adapt their
performance to current conditions. You can create map-hierarchies by defining the
related agents and the communication between them. The map (hierarchy) name
is also the net name.
RADview-HPOV maintains its own database to support sanity check algorithms
and enforce integrity among the network components. The reliability of the
integrity depends partially upon the accuracy of the configuration information that
you provide.
RADview-HPOV provides monitoring and control functions that extend from the
network down to the level of the individual ports, physical and ATM layers and per
VP/VC analysis. These functions include the preparation of network configurations,
the preparation of a set of conditions to alter the configurations as needed, the
initiation of tests and the monitoring of agent performance.
Alarms Monitoring
Upon request, you may dynamically display a list of generated alarms at the
management station. The system polls the agents for active alarm status (existence
of state or event alarms). You can display active alarms for three different levels:
TDM agent, card, and port.
Colors indicate if TDM agents, cards, and ports have active alarms.
Test Monitoring
Upon user request, the management station enforces testing on various objects.
The agents are polled for current test status.
Colors indicate test status at the card or port level.
Viewing Active Events
The RADview-HPOV screen includes an Event Window, from which you can
choose to display trap and event messages that arrive from active network
elements. It contains a choice of six types of event lists.
On-Line Help Support
Each window includes the Help menu option which allows you to access help
related to the current screen. The Help is written according to HP OpenView
Windows Online Help system guidelines.
1-2
RADview-HPOV for ATM Applications – Overview
RADview-HPOV/ATM User’s Manual
Chapter 1 Introduction
Topology and Protocol
RADview-HPOV can simultaneously monitor multiple nets of ATM agent systems.
The communication with the managed ATM agent passes through the V.24/RS-232
communication port of the host workstation, or through a dial-up modem.
The protocol of communication is SNMP over SLIP. The first directly connected
ATM agent serves as a router to the other ATM agents in the net through their
communication links, or their CL cards.
System Security
The management system is secured from unauthorized users. In order to enter the
system, you must first enter a login name and then a password. The user is able to
start HP OpenView only after password validation.
Management system security is provided through the standard security mechanism
of a UNIX system.
RADview-HPOV for ATM Applications – Overview
1-3
RADview-HPOV/ATM User’s Manual
Chapter 1 Introduction
1.2
Basic Terminology
The following terminology is used in this manual:
1-4
Net
A collection of TDM agents that can be configured as a group
connected by their communication links. A net can also
comprise a single stand-alone unit.
Configuration
A collection of operating parameters that can be set, and
upon verification of their integrity, stored and saved in the
TDM agent and/or in the management station.
Download
The process of transferring a configuration to a TDM agent. A
configuration may be programmed and stored at the
management station without being downloaded.
State Alarm
An alarm that indicates a long-term change in the agent's
status.
Event Alarm
An alarm that notifies you of a sudden change in the agent
status.
Active State
Alarm
A state alarm that is currently valid.
Active Event
Alarm
An event that you have not cleared yet.
Programmed
Card
A programmed card corresponds to an actual card that should
be installed in a specific slot position, according to the TDM
agent configuration.
Basic Terminology
Chapter 2
Installation
This chapter presents the procedures to:
•
Install the RADview-HPOV software
•
Set the operating parameters
•
Begin working with RADview-HPOV.
2.1
Installation Procedures
RADview-HPOV for ATM Applications version 5.2 can be installed only over
Solaris 2.8 Operating System, according to the following minimum hardware and
software requirements:
Hardware Requirements
Note
•
SUN ULTRA 10 or SUN Blade 150 workstation
•
Free space under /opt: from 1 GB to 2 GB (depending on the amount of
applications installed)
•
600 MB for Informix (under any partition)
•
512 MB RAM
•
768 MB swap file
•
CD-ROM drive
•
Color monitor (17" minimum) supporting 1152 X 900 resolution
•
Mouse
•
Printer and printer port (optional)
If you do not have enough hard disk space to install Informix, refer to Section 2.4 Advanced Installation Options.
Software Requirements
The following software should be installed on your computer before installing
RADview-HPOV:
Note
•
HP OpenView NNM Version 6.31
•
CDE 1.4
•
SUN Solaris Version 2.8, February 2002 or later
No other Solaris versions (for example, 2.5.1, 2.6, 2.7) are supported.
Installation Procedures
2-1
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
2.2
Installation
The RADview package comes with three CD-ROMs:
Note
•
One CD with RADview-HPOV/Database, which includes Informix
•
One CD with RADview-HPOV/Supplement, which includes cluster patches
installation.
•
One CD with RADview-HPOV/ATM, which includes the RADview application
(RAD MIB, RFC list, RADview Installation).
Starting from this version, a license server is integrated in RADview. The license
server protects the SW by restricting the installation of the RADview server to a
single host/computer and restricting the number of network elements that can
be managed by the system (according to the installed RADview license details).
In case you install this RADview version as an upgrade to an existing system,
you will be required to install a license. Contact your RAD sales manager for
additional details.
Cluster Patches Installation
This bundle provides the recommended patches for support of the JavaTM platform,
standard edition on the SolarisTM 2.8 operating environment. These patches are
considered the most important and highly recommended patches that avoid the
most critical system, user or other bugs related to the functionality of the JavaTM
platform on the SolarisTM 2.8 operating environment. They have been reported
and fixed by Sun (more information can be found in CLUSTER_README file
under “RADview-HPOV/Supplement for Solaris 8 only version 2.00” CD-ROM).
To perform the SolarisTM 2.8 patch installation:
1.
Log in as user root.
2.
Type: csh
3.
Insert the RADview-HPOV/Supplement for Solaris 8 only ver. 2.00 CD-ROM
into the CD-ROM drive.
4.
Type: cd /cdrom/cdrom0/patches
To run the install_cluster script:
1.
Type: ./ install_cluster
2.
Reboot the workstation for all patches to take effect:
Type: sync
Type: init 6.
2-2
Installation
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
Informix Installation
1.
Log in as user root.
2.
Type: csh
3.
Insert the RADview-HPOV/Database CD-ROM into the CD-ROM drive.
4.
Type: cd /cdrom/cdrom0/informix
5.
Type: ./informix.install
6.
When prompted, select the Informix home directory path.
7.
When prompted, approve the system reboot. During the Informix installation
the /etc/system file is automatically updated. The installation script prompts
you to approve a system reboot, so that the modification can take affect.
Make sure you close all running applications before initiating the Informix
installation script.
Figure 2-1. Informix Installation Terminal Screen
8.
When the system comes up, log in as user root.
9.
Type: csh
10. Type: cd /cdrom/cdrom0/informix
11. Type: ./informix.install
Figure 2-2. Informix Installation Terminal Screen (continued)
Installation
2-3
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
RADview Installation
Note
While working with the SUN Solaris 2.8 operating system, no more than 10
different types of RADview applications can be installed on the same workstation.
Passing this limit may cause the workstation to freeze when you add an icon to the
map. Since this package includes only four applications, the limitation is relevant
only when other RADview-HPOV modules are installed.
Installation will take between five and twenty minutes depending on the hardware
platform (see the sample RADview installation figure, below).
1.
Log in as user root.
2.
Type:
csh
cd /tmp
source /<INFORMIXDIR>/.mng164_inf.csh
Note
Replace <INFORMIXDIR> with your Informix installation directory (for example
/export/home/informix).
3.
Insert the RADview-HPOV/TDM Application CD-ROM into the drive.
4.
Type: cd /cdrom/cdrom0/radview
5.
Verify that Informix is running by typing: onstat –
If Informix is online the following message should appear:
INFORMIX-OnLine version 7.31.UDI - -On-Line- -
There are two options to install RADview applications:
•
Using the command line
•
Using the GUI.
Command Line Installation
To install RADview applications using the command line:
Note
2-4
1.
Type: ./install.rad
2.
Select the products to be installed according to the displayed table. Enter each
product's initials separated by spaces.
In case this is an upgrade of an existing RADview installation, the following message
will be displayed:
/opt/MNG/MNGVIEWHP/WAN already exists, Overwrite or Quit [oq] --->
Type "o" to overwrite or "q" to quit.
Installation
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
GUI Installation
To install RADview applications using the GUI Installation:
1.
Type: ./install_gui.rad
The RADview Installation window appears.
Figure 2-3. RADview Installation Dialog Box
2.
Click <OK>.
The RADview Installation Product List appears (see Table 4-5).
Figure 2-4. RADview Installation Product List
3.
Select the product/s to be installed and click <Install>.
A confirmation dialog box appears (see Figure 2-5).
Figure 2-5. Directory Confirmation Dialog Box
Installation
2-5
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
4.
Perform one of the following:
If the Informix installation directory is correct, press <Yes>.
Installation continues normally as described in Upgrade on page 2-7.
If Informix is not running, continue as described in Informix Not Running
on page 2-7.
If the Informix installation directory is not correct, press <No>.
A dialog box requests you to type the Informix Installation path (see
Figure 2-6).
Figure 2-6. Informix Path Dialog Box
5.
Press <OK>.
If the path name is correct, Informix Installation continues as described in
Upgrade on page 2-7.
If the path is correct, but Informix is not included, continue as described in
Informix Not Running on page 2-7.
If the path name is not correct, a message appears (see Figure 2-7).
Figure 2-7. Incorrect Directory Dialog Box
6.
Press <OK>.
The Informix Path Dialog Box appears (see Figure 2-6).
2-6
Installation
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
Informix Not Running
If Informix is not running or is not installed in the correct directory:
1.
Press <OK> in the dialog box shown in Figure 2-8.
Figure 2-6 appears.
2.
Follow the instructions described in GUI Installation on page 2-5.
Figure 2-8. Informix Not Running Dialog Box
Upgrade
1.
If this is an upgrade of an existing RADview installation, the message box
shown in Figure 2-9 appears.
Figure 2-9. RADview Installation – Upgrade Dialog Box
2.
Click <Overwrite> or <Quit>.
When the installation has completed, you will receive a message:
Installation Done.
Note
In case this is an upgrade of an existing RADview installation, the following message
will be displayed:
/opt/MNG/MNGVIEWHP/WAN already exists, Overwrite or Quit [oq] --->
Type "o" to overwrite or "q" to quit.
Installation
2-7
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
2.3
Post Installation Steps
After completing RADview installation, the following must be done:
•
Create a RADview User. We recommend that you select C as the user's
SHELL. For an example of how to create a user using admintool, see Creating
a User on page 2-8.
•
Set up the user's environment to include the variables needed for the
operation of RADview-HPOV. This step has to be performed for each and
every user who will use RADview-HPOV. For more information see Using the
RADview Post Installation User Environment Tool on page 2-10.
Creating a User
Before opening RADview-HPOV create a user and set the environment to include
the variables needed for RADview, HPOV and Informix.
Defining a User with Admintool
To define a user:
1.
Log in as root.
2.
Open a terminal and type: admintool &
The Admintool: Users window is displayed (see Figure 2-10).
Figure 2-10. Admintool: Users Screen
2-8
Post Installation Steps
RADview-HPOV/ATM User’s Manual
3.
Chapter 2 Installation
From the Edit menu, choose Add.
The Admintool: Add User window appears (see Figure 2-11)
Figure 2-11. Admintool: Add User Screen
4.
Specify the user identity values for the following variables:
User Name field – Type your first name (for example)
User ID field – Use the provided value
Primary Group – Use the provided value
Secondary Group – Skip
Comments – Skip
Login Shell – Select C.
Post Installation Steps
2-9
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
5.
Set the account security as follows:
From the password field, choose Normal Password.
The password must be at least 6 letters long and entered twice.
Supply a password and click OK. The Set User Password window appears
(see Figure 2-12).
Figure 2-12. Set User Password Screen
6.
Specify the Home Directory. Specify the path as /export/home/<username>.
7.
Click OK to create the user account.
8.
From File menu, click Exit to close the Admintool dialog box.
9.
Log out by clicking Exit, on the bottom of the screen, and log in as the user
that you have defined.
Using the RADview Post Installation User Environment Tool
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. Both a new user and an existing user who performs
User Environment Tests can use it.
To use the RADview Port Installation User Environment Tool:
1.
After you create a New User and login again (see Defining a User with
Admintool), type:
/opt/MNG/MNGVIEWHP/bin/user_env.csh and press <Enter>.
The script sets the User Environment.
2-10
Post Installation Steps
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
***************************************************************
*
*
*
*
*
*
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-13. RADview User Environment – New User
2.
The user files are edited automatically.
3.
A message appears for you to logout and re-login (to activate the changes).
4.
Run the script again for Environment Tests.
Post Installation Steps
2-11
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
User Environment Tests
When an existing user needs to perform User Environment Tests, such as when
RADview application does not function properly, or upon request from RAD
Technical Support, the script performs the following “User Environment and
Installation” tests according to ‘Testing the User Environment’ (RADview User
Manual):
•
HPOV NNM processes status
•
Informix variables
•
Informix database Online status
•
ODBC variables
•
ODBC driver
•
RADview application path (MNG164_APP_PATH)
•
Dynamic Libraries variable (LD_LIBRARY_PATH)
•
CDE Language Variable (LANG)
•
SHELL variables.
•
Informix disk space capacity
To perform the User Environment Tests:
1.
Login as the RADview user that you have created in Defining a User with
Admintool.
2.
Type: /opt/MNG/MNGVIEWHP/bin/user_env.csh and press <Enter>.
The script shows pass/fail messages on the screen, and writes the test
results into the file user_env.log in the user’s home directory.
***************************************************************
*
*
*
RADview 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.
*
*
*
**************************************************************
2-12
Post Installation Steps
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
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 2-14. RADview User Environment – Existing User
Post Installation Steps
2-13
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
In the example above, the script found 1 error.
*** WARNING: CDE Language variable is not set correctly. ***
Logout and modify the CDE language.
In the DTE login Dialog choose options > Language > c to
en_GB.ISO8859-15> C-POSIX
Figure 2-15 shows how to correct the error.
Figure 2-15. Correcting the Informix LANG variable (Solaris 8)
If you cannot correct the problem, send the file: /export/home/<user
name>/user_env.log to RAD Technical Support.
2-14
Post Installation Steps
RADview-HPOV/ATM User’s Manual
2.4
Chapter 2 Installation
License Installation
Working With a Remote License Server
This section is relevant only if you have installed the License Server on a different
host than the one where the Service Center is located.
Note
The license installation procedure automatically installs both the License Server and
the License Manager.
To work with a remote License Server:
Open the License Service Manager by performing the following procedure:
1.
From the Misc menu, select RADview OV.
2.
From the RADview OV sub-menu, select License Service Manager.
3.
From the Options menu, select Client Side Configuration.
4.
In the Client Side Configuration dialog box, type in the IP address of the
remote host.
Loading the License File
This section is always relevant, regardless of wherever the License Server is
installed.
To load the license file
Open the License Service Manager by performing the following procedure:
1.
From the Misc menu, select RADview OV.
2.
From the RADview OV sub-menu, select License Service Manager.
3.
From the File menu, select Add License.
A browsing dialog box will appear.
4.
Select the desired license file, and click on Save.
License Installation
2-15
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
2.5
Advanced Installation Options
Informix Home Directory
During installation, the setup script prompts you to provide the Informix home
directory path. The specified path will be the default for the location of the
Informix user's home directory and for the Informix database.
It is imperative that you create the Informix home directory before performing the
installation. Otherwise the installation procedure exits to the (#) prompt with no
explanation.
To specify a different installation directory for the Informix database:
•
Note
Set the INFORMIXDIR environment variable to the new location.
This must be done before running the Informix installation script.
For example, to set the Informix database installation directory to
/opt/informix/database, while the Informix user home directory is different, type
(for csh):
setenv INFORMIXDIR /opt/informix/database
Note
If the Informix user or Informix group exists on the UNIX machine, the home
directory will be used for Informix installation.
Database Size
By default, the installation script creates a database and allocates 500 MB in the
Informix database installation directory. In addition, Informix tools and ODBC
drivers will use approximately 100 MB.
To change the default database size:
•
Note
Run the installation script with the -r<new size> option.
A ratio of 1 MB per managed node should be used while determining the database
size.
For example, if you plan to manage 200 network elements, allocate 200 MB for
the database (additional 100 MB will be used by Informix tools and ODBC
drivers).
To run the Informix installation script with the -r option:
•
2-16
Type: ./informix.install –r300,000
Advanced Installation Options
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
RADview-HPOV Installation Directory
By default, the RADview-HPOV installation script will try to install into the /opt
partition. In case your /opt partition lacks sufficient disk space, the installation
script will stop and indicate the minimum disk space needed to install the selected
components.
In such a case, you can either free the required disk space or create a symbolic
link to another location on the disk, which has sufficient disk space.
For example, if you would like to create a symbolic link between /opt and
/export/home use the following procedure:
1.
Create a new directory named /export/home/MNG
2.
Type: ln -s /export/home/MNG /opt/MNG
Advanced Installation Options
2-17
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
2.6
Frequently Asked Questions
This section lists all RADview-HPOV for ATM FAQs relevant to installation
FAQ 1419
Question: Cannot zoom into agent, due to shared memory overflow.
Answer:
This is a shared memory problem. It can be solved by running
/opt/MNG/MNGVIEWHP/bin/mng164_clear_shm
FAQ 1391
Question: Device is connected (ping from Terminal OK), but not reachable from
HPOV map.
Answer:
While using host names as selection names, the /etc/hosts file is used
to correlate Host_name to IP, in order to enable communicating with
an SNMP agent. HPOV NNM is using a cache file, and does not
request the IP of the node from the host file on each polling, or
communication request. Thus, in case of modifications to the host file
(change of host's IP), they will not be reflected immediately in NNM.
To manually refresh HPOV's Host cashing, perform (as root)
/opt/OV/bin/xnmsnmpconf -optCache noIpAddr".
FAQ 1070
Question: Does RADview-HPOV include a built in Debug tool?
Answer:
RADview HPOV includes a built in debug tool.
By setting the MNG164_DEBUG_LEVEL environment variable before
initiating HPOV, the user will get a report on the operations
performed by RADview-HPOV during the runtime.
The environment variable should be set in the same X-terminal
window from which RADview-HPOV is launched.
Example:
While running csh:
1.
Type: setenv MNG164_DEBUG_LEVEL 5
2.
Type: script debug_data
The following message is displayed: "Script started, file is
debug_data".
3.
Type: ovw &
The debug information is stored into the debug_data file,
and can be sent to RAD technical support for investigation.
2-18
Frequently Asked Questions
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
FAQ 0837
Question: How can one modify the MTU size under Solaris?
Answer:
1.
Log in as root.
2.
Type: ifconfig <interface name> mtu <new mtu value>
3.
Type: ifconfig -a, to check that the modification took effect
To make the modification permanent, you will have to add a file into
/etc/rc3.d, which will configure the mtu size of the interface upon
startup as follows:
1.
Type: vi /etc/rc3.d/S99mtu
2.
Add the following to the file: ifconfig <Interface name> mtu
<new mtu value>.
3.
Save the file and exit.
4.
Type: chmod 755 /etc/rc3.d/S99mtu
FAQ 0988
Question: How to check the version of the RADview HPOV package?
Answer:
You must do the following:
1.
Start HP-OpenView.
2.
From the menu-bar of HPOV select Help->About OpenView
3.
In the message box select Applications.
4.
In the window that is opened scroll down and select the
RADview-HPOV package.
5.
In the upper right side you will see the version of this RADview
package.
Frequently Asked Questions
2-19
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
FAQ 0887
Question: How to connect a dial-up modem to a Solaris workstation?
Answer:
You must do the following:
1.
Log in as user root.
In order to enable remote access at root level, the
/etc/default/login file should be edited.
2.
Add a # at the beginning of the following line in the file:
CONSOLE=/dev/console.
After the modification, it should look like this:
#CONSOLE=/dev/console.
3.
Save the file and close it.
4.
Connect the modem to one of the serial ports, A or B.
5.
From a Xterm window, launch the admintool utility.
6.
From the Browse menu, select serial ports.
7.
Select the serial port to which you have connected the modem in
step 4, and from the Edit menu select Modify.
8.
In the Template field, select Modem - dial - in only.
9.
Make sure the service enable checkbox is marked.
10. Type ANSI in the terminal type field.
11. Select the baud rate to be auto.
12. Click OK.
13. Close admintool.
Your dialup modem is now configured for dial-in connections.
For dial-out or bi-directional connections, modify the Template field
(see step 8 above).
FAQ 0803
Question: How to define an additional logical network interface in Sun Solaris?
Answer:
2-20
The commands to set le0:1 are:
1.
Type: su to login as root.
2.
Type: ifconfig le0:1 up.
3.
Type: ifconfig le0:1 <IP address of the Interface> (for
example: 192.168.200.112).
4.
Using vi, create the following file: /etc/hostname.le0:1.
5.
Insert a line in the /etc/hostname.le0:1 file, with the new
hostsname, for example 2lan.
6.
Insert the following line into the /etc/hosts file: 192.168.200.112
2lan.
Frequently Asked Questions
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
FAQ 0830
Question: How to enable the on-line help system in RADview-HPOV?
Answer:
In order to use the on-line help system included in RADview-HPOV:
1.
If Netscape is installed locally, have it in the path.
2.
If Netscape is installed on a network drive, or some other browser
is used, set the MNG164_BROWSER variable to the location of
the browser.
FAQ 1302
Question: What does the "ERROR: File /etc/opt/OV/share/conf/oid_to_sym"
message mean?
Answer:
When uninstalling RADview-HPOV, using the mng164_uninstall.csh
script, the following HPOV file is not updated
/etc/opt/OV/share/conf/oid_to_sym
This file includes information about all the products previously
installed.
Upon the next start of OVW, the system will look for installed
products, according to the oid_to_sym file. The error message is a
result of the mismatch.
To solve the problem, edit the oid_to_sym file, and delete from it all
the lines for which you get error messages.
2.7
Uninstalling RADview-HPOV
If RADview does not run after the installation procedure, a possible cause is that
components of the system were not installed correctly or were installed in an
incorrect sequence. In such a case, uninstall RADview using the following
procedure:
1.
Log in as su.
2.
Type: csh.
3.
Type: source /opt/OV/bin/ov.envvars.csh
4.
Type: source /opt/MNG/MNGVIEWHP/bin/mng164_uninstall.csh
Uninstalling RADview-HPOV
2-21
RADview-HPOV/ATM User’s Manual
Chapter 2 Installation
2.8
Uninstalling Informix
1.
Log in as su.
2.
Type: csh.
3.
Type: setenv INFORMIXDIR <informix home directory>.
4.
Type: <informix home directory>/i_uninstall.
5.
Approve the 3 questions (listed in Figure 2-16).
6.
Using admintool, remove the Informix user and group.
7.
Remove Informix marked lines from the /etc/system file. These lines start
with:
* informix additions – enabling semaphores
and end with:
* end informix additions.
Figure 2-16. Uninstalling Informix
2-22
Uninstalling Informix
Chapter 3
RADview-HPOV Startup
This chapter briefly explains the HP OpenView (HPOV) features which allow the
user to create and monitor nets and agents.
3.1
Getting Started
After completing installation, the system administrator can perform initial
operations and configure agents:
•
Creating a Network Map
•
Creating Agent Nodes
•
Configuring Agents.
Detailed information about creating hierarchies/submaps and agents are found in
Creating a Net Hierarchy on page 3-9. For more information about configuring
agents, refer to the specific Agent section, further on in this manual.
To run RADview-HPOV:
•
Type ovw.
Figure 3-1. Getting Started Screen
Getting Started
3-1
Chapter 3 RADview-HPOV Startup
RADview-HPOV/ATM User’s Manual
HPOV Parameter Settings
HPOV Map Status Color Propagation
By default NNM does not propagate alarms. This means you can have a mismatch
between the hierarchy and the underling nodes.
To set HPOV Map status color propagation:
1. From Map menu, click Properties.
2. In Compound Status, check the Propagate Most Critical checkbox.
HPOV Autodiscovery
Note
RAD recommends that you disable Autodiscovery to avoid detection of irrelevant
network elements, and overloading the management station.
To disable Autodiscovery:
1.
From the Options menu, click Network Polling Configuration.
2. Make sure all of the options are unchecked.
Status Polling
Note
RAD recommends that you disable the option of automatically deleting nodes from
the HPOV map. Otherwise, there may be problems in managing the devices and
global NMS applications (i.e. TFTP File Transfer and Net Statistics).
To disable the Delete Nodes option:
1. From the Options menu, click Network Polling Configuration.
2. In the Status Polling tab, verify that the Delete Nodes if Down For... option is
not checked.
Poll Intervals, Time Outs and Poll Retries
RADview HPOV automatically polls networks nodes periodically.
To change the poll interval time:
1.
From the Misc. menu, select RADview/OV > General > Status Polling.
2.
Select 5 min, and press Set.
Each SNMP request (for example an SNMP poll) has a time-out. A retry can be
defined to compensate for the connectionless nature of the SNMP protocol.
3-2
Getting Started
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
To define SNMP Configuration:
1. From the Options menu, select SNMP configuration.
2. In the Target field, type the IP address of the node you plan to manage.
3. In the Get community field, type the get community privilege password as
defined in the device.
4. In the set community field, type the set community privilege password as
defined in the device.
5. In the timeout field, type 7.0.
6. In the Retry count field, type 2.
7. Click Add, and OK to implement the changes.
Figure 3-2. Setting Time-out
Getting Started
3-3
Chapter 3 RADview-HPOV Startup
3.2
RADview-HPOV/ATM User’s Manual
RADview-HPOV‘s WAN Maps
Hierarchical WAN maps are the basis of the RADview-HP OpenView network
management system. The user can create and modify a map using the HP
OpenView menu commands. This chapter will focus on the operations relating to
nets containing WAN agents. For complete information about HP OpenView
(HPOV) map functions, refer to HP OpenView Windows User's Guide.
Note
WAN units is a generic term for managing all RAD WAN units.
RADview-HP OpenView 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-HP OpenView the first time the system is
started up
•
Double-clicking on the WAN hierarchy will open up the next level, or WAN
submap, containing one or many nets. Each WAN submap is further broken
down at the lowest map level into a collection of IPmux units.
As nets and WAN agents are created, a single node (icon) on the lowest level map
represents each of them. An agent may be selected by clicking on it. A dark gray
box surrounds a selected agent. Once an agent is selected, all relevant HPOV
commands may 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.
3-4
RADview-HPOV‘s WAN Maps
RADview-HPOV/ATM User’s Manual
3.3
Chapter 3 RADview-HPOV Startup
HPOV Screen Display
Each HPOV map window contains the map name in the title bar and eleven
entries in its menu bar: Map, Edit, View, Performance, Fault, Tools, Options,
Window, Misc and Help.
In addition to these menus, each object on the map has an object-specific menu,
called a symbol menu, which can be accessed by clicking the right mouse button.
The button box at the bottom of the window contains command buttons for
navigating between map levels: Close, Home, Root, Parent, Quick Navigator,
Pan and Zoom, RADview Zoom, Port Labeling and About HPOV.
An alarm window is used to display traps and event messages which arrive from
active network elements. Six possible event lists are available: Error Alarms,
Threshold Alarms, Status Alarms, Configuration Alarms, Application Alert
Alarms and All Alarms.
This chapter will focus on the HPOV operations, which are necessary for the
RADview-HP OpenView system. For more detailed information about HPOV
operation, refer to the HP Open View 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 WAN 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.
•
WAN Agent Icon
Icon in the WAN submap. Double-clicking this icon displays WAN device
information.
HPOV Screen Display
3-5
Chapter 3 RADview-HPOV Startup
RADview-HPOV/ATM User’s Manual
Map Application Rules
The WAN map hierarchy includes sets of rules, which 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 may 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 may not be identical to a WAN item name within the
same hierarchy.
Root Level Rules
The following rules apply to the HPOV root map:
•
There always must be exactly one WAN Root Submap icon.
•
The user may not delete the WAN Root Submap icon.
•
Double-clicking on the WAN Root Submap icon opens the WAN Root
submap.
WAN Root Map Level Rules
The following rules apply to the WAN root map:
3-6
•
Only WAN Submap icons may appear in this map.
•
The icons in this map may not 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.
HPOV Screen Display
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
WAN Submap Level Rules
The following rules apply to the WAN submap:
•
Icons of any type may appear in this map.
•
The icons in this map may be connected.
•
After the user adds a WAN Agent icon, RADview-OV automatically polls the
agent for its status, and adds a color indication of connectivity and alarm
status for each agent, as follows:
Red
Agent is disconnected, or is connected with active Critical alarms.
Orange
Agent is connected with active Major or faulty state alarms.
Yellow
Agent is connected with active Event alarms or active Minor state
alarms.
(Event alarms are applicable only for MP2100 family.)
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.
Connection Level Rules
The following rules apply to connections within the WAN submap:
•
If the user connects a WAN agent icon to another icon, a dialog box opens.
•
In this dialog box, the user is asked to type the two endpoints of the
connection, the slot number and the port number.
•
After the user defines the connection configuration, RADview-OV polls both
endpoints' status and adds a color indication according to the following
conditions:
Red
Indicates that there is no response from the remote unit or that
there is a communication failure inside the link.
Black
Indicates that the link is functioning properly.
Moving Between Map Windows
Each map and submap is contained in a separate window. The user 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 on 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 on the desired WAN hierarchy or WAN submap icon to open
the lower level window
•
In the WAN hierarchy map, use the vertical arrow under the menu bar to
move up and down among maps.
HPOV Screen Display
3-7
Chapter 3 RADview-HPOV Startup
RADview-HPOV/ATM User’s Manual
Setting Polling Interval
RADview/HPOV automatically polls network objects periodically, relaying the
information to the user by dynamically updating the map and displaying messages.
To change the polling interval:
1.
Make sure that no map symbol is selected. From the Misc menu, select
RADview/HPOV > General > Status Polling.
The Status Polling Interval dialog box appears.
2.
Select the desired polling interval in Days, Hours and Minutes, and click Set.
The default-polling interval is five minutes.
3.4
Creating a Net
Net Functionality
A Net is a collection of IPmux units 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, the user can define nets, plan WAN agent connections, and
configure nets as desired.
At the net level, following information is displayed:
•
The net topology the communication status of each WAN agent with the
management station the status of operation of each WAN agent, as the
information is passed from the ports to the modules and to the WAN agent
the status of operation of the links connecting WAN agents.
At the WAN agent level, the following Information is displayed:
•
The operational status of the agent the operational status of each card,
including its ports the test status of each card, including its ports.
Preparing Node Names and Internet Addresses
Before you can create a new map, or add nodes to an existing map, you must
know the unique Internet address and host name for each node. The Internet
name must be a valid IP address written in dot notation, in which no single value
exceeds "255" (for example, 125.4.254.11"). Host names can be written with
normal characters (for example, "bridge1"). Refer to the TCP/IP protocol software
documentation for details of how to assign Internet addresses and to add them to
the TCP/IP protocol hosts file.
Network Topology
Before creating a map, you must know the topology of the network, e.g., which
interfaces are connected to which ports.
3-8
Creating a Net
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
Creating a Net Hierarchy
RADview-HP OpenView 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, the user can define individual WAN
agents at the lowest map level.
To create a WAN submap:
1.
In the Root map, double-click on 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-3. Network Object Palette
3.
Click on the network type to display the network objects.
Creating a Net
3-9
Chapter 3 RADview-HPOV Startup
3.5
RADview-HPOV/ATM User’s Manual
Creating an Agent for the RAD Device
To define the object for the RAD device:
1. Double-click on a WAN submap to open a WAN agent map.
2. Select <Add Object> from the Edit menu.
A dialog box opens with a selection of object classes (object palette).
Figure 3-4. Connector Palette for the Device Agent
3. Click on the Net Device icon (from the choices in Symbol Class) to display
the Class Net Device objects.
4. Press the middle mouse button while you drag the desired agent to the map.
3-10
Creating an Agent for the RAD Device
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
5. Release the mouse button.
The Add Object dialog box appears, as shown on the following page.
Figure 3-5. Add Object
6. Enter a Label for the object and select Yes to display the label on the map.
The label is the node label, a string of up to 15 alphanumeric characters with
no spaces (hyphens are permitted) that identifies the node on the map. It does
not have significance outside of the RADview-HP OpenView program.
Creating an Agent for the RAD Device
3-11
Chapter 3 RADview-HPOV Startup
RADview-HPOV/ATM User’s Manual
Selection Name
HP Open View identifies objects by their selection name. Each object must have a
selection name. The length of a selection name is limited by the maximum
number of characters allowed for file names by the operating system, or by 256
characters, whichever is lower. There are three ways to set a selection name:
•
Enter text for the selection name in the Selection Name field
•
Click <Set Selection Name> to display the Set Selection Name dialog box.
This box lists all of the names that have been set for the object. Select a
selection name from any of the names already assigned to the object, or enter
text for the selection name of the object
•
If no text is provided, HP Open View uses the name entered in the Label field
as the selection name of the object.
•
It is not recommended that you modify an icon’s selection name after it is
already created and zoomed at least once. Instead, create a new node with
new parameters.
Selection Name Format
Enter the selection name in one of the following formats:
•
For an agent node, the selection name is the Internet host name for the
object. The name must be valid and have an entry in the host's database.
Alternatively, type the IP address in dot notation (for example, 192.1.0.1)
•
For a hierarchy node, the selection name can be any string (for example,
"New York")
•
Enter the host name and IP address, by typing them in. Click <OK>.
The node appears on the map, with the information as specified. The information
is automatically updated through periodic polling.
3-12
Creating an Agent for the RAD Device
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
Setting Agent SNMP Parameters
Once the agent is added to the map, you can modify the default SNMP
configuration. The SNMP parameters for all agents are defined using the SNMP
Configuration screen.
To access the SNMP Configuration screen:
•
Select SNMP Configuration from the Options menu.
The SNMP Configuration screen appears.
Figure 3-6. SNMP Configuration
Creating an Agent for the RAD Device
3-13
Chapter 3 RADview-HPOV Startup
RADview-HPOV/ATM User’s Manual
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-HP OpenView uses for SNMP Get
operations.
Set Community
The string representing the community name in SNMP Set operations. The
default setting is "private".
Time-out
The amount of time that RADview-HP OpenView will wait for a response
before attempting to retry an SNMP request to the agent.
Retry Count
The maximum number of retries that RADview-HP OpenView will attempt
before concluding that an agent is unreachable.
Status Polling
The frequency that the application uses ping to query the agent status.
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:
3-14
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.
Creating an Agent for the RAD Device
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
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. The following warning message appears.
Figure 3-7. Confirm Delete
3.
Confirm the deletion.
Changing Agent Attributes
Map objects may be modified using the object's Symbol menu.
To modify a map object:
1.
Right-click the node to open the Symbol menu.
2.
Select Object Properties > General Attributes.
The Symbol Description dialog box appears.
3.
Modify the Label as desired. 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.
Creating an Agent for the RAD Device
3-15
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
3.6
Creating a Connection
You can add, remove or reassign connections between two WAN agents. Each
agent can connect to one or more units, but each port can only contain one
connection. Assign logical channel names for interagent connections so that the
appropriate network map appears with the appropriate network segments and
channel attachments. Assign link names so that each channel is easily identified in
the map window.
To add a connection:
1.
From the Edit menu, select Add Connection.
A palette of connection type samples appears in the Add Connection
dialog box (see Figure 3-8).
2. Select <Yes> in the Display Label field.
3. Enter the label that should appear on the map and click <OK>.
The Add Connection dialog box appears (see Figure 3-9).
4. Define the slots and ports that connect the two WAN agents and click <Set>.
The connection now appears on the map.
Note
To prevent the label from displaying on the map, select No in the Display Label field.
Figure 3-8. Add Object
3-16
Creating a Connection
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
Figure 3-9. Define Connection
Changing Connection Attributes
To view or modify the connection information:
1.
Select the connection.
2.
Select Describe/Modify Connection from the Misc/RADview/OV/General
menu.
The Describe/Modify Connection dialog box appears (see Figure 3-10).
3.
Modify the information as desired and click <Set>, or click <Cancel> to
close the dialog box without making any changes.
Figure 3-10. Connection Information
Creating a Connection
3-17
RADview-HPOV/ATM User’s Manual
Chapter 3 RADview-HPOV Startup
Viewing Multiple Connections
When two TDM units contain more than one connection between them, the
connections appear as a single line on the map.
To view multiple connections:
•
Double-click on the line between WAN agents (see Figure 3-11).
Figure 3-11. Multiple Connections
3-18
Creating a Connection
RADview-HPOV/ATM User’s Manual
3.7
Chapter 3 RADview-HPOV Startup
Agent Monitoring
HPOV automatically polls each node in the network for connectivity status at
specified intervals, and changes the color of the agent's background based on the
results of the poll. The minimum default time between two successive polls is four
seconds, and can be modified using the Status Polling command.
In addition, RADview-HPOV polls the agents itself, maintaining its own database
for RAD agents in the system. Newly created agents are automatically added to the
RAD database. The agents are monitored for the presence of active alarms and
tests.
Displaying Alarms Categories
In the RADview-HPOV screen, you can open the Alarm Categories window in
order to select the type of traps and event messages for display. This window
contains a choice of six types of alarm lists (see Figure 3-12).
Figure 3-12. Alarm Categories Window
To display an 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.
Figure 3-13. All Alarms Browser
Agent Monitoring
3-19
Chapter 3 RADview-HPOV Startup
RADview-HPOV/ATM User’s Manual
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 a object and its attributes from the map file:
Note
3-20
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. A message
informs you of the number of children in its hierarchy.
Agent Monitoring
Chapter 4
RADview-HPOV System
Functions
This chapter discusses:
•
Backup, Restore and Undo Last Restore utilities
•
Security
•
Alarm List
•
Setting Net Date and Time
•
TFTP File Transfer
•
Net Inventory
•
Automatic Configuration Upload
•
Net Statistics
•
Date and Time Auto Mode
•
RADview Licensing Function.
4.1
Backup, Restore and Undo Last Restore Utilities
RADview-OV provides utilities for backing up and restoring configurations and for
canceling a restore operation.
•
Backup – Backup is used to backup any level of the WAN hierarchy.
•
Restore – Restore is used to restore a structure stored in Backup.
•
Undo Last Restore – Cancels the last restore operation.
Backup
The Backup utility stores information needed to restore the following items:
•
WAN Root
•
WAN Submap
•
WAN Agent
A backup performed in the Root hierarchy level stores information about icons in
the Root level and all levels below the Root level. A backup performed in any
other level stores information from its level and all levels below.
Backup, Restore and Undo Last Restore Utilities
4-1
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
To backup a WAN item:
1.
Make sure that all the applications running on the source station are installed
on the target restoration station. If not, when performing a restore on the
target station, an error message will appear ONLY when restoring a submap,
and not when restoring a complete hierarchy.
2.
Click one of the following icons: WAN Root Submap, WAN Submap or WAN
Agent.
3.
From the Misc menu, select RADview/OV > General > Backup.
The Backup File Name dialog box appears.
Figure 4-1. Backup File
4.
Enter a filename for the backup file in the dialog box and click <Apply>.
If the filename already exists, select <OK> if you want to overwrite the
old file. If the file does not have write permission, RADview-HP OpenView
aborts the request.
Restore
The Restore utility restores the full configuration of a previously backed up WAN
item. Any one of the following items may be restored:
•
WAN Root Map
•
WAN Submap
•
WAN Agent
•
Connection Names.
The Restore utility has several purposes:
4-2
•
Restoring a deleted WAN item.
•
Creating a new WAN item based on the configuration and information of
another WAN item.
•
Creating a new WAN item based on the configuration and information of
another WAN item with variations.
Backup, Restore and Undo Last Restore Utilities
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
The user should adhere to the following rules to ensure error-free restoration of
backed up items:
•
Hierarchy Level: A WAN item may only be restored to the same hierarchy
level from which it was originally backed up. For example, if a WAN agent
was originally backed up from a WAN Submap, the user can only restore that
WAN agent to a WAN Submap level
•
Changing WAN Item Names: Before restoring a WAN item, the user may
change its name. However, an identical name for more than one item within
the same map hierarchy is not allowed (even over different item types or
hierarchy levels). If the restoration is stopped because of a selection name
(WAN item name) error, check to see if the desired name already exists on
the WAN item selection name list.
To restore a map to its backed up filename:
1.
From the Misc menu, select RADview/OV > General > Restore.
The Restore File Name dialog box appears.
Figure 4-2. Restore File
Backup, Restore and Undo Last Restore Utilities
4-3
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
2.
Enter the name of the backup file to be restored and click <Apply>.
If the filename does not exist or if RADview/OV cannot find the file, an
error message appears.
If the file stores data of the map, the Restore dialog box appears.
Figure 4-3. Restore Dialog Box
The hierarchical tree presents all submaps (orange), objects (red) and connections
(blue) in the root map.
To view all the elements in a submap, click on the icon next to the submap. To
hide the elements, click the icon again (or double click on the label).
3.
4-4
Click <Restore> to execute the restoration.
Backup, Restore and Undo Last Restore Utilities
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
To modify a backed-up file:
1.
From the Misc. menu, select RADview/OV > General > Restore.
The Restore dialog box appears.
Figure 4-4. Modifying in the Restore Dialog Box
2.
Click on the label of one backup file to be modified.
3.
Fill in the new Selection Name and Label in the fields at the bottom of the
dialog box. (It is advisable to have the same name for both Selection Name
and Label.)
If you click on a connection, the WanAgent 1 (source side of the link) and
WanAgent2 (destination) fields appear and are read-only. Any changes made
on the objects of this connection will register in these fields.
4.
Click <Modify>.
5.
To end the process at any time, without processing the restore or saving
changes, click Close.
6.
Click <Restore> to execute the restoration.
Backup, Restore and Undo Last Restore Utilities
4-5
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Undo Last Restore
The Undo Last Restore command cancels the last restore operation. This operation
may be invoked in the following ways:
•
Upon specific user request from any map hierarchy level
•
Upon confirmation of a program message that a problem was detected during
the restore operation. In such a case, it is recommended to abort the partial
restoration.
To undo the last restore operation:
1.
From the Misc. menu, select RADview/OV > General > Undo Last Restore.
2.
Click <OK> to confirm.
When the last restoration is successfully undone, RADview-HP OpenView
displays a message.
3.
Click <OK> to confirm and complete the Undo Last Restore operation.
4.2
Security
RADview-HPOV's advanced security feature allows operation restrictions to be
predefined for users. Users and their privileges can be set to define access to
various network elements and functions. The following instructions describe how
to set security features.
Starting an HP OpenView Session
In order to begin a session of HP OpenView the user must Login to the system.
To Login to RADview:
1.
From the submap screen, select Misc > RADview/OV > Login.
The Login dialog box appears.
Figure 4-5. Login Dialog Box
4-6
Security
RADview-HPOV/ATM User’s Manual
2.
Chapter 4 RADview-HPOV System Functions
Type in your user name and password.
If this is the first time the system is being used or users have not yet been
programmed into the system, enter the system under the User Name "root"
with the User Password "root".
Note
Once user names and passwords have been entered it is advisable to change the
"root" password.
3.
Click <OK>.
If you enter an incorrect password the Access Denied dialog box appears;
click <OK>.
Figure 4-6. Access Denied Dialog Box
To change a user password:
1.
From the submap screen select, Misc > RADview/OV > Login.
The Login dialog box appears.
2.
Click <Change Password>.
The Change Password screen appears.
Figure 4-7. 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>.
Security
4-7
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Viewing User Security Access Privileges
Users can view their own access levels for each network element from the View dialog
box. Administrators can view a list of all users and their access levels from this window.
To view user access level privileges:
1.
From the submap screen, select Misc, > RADview/OV > General > Security
> Capabilities.
The Security Capabilities dialog box appears.
2.
From the Security Capabilities dialog box Administrators can change, add or
remove users.
Figure 4-8. Security Capabilities Dialog Box
4-8
Security
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Adding Users
Administrators can add users by following this procedure:
To add a new user:
1.
From the submap screen, select Misc > RADview/OV > General > Security
> Capabilities.
2.
Click <Add>.
The Add User dialog box appears.
Figure 4-9. Add User Dialog Box
3.
Fill in the User Name, Password and Verify Password fields for the intended new user.
4.
For each Network Element from the list, define the access level of the new user.
Security
4-9
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Defining User Security Access Privileges
A single user can have different access levels for each network element. For
example, a user can be a monitor for certain elements and a technician for other
elements. A user defined as an administrator will have administrator privileges for
all network elements and cannot be defined as an operator, a technician or a
monitor for individual elements. For each user, define an access level for each
network element to be handled by the user. The following access level definitions
apply:
Administrator: An Administrator can configure path management. This includes,
adding and removing elements from the map hierarchy. An administrator can view
and configure all aspects of RADview including all the map levels, agent and edit
configuration. The administrator can add, change and remove users to the system
and define their access privileges. An administrator can view the security log to see
all Login and Logout attempts.
Operator: The operator can use the zoom application to view and configure
designated agents.
Technician: A technician can run loopback tests, clear the alarms list and view the
statistics.
Monitor: A monitor can zoom statistics in read-only mode.
Note
If a user attempts to carry out a restricted action, an "ACCESS DENIED" dialog box
will appear.
Table 4-1. Access Level Definitions
Access Level
Defining
Users
Path
Management
Map Level
Applications
Agent
Configuration
Zoom
Testing &
Alarms
Clear
Administrator
3
3
3
3
3
3
Operator
−
−
−
3
3
3
Technician
−
−
−
−
3
3
Monitor
−
−
−
−
−
3
4-10
Security
Statistics
Zoom
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
To define a user as an Administrator:
A user defined as an administrator will have administrator privileges for all network
elements and cannot be defined as an operator, a technician or a monitor for
individual elements, see Table 1.
1.
Click <Administrator> in the Access field so that the field is filled in.
2.
Click <OK>.
To define the access level of a user for each network element:
The left side of the Add User or Change User dialog box contains a list called ALL.
For your convenience, the ALL list contains all network elements (by selection
name) currently on the map. To define access to a network element not currently
on the map, see below, To Add a Network Element.
3.
In the Add User or Change User dialog box, highlight a network element in
the All list by clicking on it.
4.
Use the arrow buttons in the middle of the screen to direct the selected
network element to a User Access level (Operator, Technician, Monitor). The
network element will appear under the appropriate User Access Level category.
5.
Repeat this process for each network element to be assigned.
6.
Click <OK>.
To add a Network Element:
1.
Enter the Network Element in the empty field below the ALL list.
2.
Continue with step number two above, "To define the access level of a user
for each network element."
Security
4-11
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Changing Users
To Change User Security Capabilities:
1.
From the Security Capabilities dialog box highlight the name of the user to
be changed and click Change.
The Change User dialog box appears.
Figure 4-10. Change User Dialog Box
4-12
Security
2.
Highlight a network element by clicking on it. Add it to a user level or remove
it from a user level by directing it with the appropriate arrow in the center
column. To add a network element not currently on the map (not listed under
ALL) see above, To add a network element.
3.
Click <OK>.
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Removing Users
To remove a user:
1.
In the Security Capabilities dialog box highlight the name of the user to be removed.
2.
Click <Remove>.
The Remove User dialog box appears.
Figure 4-11. Remove User Dialog Box
3.
Click <OK>.
Security Log
An administrator can view a log of all RADview Login and Logout attempts,
including failed attempts.
To view Security Log:
1.
From the submap screen, select Misc > RADview/OV > General > Security
> View Security Log.
The Security Log appears.
Figure 4-12. Security Log Dialog Box
Security Log Status can be OK, Fail or By System.
OK: Login / Logout successful.
Fail: Unspecified user or unspecified password.
By System: If a user neglects to Logout and closes HP Open View, the
system will register this as a Logout "By System" upon subsequent Login.
Security
4-13
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
2.
To save the Security Log to a file, click <Save to File> and then enter the
designated file name and location.
3.
To print the Security Log to a file, click <Print>.
4.
To clear the Security Log, click <Clear>.
5.
Click <Close> to exit the Security Log.
Logging Out of RADview
To end your RADview-HP OpenView session you must perform Logout.
To Logout of RADview:
1.
From the submap screen, select Misc > RADview/OV > Logout.
The Logout dialog box appears.
Figure 4-13. Logout Dialog Box
2.
4-14
Security
Click <OK>.
RADview-HPOV/ATM User’s Manual
4.3
Chapter 4 RADview-HPOV System Functions
Alarm List
RADview shows you alarms, in all levels (system, card, and port) for each
ATM Network Element in the map.
To view the ATM Active Alarm List:
1.
From the HPOV Misc. menu, select RADview/OV ATM > Alarm List...
The ATM Active Alarm List dialog box appears.
Figure 4-14. ATM Active Alarm List Dialog Box
2.
Click the check box of the desired product and press the <Apply and Refresh> button.
A list of alarms for all ATM agents, in all levels is displayed. To choose a different
product, click its check box and press the <Apply and Refresh> button.
Each alarm is displayed in a separate line. The alarms are sorted according to
agent IP Address. They can also be sorted by double clicking on columns that
have an * sign (Selection Name and IP Address in ascending order). The ATM
Active Alarm List parameters are listed in Table 4-2.
Table 4-2. ATM Active Alarm List Parameters
Parameter
Function
No
Sequential numbering of alarms
Selection Name
The name of the product to which the alarm is relevant
IP Address
The IP address of the product to which the alarm is relevant
Interface
The interface type and location to which the alarm is relevant
VPI
The VPC to which the alarm is relevant
VCI
The VCC to which the alarm is relevant
Description
Text descritpion of alarm
Alarm List
4-15
Chapter 4 RADview-HPOV System Functions
4.4
RADview-HPOV/ATM User’s Manual
Setting Net Date and Time
RADview enables you to set the date and time for all managed units via a single
screen.
To set Date and Time:
1.
From the Misc. menu choose RADview-OV > Net Date & Time.
2.
Check the boxes next to all the devices in the network.
Date
Format is Day/Month/Year (according to the computer clock)
Time Format is Hour/Minute/Second (according to the computer clock)
3.
Check the User Time/NMS Time box as follows:
To User Time, which enables the user to configure, the Date & Time as
they wish.
To NMS Time, which disables all fields, and the Date & Time are taken
from the workstation.
4.
Enter the required date and time parameters.
5.
Click <Set> to implement the changes.
Figure 4-15. Network Time & Date Configuration
4-16
Setting Net Date and Time
RADview-HPOV/ATM User’s Manual
4.5
Chapter 4 RADview-HPOV System Functions
TFTP File Transfer
Introduction
TFTP File Transfer is a RADview HPOV/PC SNMPc system application. The TFTP
File Transfer application provides the user 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 RADview system, or any other host,
acts as a TFTP server
•
The application can manage multiple downloads to several agents at the same
time
•
During the TFTP process, the agent sends traps to the NMS to indicate the
download status.
The opening window is shown in Figure 4-16.
Figure 4-16. TFTP File Transfer – Opening Window
Perform the TFTP File Transfer procedure in the following order:
1.
TFTP server setup.
2.
Create profiles – TFTP File Transfer application definitions, and associate them
to network elements.
3.
Execute TFTP File Transfer functions (i.e. SW Download, Configuration Upload, etc.).
TFTP File Transfer
4-17
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
TFTP Server Setup
Before you can use the TFTP File Transfer application, you must setup the TFTP
server.
To setup the TFTP server:
1.
Ping the connected agent from the TFTP server, to make sure that the agent is
connected to the station running the TFTP server.
2.
Log in as root.
3.
Create the directory in which the SWDL file will be saved.
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 <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 TFTP File Transfer files. Follow the next steps to edit the
/etc/inetd.conf file using the Text Editor.
Right click on the desktop and select Text Editor from the Application
menu.
From the File menu select Open.
The Text Editor is displayed.
Type: /etc in the Enter Path or File Name field.
Click <Update>.
Type: inetd.conf in the Enter a File Name field.
Click <OK>.
Note
7.
Search for the line starting with #tftp (e.g. # tftp dgram udp). Remove the #
sign.
8.
At the end of that line you will see –S <TFTP_boot>. Change the
<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.
9.
Save the inetd.conf file with the current changes. From the File menu, select
<Save> and then <Close> the Text Editor.
10. Reboot the Unix workstation:
Type: sync
Type: init 6
4-18
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Creating Profiles
Before starting the TFTP File Transfer application, ensure that RADview HPOV and
a TFTP server are running.
To login:
1.
Login to Solaris as a RADview HPOV user.
2.
Enter ovw & from an X-terminal window.
3.
Login to RADview:
1. From the Misc menu select RADview/OV>>Login…
2. Use the Default Administrator Account to log into the system:
User: root/password:root
3. Click <OK>.
4.
From the Misc menu, select RADview/OV > General > Software
Download.
Figure 4-17. Opening TFTP File Transfer Application – HPOV
Note
Only RADview HPOV administrators are allowed to use the TFTP File Transfer
application.
Starting TFTP File Transfer
Once launched, the TFTP File Transfer window appears (Figure 4-16). The
window has two tabs, Operation and Report Database; these are described on
the following pages.
When first using the TFTP File Transfer application, perform these steps in the
following order:
1.
From the Configuration menu, edit the Database.
2.
Select the Operation.
3.
Check the Report.
TFTP File Transfer
4-19
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Configuration
Figure 4-18. Configuration Menu
Default Settings
You can define the RADview-HPOV System Functions Default Settings.
To configure the Default Settings:
1.
From Configuration menu, select Default Settings.
The Default Settings dialog box appears (see Figure 4-19).
2.
Configure the Default Settings parameters listed in Table 4-3.
3.
Press <Set>.
Figure 4-19. Default Settings Dialog Box
Table 4-3. Configuring Default Parameters
Parameters
Description / Remarks
TFTP Server IP
The IP address of the TFTP server for the selected object.
Exclude TFTP Directory
Path
Checked, Unchecked
Default Value: Checked (Unix)
Note: This is disabled for PC (default).
Reboot Timeout (sec)
The reboot timeout setting for the selected object.
The Software Download application waits for this period for
the Cold Start trap after performing a reboot.
4-20
Timeout (sec)
Default: 60 seconds
Retry Timeout (sec)
Default: 15 seconds
Ping Timeout (msec)
Default: 100 seconds
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Edit Database
Edit Database (see Figure 4-20) enables you to create or modify existing profiles.
This function displays the OIDs product types stored in the TFTP File Transfer
database. You can Add, Edit, or Remove a profile.
Adding a New Profile
To add a New Profile:
1.
From Configuration menu, select Edit Database.
The Edit Database dialog box appears (see Figure 4-20).
2.
Click <Add>.
The Add Product dialog box appears (see Figure 4-21).
3.
Complete fields from Table 4-4.
4.
Define the S/W Download File. There are two methods:
In the S/W Download File field, type the name of the S/W Download File.
There is no need to specify the full path, just the file name.
OR
Follow the procedure in Selecting the File to Download on page 4-25.
5.
Press <Set>.
A message appears at the bottom of the screen Database saved.
Figure 4-20. Edit Database Dialog Box
TFTP File Transfer
4-21
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Figure 4-21. Add Product Dialog Box
Table 4-4. Add/Edit Product Parameters
Parameter
Possible Values / Remarks
Select Product
The object ID (product type) of the selected profile.
SubSystem Download
Indicates whether this feature is needed or not for the
selected profile, and which are the subsystems that need it.
TFTP Server IP
The IP address of the TFTP server for the selected profile.
Reboot Timeout (sec)
The reboot timeout setting for the selected profile.
The Software Download application waits for this period for
the Cold Start trap after performing a reboot.
All the following fields except the last 2 fields, are enabled
only if the product(s) selected via the Selected (All) Nodes
field supports this field.
S/W Download File
4-22
TFTP File Transfer
The software download file path and name on the TFTP
server for the selected profile. The S/W Download
<Browse> button (see) opens a standard Open File dialog
box (see Figure 4-22) for locating the software download file.
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-4. Add/Edit Product Parameters (Cont.)
Parameter
Possible Values / Remarks
Config Download File
The configuration download file path and name on the TFTP
server for the selected profile. The <Browse> button opens
a standard Open File dialog box for locating the software
download file.
Config Upload File
The configuration upload file path and name on the TFTP
server for the selected profile. The <Browse> button opens
a standard Open File dialog box for locating the software
download file.
Note: In Config. Upload there is no need to choose Reset
Only.
Additional S/W file
The product’s card software download file path and name on
the TFTP server for the selected profile. The ... button opens
a standard Open File dialog box for locating the software
download file. (This parameter is not relevant for all
applications.)
Note: If the device includes a LAN ETH card you may need to
download the Co-processor Download File. The file name has
a *.cmp extension.
Statistics Upload File
The product’s statistics upload file path and name on the
TFTP server for the selected profile. The <Browse> button
opens the Select File to Download dialog box for locating the
software download file. (This parameter is not relevant for all
applications.)
User Download File
The product’s user download file path and name on the
TFTP server for the selected profile. The <Browse> button
opens the Select File to Download dialog box for locating the
software download file. (This parameter is not relevant for all
applications.)
User Upload File
The product’s user upload file path and name on the TFTP
server for the selected profile. The <Browse> button opens
the Select File to Download dialog box for locating the
software download file. (This parameter is not relevant for all
applications.)
File Name Within
Product
The product file name uses any file name from the file system
list (depending on the user). This field is applicable mainly for
the User Download File, User Upload File, and Statistics
Upload File, options.
Note: User must enter file name.
Timeout (sec)
Default: 60 seconds
Retry Timeout (sec)
Default: 15 seconds
The TFTP File Transfer application provides a number of functions; they are listed
in Table 4-4.
TFTP File Transfer
4-23
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
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 their application. Consult Table 4-5
for the TFTP File Transfer options and recommended TFTP values that are relevant
for your application.
Table 4-5. TFTP File Transfer Options – by Device
Product
Name
Reboot
Timeout
S/W
Dwnld
S/W
Upld
Config
Dwnld
Config
Upld
Add’l
SW
Dwnld
Statistics
Upld
User
Dwnld
User
Upld
File Name
Within
Product
Timeout
(sec)
ACE-101
300
+
–
+
+
+
–
–
–
–
300
ACE-2002
300
+
–
+
+
+
+
+
+
+
300
ACE-2002/E
300
+
–
+
+
+
+
+
+
+
300
ACE-202
300
+
–
+
+
+
+
+
+
+
300
ACE-50
300
+
–
+
+
–
–
–
–
–
300
APD-2
60
–
–
+
–
–
–
–
–
–
60
APD-8
60
–
–
+
–
–
–
–
–
–
60
APS-16
60
–
–
+
–
–
–
–
–
–
60
APS-24
60
–
–
+
–
–
–
–
–
–
60
APS-8
60
–
–
+
–
–
–
–
–
–
60
eFCD-IP
60
+
–
+
+
–
–
–
–
–
60
FCD-IP
60
+
–
+
+
–
–
–
–
–
60
FCD-IPD
60
+
–
+
+
–
–
–
–
–
60
FCD-IPM
60
+
–
+
+
–
–
–
–
–
60
FCD-155
300
+
–
+
+
–
–
–
–
–
300
FPS-12
60
+
–
+
–
–
–
–
–
–
60
FPS-4
60
+
–
+
–
–
–
–
–
–
60
FPS-8
60
+
–
+
–
–
–
–
–
–
60
IMXi-4
300
+
–
+
+
–
–
–
–
–
300
IPmux-1
60
+
–
+
+
–
–
–
–
–
60
IPmux-16
300
+
–
+
+
+
–
+
+
+
300
IPmux-1E
60
+
–
+
+
–
–
–
–
–
60
IPmux-4
300
+
–
+
+
+
–
–
–
–
300
LA-110
60
+
–
+
+
–
–
–
–
–
60
LA-140
60
+
–
+
+
–
–
–
–
–
60
LRS-12/B
60
+
–
–
–
–
–
–
–
–
60
LRS-12/F
60
+
–
–
–
–
–
–
–
–
60
LRS-52
60
+
–
–
–
–
–
–
–
–
60
4-24
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-5. TFTP File Transfer Options – by Device (Cont.)
Product
Name
Reboot
Timeout
S/W
Dwnld
S/W
Upld
Config
Dwnld
Config
Upld
Add’l
SW
Dwnld
Statistics
Upld
User
Dwnld
User
Upld
File Name
Within
Product
Timeout
(sec)
Optimux-155
300
+
+
–
–
–
–
–
–
–
300
SPS-12
60
–
–
+
–
–
–
–
–
–
60
SPS-2
60
–
–
+
–
–
–
–
–
–
60
SPS-3
60
–
–
+
–
–
–
–
–
–
60
SPS-3S
60
–
–
+
–
–
–
–
–
–
60
SPS-6
60
–
–
+
–
–
–
–
–
–
60
SPS-9
60
–
–
+
–
–
–
–
–
–
60
SuperLan
60
+
–
+
+
–
–
–
–
–
60
Vmux-2100
60
+
–
+
+
–
–
–
–
–
60
WEB RANger
60
+
–
+
+
–
–
–
–
–
60
Notes
• (+) means supported and (–) means unsupported
• The Reboot Timeout (sec) and Timeout (sec) values are the default values for
these products, and should to be used in Add Product dialog box.
• The Boot versions in ACE and IPmux products can be downloaded only via
Terminal (not via NMS).
Selecting the File to Download
To select file to download:
1.
In the Enter Path Or Folder Name field, type the name of the directory on
the TFTP file (e.g. /export/home/tftp boot)
2.
Select the folder name and file name.
TFTP File Transfer
4-25
Chapter 4 RADview-HPOV System Functions
3.
Note
RADview-HPOV/ATM User’s Manual
Press <Select File to Download>.
Press <Update> if the directory and file were changed from another compute. This
updates the directory and file names.
Figure 4-22. Select File to Download Dialog Box – Unix
Figure 4-23. Select File to Download Dialog Box – PC
4-26
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Edit Product
To edit the database:
1.
From Configuration menu, select Edit Database.
The Edit Database dialog box appears (see Figure 4-20).
2.
Highlight the product that you want to edit.
3.
Click <Edit>.
The Edit Product dialog box appears (see Figure 4-24).
4.
In the Edit Product dialog box, complete the fields (explained in Table 4-4).
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
Press <Browse> and follow the procedure in Selecting the File to
Download.
6.
Press <Set>.
7.
On the Edit Database dialog box, press <Close>.
Figure 4-24. Edit Product Dialog Box
TFTP File Transfer
4-27
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
To remove an entry of the list:
1.
Highlight a line that contains the entry you want to delete.
2.
Press <Remove>.
A confirmation message is displayed: Removing <Product Name>.
3.
Note
Press <OK>.
When entering a file name for the first time, enter any name that you want. During
the Configuration Upload process, a file with the same name that contains the
device configuration will replace the selected file.
Operation
Associating the Device Profile to Network Elements
The Operation tab (see Figure 4-25) enables you to select all agents or specific
agents for TFTP File Transfer operations (see Table 4-6).
You can perform TFTP File Transfer operations on All Nodes, or Selected Nodes.
You can add nodes individually or from the map to link profiles to specific IP
addresses.
Figure 4-25. Operation Tab
Note
4-28
When the Operation tab first appears, it is empty. Open the Edit Database tab first
to define the initial parameters.
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-6. TFTP File Transfer Operation Parameters
Parameter
Possible Values / Remarks
Node 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's IP Address
The IP address of the server, as assigned for this mode in the SWDL database.
File's Location
The location of the file. By default, the UNIXPC Windows user home location is
displayed, according the type of station running the present application
Last Operation
Last selected operation for each node:
S/W Download Only, S/W Download &Reboot, Config. Download Only,
Config. Download & Reboot, Config. Upload, Additional SW Download Only,
Additional SW Download & Reboot, Statistics Upload, User Download Only,
User Upload, Reset Only
Last Status
Last TFTP status of each Node. The default is blank.
[All Nodes Operation...]
Performs operation for all nodes in list
[Selected Nodes]
Opens a selection list box to choose operation for selected nodes
[Add from Map]
Opens a selection list box, containing all SNMP nodes on map
[Add…]
Opens a dialog box for Adding a new agent (node)
[Remove]
Removes an agent
Note
In order to upgrade SW, you should reboot the agent after you have downloaded
SW to the agent. In some cases, you may want the to reboot (reset) the device only
at a specific time. Therefore, when required, you can select an operation that
includes Download Only for file download only, an operation that includes
Download & Reboot for complete software upgrade or an operation of Reset Only
for rebooting at a specific time after having successfully downloaded the software.
TFTP File Transfer
4-29
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Associating Profiles to Nodes
You can add an agent to the agent list in the Operation tab by the one of the
following methods:
Note
•
Add Agent directly from the HPOV/PC SNMPc Map
•
Add Agent dialog box.
The Add from Map method is preferred because the Community, Timeout, and
Retries of the SNMP node are obtained automatically from the map. This is faster
and more accurate since there is no need for you to define them.
To add an agent from the map to the list in the Operation tab:
1.
Click <Add from Map>.
The Add Agent from Map dialog box appears (see Figure 4-26). As
RADview polls all the agents, it lists it on the dialog box. When it finished,
the status bar at the bottom of the screen says Ready.
2.
Highlight the Name–IP Address–Product of the SNMP node to be added.
3.
Press <Apply>.
The SNMP node is added to the list in the Operation tab.
Note
The Node Name column in Operation tab displays the Node Name as it was, when
Add from Map was performed (for HPOV, Selection Name). If afterwards user
changes the Selection Name/Node Name of this node in the map, the Node name
in SWDL application will NOT be updated (implementation problems).
Figure 4-26. Add Agents from Map Dialog Box
4-30
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Add Agent
To manually add an agent to the list in the Operation tab:
1.
Click <Add>.
The Add Agent dialog box appears (see Figure 4-27).
2.
Enter the IP address of the SNMP node to be added.
3.
Enter the parameters from Table 4-7.
4.
Click <Apply>.
The SNMP node is added to the list in the Operation tab.
Figure 4-27. Add Agent Dialog Box
TFTP File Transfer
4-31
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-7. Add Agent Parameters
Parameter
Possible Values / Remarks
Node Name
Edit field
IP Address
IP Address format field
Default: 0.0.0.0
Community
Get
Default: public
Set
Default: private
Trap
Default: private
Timeout (msec):
Edit field
Default: 4000
Retries
Edit field
Default: 0
Note
This added node may exist in the SNMPc/HPOV map with a different
name. In this case, the Node Name entered by user via this dialog box will be
the one that appears in the Operation tab list as Node Name.
To set Default Values on Add Agent Dialog Box
•
Press <Default>.
The dialog box reverts to the Default Values listed in Table 4-7.
To remove an agent from the Operation tab:
1.
Select a node from the list displayed.
2.
Click <Remove>.
The SNMP node is removed from the list in the Operation tab.
4-32
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Performing TFTP File Transfer Operations
This section explains how to perform TFTP File Transfer via the Operation tab.
Figure 4-28. TFTP File Transfer – Operation
TFTP File Transfer
4-33
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
To perform TFTP File Transfer Operations:
1.
Perform one of the following:
Highlight the specific nodes from the list on which you want to perform
TFTP File Transfer (press Shift for several nodes).
Press <All Nodes Operation>
Press <Selected Nodes Operation>. This can be used in case of TFTP
failure. Select only those nodes where the transfer of new software was not
successful, according to "Last Status" column, and reinitialize TFTP session.
2.
If using Selected Nodes (see Figure 4-29), select any TFTP File Transfer
Operation. Only options that are supported by all Nodes of the list are
selectable (see Figure 4-30).
3.
Press <Set>.
A confirmation message appears (see Figure 4-31).
Note
4.
Press <OK>.
5.
Look at the status reported on the Last Status column (see Figure 4-25) to
check whether the download was successful. Additional information is
available via the Report Tab.
In order to upgrade SW, agent should perform Reboot after the SW was
downloaded to Agent. In some cases, user may want the device to Reboot (Reset)
only on a specific time. Therefore, as relevant, user can select an Operation that
includes Download Only for file download only, an Operation that includes
"Download & Reboot" for complete software upgrade or an Operation of Reset
Only for rebooting at a specific time after having successfully downloaded the
software.
When Operation selected in Operation TAB, [All Nodes Operation...] or [Selected
Nodes Operation...] includes Download & Reboot, NMS will perform the
operations mentioned in Table 4-8.
4-34
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-8. Download & Reboot NMS Operations
Product Name
Operation
ACE-101
A
ACE-2002
A
ACE-2002/E
A
ACE-202
A
ACE-50
A – when the Operation is “Config. Download & Reboot” or
“Additional SW Download & Reboot“
C – when the Operation is “SW Download & Reboot”
IPMUX-1
A
IPMUX-1E
A
IPMUX-4
A
IPMUX-16
A
LA-110
B
LA-140
B
LRS-12/F
A
LRS-12/B
A
LRS-52
A
Legend:
A
Same as Download Only + Reset.
Same as Download Only (above) + upon successful completion, activate
the Reset process of para.2.8.
B
Same as Download Only.
For these products, no additional operation is needed, because these
products automatically perform a Reboot after downloading TFTP.
C
Same as Download Only (above), except that for fileTransCmd, NMS
will Set the value of swDwnLoadAndReset(8) (instead of swDwnLoad(1)).
If this Set fails, it means that the SW Version of this Agent doesn't support
this value (we know that there are higher versions that support it for this
device).
In this case, NMS will do 'A' operation, above.
Note: This case takes care of products that part of their versions support
the new swDwnLoadAndReset(8) value, while their older versions
do not support it.
Storing SW Version of each device is too complicated. Therefore this
implementation is selected.
TFTP File Transfer
4-35
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Figure 4-29. Selected Nodes Operation Dialog Box
Figure 4-30. Selected Nodes Operation Dialog Box – Selection
Figure 4-31. Selected Nodes Operation Dialog Box – Confirmation
Warning
If you choose TFTP and Reboot, the software version of the nodes is replaced
and the system resets. Depending on the reboot time of the specific device,
traffic downtime is experienced.
Reset
After you successfully download the new software, reboot the agent in order to
load it.
4-36
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
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-9. Messages are
listed in Table 4-10.
Only Nodes for which Download/Upload is currently processed will be displayed in
this tab. A new row will be added each time the tftpStatusChangeTrap is received.
Note
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 each
particular agent.
Figure 4-32. Report Tab
Table 4-9. TFTP File Transfer - Report Tab Parameters
Parameter
Remarks
Date
Local date at the NMS when the message was registered
Time
Local time at the NMS when the message was registered
Node Name
Name of the relevant agent
IP Address
IP address of the relevant agent
Product Name
Name of product whose file transfer process is reported
Message
Status of the download process.
Possible messages are listed in Table 4-10.
TFTP File Transfer
4-37
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-10. Status Messages
Message (Standard TFTP messages)
Color
Connectin
Yellow
Connected. Transferring Data.
Yellow
Giving up. Server does not respond.
Red
File transferred.
Green
File not found.
Red
Illegal TFTP operation.
Red
Unknown transfer ID.
Red
Server overflow.
Red
No available UDP port.
Red
No available resources.
Red
Illegal file mode.
Red
Illegal pdu size.
Red
Rebooting...
Yellow
Device successfully upgraded.
Green
No SNMP connectivity.
Red
Bad file. Use alternative file to reboot.
Red
IP Address format of the node is not valid.
Red
IP Address format of the node is not valid.
Red
Unknown sysObjectID.
Red
Connecting…
Yellow
To remove messages from the Report tab:
•
In the Reports tab, select a row and click <Remove>, or click
<Remove All> to clear all messages from the list.
Save the Database
If you keep the TFTP File Transfer application open for a long time, it is suggested
that you Save the Database so that these parameters will not be lost upon a
power failure.
To save the Database:
•
4-38
From the Configuration menu, select Save Database.
TFTP File Transfer
RADview-HPOV/ATM User’s Manual
4.6
Note
Chapter 4 RADview-HPOV System Functions
Net Inventory
For this version of RADview-HPOV/ATM, the only RAD agents that support Net
Inventory are: ACE-202 and ACE-2002/2002E phase 2.5 or higher.
Introduction
The Net Inventory application enables you to display an Inventory Table for all
products that support Entity-MIB according to RAD implementation. The Inventory
Table (see Figure 4-33) includes inventory information about each node (agent) in
the map that supports Entity-MIB.
The table is a hierarchical system. Click on the left side of an Entity and the tree
opens to display all components that have the selected component ID in their
entPhysicalContainedIn MIB parameter.
Figure 4-33. Net Inventory Opening Window
The parameters in the Inventory Table window and their actions are described in
Table 4-11.
Notes
• The HPOV map should be open when activating Net Inventory for the first time.
• When you begin the application, information is read from all nodes that
represent agents supporting ENTITY-MIB on the map.
Net Inventory
4-39
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Opening Application
To open the Net Inventory application:
• Select HPOV Map go to Misc > RADview/OV > General > Net Inventory …
The Inventory Table window appears (see Figure 4-34).
Figure 4-34. Opening Unix Application
Using the Net Inventory Table
The Net Inventory Table (see Figure 4-33) parameters are listed in Table 4-11.
Table 4-11. Inventory Table Parameters
Parameter
Possible Values / Description
Last Refresh
NMS time when the last time Refresh was performed
Entity
Unique value identifies the physical entity
Desc.
Description of the entity
Class
Class of the component
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 will return a virtual
Stack as its “Parent”. This virtual stack will be the “Parent” of all Remote chassis
connected to the same “Parent”.
Managed Remote chassis will not be taken in account, and is not part of the virtual
stack.
HW ver.
Hardware revision of the component
SW ver.
Software revision of the component
FW ver.
Firmware revision of the component
FW usually applies to ASIC
Name
4-40
Name of entity
Net Inventory
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-11. Inventory Table Parameters (Cont.)
Parameter
Possible Values / Description
Serial No.
Read/Write field containing the component Serial Number (on the sticker that is
attached to the component when it leaves RAD).
Alias
Read/Write field containing the User Alias for the component
FRU
Field Replaceable Unit
True – this component can be replaced at the field
[Filter…]
Opens a dialog box to filter the entity
[Display all Nodes]
Displays all Map Nodes
[Edit…]
Opens a dialog box to edit the Serial Number and Alias of the highlighted row
[Close]
Closes the application
[Print…]
Prints all highlighted rows
[Save to File…]
Saves all highlighted rows
[Expand All]
Opens all “tree” entries to the lowest level
[Collapse All]
Closes all “tree” entries to “Node” level only
[Help]
Displays Help file
[Refresh]
Refreshes file
[Refresh Selection]
Refreshes selected entity
False – this component can not be replaced at the field
You can sort each column if the left-side “tree” is at the NODE level.
Note
In order to Save/Print the entire display, make sure that no row is selected (press
<Ctrl> and click the left mouse button to de-select any highlighted rows).
Net Inventory
4-41
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Using Filters for the Display
To filter display:
1.
On the Inventory Table, press <Filter>.
The Inventory List Filter screen appears (see Figure 4-35).
2.
Select whether you want to filter on:
All Map Nodes
Displayed Nodes Only.
Note
Only one selection can be made at a time.
3.
Click on any parameters that you want to use as a filter, and enter the filter
criteria.
4.
Press <OK>.
Only those Nodes that have entities matching all the filter criteria will be
displayed.
Notes
• Filtering is not case-sensitive.
• The only wild character that can be used in the Edit boxes is *.
Figure 4-35. Inventory List Filter
4-42
Net Inventory
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-12. Inventory List Filter Parameters
Parameter
Possible Values / Description
Filter on all Map Nodes
Note: Only one selection can be made at a time.
Filter on displayed Nodes only
Node
Checked, Unchecked
Note: If checked, enter value for filtering.
Desc
Checked, Unchecked
Note: If checked, enter value for filtering.
Class
If checked, select value from: Modem, Chassis,
Back-Plane, Slot, PS, FAN, Sensor, Card, Port,
Stack, CPU
HW ver.
Checked, Unchecked
Note: If checked, enter value for filtering.
SW ver.
Checked, Unchecked
Note: If checked, enter value for filtering.
FW ver.
Checked, Unchecked
Note: If checked, enter value for filtering.
Name
Checked, Unchecked
Note: If checked, enter value for filtering.
Serial No.
Checked, Unchecked
Note: If checked, enter value for filtering.
Alias
Checked, Unchecked
Note: If checked, enter value for filtering.
FRU
Field Replaceable Unit
If checked, select: Yes, No
Note: If checked, enter value for filtering.
Net Inventory
4-43
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Editing an Entity
To edit:
1.
On the Inventory Table, highlight a row and press <Edit>.
The Edit dialog box opens (see Figure 4-36).
2.
Modify Serial No. or Alias.
3.
Press <Set>.
Figure 4-36. Edit Dialog Box
Expanding/Collapsing Sublevels
To expand/collapse sublevels of an Entity:
•
On the Inventory Table, highlight a row and double-click an <Entity>.
To expand all sublevels of all Entities in a tree:
•
On the Inventory Table, press <Expand All>.
All “tree” entries are displayed to the lowest level (see Figure 4-37).
Figure 4-37. Expand All
4-44
Net Inventory
RADview-HPOV/ATM User’s Manual
4.7
Overview
Chapter 4 RADview-HPOV System Functions
Automatic Configuration Upload
The Automatic Configuration Upload (ACU) application automatically, and
periodically, backs up the Configuration of a predefined list of RAD devices (such
as ATM, and TDMoIP products). It is based on Client/Server architecture.
This application can be used for:
•
ACE-101
•
ACE-50
•
ACE-202
•
ACE-2002
The Configuration of the device is defined in special Configuration and User files
(located on the device) and can be uploaded to the computer disk by
TFTP protocol. The ACU application only requests the device’s Agent to open an
Upload TFTP session.
Server
The Automatic Configuration update is performed in the following way: for every
RAD device (agent) in the list, the ACU Server sends a request to start Trivial File
Transmit Protocol (TFTP) to save the Configuration and User files on the computer
disk. 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) for every TFTP session is determined by the SNMP trap that was
received from the Agent, or by timeout (where result = failure).
Client
The ACU Client is a graphical application that allows you to view and configure
parameters of the Server, and perform an Upload session immediately according
to predefined parameters. An Upload session is a set of all TFTP Upload sessions
for every Agent in the list. After the Upload session you can display results for
Upload sessions that were completed (Reports). In the Reports, you can choose
the number of sessions to be displayed.
The Client can configure the following Server parameters:
•
Date and Time to start the Upload
•
Time interval to perform the Upload sessions
•
Directory and File name to save the uploaded files
•
Setting TFTP parameters
•
Adding/Removing nodes to the agent list.
Any number of Client applications can be opened simultaneously.
Uploads will take place if the Server is running, even if the Client is closed.
Automatic Configuration Upload
4-45
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Setting up the TFTP Server in a Unix Workstation
Note
Verify that the TFTP Server is enabled before you begin the ACU application.
To setup 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 the ACU file will be saved.
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.
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.
Right click on the desktop and select Text Editor from the Application
menu.
From the File menu select Open.
The Text Editor is displayed.
Type: /etc in the Enter Path or File Name field.
Click Update.
Type: inetd.conf in the Enter a File Name field.
Click OK.
Search for the line starting with #tftp.
(e.g. # tftp dgram udp). Remove the # sign (see Figure 4-38).
At the end of that line you will see –S <TFTP_boot>. Change
<TFTP_boot> to the directory you just created.
(e.g. /export/home/tftp).
Note
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 (see Figure 4-42).
7.
4-46
Save the inetd.conf file with the current changes. From the File menu, select
Save and then Close the Text Editor.
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
8.
Chapter 4 RADview-HPOV System Functions
Reboot the UNIX workstation:
Type: sync
Type: init 6
# sign
removed
Figure 4-38. Edit inetd File
Opening the ACU Application
Before starting the Software and Configuration Download application, ensure that
RADview HPOV and a TFTP server are running.
To login:
1.
Login to Solaris as a RADview HPOV user.
2.
Enter ovw & from an X-terminal window.
3.
Login to RADview:
From the Misc menu select RADview/OV>>Login…
Use the Default Administrator Account to log into the system:
User: root/password:root
Click OK.
Note
Only RADview HPOV administrators are privileged to use the Software and
Configuration Download application.
Automatic Configuration Upload
4-47
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
To open the ACU application:
1.
From the Misc menu select RADview/OV > General > Auto Config Upload
> Start Server (see Figure 4-39).
The terminal displays a message that “ACUD Server was started
successfully” (see Figure 4-40).
2.
From the Misc menu select RADview/OV > General > Auto Config Upload
> Start Client.
The ACU main window appears (see Figure 4-45). If the ACU Server is not
running an error message is displayed (see Figure 4-41) and the ACU
application will not start.
3.
Verify that the TFTP Server is enabled when the ACU Client application starts.
If the TFTP Server is closed and you try to upload any device, an error
message appears (see Figure 4-41). This message appears for any activity
that requires the Server to be open (i.e. Save File).
Figure 4-39. Opening the ACU application
4-48
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Server started
successfully
Figure 4-40. Start Server Terminal Message
Figure 4-41. ACU Server Disable Message
Figure 4-42. TFTP Disable Message
Automatic Configuration Upload
4-49
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Closing the ACU Application
To close the Server:
1.
From the Misc menu select RADview/OV > General > Close Server (see
Figure 4-39).
The Auto Config Upload Stop Server confirmation dialog appears (see
Figure 4-43).
2.
Press <OK>.
The terminal displays a message that “ACUD Server exited” (see
Figure 4-44).
Figure 4-43. Close Server Confirmation Dialog Box
Server exited
successfully
Figure 4-44. Close Server
4-50
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
ACU Configuration Operations
Table 4-13 lists the different management options for ACU.
Table 4-13. ACU Management Options
Tasks – Configuration
Dialog Box and
Parameter Location
Path
Saving a report as a file
Save Report dialog box
(Figure 4-47)
Configuration
Report
Save As…
Printing a report
Print Report dialog box
(Figure 4-48)
Configuration
Report
Print
Clear the report
Clear Report dialog box
(Figure 4-49)
Configuration
Report
Clear
Upload the configuration
immediately
Upload Configuration
Confirmation dialog box
(Figure 4-50)
Configuration
Upload Now
Exit ACU application
Exit ACU dialog box
(Figure 4-51)
Configuration
Exit
Schedule the Upload
ACU Schedule dialog box
(Figure 4-52)
Options
Schedule
Set TFTP
ACU TFTP Settings dialog
box (Figure 4-57)
Options
TFTP Settings
Select Nodes
ACU Nodes Selection
dialog box (Figure 4-58)
Options
Node Selection
Automatic Configuration Upload
4-51
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
ACU Main Window – Reports Filter
The ACU Application opens with the Report Filter window (see Figure 4-45). It
shows a set off all TFTP upload sessions for every agent in the list and lists the
results for Upload sessions:
You can filter the report by:
•
Type of product
•
Status –show all statuses (i.e. “Connecting..”; ”Connected. Transferring Data”,
“Created New Directory”, “Agent Reject Request to Upload File”), or show
only the final status.
You select a number that reflects the most recent number of Upload Sessions that
will be shown in the Report. This number also reflects the number of directories.
Each FTP upload session creates a file, which is displayed as one row in the
Report.
The color of the row indicates its status:
•
Green – indicates success
•
Red – indicates failure
•
Yellow – indicates that the directory has been removed
•
Clear – indicates such statuses as “Connecting..”; ”Connected. Transferring
Data”; “Created New Directory”.
An ACU Session consists of all the FTP upload files for all agents that were
selected. Figure 4-45 shows the difference between an FTP session and an ACU
session.
For each ACU session, and each node that was selected, the Report lists:
•
Node Name
•
Type (OID)
•
Time of Upload
•
Location of Configuration file
•
File Type
•
Last Status
•
Name Within product –for User file only = "mc1cfg”.
To filter reports:
4-52
1.
In the Report Filter window, select the agent type that you want to view in
the Report. Click on those agents that you want to be included in the Report.
2.
Type a number for Last Sessions. This determines the number of upload
sessions (1–1000) that you see in the ACU Main Window.
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
3.
Chapter 4 RADview-HPOV System Functions
Check (see Figure 4-45) or Uncheck (see Figure 4-46) Final Status Only.
Check means that one final status (file) will appear for a TFTP session.
Uncheck means that all intermediary statuses will appear for a TFTP
session.
4.
Press <Apply> to save the filter settings.
The filter settings are saved and the report settings are refreshed.
Note
A file can also be created for all failures, for example if a file transmission was
started but not finished, or SNMP Trap (“TFTP upload finished successfully ”) was
lost.
Number
of ACU
sessions
in Report
(scroll to
bottom
for all 20)
One TFTP
Session
(for 1 file)
Last
Upload
Session
(for all
Agents)
End of
ACU
Session
Previous
Session
Figure 4-45. Report Filter – Final Status Only
Automatic Configuration Upload
4-53
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Figure 4-46. Report Filter – Showing Intermediate Reports
4-54
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Configuration
The Configuration menu provides options for saving, printing, or clearing the
report.
Saving the Report
To save the reports to a file:
1.
From the Configuration menu, select Report > Save As.
The Save dialog box appears (see Figure 4-47).
2.
Enter directory and file name.
3.
Press <Save>.
Figure 4-47. Save Report Dialog Box
To refresh the list of folders and file names:
•
In the Save dialog box press <Update>.
If directory and file were changed from another computer, this updates the
directory and file names.
Automatic Configuration Upload
4-55
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Printing the Report
To print the report:
1.
From the Configuration menu, select Report > Print.
The Print dialog box appears (see Figure 4-48).
2.
Enter the Print parameters.
3.
Press <Print>.
Figure 4-48. Print Report Dialog Box
Clearing the Report
To clear the report:
1.
From the Configuration menu, select Report > Clear.
The Clearing Report confirmation dialog box appears (see Figure 4-49).
2.
Press <OK>.
Figure 4-49. Clearing Report Dialog Box
4-56
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Upload Now
To upload the configuration:
1.
From the Configuration menu, select Upload Now.
The Automatic Configuration Upload confirmation dialog box appears (see
Figure 4-50).
2.
Press <OK>.
When ACUD Server uploads a session, the following status bar messages
are displayed:
“Upload in Process (Started at <HH:MM:SS>)”
“Upload in Process - <x> from <y> nodes completed”
“Upload in Process - <x> from <y> nodes completed (Iteration
No. 2)”
Figure 4-50. Upload Now Confirmation Dialog Box
Note
During the Upload Session, all menus are disabled (except Report→Save As…/
Print… and Help).
Exit
To exit the Automatic Configuration Upload application:
1.
From the Configuration menu select Exit.
The Exit Automatic Configuration Upload confirmation dialog box appears
(see Figure 4-51).
2.
Press <OK>.
Figure 4-51. Exit Automatic Configuration Upload Confirmation Dialog Box
Automatic Configuration Upload
4-57
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Options
ACU options include:
•
Scheduling
•
Setting TFTP parameters
•
Node selection.
Scheduling the Upload
To schedule the upload procedure:
1.
From the Options menu select Schedule
The Automatic Configuration Upload Schedule dialog box appears (see
Figure 4-52).
2.
Click on the arrow to the right of Date.
A pop-up menu appears (see Figure 4-53); click on the selected Date for
ACU.
3.
Click on the arrow to the right of Time.
A pop-up menu appears (see Figure 4-54); click on the selected Time for
ACU.
4.
Click on the arrow to the right of Time Interval.
A pop-up menu appears (see Figure 4-55); click on the selected Time
Interval for ACU.
5.
Enter number for No. of Saved Sessions.
6.
Press <Set>.
The date and time are displayed for Next Session and the Status bar at the
bottom of the dialog box displays: “DB GET successful” (see Figure 4-52).
Table 4-14 lists the Schedule parameters.
Note
4-58
If the date and time occurred in the past, an error message is displayed in the Status
Bar (in red) “New Start Date & Time cannot be in the past”. The dialog box does not
close until a valid Date and Time have been selected.
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Figure 4-52. Schedule Start Time and Date Dialog Box
Figure 4-53. Schedule Date
Figure 4-54. Schedule Time
Automatic Configuration Upload
4-59
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Figure 4-55. Schedule Time Interval
Table 4-14. Schedule Parameters
Parameter
Possible Values / Notes
Date
Date of first upload session (a new Date must be in the future)
Default value: current date
Time
Time of first upload session (a new Time must be in the future)
00:20 – 23:20
Default value = 00:20
20 min. after the hour allows for other tasks that are performed periodically
for other applications, so that the computer won’t be overloaded
Time Intervals
Time period for periodical Upload Sessions
6 hrs, 8 hors, 12 hrs, 1 day, 3 days, 7 days, 10 days, 15 days, 30 days
Default value = 1 day
No. of Saved Sessions
Number of upload sessions in report (see Figure 4-45) 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 will be saved in the Reports.
Also, the last “n” directories that were created will be saved.
Next Session
Date and nearest time of next upload
(Read only)
Equals (<Start Date & Time> + K*<Time Interval>) where K is integer,
or, if is any session was missed - it is the nearest XX:20 (HH:MM).
4-60
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Each upload session creates one upload directory:
•
mng164_FileTransfer_<yyMMdd_hhmm>.
Each “mng164_FileTransfer_” directory contains all the Upload Configuration files.
The name of the Upload Configuration file is the IP address of the device whose
configuration file was uploaded.
To view the IP Addresses of those nodes whose configuration was uploaded:
1.
Type >cd <name of root directory that you have selected>.
2.
Type >ls
The IP Addresses are displayed.
mng164File Transfer
directory
IP Addresses
that were
updated
Figure 4-56. IP Addresses in mng164_FileTransfer
Example
Figure 4-56 shows the file: mng164_FileTransfer_020105_2320. This configuration
file was uploaded on January 5, 2002 at 11:20 PM, i.e. yy=02, MM=01, dd=05,
hh=23, mm=20. The devices whose configuration was uploaded have IP
addresses: 172.17.152.50, 192.168.226.20, and 192.168.226.60.
”172.17.152.50” is the name of the Configuration file.
“172.17.152.50.mc1cfg” is the name of the User file.
Automatic Configuration Upload
4-61
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
TFTP Settings
To set TFTP:
1.
From the Options menu select TFTP Settings.
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>.
Figure 4-57. TFTP Settings
Table 4-15. TFTP Settings
Parameter
Possible Values / Notes
TFTP Server IP
Due to UNIX security, it must be the local computer
File’s Location
The path where all upload directories are created and saved
For UNIX: File's Location must be an existing directory under TFTP Root
For PC : File's Location must be an existing directory
Default value: TFTP root
Total Timeout (sec)
1–600
Default value = 60
Note: Agent tries to perform file TFTP upload (number of retries) during this
time (maximum). If no snmp_trap is received during this time – the “Time-Out”
report is written to Data Base.
Retry Timeout (sec)
1–120
Default value = 15
Note: Agent tries to perform file TFTP upload (only 1 retry) during this time
(maximum). If no success – it tries again, until “Total Timeout” is finished.
Retry timeout must be less than Total timeout.
4-62
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Selecting Nodes
You can select which agent configurations will be updated by:
•
Agent type (ACE-101, ACE-50, ACE-2002, IPmux-1/1E, IPmux-4, IPmux-16)
•
Node (IP Address).
Adding/Removing Nodes
To Add/Remove nodes to ACU list:
1.
From the Options menu, select Nodes Selection.
The Automatic Configuration Upload Nodes Selection dialog box appears
(see Figure 4-58).
2.
Press <Node Selection> for an agent type.
The ACU application checks the database for all nodes of that agent type.
The Node Selection dialog box for a specific agent type appears, showing
IP Addresses for all nodes of that agent type, in two columns (see
Figure 4-59). You can move nodes from one column to the other by the
<Add> or <Remove> button. The nodes that appear in these lists are
only of the agent type in the row that was pressed in the previous dialog
box.
Remaining Nodes are those nodes from HPOV that are not in the ACU
database (not scheduled for ACU).
Selected Nodes are those nodes from HPOV that are in the ACU
database (scheduled for ACU).
3.
Perform one of the following (see Figure 4-59):
Check <All> for all remaining nodes of an agent
Check <Selected> if you want to make any changes, i.e. to add or
remove nodes from the list that will be uploaded in the next session.
4.
Highlight a node and press <Add> or <Remove>.
The node(s) moves to the opposite column.
5.
Press <Set>.
The Automatic Configuration Upload Nodes Selection dialog box appears
(see Figure 4-58).
6.
Click on the checkbox for each agent where you want to apply ACU and
press <Apply>.
The Status bar on the bottom of the dialog box says “DB Set successful”.
7.
Press <All Nodes> to verify that you have selected the correct node name (IP
Address) and agent type.
The All Agents dialog box appears (see Figure 4-60). Only those nodes that
have Yes in the Uploaded column will be updated in the next scheduled
ACU operation. They are highlighted in green.
Automatic Configuration Upload
4-63
Chapter 4 RADview-HPOV System Functions
8.
RADview-HPOV/ATM User’s Manual
Press <Close> on the All Agents dialog box.
The Automatic Configuration Upload Nodes Selection dialog box appears.
9.
Press <Cancel> on the Automatic Configuration Upload Nodes Selection
dialog box.
During the next scheduled upload session, only the configurations of those
nodes that you have selected will be updated.
Figure 4-58. Automatic Configuration Upload Nodes Selection Dialog Box
4-64
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Figure 4-59. Nodes Selection Dialog Box– for Agent
Automatic Configuration Upload
4-65
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
For example: Figure 4-59 lists the IP addresses for all IPmux-1E products in the
database. The nodes in Selected Nodes will have Configuration Upload in the
next scheduled session. You can add nodes from Remaining Nodes to this list or
remove some nodes form the Selected Nodes. The final list in Selected Nodes
contains those IP addresses that will have Configuration Upload in the next
scheduled session. Figure 4-60 shows Yes that Configuration Upload is scheduled
for those nodes.
Figure 4-60. All Agents Dialog Box – Status
4-66
Automatic Configuration Upload
RADview-HPOV/ATM User’s Manual
4.8
Chapter 4 RADview-HPOV System Functions
Net Statistics
The ATM Statistical Information Collecting Application is a tool for saving into files
statistical information collected from an ATM device.
Note
If a new RADview version, containing updated statistic features is installed while the
statistics process is active, the new statistics process will not take place until the old
process will be killed and the new process will be started from the HPOV menu
entry.
The processes that should be killed are:
ACE-101: /opt/MNG/MNGVIEWHP/WAN/bin/mng164_gen_net_statistics
ACE-2002: /opt/MNG/MNGVIEWHP/WAN/bin/mng164_ace0_statistics
Setting up the TFTP Server in a Unix Workstation
Note
Verify that the TFTP Server is enabled before you begin the statistical collection
application.
To setup 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 /export/home/tftpboot by typing:
mkdir -p /export/home/tftpboot
4.
Type: chmod -R 777 /export/home/tftpboot to change the permission of the
directory you created to Read/Write.
Net Statistics
4-67
Chapter 4 RADview-HPOV System Functions
5.
RADview-HPOV/ATM User’s Manual
Edit the /etc/inetd.conf file in order to enable the TFTP Server. Follow the
next steps to edit the /etc/inetd.conf file using the Text Editor.
Right click on the desktop and select Text Editor from the Application
menu.
From the File menu select Open.
The Text Editor is displayed.
Type: /etc in the Enter Path or File Name field.
Click Update.
Type: inetd.conf in the Enter a File Name field.
Click OK.
Search for the line starting with #tftp.
(e.g. # tftp dgram). Remove the # sign (see Figure 4-61).
In Solaris 2.8TM, change the udp6 to udp.
At the end of that line you will see -S /tftpboot. Change to the directory
you just created /export/home/tftpboot.
Note
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 (see Figure 4-61).
6.
4-68
Net Statistics
Save the inetd.conf file with the current changes. From the File menu, select
Save and then Close the Text Editor.
RADview-HPOV/ATM User’s Manual
7.
Chapter 4 RADview-HPOV System Functions
Reboot the UNIX workstation:
Type: sync
Type: init 6
# sign
removed
Figure 4-61. Edit inetd File
Station's UDP Receive Buffer
The UDP receive buffer has a maximum size limitation therefore, there is a chance
that NOT all the Agents responses will be handled correctly for the Statistic
Collection application.
To overcome this limitation the following steps should be performed:
1.
Login as user root.
2.
Enlarge the UDP buffer size using the command
”ndd -set /dev/udp udp_max_buf 10000000”
Net Statistics
4-69
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
To enable statistical gathering into files:
1.
From the HPOV Misc menu, select RADviewOV, ATM > Net Statistics...
The Net Statistics dialog box appears (Figure 4-62).
Figure 4-62. Net Statistics Dialog Box
2.
Click on Agent Selection... for a product to set the agents for which statistics
will be gathered.
The Agent Selection dialog box appears (Figure 4-63).
Figure 4-63. Agent Selection Dialog Box
4-70
Net Statistics
RADview-HPOV/ATM User’s Manual
Note
Chapter 4 RADview-HPOV System Functions
3.
Select agents from the Remaining Agents list and transfer them to the
Selected Agents list using the right-pointing arrow.
4.
Unselect agents from the Selected Agents list and transfer them to the
Remaining Agents list using the left-pointing arrow.
To select all agents from a list, click the All button. To select agents one by one,
click the Selection button.
5.
Click OK.
6.
Click the check box of the product for which statistics will be gathered and
stored. The statistics are gathered for the selected type only.
7.
Press Set to activate the statistics gathering.
8.
In the Storage Period field, set the number of days the application will store
the statistic files.
Since every hour, many statistic files are being generated; it is possible for the
hard disk to reach full capacity. In order to prevent this from happening, the
Storage Period field enables the user to set the number of days that the
application stores the statistic files, after which they are deleted. The deletion
is performed according to the file’s date and not the file’s name.
ACE-50/ACE-101 Statistics Collection
Normal Operation
The Statistical Information Collecting Application sets a timer that expires on the
hour. On the hour, every hour, the relevant nodes (of the type that you requested)
are queried for the last four intervals for the variables that were requested.
Note
In order to mark the end of the collection stage an empty file is created under
"/opt/MNG/MNGVIEWHP/WAN/StatCollect" and called AC1StatFinished this file is
removed at the beginning of the next collection stage.
Net Statistics
4-71
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
First Hour after Statistical Information Collecting Application was
Started
The following three situations may exist:
•
No files exists in the Statistical Information Collecting Application for the
current day
•
Files already exist for the current day
•
The hour is 24:00.
In the first case, the Statistical Information Collecting Application determines the
number of intervals that it needs to get from each agent by checking the number
of intervals that have passed since midnight.
In the second case, the Statistical Information Collecting Application considers the
number of intervals that appear in the files already, and only collects what is still
needed from the agent.
In the third case, no writing to a file is done. The Statistical Information Collecting
Application waits another hour, at which time it starts to save statistical information
for a new day.
When the Next Collection is Enabled/Disabled
The Statistical Information Collecting Application monitors the completion of data
collection for each agent. It will not enable the next writing to the files until the last
one has been completed for all agents. If the last data collection has not finished
by the time the next one is due to start, the next one is postponed to the next top
of the hour, which means that more intervals will have to be collected.
Node Not Responding
If at any time during the data collection the Statistical Information Collecting
Application loses connection with a node, the process for the specific thread of
data collection is stopped and is resumed again at the next top of the hour. Note
that work is stopped only for the specific group of variables for a specific interface.
Other interfaces on the same node may not have communication problems, and
so the process for them will continue as normal.
Non-Existing Intervals
For each requested interval that does not exist, the Statistical Information
Collecting Application writes -1s for each variable for the specific interface.
Change of Interval During Collection
If at the top of the hour, the time since the last interval for a specific node is
greater than 10 minutes, the operation is postponed until the start of the next
interval. This is to minimize the risk of a change of interval in the agent while the
Statistical Information Collecting Application is in the process of getting the last N
intervals. If a change of interval still occurs, there will be a loss of one interval.
4-72
Net Statistics
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Change of Network Management Station Time
If the Network Management Station time is changed, it will cause a loss or
duplication of intervals the next time the files are written to. After that there will be
no problem. The loss of intervals occurs when the Network Management Station
time is set back. The duplication of intervals occurs when the Network
Management Station time is set ahead.
The tables for VC and VP contain too many variables to be able to get them in one
SNMP request. Therefore, several files will be created and a file grouping utility is
provided. For the PM tables there may be forward and/or backward directions. If
this table is requested, there should be space in the file for both directions, and if
only one is defined, the Statistical Information Collecting Application inserts -1s for
the other. Files will be automatically grouped at the end of the day.
Setting Variables
A configuration file is used for the purpose of saving statistical information and is
called (in the case of ACE101):
/opt/MNG/MNGVIEWHP/WAN/StatConfig/ac1_ NetStatisticsVariablesList
The file contains the names of the requested tables preceded by a # and followed
by the requested variable names that belong to this table. A comma follows each
word. The word NULL should end the list of variables for each table.
The following example is part of a file that describes the "#atmVpIntervalTable"
and the "#atmLoopbackVpIvlTable" tables and their variables.
#atmVpIntervalTable,atmVpIntervalVpi,atmVpIntervalNumber,atmVpIntervalR
xCellsClp01,atmVpIntervalRxCellsClp0,atmVpIntervalGcra0Violations,atmVpIn
tervalGcra1Violations,atmVpIntervalRxAIS,atmVpIntervalTxAIS,atmVpIntervalR
xRDI,atmVpIntervalTxRDI,atmVpIntervalContinuityLoss,atmVpIntervalUAS,atm
VpIntervalSES,atmVpIntervalCDC,NULL,
#atmLoopbackVpIvlTable,atmLoopbackVpIvlIfIndex,atmLoopbackVpIvlVpi,atm
LoopbackVpIvlIvl,atmLoopbackVpIvlOperStatus,atmLoopbackVpIvlCDV,atmLo
opbackVpIvlAverageDelay,atmLoopbackVpIvlMaxDelay,atmLoopbackVpIvlMin
Delay,NULL,
You can edit the ac1_NetStatisticsVariablesList file using any text editor so that
only the appropriate variables will be gathered from that type of device.
Note
A variable can be added only if the agent supports it. Consult RAD’s Technical
Support before adding variables.
Net Statistics
4-73
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Omitting Fields from the Table
You can omit any single field or multiple fields from the table. You can even omit
all the fields and leave only the name of the table.
Note
You can omit all the fields from the table and the name of the table. However, if
the table is a type that is joined, you will get messages saying that that the specific
files cannot be found.
Generated Files: Structure
The files are created in the directory:
/opt/MNG/MNGVIEWHP/WAN/StatCollect.
The first two columns in the file are: Interval-No. and Interval-Start-Time.
The format for the Interval-Start-Time is hour:min, and the value reflects the
Network Management Station time at the start of the interval.
The values collected and stored are separated by a space.
The variables collected are standard
Generated Files: Names
The convention for the file names is as follows:
<selection name>_<product type>_Interface#x.y.z_<table family>layer_year-mm-dd
Examples for the naming convention are as follows:
192.168.226.4_Ace101_Interface#2.0.30_vc-atm-layer_1999-09-14
192.168.226.4_Ace101_Interface#2.0.53_vp-atm-layer_1999-09-14
192.168.226.4_Ace101_Interface#2050_physical-layer_1999-09-14
Exiting NMS Station
The statistics collection continues even if the user exits the NMS station. When the
station reboots the statistics collection is activated automatically. The collection will
be made from the selected agents.
4-74
Net Statistics
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
ACE-202/ACE-2002 Statistics Collection
The Ace-202/2002 Statistics Collection is based on the TFTP upload process and
therefore has minimum overhead on the net (compared to SNMP).
At the beginning of a round hour, the application determines how many intervals
were logged so far. According to the number of missing intervals it issues a request
for the missing intervals. For each missing interval the agent creates a compressed
file, which contains all the relevant statistics data. This file is transferred by TFTP to
the NMS, under <TFTP_boot>/AC0Stat. A trap with the number of successfully
uploaded files is sent at the end of the upload stage, after which the compressed
files are decoded and the final statistics files are created.
The date and the number of successfully logged intervals are written to the
database.
Notes
• The Ace-2002/202 devices can handle only one TFTP session at any given
moment.
• It is possible to delay the collection start time. The offset, from the round hour, is
defined at the file: "StatStartTimeOffset", under
/opt/MNG/MNGVIEWHP/WAN/StatConfig.
The values should be in minutes, range 0-59, default=0.
• In order to mark the end of the collection stage an empty files are being created
under "/opt/MNG/MNGVIEWHP/WAN/StatCollect" and called AC0StatFinished
and ACE202StatFinished these files are removed at the beginning of the next
collection stage.
Determining the Number of Missing Intervals
The number of missing intervals is determined by the information in the database.
For example:
If today there are 40 logged intervals and the hour is 11:00 there are 4 missing
intervals. The application can retrieve up to 96 intervals per agent, not necessary
from the current day's midnight. If there are missing intervals from yesterday they
will be collected as well.
It is possible to limit the maximum number of intervals that the application can
request. This is done by editing the file
"/opt/MNG/MNGVIEWHP/WAN/StatConfig/ac0_IvlLimit", which contains, by
default, the number 96. This number can be set to any value in the range 1–96.
When the Next Collection is Enabled/Disabled
The Statistical Information Collecting Application monitors the completion of data
collection for each agent. It will not enable the next writing to the files until the last
one has been completed for all agents. If the last data collection has not finished
by the time the next one is due to start, the next one is postponed to the next top
of the hour, which means that more intervals will have to be collected.
Net Statistics
4-75
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Non-Existing Intervals
For each requested interval that does not exist, the Statistical Information
Collecting Application writes -1s for each variable for the specific interface.
Change of Interval During Collection
The agent handles interval switching. Meaning, if the NMS asked for intervals 1–4,
and during the creation of the file of interval 1 an interval switch was performed,
than the agent will in fact upload interval 2 and send it to the NMS as interval 1.
Change of Network Management Station Time
If the Network Management Station time is changed, it will cause a loss or
duplication of intervals the next time the files are written to. After that there will be
no problem. The loss of intervals occurs when the Network Management Station
time is set back. The duplication of intervals occurs when the Network
Management Station time is set ahead.
The tables for VC and VP contain too many variables to be able to get them in one
SNMP request. Therefore, several files will be created and a file grouping utility is
provided. For the PM tables there may be forward and/or backward directions. If
this table is requested, there should be space in the file for both directions, and if
only one is defined, the Statistical Information Collecting Application inserts -1s for
the other. Files will be automatically grouped at the end of the day.
Setting variables
The application uses two files, which contains the statistics interval table’s names
and the corresponding variables. The files names are:
Ace-202:
/opt/MNG/MNGVIEWHP/WAN/StatConfig/ace202_NetStatisticsVariablesList
Ace-2002:
/opt/MNG/MNGVIEWHP/WAN/StatConfig/ac0_NetStatisticsVariablesList
Since every uploaded interval file contains all the statistical information that is
relevant for that interval, the application doesn't have control on which tables and
variables the agent send. Therefore these files are used only for presenting the
variables names.
4-76
Net Statistics
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Generated Files: Structure
The files are created under the directories:
Ace-202:
/opt/MNG/MNGVIEWHP/WAN/StatCollect/ACE202Stat
Ace-2002:
/opt/MNG/MNGVIEWHP/WAN/StatCollect/AC0Stat
The first two columns in the file are: Interval-No. and Interval-Start-Time.
The format for the Interval-Start-Time is hour:min, and the value reflects the
Network Management Station time at the start of the interval.
The values collected and stored are separated by a space.
The variables collected are standard
Generated files: Names
The convention for the files names is as follows:
<selection name>_<product type>_Interface#i.j.k.l_<table name>_year-mm-dd
Examples for the naming convention are as follows:
192.168.226.20_Ace2002_Interface#4105_atmIfIntervalTable_2002-2-19
192.168.226.20_Ace2002_Interface#9.55.44.2_atmVcPMIntervalTable_2002-2-19
192.168.226.20_Ace2002_Interface#9.55.44_atmVcIntervalTable_2002-2-19
Note
For the ACE-202/2002 there is a file for every table
Exiting NMS Station
The statistics collection continues even if the user exits the NMS station. When the
station reboots the statistics collection is activated automatically. The collection will
be made from the selected agents.
Net Statistics
4-77
Chapter 4 RADview-HPOV System Functions
4.9
RADview-HPOV/ATM User’s Manual
Date and Time Auto Mode
The NMS can automatically update date and time parameters for the ACE agents
according to the computer clock.
Notes
• Closing HP OpenView does not affect the automatic update
• If the automatic update was activated and the station reboots, the update is still
performed with the same settings.
To set the parameters for automatic update:
1.
From the HPOV Misc menu, select RADview/OV, ATM > Date & Time Auto
Mode... Do not click an agent icon on the WAN map.
The Date & Time Auto Mode dialog box appears (Figure 4-64).
Figure 4-64. Date & Time Auto Mode dialog Box
4-78
2.
Click the check box next to the desired product and set the Update period in
Days/Hours.
3.
Click Set to implement the changes.
Date and Time Auto Mode
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
4.10 RADview Licensing Function
Introduction
The RADview licensing mechanism protects the system by restricting its installation
to the specific host for which the RADview license has been generated. In
addition, RADview licenses can be ordered at incremental sizes, to allow optimal
correlation between the types of managed devices and size of the network, with
the price of the management system.
The RADview license mechanism does not restrict or limit simultaneous usage by
different users in Client-Server applications (RADview-EMS, RADview-SC/TDM,
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 license agreement included in the
RADview package (Publication No. 351-803-04/03).
Network Size
Each managed RAD SNMP network element is subject to a license. Cards within a
chassis, or non-SNMP devices that are managed by a central RAD SNMP-based
unit, are not subject to a license. For example, cards within a DXC-30 chassis or a
remote ASMi-52 modem connected to the DXC-30 do not require a license. Only
the DXC-30 node itself will require and consume a license. As another example,
consider an LRS-24 modem rack, which allows you to manage not only the
modem cards installed in the specific rack, but also the remote modems
connected to these cards. In this case, only the LRS-24 itself will require and
consume a license.
Device Type
Each RAD manageable device is assigned an Equivalent Node Weight (ENW).
Different node types are assigned different ENW values according to their
complexity (starting from the lowest value of 1). The more complex the node, the
higher is the ENW. Managing a device with a higher ENW requires a larger license.
Note
A RAD node whose type cannot be identified by the License Server (such as when
the device is disconnected, or if the NMS does not have the correct community
name) is assigned a default value of 300.
Table 4-16 lists the different RAD devices and their respective ENW.
RADview Licensing Function
4-79
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-16. Equivalent Node Weights
Device
ENW
Device
ENW
ACE-101
65
IMX-2T1/E1
5
ACE-2002
80
IPmux-1
20
ACE-2002E
90
IPmux-4
70
ACE-202
65
IPmux-8
100
ACE-50
50
IPmux-16
190
ACE-52
45
KM-2100
40
ASMi-450
10
LA-104
15
DXC-30
80
LA-110
5
DXC-30E
110
LA-140
15
DXC-STM-1
100
LRS-12
50
DXC-8R
60
LRS-24
50
DXC-10A
60
LRS-52
85
FCD-E1A
15
MP-104
15
FCD-E1L
5
MP-204
25
FCD-E1T1
15
MP-2100
75
FCD-I
25
MP-2104
55
FCD-IP/WR
10
MP-2200
80
FCD-IPD
15
MP-2100H
70
FCD-IPM
15
Optimux-4E1/4T1
25
FCD-E1M
25
Optimux-T3
40
FCD-NTU
5
Optimux-T3L
30
FOMi-E3/T3
30
Optimux-XLE1/T1
40
HCD-E1
15
PRBi
20
HTU-2
10
RIC-155
20
HTU-E1
10
Vmux-2100
300
IMXi-4
20
Vmux-110
35
Bundled License
Every RADview package includes a built-in bundled license that allows you to
manage a small-to-medium sized network (depending on the actual devices
managed by the system). Larger networks require you to purchase and install
additional licenses, as they expand.
The different RADview packages and their respective bundled ENW, free of charge
are listed in Table 4-17.
4-80
RADview Licensing Function
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-17. Bundled Licenses
Platform
Bundled License Points
(Free of Charge)
RADview-PC packages
200
RADview-HPOV packages
400
RADview-EMS (PC) packages
300
RADview-EMS (Unix) packages
400
RADview SC TDM
800
RADview SC TDMoIP (PC)
300
RADview SC TDMoIP (Unix)
600
RADview SC Vmux (PC)
300
RADview SC Vmux (Unix)
600
License Size Calculations
To determine the license size required to manage a given network, perform the
following calculation:
Number of License points (for each type) = (Product type ENW) x (Number
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 size of license points is bundled within every RADview
package, the actual license size that must is required is smaller, and can be
calculated as follows:
Required License points =
Total Number of Licenses points (for all types) − RADview package bundled
license
Calculation Example
Let’s assume a network to be managed by RADview PC consists of:
•
Two DXC-8R unit
•
Twenty FCD-E1L units
•
Four FCD-IP devices.
Consulting the above product ENW table, we find that:
•
DXC-8R = 60 ENW
•
FCD-E1L = 5 ENW
•
FCD-IP = 10 ENW
RADview Licensing Function
4-81
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Consulting the above RADview package bundled license table we find that:
•
RADview-PC packages include a 200-point free-of-charge bundled license.
Thus, the license you need to order = [(2x60) + (20x5) + (4x10)] –(200) = 60.
Although the actual license size that is needed to manage the given network is
260, and since 200 points are bundled free-of-charge within the RADview PC
package, you only need to order 60 license units.
To simplify the calculations for larger networks, that contain many different
products, use the RADview License Calculator.
License Service Manager
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.
Opening the Program
Note
For UNIX stations, you must log into the system before opening the License Service
Manager application.
To open the License Service Manager for UNIX:
•
Select: Misc > RADview OV > License Service Manager.
To open the License Service Manager for PC:
•
4-82
Select: Programs > Network Manager > General > License Service
Manager.
RADview Licensing Function
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
General Tab
The General tab allows you to check the growth potential 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.
If a temporary license has expired, it is displayed as a red line in the table.
Figure 4-65. General Tab
Table 4-18. License Status
Parameter
Possible Values / Notes
Total installed license
points
Total License Points to which the user is entitled (for all valid licenses that
have not expired)
Consumed license points
License Points that the user has already used (for RADview managed
elements)
License ID
Unique identifier given by RAD to a certain existing license
Licnse points
License points included in the specific license file
Exp. Date
Expiration Date of a temporary license. If the license is permanent, it will be
indicated as “permanent”.
Host Identifier
For Windows – IP Address
For UNIX – HOST ID
Platform
Platform for which the license was generated (Windows or UNIX)
RADview Licensing Function
4-83
Chapter 4 RADview-HPOV System Functions
RADview-HPOV/ATM User’s Manual
Managed Element List
The Managed Element List tab displays all the devices which are managed by
RADview.
Figure 4-66. Managed Element List
Figure 4-67. Managed Element List – Continued
4-84
RADview Licensing Function
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Table 4-19. Managed Element List
Note
Parameter
Possible Values / Notes
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 without requiring an
additional license. The RADview license service makes sure that different logical
representations of single network elements will 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 will not be reflected
in the Managed Element List until you refresh the entry (File > Refresh).
The display is in order by IP Address. You can sort the list by clicking on any
column.
File Menu
Figure 4-68. File Menu
RADview Licensing Function
4-85
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Add License
To add a license file:
1.
Display the License Service Manager – General tab.
2.
Select: File > Add License.
3.
Select a license file.
4.
Press <Save>.
The data of the new file is added to a new row of the General tab.
5.
If the license file already exists, a message is displayed: “This License already
exists.” Press <OK> and select the entry again.
Figure 4-69. Add License
4-86
RADview Licensing Function
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Remove License
To remove a license file:
1.
Display the License Service Manager – General tab.
2.
Select one of the rows.
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 doesn’t cause Total Installed License Points value
to be less than the Consumed License Points, it is removed from the
General tab list.
If the removal of this row causes Total Installed License Points value to be
less than the Consumed License Points, the following warning message
will be displayed.
Figure 4-70. Remove License Warning
Press <OK> to confirm, or <Cancel> to cancel this operation.
The row is removed from the General tab list. Management Services will
not work anymore (until another valid License is added).
Refresh
Each tab of the License Service Manager must be refreshed separately.
RADview Licensing Function
4-87
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Action Menu
Figure 4-71. Action Menu
The Service Console allows the user to manage the License Server.
To start the License Server:
1.
Select Action > Service Console.
2.
In Service Action field select Start.
To stop the License Server:
1.
Select Action > Service Console.
2.
In Service Action field select Stop.
A message is displayed: “Stopping License Server operation.”
Figure 4-72. Service Console
Options Menu
Figure 4-73. Options Menu
4-88
RADview Licensing Function
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Server Side Configuration
Note
This is applicable only if Client and Sever are installed on the same computer.
To configure the Server Side:
1.
Select Options > Server Side Configuration.
2.
Enter Socket Port and INS Port.
3.
Press <Set>.
Figure 4-74. Server Side Configuration
Table 4-20. Server Side Configuration
Parameter
Possible Values / Notes
Socket Port
Socket Port of the Server
Valid values: ≥ 1000 (blank is not a valid value)
INS Port
INS Port of the Server
Valid values: ≥ 1000 (blank is not a valid value)
RADview Licensing Function
4-89
RADview-HPOV/ATM User’s Manual
Chapter 4 RADview-HPOV System Functions
Client Side Configuration
To configure the Client Side:
1.
Select Options > Client Side Configuration.
2.
Select Server CORBA Mode, and enter Socket Port, INS Port, and Server IP
Address.
3.
Press <Set>.
Figure 4-75. Client Side Configuration
Table 4-21. Client Side Configuration
Parameter
Possible Values / Notes
Server CORBA Mode
For future use
Socket Port
Socket Port of the Server
Valid values: ≥ 1000 (blank is not a valid value)
INS Port
INS Port of the Server
Valid values: ≥ 1000 (blank is not a valid value)
Server IP Address
Note
4-90
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.
RADview Licensing Function
Chapter 5
RADview-HPOV for ATM
This chapter briefly explains the HP OpenView (HPOV) features which allow the
user to create and monitor nets and agents.
5.1
Introduction
The RADview-HP OpenView management system, running on a workstation
connected to the ATM network, provides a complete solution for monitoring and
controlling ACE devices, while simplifying the configuration and maintenance
requirements. In addition to the general RADview-HP OpenView administrative
tasks and functions, the management system enables the following specific
functions:
•
Displaying alarm status and system configuration through the management
system at all times.
RADview-HP OpenView for ATM on the SNMP Platform
SNMP is the protocol for inter-networking between the agent and the network
management station for TCP\IP based networks. SNMP defines two-way
communication between the management station and the agent.
The SNMP provides network managers with a central station for observation,
control and management of their installation. As such, SNMP is fully independent
of manufacturer-linked concepts.
Querying values that the agent assembles enables the software in the network
management to monitor and control devices. The most important task of an agent
program is to provide information about objects, which correspond to the critical
parts and, actions of the device for which the agent is responsible. The agents store
this information and deliver it to a management station upon request. Agents in
critical circumstances such as unusual errors issue only Un-requested signals
(alarms).
SNMP also functions as a proxy agent, thus permitting a management station to
monitor and control network elements that do not conform to SNMP
specifications. The proxy is able to convert protocols and provide the network
management station with a uniform picture.
Introduction
5-1
RADview-HPOV/ATM User’s Manual
Chapter 5 RADview-HPOV for ATM
5.2
ATM Functionality
The System Level contains a graphic representation of the ATM device front panel.
The Agent View includes the agent interfaces and their operational and
communication status.
The System Level enables you to:
•
Add and update configuration parameters of the ATM device
•
View configuration information for ATM device interfaces
•
View the operational status for all interfaces
•
Reset the agent hardware and restore agent default configurations
•
View active alarms
•
View self test results
•
Register a management station
•
View the last 24-hour statistics.
An ATM Agent View window exists for each ATM agent node on the local map of
the WAN hierarchy.
To open the ATM Agent View window:
1.
Select an ATM agent node on the map and choose Zoom from the Misc>
RADview-OV submenu, or from the RADview Zoom button on the menu bar.
2.
Zoom on a ATM agent node on the map.
If there is no initial communication, the Select WAN Type dialog box
appears.
3.
In the WAN Type list box, select the appropriate agent name and click
<OK>.
The ATM main window appears.
Figure 5-1. ACE-101 Agent View
5-2
ATM Functionality
RADview-HPOV/ATM User’s Manual
Chapter 5 RADview-HPOV for ATM
The Agent View window contains:
•
A view of the front panel of the ATM device
•
A title bar which displays the name of the agent and its communication status
in relation to the management station
•
A menu bar containing Configuration, Fault, Diagnostics, Statistics (for
ACE-2002 only), Options and Help menus. (Menu options vary according to
the selected item)
•
Network and User Ports, which you can select to switch to the Port Level.
5.3
The Port and Card Levels
The Port and Card Levels contain a graphic representation of the selected port’s
ATM and physical layers.
In the Port and Card Level, you can:
•
View, add and update Network port configuration parameters for the logical
and physical layers
•
View, add and update User port configuration parameters for the logical and
physical layers
•
View and set performance monitoring
•
View and update loopback tests
•
View the traffic in a port.
To access the Port Level:
•
Click on the port.
A light blue frame surrounds a selected port.
At the Port Level, you can do the following:
•
View and set hardware and software parameters of a port
•
Display and set time slot assignments
•
View the current or last 24-hour statistical information
•
View, start and stop diagnostic tests in the selected port
•
View statistical information for external ports.
RADview-HP OpenView polls WAN agents in focus at a factory-set poll interval of
60 seconds, which is sufficient for most applications. If for whatever reason, you
wish to change this poll interval temporarily or permanently, perform one of the
following procedures.
The Port and Card Levels
5-3
Chapter 5 RADview-HPOV for ATM
RADview-HPOV/ATM User’s Manual
To set the poll interval temporarily:
1.
Verify which shell your workstation is operating in (bin/sh, bin/zsh, bin/csh or
bin/tcsh).
If your workstation operates in bin/csh or bin/tcsh:
2.
Exit HP OpenView.
3.
Enter the following command: setenv NG164_WAN_POLL_INTERVAL [no. of
seconds]
4.
Press Enter and type ovw& to return to HP OpenView.
If your workstation operates in bin/sh or bin/zsh:
5.
Type the following command:
MNG164_WAN_POLL_INTERVAL=[no.
of seconds]; export MNG164_WAN_POLL_INTERVAL
6.
Press Enter and type ovw& to return to HP OpenView.
To set the poll interval permanently:
1.
Verify which shell your workstation is operating in (bin/sh, bin/zsh, bin/csh or
bin/tcsh).
If your workstation operates in bin/csh or bin/tcsh:
2.
Edit the .login file in the user home directory.
3.
Type the following command: setenv MNG164_WAN_POLL_INTERVAL [no.
of seconds]
4.
Save the file.
5.
Log out and log in again.
If your workstation operates in bin/sh or bin/zsh:
5-4
6.
Edit the .profile file in the user home directory.
7.
Type the following command: MNG164_WAN_POLL_INTERVAL=[no. of
seconds]; export MNG164_WAN_POLL_INTERVAL
8.
Save the file.
9.
Log out and log in again.
The Port and Card Levels
RADview-HPOV/ATM User’s Manual
5.4
Chapter 5 RADview-HPOV for ATM
Communication With the Agent
If the network management station is communicating with the agent, complete
management functionality is available. The current Agent View of the device
appears, and all dialog boxes contain updated information. The title bar of the
Agent View displays the agent name followed by ‘Connected’.
If there is no communication with the agent, the Agent View that appeared the last
time that you closed RADview-HPOV appears. All the dialog boxes are empty and
only the Close and Cancel buttons are available.
If there was no previous communication with the device, the default configuration
is:
For ACE-101:
Network Port
SONET with card type CX/BNC/155
User Port
E3/T3
For ACE-2002/2002E/202:
Slot 1
E3
Slot 2
CX/BNC/155
Slot 3 and 4
Empty
Two AC power supply units
When communication with the agent resumes, complete management
functionality is available. The current Agent View of the device appears, and all
dialog boxes contain updated information. The title bar of the Agent View displays
the agent name followed by ‘Connected’.
5.5
Traps Monitoring
RADview-HPOV polls the agent every 60 seconds to monitor the performance of
the agent. The agent sends traps (for example, alarms and events) to the Network
Management Station.
A trap is sent (if enabled) when a problem starts or ends. Each trap can be
independently masked/enabled per manager. The Alarm trap is regarded as a
group of traps that can be enabled or disabled per manager as a whole.
Traps Monitoring
5-5
RADview-HPOV/ATM User’s Manual
Chapter 5 RADview-HPOV for ATM
5.6
LED Indications
RADview-HPOV displays LED indications in real-time as they actually appear on
the ATM device. The LED indications describe communication and operation
status of the ATM device.
The agent sends a trap if there is a change in a LED’s status.
Table 5-1 shows the LED indicators of the ACE products and describes their
functionality.
Table 5-1. ACE LED Indicators
Name
On
Off
PS1
PS1 works normally (green)
PS1 failure (red)
Blinking
Not installed (gray)
PS2 (for ACE-101
and ACE-2002 only)
PS2 works normally (green)
RDY
Self-test ended successfully
(green)
During self-test (red)
SYNC
Port synchronized (no
alarm) (green On)
Active local alarm (green Active remote alarm (green)
Off)
ATM
No ATM HEC errors (green)
(green Off)
ALM
Alarm is present
(red/orange)
No alarms present
(red/orange Off)
Link (for ACE-101
and ACE-2002 only)
Port is connected to a live
Ethernet network (green)
Disconnected from
network (green Off)
FDX (for ACE-101
and ACE-2002 only)
Working in full duplex
mode (green)
Working in half duplex
mode (green Off)
100M (for ACE-101
and ACE-2002 only)
Working in 100 Mbps rate
(green)
Working in 10 Mbps
rate (green Off)
Note
5-6
PS2 failure (red)
Not installed (gray)
The ACT LED is not managed.
LED Indications
Self-test failed (green)
ATM HEC errors occurred
(green)
RADview-HPOV/ATM User’s Manual
5.7
Chapter 5 RADview-HPOV for ATM
VPI/VCI Range for ACE-101
The Virtual Path/Virtual Channel Indicator (VPI/VCI) range determines the number
of bits used in the VP/VC indicator.
The VP/VC range determines the number of VPCs or VCCs available.
VPI 0-15 are allocated for VCCs and other VPIs are allocated for VPCs.
The range of the VPI and VCI bits respectively is determined by the variables:
VPI Bits: atmInterfaceMaxActiveVpiBits (5, 6, 7, 8)
if atmConfAtmIfVpiVciLimit = bits 15(2):
VCI Bits atmInterfaceMaxActiveVciBits (7, 8, 9, 10)
if atmConfAtmIfVpiVciLimit = bits 17(3)
VCI Bits
atmInterfaceMaxActiveVciBits (9, 10, 11, 12)
Table 5-2. VPC Ranges
VP bits
VC bits
VPI Range
VCs Passing through
VPCs
Maximum number of
VPCs available
10
-
0-255
All
256
8
7
0-239
0-127
240
7
8
0-127
0-255
128
6
9
0-63
0-511
64
5
10
0-31
0-1023
32
Table 5-3. VCC Ranges
VP bits
VC bits
VPI Range
VCI Range
Maximum number of
VCCs available
10
-
8
7
0-255
0-127
48
7
8
0-127
0-255
256
6
9
0-63
0-511
256
5
10
0-31
0-1023
256
When the user sets the VPI bit and VCI bit values, the VP and VC ranges in all the
dialog boxes are affected as follows:
VPI
0…(2**(atmInterfaceMaxActiveVpiBits) - 1)
VCI
0…(2**(atmInterfaceMaxActiveVciBits) - 1)
VPI/VCI Range for ACE-101
5-7
Chapter 5 RADview-HPOV for ATM
5.8
RADview-HPOV/ATM User’s Manual
VPI/VCI Range for ACE-2002/2002E/202
The range of the VPI and VCI bits respectively is determined per port by the
variables:
VPI Bits
atmInterfaceMaxActiveVpiBits
VCI Bits
atmInterfaceMaxActiveVciBits
VCI is 16 bits, i.e. the entire VCI range is supported (216-1).
VPI is 8/12 (UNI or NNI) all VPI values are supported according to the UNI/NNI
setting (28-1 or 212-1). NNI might be 10/12 according to IMA cards. This parameter
is configured in the ATM Parameters dialog box.
In all controls (These are mostly edit-boxes) where the user can insert a VPI or a
VCI value, the NMS limits the user’s input to the following range:
Notes
5-8
VPI
0...(2**(atmInterfaceCurrentMaxActiveVpiBits) - 1) = 0...255/0...4095.
VCI
0...(2**(atmInterfaceCurrentMaxActiveVciBits) - 1) = 1...65535.
•
•
•
•
VPI = any value.
VCI = 0/3/4 – can't be opened by the user (0,3 is used for OAM).
In some cases VCI=16 is also forbidden.
RAD recommends using VCI > 32.
VPI/VCI Range for ACE-2002/2002E/202
Appendix A
RADview User's Environment
A.1 Setting Up the RADview User’s Environment
In order for RADview-HPOV to operate, it is mandatory to include several
variables in the user environment. RAD recommends that you add the HPOV
NNM /bin directory (/opt/OV/bin) to the user’s path. (This should be done for
every user that you have defined.)
To set up the RADview User’s Environment:
1.
Type: /opt/MNG/MNGVIEWHP/bin/mng164_setenv.sh
2.
By right clicking go to Applications > Text Editor
3.
Under File > Open, enter: .cshrc
4.
Click <OK>.
5.
Add the following lines to the end of the file:
#HPOV environment variables
set path = ( $path /opt/OV/bin )
#Informix environment variables
if ( -f <INFORMIXDIR>/.mng164_inf.csh ) then
source <INFORMIXDIR>/.mng164_inf.csh
endif
6.
Note
Press <Enter>.
In the above lines, replace <INFORMIXDIR> with the Informix installation
directory, for example /export/home/informix.
Figure A-1. Text Editor - .cshrc
7.
Save and exit the .cshrc file.
8.
Log out and log in to activate the new user environment.
Setting Up the RADview User’s Environment
A-1
RADview-HPOV/ATM User’s Manual
Appendix A RADview User's Environment
A.2 Testing the User Environment
Run the commands in Table A-1 to verify that the user environment is set correctly.
Table A-1. Setting the User Environment
1
Environment Test
Result
Note
To check Informix
installation directory,
type:
informix:x:101:100::<I
NF_HOME>:/bin/sh
Example
cat /etc/passwd |
grep informix
2
To verify INFORMIX
installation Directory,
Server, and SQL Hosts
file are defined, type:
If the Informix installation directory is:
/opt/informix then:
informix:x:101:100::/opt/inform
ix:/bin/sh
INFORMIXDIR=<INF_HOME>
Example
INFORMIXSERVER=mng164
If the Informix installation directory is:
/opt/informix then:
INFORMIXSQLHOSTS=<INF_
HOME>/etc/sqlhosts
env | grep INF
INFORMIXDIR=/opt/informix
INFORMIXSQLHOSTS=/opt/informix/
etc/sqlhosts
Else
Verify RADview user's .cshrc file was edited
correctly, and log-out / log-in performed
(see step #3).
3
To verify ODBC
installation and home
directories are defined,
type:
ODBCDIR=<INF_HOME>/
odbc
ODBCHOME=<INF_HOME>/
cli/cli
Example
If the Informix installation directory is:
/opt/informix then:
ODBCDIR=/opt/informix/odbc
env | grep ODBC
ODBCHOME=/opt/informix /cli/cli
Else
Verify RADview user's .cshrc file was edited
correctly, and log-out / log-in performed
(see step #3).
4
To verify
MNG164_APP_PATH
(RADview HPOV's home
directory) is defined,
type:
/opt/MNG/MNGVIEWHP
echo
$MNG164_APP_PATH
A-2
Testing the User Environment
Else
Verify the mng164_setenv.sh script was
executed by the RADview user, and log-out
/ log-in performed.
RADview-HPOV/ATM User’s Manual
Appendix A RADview User's Environment
Table A-1. Setting the User Environment (Cont.)
5
Environment Test
Result
Note
To verify the LD-LIBRARY_PATH
variable exists and points to the
Informix installation directory,
type:
LD_LIBRARY_PATH=/opt/in
formix/odbc/lib:/opt/in
formix/odbc/drivers:/us
r/lib:/opt/informix/odb
c/lib:/opt/informix/odb
c/drivers:/usr/lib:
Example
env | grep LD_LIB
/opt/informix/odbc/lib:
/opt/informix/odbc/driv
ers:/usr/lib:/opt/OV/li
b:/opt/informix/cli/lib
:/opt/informix/cli/lib/
esql:/opt/informix/cli/
cli/dlls::/opt/OV/lib::
/opt/informix/cli/lib:/
opt/
6
To verify the CDE Language
variable is set to the right, type:
echo
8
onstat –
9
To verify the RADview-HPOV
user's home directory includes a
.odnb.ini file, pointing to an
ODBC driver located under the
Informix installation directory,
type:
Verify the mng164_setenv.sh script
was executed by the RADview
user, and log-out / log-in
performed.
Else
/bin/csh
Change user shell to csh via
admintool
$SHELL
To verify Informix Database is
On-Line, type:
Else
Modify the CDE language as
follows: In the CDE login dialog
choose options > language > c to
en_GB.ISO8859-15 > c-posix
(see Figure A-2 for Solaris 8 )
To verify the RADview-HPOV
user's Shell is csh, type:
LD_LIBRARY_PATH=/opt/inf
ormix/odbc/lib=/opt/info
rmix
/odbc/drivers:/usr/lib
Else
C
echo $LANG
7
If the Informix installation
directory is: /opt/informix then:
INFORMIX-OnLine Version
7.20.UC2
-- On-Line - Up 11 days 22:33:56 - 12272 Kbytes
Driver=<INF_HOME>/odbc/
drivers/vsifmx7.so.1
Else
Unless Informix is reported to be
On-Line, Database is down.
Replace <USER_HOME_DIR>,
with the RADview-HPOV user’s
home directory.
cat
/<USER_HOME_DIR>/.odbc.
ini|grep vsifmx7.so.1
Testing the User Environment
A-3
Appendix A RADview User's Environment
RADview-HPOV/ATM User’s Manual
In case the above recommendations 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 RADview users .dtprofile and .cshrc files.
Figure A-2. Correcting the Informix LANG variable (Solaris 8)
A-4
Testing the User Environment
24 Raoul Wallenberg St., Tel Aviv 69719, Israel
Tel: +972-3-6458181, Fax: +972-3-6483331, +972-3-6498250
E-mail: erika_y@rad.co.il , Web site: 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!
RADview-HPOV/ATM
Manual Name: ______________________________________________________________
357-250-02/04
Publication Number: __________________________________________________________
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?
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
Error Report
Type of Error(s)
Incompatibility with product
or Problem(s):
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: _____________________________________________________________________
www.rad.com
INTERNATIONAL HEADQUARTERS:
24 Raoul Wallenberg Street, Tel Aviv 69719, Israel, Tel: 972-3-6458181
Fax: 972-3-6498250, 972-3-6474436, Email: rad@rad.co.il
U.S. HEADQUARTERS:
900 Corporate Drive, Mahwah, N.J. 07430, Tel: (201) 529-1100
Toll Free: 1-800-444-7234, Fax: (201) 529-5777, Email: market@radusa.com
Publication No. 357-250-02/04