RADview (Windows) 4.0
RADview (Windows) 4.0
RADview (Windows)
Carrier-Class Network Management System
Version 4.0
RADview (Windows)
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
(Windows) 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 (Windows). 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 (Windows), based on or derived in any way from the RADview (Windows). Your
undertaking in this paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the RADview (Windows) 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 (Windows) and all copies and portions thereof.
For further information contact RAD at the address below or contact your local distributor.
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
(Windows) shall not exceed the sum paid to RAD for the purchase of the RADview (Windows). In
no event shall RAD be liable for any indirect, incidental, consequential, special or exemplary
damages or lost profits, even if RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Foreword
RADview, RAD’s network management software is a portfolio of integrated software suites that
allows management of heterogeneous networks from a single console. The PC and Unix-based
solutions are Client-Server based systems that include “System” software application that’s
integrated with several “Agent” applications that enable management of individual elements
within the network.
RADview (Windows) is a PC-based Element Management System (EMS) providing configuration,
fault and performance management over SNMP. The modular Element Management System
(EMS) implements the first three layers of the industry standard TMN model:
• Network element layer
• Element management layer
Glossary
Cell The 53-byte basic information unit within an ATM network. The
user traffic is segmented into cells at the source and reassembled
at the destination. An ATM cell consists of a 5-byte ATM header
and a 48-byte ATM payload, which contains the user data.
EMS Server The application that manages client devices and provides RADview
system functions.
Ethernet A local area network (LAN) technology which has extended into
the wide area networks. Ethernet operates at many speeds,
including data rates of 10 Mbps (Ethernet), 100 Mbps (Fast
Ethernet), 1,000 Mbps (Gigabit Ethernet), 10 Gbps, 40 Gbps, and
100 Gbps.
Latency The time between initiating a request for data and the beginning
of the actual data transfer. Network latency is the delay
introduced when a packet is momentarily stored, analyzed and
then forwarded.
Load Balancing A technique that distributes network traffic along parallel paths in
order to maximize the available network bandwidth while providing
redundancy.
Network Element A manageable logical entity that represents a physical device. This
allows distributed devices to be managed by a network
management system.
Parameters Parameters are often called arguments, and the two words are
used interchangeably. However, some computer languages such as
C define argument to mean actual parameter (i.e., the value), and
parameter to mean formal parameter. In RAD CLI, parameter
means formal parameter, not value.
Routing The process of selecting the most efficient circuit path for a
message.
Shelf View Network Element (NE) management application for managing and
monitoring node configuration (formerly referred to as zoom)
Note Make sure to install an ENW license with a sufficient number of points installed
for the number and nature of devices being added. For further information, refer
to Chapter 2 of the RADview System manual.
1. Installing Licenses
Use the License Service Manager to add the required licenses as listed below..
2. Operation
This section provides an overview on how to log on and populate the topology
map with levels and network elements.
The instructions below assume that the topology map is empty and no levels
have been added to the root level.
To log on to RADview:
1. Navigate to
All Programs > Network Manager > RADview > Network Manager.
The Logon prompt appears.
2. Log on using the default user name and password. The default user name
and the default password are both root.
The RADview Network Manager window appears displaying the Topology
view. The map is empty when logging in for the first time after installing.
To add levels:
3. Right-click the root level in the Network Element Repository (/) and select
New Level from the shortcut menu.
The New Level dialog box appears.
4. Under Level Name, assign a name to the level and click <OK>.
The new level is added with default settings.
5. To modify parameters such as SNMP settings for the entire level, refer to
Working with Levels in Chapter 3 of the RADview System User Manual.
Note • Clouds are only relevant if RADview is run with RADview-Service Manager
• For additional information on adding a cloud if RADview-Service Center is
installed, refer to Chapter 3 of the System User’s Manual for Unix or Windows.
2 Operation RADview
User's Manual Quick Start Guide
To search and automatically add devices according to rules using Zero Touch:
Note Device names must have the group name as part of the file name. For example, if
the name of devices is <IP address> and the desired group name is Group1, the
relevant devices must be renamed to Group1-<IP address>.
3. Rename the relevant devices across all levels from <Name> to <Group1>-
<Name>.
4. Under Groups, Right-click the respective group.
RADview Operation 3
Quick Start Guide User's Manual
8. Select Delete from the shortcut menu to delete the respective network
element..
To remove levels:
9. Remove all network elements from the desired levels.
10. Select Delete from the shortcut menu to delete the respective level.
3. Configuration Management
To define SNMPv3 defaults for a level and its sublevels in the NER:
1. Right-click the desired level of the NER or on the desired tab of the
respective level of the map and select Properties from the shortcut menu.
The Level Properties dialog box appears.
2. To modify the SNMP parameters, refer to Configuring Level Properties in
Chapter 3.
4. Security Management
This section explains how to manage basic security settings such as users,
passwords, permissions etc. For additional information, refer to Security
Management (Chapter 6). Security settings are available in the Security
Administrator.
Managing Users
To open the Security Administrator:
1. From the RADview Manager menu, select Tools > Admin Console .
The Admin Console appears.
2. In the Admin Console’s navigation pane, select Security Service.
The Profiles tree appears with existing security profiles and users.
To add users:
1. From the menu, select User > Add...
The Add User dialog box is displayed.
2. Under User Name and Description, enter the desired user name and a
description (optional) respectively.
3. To base the new user on a security profile, select Profile and select the
desired user profile.
RADview i
Table of Contents User's Manual
Chapter 3. Operation
3.1 Running RADview ............................................................................................................... 3-1
Logging Into RADview ...................................................................................................... 3-1
Logging Out of RADview................................................................................................... 3-3
3.2 Using the RADview GUI ....................................................................................................... 3-3
The RADview GUI.............................................................................................................. 3-4
Customizing the RADview View ......................................................................................... 3-5
Customizing the Windows ............................................................................................ 3-5
Setting the Preferences ............................................................................................... 3-8
Customizing Tables .................................................................................................... 3-13
Customizing Displayed Fields ..................................................................................... 3-18
Sorting the Displayed Table ....................................................................................... 3-19
Customizing Views ..................................................................................................... 3-23
Searching Table Data ................................................................................................. 3-24
Filtering Table Data ................................................................................................... 3-26
Exporting the Table Data ........................................................................................... 3-38
Working with Topology................................................................................................... 3-38
Searching in Topology Panes ..................................................................................... 3-39
Working with the Map ............................................................................................... 3-41
Working with Levels................................................................................................... 3-48
Working with Network Elements ................................................................................ 3-61
Working with Links .................................................................................................... 3-87
Working with Groups ................................................................................................. 3-90
Working with the Jobs GUI .............................................................................................. 3-93
Working with the Jobs Table ...................................................................................... 3-94
Working with the Job Toolbar ..................................................................................... 3-96
Working with Wizards..................................................................................................... 3-97
Jobs........................................................................................................................... 3-98
Zero Touch .............................................................................................................. 3-100
Maintenance Windows ............................................................................................. 3-101
Service Catalogs and Services .................................................................................. 3-102
3.3 Working with Utilities ..................................................................................................... 3-102
3.4 Accessing Devices for Configuration ............................................................................... 3-103
Using the Shelf View .................................................................................................... 3-103
Edit and Agent Configurations ................................................................................. 3-108
Device Level ............................................................................................................ 3-109
Card Level ............................................................................................................... 3-110
Port Level ................................................................................................................ 3-112
Using the Web Browser ................................................................................................ 3-113
Using Telnet/PuTTY ...................................................................................................... 3-115
ii RADview
User's Manual Table of Contents
RADview iii
Table of Contents User's Manual
iv RADview
User's Manual Table of Contents
RADview v
Table of Contents User's Manual
vi RADview
User's Manual Table of Contents
RADview vii
Table of Contents User's Manual
viii RADview
Chapter 1
Introduction
1.1 Overview
RADview is a Windows-based modular, client-server, scalable management
system that can be used in a distributed network topology or a single-station
configuration. RADview consists of the system and the following optional
modules:
• Service Manager (SM) – end-to-end Carrier Ethernet service provisioning for
Ethernet Access products. This module includes the Service Center (SC)
module, which is an end-to-end Carrier Ethernet and TDM service provisioning
for AXCESS+ products.
• Performance Monitor (PM) – Portal for service SLA monitoring for both
carriers and their customers.
The RADview element and network management systems include a CORBA
northbound interface, enabling easy integration into the customer’s umbrella
NMS. CORBA enables interconnectivity and communication across heterogeneous
operating systems and telecommunications networks. CORBA effectively supplies
a software interface that defines data models used between various
management layers. It supports multi-vendor distributed network management
applications, providing the data interface between clients and servers.
The system is bundled with agent components, each dedicated to controlling a
specific RAD product on the network. For a list of currently supported RAD
products, refer to Managed Products.
Management Modules
This section introduces and explains the RADview modules.
System
The RADview system contains the element management system (EMS/NMS)
system with FCAPS (Fault, Configuration, Administration, Performance and
Security) capabilities and provides an intuitive graphical user interface for
discovery, management and monitoring of the network elements.
Service Manager
The Service Manager module is designed to minimize the effort of a multi-service
Carrier Ethernet network management. RADview-Service Manager enables easy
point-and-click E-Line and ELAN Ethernet service creation, monitoring and SLA
assurance for networks based on RAD Ethernet Access product family. For
additional information, refer to Section 1 of the RADview-Service Manager
manual section.
Service Center
As part of the Service Manager module, Service Center extends Service Manager
capabilities to the AXCESS+ product family, such as the Megaplex-4 product line
and to PDH and SDH/SONET networks for providing TDM-based services in
addition to E-Line Ethernet services.
Note Service Center supports MP-2 and MP-4 with ASMi-52/53/54 and OP-108, as well
as the FCD family.
Performance Monitor
The Performance Monitoring portal is an SLA assurance monitoring system. This
system enables long term monitoring of Ethernet service performance by
collecting KPI (key performance indicators) data from RAD devices. Measured
metrics are based on ITU-T Y.1731 and include Frame Delay, Delay Variation,
Frame Loss, and Availability. Latency and jitter results are based on round-trip
measurements. It allows service providers to easily evaluate actual performance
over time and compare it to their committed SLA agreements. In addition, it
enables immediate detection of service degradation, so that action can be taken
to quickly restore committed performance levels to the end customer.
Features
RADview includes the following features:
• Supports inband and out-of-band management
• Presents networks and their components in an easy-to-view graphical map
format. Maps can be grouped according to hierarchies and their sublevels.
User-defined graphics can be included.
• “Learns” the network by automatically discovering SNMP-manageable
elements
• Polls nodes at periodic intervals or on user command, and relays the results
of the polls by a combination of messages, color codes, log files, and other
action.
• Allows exporting and printing information from selected screens
• Gathers real-time statistics that can be displayed in line graph, bar chart, or
tabular format
• Allows for security control at the lobe and segment levels
• Supports basic management of third-party equipment
• Supports security protocols
• Allows creating sound profiles for events and event groups.
Service Applications
RADview includes utilities that improve system performance and simplify its
maintenance:
• Backup and Restore – Back up and restore RADview system components
• License Manager – Manage RADview licenses
• Net Inventory – Display inventory table of RADview agents
• SNMPv3 Manager – Manage SNMPv3 parameters of RAD devices that support
SNMPv3.
• Zero Touch – Automatically add network elements and upload software and
configurations according to user-defined rules.
Managed Products
RADview provides network management for the products shown in the following
table. The information shown in the table applies to the latest product version
released for general availability (GA).
Devices that support RADOS Generic Agent also support trap synchronization
explained under Configuring Trap Synchronization in Chapter 3. These devices
reflect the device status with respect to alarms and their respective coloring and
symbols on the map, in the Resources table and the Network Element Repository.
For a table that reflects the device status accordingly, refer to Monitoring Agents
in Chapter 5.
Note The agent manuals of ETX-1002 can be found in the User Manual folder on the
RADview DVD, as it does not have a shelf view from where you could access it.
1.3 Requirements
Note If you install RADview-Service Center, you have to install the server on Unix and
the RADview and RADview-Service Center clients on a PC.
The RADview package can be installed with various Windows operating systems
as outlined under Software Requirements.
Hardware Requirements
Requirements for CPU, RAM and hard disk resources depend on the number of
managed elements in the system as outlined in the table below.
This section also outlines required hard disk resources for sample collection using
RADview-Performance Manager.
Notes
• Operating RADview together with RADview-Service Manager and/or RADview-
Performance Manager also requires a minimum of 8GB for installations of 500
managed elements or less.
• Each simultaneous user working on the server via any remote desktop client
technology requires an additional 512 MB RAM and 1 CPU core
• If installing more than 10 clients, consult your RAD distributor for the required
hardware configuration.
• When running the RADview client on a different workstation than the RADview
server, it is not necessary to add RAM or CPU for simultaneous users.
Notes • Additional disk space may be required when using the Jobs utility to collect
statistics for the RADview Performance Portal, according to the amount of
data collected and saved in the system.
• It is recommended to work with a 19-inch or larger monitor.
Table 1-2. Hard Disk Requirements for Performance Monitoring – 12-Month Period
*
Scope Servic Flows per OAM, CoS Ports Sample Rate of Required Hard
es Service per Service Collection / [Min] Disk Space / [GB]
Full 10 4 (2 flows 1 6 5 1
[TX & RX]
per device)
Full 10 4 (2 flows 1 6 1 2
[TX & RX]
per device)
Ports 0 0 0 6 5 0.63
throughput
only
* PM Data of one service, assuming that raw samples are saved for 12 months
Virtual Machines
In addition to physical stations, RADview systems can be installed on virtual
machines. The RADview and database requirements for virtual machines are the
same as for physical stations.
Note The virtual machine’s infrastructure consumes memory and disk space of its own,
which must be taken into account when dimensioning the server.
Software Requirements
Before starting the RADview installation and setup, the following software
components must be installed and working:
• One of the following Windows operating systems:
Microsoft Windows 7 or Windows 8.x (64-bit) Professional Edition, with
English Multilingual User Interface (MUI)
Microsoft Windows Server 2008 R2 or Windows Server 2012 R2 (64-bit)
Standard Edition, with English Multilingual User Interface (MUI)
• Microsoft Windows display font size set to normal (96 dpi)
• Microsoft Windows default input language set to English;
• Microsoft Windows SNMP trap service, configured to run automatically (only if
installing Airmux or LRS-24 devices)
• Microsoft .NET Framework version 4.0 (required only if installing Airmux
devices; an installation file for .NET Framework version 4.0 is included on the
RADview installation DVD)
• In addition, the Oracle database requires .NET Framework version 3.5 be
installed prior to its installation under Microsoft Windows 8/8.1 and Windows
Server 2012.
• Oracle 11g (Version 11.2.0.2 64-bit) for Microsoft Windows 7 (64-bit) or
Server 2008 Server
• Mozilla Firefox, latest version (required for Web-based access to devices)
• Adobe Reader, latest version (required for opening help files)
• TFTP/SFTP server for running jobs (if you wish to collect OAM statistics, you
must install a TFTP server).
Note • It is recommended to use a TFTP server with support for a large number of
concurrent sessions. See Table 1-3 for recommended SFTP/TFTP servers that
work optimally with RADview.
• If you run the Zero-Touch functionality, the WinAgents (enterprise) TFTP
server is required.
• Software upload and download to and from ETX-5 require an SFTP server.
• Google Chrome web browser if you wish to work with the RADview
Performance Portal. You must be connected to the Internet in order to view
the graphs.
TFTP SFTP
* SolarWinds SolarWinds
0–1000 network elements, with PM
* WinAgents (standard) Cerberus
1001–5000 network elements, with PM
* WinAgents (enterprise) Cerberus
More than 5000 network elements, with PM
* SolarWinds SolarWinds
0–1000 network elements, without PM
Server-Client Combinations
RADview servers can run on Windows, Unix and Linux operating systems as
specified under Software Requirements and support clients across platforms as
outlined below.
Note Servers and clients must be of the same version and build, otherwise the attempt
of opening a client results in an error message indicating a version mismatch.
Windows Client √ √ √
Unix Client √ √
Note • The Windows station on which you install must be actively connected to the
hub/IP network throughout the entire installation process.
• This version of RADview supports Windows 8 and Windows Server 2012. The
procedures for pre-installation steps, installing the database, installing
RADview and post-installation steps are identical unless noted otherwise.
• Before you start installing, make sure that no antivirus, antispyware or firewall
application blocks Oracle or RADview applications.
• Installation guide.
2.2 Installation
If you are installing RADview-Service Center or RV-SC/TDMOIP on top of RADview,
the installation order is:
1. RADview
2. RADview-Service Center and/or RV-SC/TDMOIP.
Network
OSS
Network
RADview
Server
Network
RADview
Client
*Optional
*Optional
Telnet* 23 (TCP)
SSH* 22 (TCP)
HTTP* 80 (TCP)
*Optional
TFTP 69 (UDP)
SFTP 22 (TCP)
Telnet* 23 (TCP)
SSH* 22 (TCP)
HTTP* 80 (TCP)
*Optional
**For devices with Legacy Shelf View
In case you are using a DMZ configuration, you have to open the ports of
RADview components and the DMZ station in addition to the ports listed in the
tables associated with Figure 2-1.
A DMZ (De-Militarized Zone) configuration enables end users outside the firewall
to view the performance monitoring (PM) portal.
Note DMZ configurations are not standard and are implemented only upon request.
-
NTU NTU
Network
OSS
Network
RADview
Server
Network
Protocol Port
HTTP 80
HTTPS 443
1. If you use Windows 8.1 and you are in the Desktop view, click to toggle
to the Start (tile) view.
Note This button does not exist for Windows 8.0, which only operates from the Start
(tile) view.
3. Navigate to and click Control Panel (located to the right under Windows
Systems).
The All Control Panel Items dialog box appears.
To access the Action Center in Windows 7 and Windows Server 2008 R2:
2. From the Start menu, open the Control Panel.
The Control Panel appears (Figure 2-5).
Figure 2-8. Windows 7 System and Security – User Account Control Settings
Notes • In some cases, corporate policies regarding power plans may apply. Before
creating a power plan and installing RADview, it is recommended to verify with
the local IT department that changes to existing power plans and new power
plans are persistent.
• The instructions below apply to all supported Windows operating systems,
although they illustrate dialog boxes using Windows 7.
3. Create a new power plan. To do so, click Create a Power Plan in the
Navigation pane.
4. The Create Power Plan dialog box appears (see Figure 2-11).
5. Assign a name to your new power plan, for example RV-EMS and select High
Performance.
6. Click <Next>.
You are asked to change settings for the plan (see Figure 2-12).
7. Set Turn Off the Display and Put the Computer to sleep to Never and then
click <Create> as illustrated in Figure 2-12.
The new power plan is added to the list of preferred plans and selected
as illustrated in Figure 2-13.
3. Under Format, select English (United States) and select the options illustrated
below for Short Date, Long Date, Short Time and Long Time as illustrated in
Figure 2-14.
For First Day of Week, select the first business day of the week in your
region.
4. Click <Apply>.
The changes are applied to the current user and the Region or Region
and Language dialog box remains open respectively.
You have to copy these settings now to all system and user accounts.
Figure 2-15. Windows 7 – Copying Settings to all New User and System Accounts
Note When installing the Oracle database under Windows 8/8.1 or Windows Server
2012, Microsoft .NET Framework version 3.5 must be installed and enabled prior
to installing the Oracle database. The installation for Microsoft .NET Framework
version 3.5 is available on the RADview installation DVD.
Before installing Oracle the first time, some adjustments of the computer settings
may be needed. If this has already been done or is not necessary, refer to
Installing Oracle for the procedure to install the Oracle database.
The adjustments depend on the computer IP address setting:
• Static IP address – The computer is assigned a specific IP address. No
adjustment is necessary in this case.
• Multiple IP addresses – The computer is assigned multiple specific IP
addresses. No adjustment is necessary in this case.
• DHCP – The computer IP address is obtained from a DHCP server, and can
vary. In this case, it is necessary to do the following, in order to provide a
fixed IP address for Oracle:
Install a virtual network adapter (Microsoft Loopback Adapter), assign it
an IP address, and set it to be the primary network adapter – see
Installing Virtual Network Adapter
Enter the IP address in the hosts file – see Editing the Hosts File.
• Non-network – The computer does not have a network adapter, or the
network adapter has not been configured for use. In this case, it is necessary
to make the same adjustments as described above for the DHCP case.
3. Right-click the computer name at the top, and select Add legacy hardware
from the shortcut menu.
Notes • The Add Hardware wizard is identical for all supported Windows platforms,
although illustrated for Windows 7 in this example.
• Available options visible in the illustrations vary from PC to PC, depending on
their respective configurations.
4. Click <Next>.
5. Select Install the hardware that I manually select from a list (Advanced), and
click <Next>.
A list of hardware types is displayed.
8. Click <Next>.
The adapter is installed, and when the installation is completed, the
following is displayed:
4. Select Use the following IP address and do the following (see Figure 2-27 for
an example):
a. In IP address, enter a non-routable IP address that is not used in your
network. Oracle recommends using one of the following non-routable IP
addresses:
192.168.x.y
(x = 0–255; y = 1–254)
10.10.10.x
(x = 1–254; recommended value is 10).
Note Be sure to verify that the IP address does not conflict with IP addresses being
used in your network.
Note If the Advanced entry is not visible in the Network Connections dialog box, type
<ALT>+n to access it.
2. In the Adapters and Bindings tab, verify that the network connection
corresponding to the Microsoft Loopback Adaptor is on the top of the
Connections list. If it is not on top, use the arrows on the side of the dialog
box to move it to the top.
Note It is necessary to view the computer system information to obtain the ‘computer
name’ and the ‘full computer name’ as explained below.
3. Write down the Computer name and the Full computer name (highlighted
yellow).
4. Navigate to <system-drive>:\Windows\System32\drivers\etc\ and open the
hosts file in an editor.
To edit the hosts file with the IP address for the Microsoft Loop Adaptor:
• In the hosts file, add the following line after the localhost line:
<IP-address> <Full-computer-name> <Computer-name> ORACLE_LOOPBACK
<IP-address> – Use the IP address assigned to the Microsoft Loopback
Adapter in Installing Virtual Network Adapter
Installing Oracle
Before initiating the Oracle installation, close all running applications.
Notes • If you use an Oracle installation available from a network drive, make sure to
first copy the entire installation to the relevant PC and then install from a local
drive.
• The instructions apply to all supplied Windows platforms, although the screen
images reflect the installation under Windows 7.
• During the installation, you may be asked whether you wish to install a Java
Virtual Machine (JVM) that overwrites files in a certain folder. In this case, you
have to click <Yes> to allow as the Java Virtual Machine is required.
3. Click Folders.
The DVD content appears.
4. Click Setup.
The Oracle installation wizard appears as illustrated in Figure 2-36 (for
Windows 7).
7. Click Setup.exe.
The Oracle installation wizard starts as illustrated below.
Note The instructions apply to all supported Windows platforms, although the screen
images below illustrate the installation under Windows 7.
9. Read the license agreement and select I accept the terms of the license
agreement to indicate that you accept the terms of the license agreement,
then click <Next>.
The Select Installation Type dialog box is displayed.
Note During the installation, the Oracle setup detects previously installed files. If such
files are detected (for example, DLL files), a confirmation message appears,
asking you whether to replace a specific file or all files. It is recommended to
replace all files, by clicking <Yes to All>.
Installing RADview
This section explains how to install. If you already have RADview installed and you
wish to install a newer version, you can upgrade to the newer version by
installing it without uninstalling your existing version, which preserves your
existing database. For further information, refer to Upgrade.
Notes • To properly manage Gmux and IPmux products, you have to select them in the
Select Products dialog box (Figure 2-56) during the RADview installation.
• For circuit management in Gmux and IPmux products, you must install
RV-SC/TDMOIP after installing RADview.
• If you are installing Airmux or LRS-24 devices, Windows SNMP trap service
must be active. To enable this service, open the Control Panel, navigate to
All Control Panel Items > Administrative Tools > Services.
• If you are installing Airmux products, Microsoft .NET Framework version 4.0
must be installed before you start installing RADview. You can use the
installation file provided in the RADview disk to install it if necessary.
• The service corresponding to the database should be active before starting
installation (OracleServiceMNG164). Normally this service starts automatically
and there is no need to start it manually.
• To perform the installation you must be defined as a “Computer
Administrator” (found in the Control Panel under User Accounts).
• Do not press <Cancel> during the installation.
Note It can take up to a minute for the RADview Setup window to appear. If for some
reason the window does not appear automatically, execute setup.bat from the
DVD directory \EMS\disk1.
Note • You can run the RADview setup from a local hard drive by copying the
contents of the disk1 directory, then executing setup.bat. In this case, the
Welcome dialog box is the first dialog box that appears (refer to the
instructions starting with Figure 2-47).
• Do not run the RADview setup from a network drive.
• The instructions below apply to all supported Windows platforms, although
they are illustrated with Windows 7 screen images.
Note It can take up to a minute for the RADview Setup window to appear. If for some
reason the window does not appear automatically, execute setup.bat from the
DVD directory \EMS\disk1.
To install RADview:
1. In the RADview Setup window click RADview.
The Welcome dialog box is displayed.
2. Click <Next>.
The Select Installation Directory dialog box is displayed.
Note If you choose Typical and this is the first time you are installing RADview, the
Database Settings dialog box is displayed in this case as well.
7. Click <Next>.
The General Information dialog box appears with your station’s system
name displayed.
8. Click <Next>.
The OS international information is loaded and then one of the following
occurs:
If this is an Advanced installation, the International Settings dialog box is
displayed (Figure 2-52).
If this is a Typical installation and this is the first time you are installing
RADview on this station, the Database Settings dialog box is displayed
(Figure 2-54), and you should skip to step 13 of this procedure.
If this is a typical installation and you are performing an upgrade, the
Installation Summary dialog box is displayed (Figure 2-59) and you should
skip to step 18 of this procedure.
9. Select the Language, Country, Time Zone, and First business day of the week
as needed (the default values for the first three are taken from the operating
system).
Notes • Language support for the RADview packages may apply to specific
components and is subject to change from version to version.
• Select the appropriate Time Zone so that the time that is displayed in Current
Time Test matches the correct time in your country and area.
• You can change the first business day of the week after installation, via the
system console (EMS server parameters – Advanced tab).
11. Select Standalone EMS Network Manager with Oracle Database to install
RADview.
12. Click <Next>.
The installation attempts to connect to the Oracle database, and when
the connection is established the Database Settings dialog box is
displayed.
13. Set the option to create new database according to the following:
For first-time installation on this station or if you want to overwrite the
existing database, select the option to create a new database
If you are upgrading and you want to keep the existing database, do not
select the option to create a new database (by default the option to
create a new database is not selected if you are upgrading).
Note If this is not a first-time installation and you create a new database, your map is
deleted along with all network elements.
14. Verify that the values displayed are correct. If you are upgrading RADview,
the displayed user and password should be the ones formerly used for the
database. You must use them to be able to connect to the database.
If you did not select the option to create a new database, the Select
Products dialog box is displayed; skip to step 17.
16. Click <OK> to continue.
The Select Products dialog box is displayed. All products are selected by
default.
Note If there are products that you do not want to install, you can select the
corresponding product group from the list on the left to display a list of products
on the right side of the dialog box, and then clear the products that you do not
want to install. The <All Products> can be clicked to toggle between all products
selected and none selected.
When the condition above was not true or it has been fixed, the
Installation Summary dialog box is displayed, showing the products that
you selected for installation.
Note During the installation, the RADview setup detects any previously installed files
that are used by the EMS system. If such files are detected, a confirmation
message appears, asking you whether to replace a specific file or all files. It is
recommended to replace all files, by clicking Yes to All.
Note The RADview setup disables hibernate and sleep mode upon installation, by
creating and adding the power plan RV-EMS to the computer power options. For
additional information and instructions, refer to Creating a Power Plan for
RADview.
Notes • Verify that your license has enough license points for the additional devices.
For further information, refer to Licensing in Chapter 4.
• If you selected all supported devices by when installing RADview as illustrated
in Figure 2-71, all supported devices are already installed.
Notes • Make sure that client and server belong to the same version of RADview
• Do not run the RADview setup from a network drive.
• You can run the RADview setup from a local hard drive by copying the
contents of the disk1 directory, then executing setup.bat. In this case, the
Welcome dialog box is the first dialog box that appears (refer to the
instructions starting at step 3).
• It can take up to a minute for the RADview Setup window to appear. If for
some reason the window does not appear automatically, execute setup.bat
from the DVD directory \EMS\disk1.
1. Insert the RADview DVD into the CD/DVD drive and follow the instructions
under Installing RADview until the first step of the wizard appears as
illustrated below.
3. Click <Next>.
The Select Installation Directory dialog box is displayed.
Note For a single-station installation, any string of characters without a space can be
used for Zone/Area names.
8. Click <Next>.
The International Settings dialog box is displayed.
9. Select the Language, Country, and Time Zone for your station, and click
<Next>. The default values are taken from the operating system.
Notes • Language support for the RADview packages may apply to specific
components and is subject to change from version to version.
• Select the appropriate Time Zone so that the time that is displayed in Current
Time Test matches the correct time in your country and area.
The Select Products dialog box is displayed. All products are selected by
default.
Note If there are products that you do not want to install, you can select the
corresponding product group from the list on the left to display a list of products
on the right side of the dialog box, and then clear the products that you do not
want to install.
12. When the installation completes, the Installation Complete dialog box is
displayed.
Note Make sure that client and server belong to the same version of RADview. If the
versions do not match, an error message appears and the relevant RADview client
does not run.
Note Language support for the RADview packages may apply to specific components
and is subject to change from version to version.
9. Click <Next>.
The Product Selection dialog box appears.
10. Select the desired products or select All Products to include all products
supported with the current version of RADview and then click <Next>.
The list of selected products appears.
12. When the installation is completed and the Installation Completed dialog box
appears, click <Finish>.
The installation is complete.
3. Under Server IP Address, enter the IP address of the station that hosts the
RADview server with the desired License Server.
4. Make sure that the other settings match the settings on the other side.
If you have to adapt the settings to different settings on the other side,
refer to Table 2-9.
If you have to change settings on the other side to match the settings on
your client side, refer to Configuring Access to a License Server.
Table 2-9. Client Side Configuration
Parameter Function
• If you make any changes to the Server Side Configuration, you must restart
Note
the License Server before they can take effect.
• Once you restart the License Service Manager, the license profile defined for
the new License server applies. For additional information on licenses, refer to
Licensing in Chapter 4.
Parameter Function
Installing Licenses
Each RADview license is associated with a single management station. This
station is identified by its IP address/MAC address for Windows-based stations. If
you do not know for which IP address/MAC address to obtain the license, refer to
Frequently Asked Questions in Chapter 7.
If you need a RADview license for your RADview package, you can activate it at
the RAD Value Point website (via MyRAD or the Customer Information
application). You can also add license points at the RAD Value Point website.
Details on using RAD Value Point can be obtained from your local RAD distributor.
Note The Windows station must be connected to the LAN/IP network in order to work
with the license.
Note • Without ENW and EMS-MAP licenses, RADview does not log you on. A message
returns indicating that no sufficient license is installed.
• No EMS-Clients license is required for up to five RADview clients logged on
simultaneously.
To install licenses:
Note You have to install each license separately. You cannot select and install multiple
licenses.
1. Open the License Service Manager by selecting All Programs > Network
Manager > General > License Service Manager.
The License Service Manager dialog box appears.
Figure 2-87. Open License File – With all Possible License Files Except for DXC-100
3. Navigate to the license folder and select the desired license file, and then
click <Save>.
The Open License File dialog box closes and the license is installed.
4. Repeat this procedure for every license file you need to install.
Removing Licenses
If you decide not to use an already-installed license (for example the DXC-100
license) or if you installed a temporary license that has expired, you may wish to
remove the respective license file.
Note If there are no additional valid ENW and/or EMS-MAP licenses installed, you
cannot continue to use management services until another valid license is added.
Note Alternatively, you can enable the Telnet client by typing the following in a
command prompt window:
servermanagercmd –install Telnet-Client
2.3 Upgrade
Earlier versions of RADview installed can be upgraded as explained below.
Notes Verify that your hardware and the installed Windows version are supported. For
additional information, refer to Requirements in Chapter 1.
Note yyMMdd stands for the installation date. If the installation date is the 29/9/2014,
the backup folder is called C:\RV32\ems\utils\backups\pm_140929
Note You can install the new version of RADview over the current one only if the
current one is not more than two versions older than the new version. To
upgrade an older version requires uninstalling RADview, manually deleting the
RV32 folder and then re-installing RADview.
Table 2-11. Supported Backup &Restore Options across Windows Operating Systems
Windows XP √
Windows 7 32-bit √ √ √
Windows 7 64-bit √ √ √
Notes • Newer RADview versions can still be installed on Windows XP and Windows
2003 Server for migration and upgrade procedures, although full support for
new functionalities and options of RADview is not guaranteed.
• Make sure to upgrade all clients that access the upgraded RADview server.
• Make sure to install additional licenses as needed. Refer to Installing Licenses
for further information and instructions.
2.4 Uninstallation
Uninstalling RADview
Notes • If you have other RADview system packages installed on your workstation (e.g.
RV-SC/TDMoIP) and you uninstall RADview then you must also uninstall the
other RADview system packages
• The RADview system packages should be uninstalled in the opposite order in
which they were installed.
• The instructions below apply to all supported Windows platforms, although the
steps are illustrated with Windows 7 dialogs.
To uninstall RADview:
1. Go to the Control Panel as explained above and click Programs and Features.
The list of installed programs appears.
3. Click <Next>.
The RADview system and all its components are uninstalled.
Note If you plan to uninstall Oracle as well, you can postpone the reboot until Oracle is
uninstalled.
To uninstall Oracle:
1. Insert the Oracle database DVD into the CD/DVD drive.
2. Run Setup.exe from the CD.
The Oracle installation wizard starts.
3. Click <Next>.
The License Agreement dialog box is displayed.
4. Read the license agreement and select I accept the terms of the license
agreement to indicate that you accept the terms of the license agreement,
then click <Next>.
The Select Installation Type dialog box is displayed.
Notes • After installing RADview, it is necessary to restart the workstation and wait at
least 2–3 minutes before starting to work with the RADview system. This is
required for the Oracle database to initialize its tables and for the RADview
Server service to start, before using the system for the first time.
• RADview does not operate in an NAT environment.
• If the Low Memory Detected message appears, click <OK> and refer to
Troubleshooting in Chapter 7 for further instructions.
Notes • For the very first login (before users are defined) use the default user:
Username=root, Password=root
• You must install a license for the EMS Map feature to be able to login to
RADview
• If you want to have more than five users logged in to the RADview Network
Manager simultaneously, you must install a license for multiple RADview clients
• The same user can have many open sessions (logged in from different
sessions/terminals, subject to the limit on multiple RADview Network Manager
clients as mentioned above
• You can change your password or another user’s password. Refer to Chapter 6
for instructions.
To start RADview:
• From the Windows Start menu, select
All Programs > Network Manager > RADview > Network Manager.
The RADview Network Manager and login dialog box appear, with the
RADview server name and Logged Out displayed in the lower right
corner of the RADview Network Manager (see Figure 3-1).
Note • If the user name is displayed in yellow instead of green, this indicates there is
a problem with one of the RADview services, which can be viewed via the
system console (see Chapter 4 for details on the RADview services).
• If you did not install the appropriate license or exceed available license points
or the number of clients, you receive an error message. In this case, refer to
Installing Licenses in Chapter 2 for information and instructions on installing
the required license(s).
• If the client and server versions do not match, an error message appears
stating the currently installed client and server versions.
Menu
Work Space
Selection
Work
Space
Navigation
Panes
Task
Auxiliary
Bar
Pane
Note • When logging in for the first time, all devices and levels n the map may appear
superimposed at the same spot. To display them correctly, click Layout
and then select a layout option, for example Orthogonal Layout.
• When logging in again, the work space from where you logged out appears.
For example, if you logged off from your last session after working in the Jobs
work space, the Jobs work space shows when you log in the next time.
Topology map(s). For • Network Element Repository. Displays Event Browser. Events and
additional the managed devices on their alarms of network
information, refer to respective levels, adds single devices elements. For additional
Working with or groups of devices. The network information, refer to
Topology repository tree appears when Chapter 7.
selecting the Topology view
• Groups. Dynamic user groups, for
additional information, refer to
Chapter 6.
Catalog*
Services*
Business Entities*.
Transport*
Note
Work spaces marked with * are relevant for RADview-Service Manager only.
Docking Windows
You can undock each dockable window component so that it becomes a floating
window, and you can redock it, in whatever position is suitable.
Note You can specify dockable windows by selecting Floatable Views in the Look and
Feel parameters in the Preferences dialog boxes (see Table 3-4).
To undock a window:
• On the window title bar, click Toggle floating to change the window to a
floating window.
The window is undocked and becomes a floating window.
1. On the window title bar, click Toggle floating to change the window to a
dockable window.
Or
Right-click the title bar of the window and in the submenu that appears, clear
Floating and select Dockable
Autohiding Windows
You can autohide the windows when it is not necessary to view their contents.
Figure 3-4. RADview Network Manager, Network Element Repository Window Hidden
Figure 3-5. RADview Network Manager, Network Element Repository Window with Autohide Still
Active (Windows)
Parameter Description
Parameter Description
Time Zone
Time Zone Selects the time zone for your RADview installation
Default: The time zone selected during installation
EMS Monitor
Monitor Interval (sec) Specifies time interval for monitoring EMS server status
Parameter Description
Check Security Domain by Name If checked, the device is identified by its node name
Check Security Domain by Net If checked, the device is identified by its IP address
Address
Parameter Description
Parameter Description
Windows Settings
Always on Top If selected, other windows cannot overlap the RADview Network
Manager window; it is always on top of other windows
Rearrangable Views If selected, you can rearrange the position of the panes in the
RADview Network Manager, such as the Network Element
Repository or Groups
Default: cleared
Note: When you change this parameter, you must log out and back
in before the change is applied.
Floatable Views If selected, panes are floatable and dockable (see Docking
Windows for details on docking)
Default: cleared
Note: When you change this parameter, you must log out and back
in before the change is applied.
Note When you change a map parameter, the change is applied only to maps that are
opened after changing the setting; it is not applied to maps that are already
open. To see the change in a map that is open, you must close and reopen the
map.
Parameter Description
Opened Maps –Controls whether more than one map can be opened simultaneously
Multiple If selected, you can open more than one map (each map opens a
new tab in the map pane)
Single If selected, you can open only one map. When you open another
map, the current map is automatically closed.
Duplication Policies
Allow Duplicated Net Addresses If checked, you can create more than one network element with
the same IP address
Parameter Description
Graph Settings
Low Resolution Scale Trigger This specifies the resolution of the map. The higher the number,
the less detail can be seen.
Range of values: 0.1 to 1.0, in increments of 0.1
Default: 0.5
Mouse Zoom Reverse Default: Cleared
Animation Enabled If checked, applying a new layout to a map displays animated
movement of the network elements.
Default: Cleared
Note: This setting can cause excessive CPU load when the layout is
changed for large maps.
Show parent clouds If checked, shows the parent cloud of a cloud on the map.
Default: Checked
Node Settings
Framed If checked, a frame shows around the node and its label.
Default: Cleared
Label Settings
Floating Labels If checked, title moves with the node. If cleared, you have to move
the title separately, allowing you to individually position it.
Default: Checked
Parameter Description
Customizing Tables
This section provides an overview of customizable tables, which are used by some
device shelf view GUIs and RADview system tables such as Software File
Management, and the tables in the workspaces Configuration, Jobs,
Customers/Providers (Business Entities), and Resources. The customizable tables
in devices provide the customizing functions via buttons, and the system-level
customizable tables provide the customizing functions via a toolbar and right-click
menus.
This section describes only the customizable table functions. For device-specific
configuration details, refer to the device agent manual. For details of
system-level tables refer to the relevant sections in this manual.
Customizable tables provide the following options:
• Show/hide a details pane that displays all the fields of a particular table entry
(device shelf view GUIs only)
• Customize the displayed table data, by adding/removing/reordering displayed
fields
• Auto-resize column widths to make all data visible
• Sort the displayed table data according to one or multiple columns (ascending
or descending)
• Search the table data
• Filter the displayed table data
• Save customized table view for later use, load previously saved views
• Export the displayed table data.
The following customizable table items appear in every right-click menu in system
tables that have customizable table functions.
View Click to open a submenu that includes commands for customizing views and
columns.
Not Provides a quick search function via an editable dropdown box, containing a list of
applicable previously typed items. If the list does not contain any items, the default text
Search appears in italic font.
You can type search text in the box or select a previously typed item from the list,
then click <Enter> to search.
To remove an item from the list, select the item in the dropdown box and click
<Delete>.
Not Provides a quick search function according to a certain criteria via a text field. If
applicable there is no list entry, the default text Search appears in italic font.
To filter list entries, type search text in the text field and then click <Enter> to only
display the list entries matching the criteria you entered.
Not Provides a quick filter function via a non-editable dropdown box, containing a list of
applicable previously saved filters.
To apply a filter, select it in the box. Alternatively, you can start to type the filter
name; it is applied if filter name is in list (even partially).
To remove the filtering from the table, select No Filter.
A right-click menu on the table header of system tables and device tables
provides quick access to auto-resizing columns and customizing the displayed
table data.
Auto Resize Column <Column Name> Auto-resize the specific column such that all the data in the column
can be displayed
Auto Resize All Columns Auto-resize all columns such that all the data in all the columns can
be displayed
[List of column names] Each column name appears in the menu. Visible columns are checked
and hidden columns are unchecked.
Select a visible column to hide it.
Select a hidden column to make it visible as the last column
Note The customizable tables in some RADview devices may not have all the functions
described in this section. Also, some devices could have additional device-specific
buttons in their customizable tables.
Button Description
View Click to open a submenu that includes commands for customizing the columns, sorting,
and filtering. Refer to the sections following this table for details.
Show Details/ Click <Show Details> to show the data for the selected table entry in the details pane.
Hide Details This button changes to <Hide Details> when the details are displayed.
Click <Hide Details> to close the details pane. This button changes to <Show Details>
when the details are hidden.
Note: You can also double-click a table entry to show/hide the details.
You can customize the displayed fields and the dialog size as desired, then save
your customized view. An administrator can save a common customized view to
be available for all users, and a user can save a view to be available to that user.
When the device shelf view dialog box with the table is opened it displays the last
displayed view. The first time the dialog box is opened, it tries to load the
common view if available, then the user view, then the default view.
The <View> submenu is used to customize the view of the displayed table data.
2. To change the order of the displayed fields, select a field and click
<Move Up> or <Move Down> to change its order, or drag it to the desired
postion.
3. To stop displaying a field, select it in the Show Fields text box and click
<Remove> to move it to the Available Fields text box, or drag it to the
Available Fields text box.
4. To display a field, select it in the Available Fields text box and click <Add> to
move it to the Show Fields text box, or drag it to the Show Fields text box.
Note To sort by a different field, simply click that field’s column header.
If you add or change table entries or refresh the table data, the table entries
remain sorted. You can cancel the sorting in the following ways:
• Close the table dialog box
• Click any column header with <CTRL> held down. Although the sorting is
canceled, the table remains sorted until you perform an add, change, or
refresh operation.
1. In a device table, select View > Sort. In a system table, click on the
toolbar or select Sort from the right-click menu on the table data.
The Sort dialog box appears, giving you the possibility to select up to
three columns by which to sort, and select ascending or descending order
for each column.
Note If you want to sort by more columns than are available in the Sort dialog box,
click <Add Category>. The maximum number of columns by which you can sort is
smaller: six or the number of columns in the table.
2. Select the fields by which to sort and then click <OK> to implement the
sorting.
The table rows are sorted as specified. Triangles are displayed in the
column header according to the sorting level and direction. Up to three
triangle indicators appear even if sorted by more than three columns.
Notes • If you selected the same column name more than once, the Sort dialog box
stays open, the sort is not done, and message box appears to notify you of
the duplication.
• If you selected columns that are currently not visible in the table a message
box appears for each field with the option to add it to the table.
• If you click <Yes>, the column is added at the right side of the table. The table
is sorted by all the selected columns even if some of them remain invisible.
If you add or change table entries or refresh the table data, the table entries
remain sorted. You can cancel the sorting in the following ways:
• Close the table dialog box
• Click any column header with <CTRL> held down. Although the sorting is
canceled, the table remains sorted until you perform an add, change, or
refresh
• Open the Sort dialog box, select (None) in the top Sort By field, then click
<OK>. Although the sorting is canceled, the table remains sorted until you
perform an add, change, or refresh.
Figure 3-19. Table Sorted by CIR Column in Descending Order, CBS Column in Ascending Order, EIR
Column in Descending Order
Customizing Views
You can save customized views including the size of the dialog box for later use,
and load views that were saved. If the dialog box size is too small it is not saved.
If you have applied sorting or filtering before saving a view, it remains active
when loading the view only while the table dialog box remains open. After you
close the table dialog box, the sorting or filtering is no longer active in the view
when you load it.
Select Common Settings to save the view as a common view for all users
using this table.
Note You can save the view as a common view only if you have administrator rights.
Users can load a common view that was saved by their administrator.
Select Common Settings to load the view that was defined as a common
view for all users using this table.
Select My Settings to load the view that was defined the specific user
Select Default to load the default view.
1. In a device table, select View > Search. In a system table, click on the
toolbar or select Search from the right-click menu.
The Search dialog box appears.
Note If the item was found and the end of the table has not been reached, the status
bar does not display any message.
Parameter Function
Whole words only Selected – The text being searched for must match a whole
word
Cleared – The text being searched for can match a whole word
or part of a word.
Default: Cleared
Parameter Function
<Find Next> Click <Find Next> to search for the next occurrence of the string
Note Single column sorting of device tables by clicking a column header is not available
while filtering is applied.
Simple Filtering
You can filter each column by a single criterion.
1. In a device table, select View > Filter. In a system table, click on the
toolbar or select Filter from the right-click menu.
The column headers in the table are changed to contain dropdown
filtering lists. For device tables, the Filter option in the View submenu is
marked with a checkmark to indicate that filtering is enabled.
2. In the column(s) which you wish to filter, click the arrow to open the list of
filtering options.
The list opens to show all unique values, and also the following standard
items that are in each column filtering list:
All – This can be selected to disable filtering
Top 10 – This can be selected to display all rows that fall within
user-specified upper or lower limits.
Custom – This can be selected to display rows according to user-specified
criteria.
3. Select the desired filtering criteria.
Only the rows meeting the criteria are displayed, and the status bar of
the table displays Filtering Applied.
If you add or change table entries, the table entries remain filtered. You can
disable the filtering in device tables in the following ways:
• Close the table dialog box
• Click <Refresh>. This closes the dropdown filtering lists in the column headers
and removes the filtering (displays all the table rows).
• Select All in the filtering lists in one of the column headings. This does not
close the dropdown filtering lists in the column headers, but it removes the
filtering (displays all the table rows).
• Select View > Filter. This closes the dropdown filtering lists in the column
headers but the table remains filtered. You can click <Refresh> to view the
unfiltered table.
You can disable the filtering in system tables by clicking on the toolbar when
filtering is enabled.
Note The examples below are provided for Windows 7, but apply to Windows 2008
Server and Unix as well.
Advanced Filtering
1. In a device table, select View > Advanced Filter. In a system table, click
on the toolbar or select Advanced Filter from the right-click menu.
The Advanced Filter dialog box appears. It contains rows of fields called
categories where each category contains:
Dropdown list of table columns – Select the column for filtering
Dropdown list of filtering criteria that specify how to check the table
column against the value list:
Equals
Do not equal
Is less than
Is less than or equal to
Is greater than
Is greater than or equal to
Contains
Matches – Refer to Filtering by Match for details on filtering by
match.
Value list, filled according to the selected table column – Select the
value(s) for which to filter (if filtering by match then refer toFiltering
by Match)
And option and Or option (for all categories except the last one) –
Select And to perform ‘AND’ operation between this category and the
next category.
Select Or to perform ‘OR’ operation between this category and the
next category.
2. Select the columns, criteria, and values for which you wish to filter. You can
apply multiple criteria to a single column or to multiple columns.
3. If you need more categories than are shown in the dialog box, click <Add
Category> to add another.
Fields for another category are added in the Advanced Filter dialog box.
Note The maximum number of categories in the Advanced Filter dialog box is the
number of table columns or six, whichever is the smaller value.
4. Click <OK> to close the Advanced Filter dialog box and apply the filtering.
Only the rows meeting the criteria are displayed, and the column headers
in the table are changed to contain dropdown filtering lists. In device
tables the Filter option in the View submenu is marked with a check to
indicate that filtering is enabled. In system tables the quick filter
dropdown box displays Filter Applied. The status bar of device tables
displays Filter Applied. Figure 3-34 shows a filtered device table.
If you add or change table entries, the table entries remain filtered. You can
disable the filtering in device tables in the following ways:
• Close the table dialog box
• Click <Refresh>. This closes the dropdown filtering lists in the column headers
and removes the filtering (displays all the table rows).
• Select View > Filter. This closes the dropdown filtering lists in the column
headers but the table remains filtered. You can click <Refresh> to view the
unfiltered table.
You can disable the filtering in system tables by selecting No Filter in the quick
filter dropdown box.
Filtering by Match
When you select matches in the criteria dropdown list in the Advanced Filter
dialog box, the value list changes to a text box with an info button next to it
(click the info button to see information on filtering expressions, as shown in
Figure 3-33). You have to type a filtering expression in the text box as specified
in the following.
The filtering expression language comprises two basic character types: literal text
characters and meta-characters. The following table describes some basic filter
expression language definitions.
The following tables describe some of the basic meta-characters of the filter
expression language.
A literal Match all strings with the exact ‘mux’ matche ‘mux’ strings, but
expression not ‘Vmux’
The following table describes iteration meta-characters that control the number
of times a character or string matches.
. (dot) Matches any single character ‘x.z’ matches ‘xyz’, ‘xgz’, ‘xpz’,
etc.
The following illustrates some examples of filtering by match. Table 3-17 shows a
table of data, and Table 3-18 shows examples of filtering the table with match
criteria.
1 Vmux110
2 Vmux210
3 Vmux2100
4 MiniCVS
5 Gmux2000
6 SC-Vmux
7 Ip-Mux14
8 Gmux2000
Filter all rows which... Filter Expression Filtered Rows that Match
2. Enter a new name for the filter or select one of the existing filter names to
overwrite. If you enter a new filter name, it must start with a letter, must not
contain spaces, and must not contain any of the following characters: / \ : * ?
"<>|,
Note Select Save as Common if you have administrator rights and you wish the filter to
be available for other users. Users can load a common filter that was saved by
their administrator.
3. Click <OK>.
The filter is saved.
To load a filter:
Note In system tables you can load a filter by selecting it in the quick filter dropdown
box.
To remove a filter:
1. In the Advanced Filter dialog box, select Filter > Remove.
The Remove Filter dialog box appears, containing a list of previously saved
filters.
Note You can remove common filters only if you have administrator rights.
To export:
Select Print to print the visible table columns and the filtered rows. If
rows are selected then only the selected rows are printed.
Select Save to File to save all table columns (including the invisible
columns) with the filtered rows.
Term Definition
Map Covers the main part of the user interface and provides a
visual representation of levels (submaps) and nodes
(network elements and clouds) and links in the RADview
network. The levels and the nodes on each level of the
map correspond with the tree in the Network Element
Repository
Event Browser Shows events received from the network devices. Refer to
Chapter 7 for details on the Event Browser.
You can add new levels and nodes in the Network Element Repository or map
pane. New levels and nodes added in the Network Element Repository are
immediately shown in the map, and new levels and nodes added in the map are
immediately shown in the Network Element Repository.
Note
For the search utility to operate, you have to select Topology . All other
work spaces do not support the search for devices (NEs), even if the Navigation
Pane displays the NER.
2. If an element is found with a name that matches the text, the element is
highlighted in the Network Element Repository or Groups, or is surrounded by
a frame in the map.
Parameter Function
Find what Specifies the text string to search for. If you choose to run a
recursive search, you can enter part of the string to search for.
Parameter Function
Whole words only Checked – The text being searched for must match a whole
word
Cleared – The text being searched for can match a whole word
or part of a word.
Default: Cleared
<Find Next> Click <Find Next> to search for the next occurrence of the string
Notes
• In the Network Element Repository or under Groups, all elements found with a
name that match at least part of the text are highlighted or surrounded by a
frame in the map respectively.
• On the map, only the current level is searched while in the Network Element
Repository, a search through all levels (recursive) is performed. Therefore,
searches in the Network Element Repository can take up to a minute,
depending on the number of nodes in the system.
Map Functions
You can perform the following functions with the map.
Task Description
Change layout of map Click on the map toolbar. Refer to Changing Level Layout for details.
Task Description
Save the map as an image file Right-click and select Save as image
Export the map as Tom Sawyer To export the map, right-click somewhere inside the map, select Export
Visualization file (*.TSV). which from the shortcut menu, and then choose Tom Sawyer Visualization File
can be loaded by the Tom and specify the desired location.
Sawyer Tomahawk utility for
review.
To display a submap:
• In the Network Element Repository, double-click the desired level.
The submap of the desired sublevel appears.
Note The level and the corresponding submap have been highlighted yellow for
illustration purposes.
Each submap contains icons corresponding to the content belonging to the level
in the Network Element Repository.
You are able to navigate between submaps, view multiple submaps in the work
space or close submaps from the Submap Tab menu.
Figure 3-47. Map with two Horizontal Groups from two Submaps
Figure 3-48. Map with two Horizontal Groups from three Submaps
Figure 3-49. Submap Tab Menu – for two Horizontal Groups from three Submaps
Figure 3-50. Submap Tab Menu – for three Horizontal Groups from three Submaps
Note The New Horizontal Group menu item does not show if horizontal groups already
exist for all submaps.
Figure 3-51. Map with two Vertical Groups from three Submaps
Figure 3-52. Submap Tab Menu – for two Horizontal Groups from three Submaps
Figure 3-53. Submap Tab Menu – Add a Submap to an Existing Floating Window
Figure 3-54. Map with two Horizontal Groups from three Submaps – One Floating
Add a level under the selected New Level New Level –––
level (see Adding New Levels)
Add a range of IP addresses as New NEs ––– New NEs ––– –––
network elements to the selected
level (see Adding RAD Devices)
Expand all levels as overview maps ––– ––– Expand > ––– –––
(see Expanding Levels) Expand All
Expand level as overview map (see ––– ––– ––– Expand –––
Expanding Levels)
Collapse all expanded level ––– ––– Collapse > ––– –––
overview maps Collapse All
Remove the selected level and all Delete ––– ––– Delete –––
subordinate levels (this function is
not available for the highest level)
(see Deleting Levels)
Locate the level icon on the map Locate on Map ––– ––– ––– –––
(this function is not available for
the highest level) (see Locating
Levels)
Hide the nearest neighbors of the ––– ––– Hide > Hide ––– –––
level Neighbors >
One Level
Hide the entire neighbor hierarchy ––– ––– Hide > Hide ––– –––
of the level Neighbors> All
Levels
Represent the nearest neighbors ––– ––– Fold > Fold ––– –––
of the level as a folder, which can Neighbors >
be double-clicked to open an One Level
overview
Represent the level’s entire ––– ––– Fold > Fold ––– –––
neighbor hierarchy as a folder, Neighbors> All
which can be double-clicked to Levels
open an overview
Transfer any elements in a folder ––– ––– Fold > Unfold –––
back to their original location
Update the level with the latest Refresh ––– Refresh ––– –––
configuration
Job Parameters Defines the job parameters of the level and, if desired, all
subordinate levels and nodes, for authentication if a
script is sent to network elements. Refer to Figure 3-59
and Table 3-26 for a description of the parameters.
2. Click <Set>.
The level is configured with the new properties and added to the Network
Element Repository tree under the selected level, and added to the map
as a level icon ( ). You can double-click the level icon to open the
submap for the new level.
Note • The corresponding submap tab appears at the bottom of the map pane only
after you double-click the new level icon to open its submap.
• It is recommended to use systematic level names, such as names or locations
of units or a part of the IP address range. Names assigned to NEs should
reflect the naming convention of the respective levels. This allows for easy
location of NEs in large systems when grouping NEs and creating security
domains for those groups.
Figure 3-56. New Level Dialog Box – General Tab Figure 3-57. New Level Dialog Box – SNMP Tab
Figure 3-58. New Level Dialog Box – SNMPv3 Tab Figure 3-59. New Level Dialog Box – Job Parameters Tab
Figure 3-60. New Level Dialog Box – External Tools Tab Figure 3-61. New Level Dialog Box – Note Tab
Job Parameters Selets Telnet or SSH to access the device via the CLI or
menu interfaces respectively. Refer to Figure 3-65 and
Table 3-26 for additional information.
External Tools Defines default command parameters for external tools
for nodes in the level. Refer to Figure 3-66 and
Table 3-27 for a description of the parameters
Notes Holds optional text description
2. Click <Set>.
The level and, if selected, all subordinate levels and nodes, are configured
with the new properties.
Figure 3-62. Level Properties Dialog Box – General Tab Figure 3-63. Level Properties Dialog Box – SNMP Tab
Note
If you are not logged on as su, the Read and Write community entries appear as
read-only.
Figure 3-64. Level Properties Dialog Box – SNMPv3 Tab Figure 3-65. Level Properties Dialog Box –
Job Parameters Tab
Figure 3-66. Level Properties Dialog Box – Figure 3-67. Level Properties Dialog Box – Note Tab
External Tools Tab
Default double-click Specifies default double-click action, used Shelf View: Open shelf
action for default node properties when new view
network elements are added as nodes to Web Browser: Connect to
the level network element via Web
browser
Telnet/SSH: Connect to
network element via
Telnet.
Parameter Function
Polling Interval (sec) The SNMP polling interval for the level, in seconds
Apply changes to subnodes Select to apply the same changes to all levels and
and sublevels network elements subordinate to this level
Note: This parameter is available only in the Level
Properties dialog box.
Telnet Port 23
SSH Port 22
HTTP Port 80
Menu Option Specifies for which external tool to Ping – Define the command
define the command parameters line and parameters for
sending ping to network
element
Trace Route – Define the
command line and
parameters for tracing route
to network element
Note: If you added external
tools as described in , they
appear in the list.
Command Line Defines the command line for the
external tool, used for default node
properties when new network
elements are added as nodes to
the level
Note: This parameter is read-only.
Command Parameters Defines the command parameters
Note: If you change the for the external tool, used for
command parameters, the default node properties when new
attribute is stored in the network elements are added as
EMS database and used for nodes to the level
command line generation
for this object.
Expanding Levels
You can expand levels as overview maps, or expand a sublevel as a submap.
Deleting Levels
You can delete any level except the highest level.
1. In the level map’s toolbar, click Layout or right-click the level in the map
and select Layout from the shortcut menu.
2. In the Layout submenu, select or clear Incremental Layout. If Incremental
Layout is selected, RADview attempts to preserve map element locations
whenever possible, possibly relocating some elements if necessary, according
to the layout type.
Figure 3-75. Orthogonal Layout Diagram Figure 3-76. Circular Layout Diagram
Figure 3-79. Symmetric Layout Diagram Figure 3-80. Hierarchical Layout Diagram
Locating Levels
The locate function is useful for navigating directly to a level icon. This function
does not exist for the highest level.
To locate the level on the map:
• Right-click the level in the Network Element Repository navigation tree and
choose Locate on Map.
The level submap is opened that contains the icon corresponding to the level that
you wish to locate. The submap is positioned to show the part that contains the
level icon, with a frame surrounding it.
Summary of Tasks
The following table shows the tasks you can perform with RAD devices together
with the corresponding menu items/toolbar icons.
Configure trap synchronization Fault > Trap Sync ––– Fault > Trap Sync –––
groups for the selected network Groups Groups
element (see Configuring Trap
Synchronization)
Synchronizing the RADview fault Fault > Alarms ––– Fault > Alarms Sync –––
data with the network element Sync
(see Synchronizing Alarms)
Connect to network element via Web Browser ––– Web Browser –––
Web Browser (see Connecting to )
Test connectivity of a network External Tools > ––– External Tools > –––
element by sending ping (see Ping Ping
Testing Connection to )
Trace route to network element External Tools > ––– External Tools > –––
(see Testing Connection to ) Trace Route Trace Route
Run a custom external tool for External Tools > ––– External Tools > –––
network element <customized tool> <customized tool>
Note: If you added external tools
as described in , they appear in
the External Tools submenu.
View active alarms for the Active Alarms ––– Active Alarms –––
network element in the Event
Browser, via filter (refer to
Chapter 7 for details on viewing
device events)
View previous alarms for the History Events ––– History Events –––
network element in the Event
Browser, via filter (refer to
Chapter 7 for details on viewing
device events)
Hide the nearest neighbors of the ––– ––– Hide > Hide –––
network element Neighbors > One
Level
Hide the entire neighbor hierarchy ––– ––– Hide > Hide –––
of the network element Neighbors> All
Levels
Represent the nearest neighbors ––– ––– Fold > Fold –––
of the network element as a Neighbors > One
folder, which can be Level
double-clicked to open an
overview
Represent the network element’s ––– ––– Fold > Fold –––
entire neighbor hierarchy as a Neighbors> All
folder, which can be Levels
double-clicked to open an
overview
Transfer any elements in a folder ––– ––– Fold > Unfold –––
back to their original location
Note
If you added external tools, they appear in the External Tools submenu.
This section explains how to add network elements and configure them for the
first time. You have the following options to add network elements to a certain
level on the map:
• Adding a single network element manually
• Adding multiple network elements manually within a defined IP address
range. In addition, you can define adding RAD devices only and/or RAD and
third-party devices. You also have the option to add network elements
without verifying connectivity
• Adding and configuring network elements automatically according to preset
rules. For further information and instructions, refer to Adding and
Configuring Network Elements Automatically in Chapter 4.
To add a single network element to the Network Element Repository and map:
1. Select the level in the Network Element Repository for which you wish to add
a network element and select New NE on the toolbar, or right-click the
level in the Network Element Repository or in the map and select New NE
from the shortcut menu.
The New NE dialog box is displayed (see Figure 3-81 to Figure 3-86). It
contains the following tabs:
General – Defines general network element parameters. Refer to
Figure 3-81 and Table 3-29 for a description of the parameters.
SNMP – Defines the SNMP parameters of the network element if it is
managed via SNMPv1. Refer to Figure 3-82 and Table 3-30 for a
description of the parameters.
SNMPv3 – Defines the SNMP parameters of the network element if it is
managed via SNMPv3. Refer to Figure 3-83 and Table 3-31 for a
description of the parameters.
Custom Ports - Defines the ports for communication and access
protocols. For details, refer to Table 3-32.
Job Parameters – Defines the job parameters of the network element, for
authentication if a script is sent to it. Refer to Figure 3-84 and Table 3-33
for a description of the parameters.
External Tools – Defines default command parameters for external tools.
Refer to Figure 3-85 and Table 3-34 for a description of the parameters
Note – Holds optional text description.
2. Click <Set>.
The network element is configured with the new properties and appears
in the navigation tree as a node in the selected level. A new icon
corresponding to the network element appears on the level map.
Figure 3-81. New NE Dialog Box – General Tab Figure 3-82. New NE Dialog Box – SNMP Tab
Figure 3-83. New NE Dialog Box – SNMPv3 Tab Figure 3-84. New NE Dialog Box – Job Parameters Tab
Figure 3-85. New NE Dialog Box – External Tools Tab Figure 3-86. New NE Dialog Box – Note Tab
Default double-click action Specifies action to take when Shelf View: Open shelf view
node is double-clicked. The Web Browser: Connect to
default is the action that was network element via Web
defined for the level, but you can browser
specify a different action for the
Telnet/SSH: Connect to
node if you wish.
network element via Telnet.
Parameter Function
Polling Interval (sec) The SNMP polling interval for the network element(s), in
seconds
Telnet Port 23
SSH Port 22
HTTP Port 80
Menu Option Specifies for which external tool Ping – Define the command
to define the command line and parameters for
parameters sending ping to network
element
Trace Route – Define the
command line and parameters
for tracing route to network
element
Note: If you added external
tools as described in , they
appear in the list.
Command Line Defines the command line for
the external tool
Note: This parameter is read-
only.
Command Parameters Defines the command
Note: If you change the parameters for the external tool
command parameters, the
attribute is stored in the
EMS database and used for
command line generation
for this object, rather than
the value in the External
Tools tab in the Level
Properties dialog box.
To add multiple network elements to the Network Element Repository and map:
1. Right-click the selected level and select New NEs from the shortcut menu.
The New NEs dialog box is displayed (see Figure 3-87 to Figure 3-92). It
contains the following tabs:
General – Defines general network element parameters. Refer to
Figure 3-87 and Table 3-35 for a description of the parameters.
SNMP – Defines the SNMP parameters of the network element. Refer to
Figure 3-88 and Table 3-30 for a description of the parameters.
SNMPv3 – Defines the SNMPv3 parameters of the node. Refer to
Figure 3-89 and Table 3-31 for a description of the parameters.
Custom Ports – Defines the ports for communication and access
protocols. For details, refer to Table 3-32.
Job Parameters – Defines the job parameters of the network element, for
authentication if a script is sent to it. Refer to Figure 3-90 and Table 3-33
for a description of the parameters.
External Tools – Defines default command parameters for external tools.
Refer to Figure 3-91 and Table 3-34 for a description of the parameters.
Note – Holds optional text description.
2. Click <Set>.
The range of network elements is added as nodes with the new
properties to the selected level. They appear in the navigation tree, and
corresponding icons appear on the level map.
Figure 3-87. New NEs Dialog Box – General Tab Figure 3-88. New NEs Dialog Box – SNMP Tab
Figure 3-89. New NEs Dialog Box – SNMPv3 Tab Figure 3-90. New NEs Dialog Box – Job Parameters Tab
Figure 3-91. New NEs Dialog Box – External Tools Tab Figure 3-92. New NEs Dialog Box – Note Tab
Default double-click Specifies action to take when node is Shelf View: Open shelf
action double-clicked. The default is the view
action that was defined for the level, Web Browser: Connect
but you can specify a different action to network element via
for the range of network elements if Web browser
you wish.
Telnet/SSH: Connect to
network element via
Telnet.
Add only connected If selected, only devices that respond Selected or cleared
devices to SNMP request for OID are added
Add only RAD devices If selected, only devices whose OIDs Selected or cleared
identify them as RAD devices are
added
Note: This option can be selected
only if the option Add only connected
devices is selected.
Job Parameters – Defines the job parameters of the network element, for
authentication if a script is sent to it. Refer to Figure 3-96 and Table 3-33
for a description of the parameters.
External Tools – Defines default command parameters for external tools.
Refer to Figure 3-97 and Table 3-34 for a description of the parameters.
Note – Holds optional text description.
2. Click <Set>.
The network element is configured with the new properties.
Figure 3-93. Node Properties Dialog Box – General Tab Figure 3-94. Node Properties Dialog Box – SNMP Tab
Figure 3-95. Node Properties Dialog Box – SNMPv3 Tab Figure 3-96. Node Properties Dialog Box –
Job Parameters Tab
Figure 3-97. Node Properties Dialog Box – External Tools Figure 3-98. Node Properties Dialog Box – Note Tab
Tab
Notes • Trap synchronization can be configured only for devices that support trap
synchronization, which is usually implemented with Generic RADOS. Refer to
the device Installation and operation manual to determine whether the device
supports trap synchronization.
• Service Center devices must have trap synchronization enabled and
configured.
• Refer to Chapter 7 for details on how to set the trap synchronization group ID
of the EMS server.
• In case that the TrapSync mechanism cannot synchronize the alarms between
the NMS and a specific device in a specified range (SoftSync), it requests all
active alarms from the device (HardSync).
• The TrapSync mechanism is supported for devices that support RADOS.
3. Click the browse button next to the Managers column to display a list of
network managers. If the device is managed via SNMPv3, the list contains the
EMS servers that have been defined by the device to receive SNMPv3 traps,
otherwise it contains the EMS servers that have been defined in the device’s
manager list.
Notes You can use the SNMPv3 Manager application to add EMS servers that receive
SNMPv3 traps from the device (Notifications, snmpTargetParamsTable and
snmpTargetAddrTable). Refer to Chapter 4 for details on the SNMPv3 Manager
application.
Note If the device is not managed via SNMPv3, the :162 does not appear after the
manager IP address.
4. Select the manager(s) that you wish to add to the trap synchronization group
(hold down <CTRL> to select more than one manager), then click <Set>.
The selected managers are displayed in the Managers column.
5. Click <Apply> to save the new trap synchronization group in the device.
Synchronizing Alarms
You can manually synchronize RADview fault service data with a network
element, if for some reason traps from the device may have been lost, or if
device alarms were configured in some way that requires synchronization.
RADview performs internal alarm synchronization, but you may wish to manually
start the synchronization.
To synchronize alarms:
1. Right-click the RAD device in the Network Element Repository or map, then
select Fault and then Alarms Sync from the shortcut menu.
You are prompted to confirm the synchronization.
Note • If there is a shelf view already open for the device when you try to open the
shelf view, you are given the choice of opening the shelf view in read-only
mode or in read-write mode, or of canceling the open, since only one user at
a time can have the shelf view open in read-write mode (see Figure 3-134).
• If you choose to open the shelf view in read-write mode, the user that has it
already open receives a warning message that you have taken read-write
access. The other user now has read-only access (see Figure 3-135).
Note You can quickly view system information and alarm status for an agent by
positioning the mouse over the node in the Network Element Repository
navigation tree or map, until a tooltip appears that displays the device
information.
Note If you create a network element for a product that has not been selected when
installing RADview, you cannot connect to it. When you double-click such a
device, you receive a warning that no RADview application was defined for this
type of product.
Note The SNMP ping tests SNMP connectivity for an SNMP GET.
• Right-click the network element and select External Tools and then Ping
from the shortcut menu.
A command window appears showing ping to device. The ping continues
to be sent until you close the window.
• Right-click the network element and select SNMP Ping from the shortcut
menu.
A command window appears showing SNMP ping to device.
• Right-click the network element and select External Tools and then Trace
Route from the shortcut menu.
A command window appears showing the number of hops needed to
reach the device.
To delete a RAD device from the Network Element Repository and map:
Note Before removing a network element from the network, you have to first remove
all the links associated with the relevant network element.
1. Right-click the RAD device in the Network Element Repository and select
Delete from the shortcut menu.
You are prompted to confirm the deletion.
Note This section and the following ones are illustrated with screen images recorded
on a Windows station. These screen images are identical to the ones at Unix and
Linux platforms except for the frame.
Clouds can be entire networks or third-party devices that can be part of a service
you define. RADview supports the following types of clouds:
• Ethernet based clouds for EtherAcess devices managed via RADview-Service
Manager
• Ethernet based clouds for units managed via RADview-Service Center
• SDH/SONET clouds for DS0 and DS1 interfaces of units managed via RADview-
Service Center.
Once a cloud is added, existing physical interfaces must be specified. These
interfaces are referred to as logical access points and can be used for multiple
services.
This section explains how to add a cloud, specify logical access points and how to
remove a cloud.
Note • Clouds are associated with a provider, therefore at least one provider must be
added to the Business Entities list (in the Business Entities work space) before
you can add a cloud.
• If you try to add a cloud without selecting a provider, an error message is
displayed.
To add a cloud:
1. Select the level in the Network Element Repository for which you wish to add
the cloud and select New Cloud on the toolbar, or right-click the level in
the Network Element Repository or in the map and select New Cloud
from the shortcut menu.
The New Cloud dialog box is displayed (see Figure 3-111).
Note If RADview-Service Center is not installed, the Technology list does not show and
the cloud is added for EtherAccess devices for use in RADview-Service Manager.
The selected provider is added to the Provider field in the New Cloud
dialog box.
Note • Clouds for use with RADview-Service Center are added to both the Network
map of RADview and the RADview-SC Client map as illustrated in Figure 3-114
(highlighted pink).
• Clouds for use with RADview-Service Manager are added to the RADview
Network Manager map only as illustrated in Figure 3-114 (highlighted yellow).
6. Click <Set>.
The cloud is added to the map.
In order to include it in services, you now have to define access points, virtual
private networks and a service level as explained under Configuring Clouds in the
RADview-Service Manager manual section.
Note Access points for SDH/SONET and Ethernet clouds used with RADview-Service
Center must be configured in the RADview-Service Center application as explained
in Chapter 4 of the RADview-Service Center manual section.
To remove a cloud:
1. Remove all services that use the relevant cloud. For additional information on
removing services, refer to the RADview-Service Manager manual section.
2. Remove all VPNs and access points from the cloud.
3. Right-click the cloud.
A shortcut menu appears.
Figure 3-117. New Link – Network Elements Selected for Legacy Link
4. Click <Set>.
The legacy link is created and appears gray on the map.
Figure 3-118. Legacy Link Created on the Map between two NEs in the Same
Level
To delete a link:
1. Right-click the link and select Delete from the shortcut menu.
The Delete Link dialog box opens, showing a list of links between the two
devices.
2. In the list, select the link that you wish to delete and click <Delete>.
You are prompted to confirm the deletion.
3. Click <Yes> to confirm the deletion.
The selected link is deleted.
Group Operations
You can perform group operations as shown in Table 3-36.
You can perform the same operations on group members as for levels/NEs in the
Network Element Repository, except you cannot explicitly add or delete members
of dynamic groups.
Operation Description
Open (double-click) Opens a tab in the map pane, showing the devices that belong to
group
New Level Opens a dialog box to add a new level to the group
(Static group only)
Locate on Map Opens a tab in the map pane, showing the groups in the subtree
Paste Pastes the previously copied or cut device(s) into the selected group
(Static group only)
Operation Description
Note • If you copy a level from the map or Network Element Repository, the
corresponding network elements are added to the group, but the level itself is
not copied
• If you copy/move a level from another static group, the level is added with the
corresponding network elements.
To work with Jobs, you have to select Jobs in the work space selection
area.
When working with Jobs, the GUI is divided into the following four window
elements:
Jobs Table Displays the jobs that are defined in the system (refer to
Working with the Jobs Table for more information).
Reports Displays job reports (refer to Working with Job Reports in
Chapter 4 for more information).
Attribute Description
Job Name A user-defined string of up to 255 characters that is used to identify the job
Job ID A number that is used to uniquely identify the job, set by the management
system at job creation. Each execution of a recurring job has the same job ID,
but can be distinguished by the execution date and time.
Action Action defined for job, e.g. Download Software
Description Description of job
Creator User name of the user who created the job
Creation Time Date and time (YYYY-MM-DD HH:MM:SS) that the job was created
Last Updated By User name of the user who last updated the job parameters via edit job operation
Last Update Time Date and time (YYYY-MM-DD HH:MM:SS) that the job parameters were last
updated
Last Operation By User name of the user who last performed any action on this job such as: run,
stop, activate, deactivate, cancel
Last Operation Time Date and time (YYYY-MM-DD HH:MM:SS) that the job operation (stop, active,
deactive, cancel) was last performed – RO, set by the management system.
Attribute Description
Next Execute Displays the date and time of the next execution of the job, in format
YYYY-MM-DD HH:MM:SS
Owner The owner is the user name of the job owner. The default owner is the user
who created the job. A user can become the new owner of a job if permitted by
administrator.
Since job is running on server side, the owner security profile is used for the job.
Refer to Job Security in Chapter 4 for additional information.
Security Domain This is empty by default. You can add a domain name during job creation or
when editing a job, to control access to the job (the domain must be defined in
the user security profile with relevant permissions). When security domain is set
for a job, some users may not be able to access the job.
Refer to Job Security in Chapter 4 for additional information.
The shortcut (right-click) menus for the History and Active tabs are illustrated
below.
Figure 3-123. Active Tab Shortcut Menu Figure 3-124. History Tab Shortcut Menu
The sections below outline the wizards used to configure the utilities and explain
how to start each one of them.
Jobs
Jobs are administrative tasks performed on one or more pre-defined network
elements (NEs) at a specific time, usually involving TFTP/SFTP file transfers. For an
overview over the Jobs GUI, refer to Working with the Jobs GUI in Chapter 3.
Jobs can be scheduled to execute periodically or once. Table 3-40 outlines tasks
available via Jobs.
Note The availability of jobs depends on whether the selected NE(s) support(s) them.
Download Auxiliary File Load a specific file from NE (for example the MAC
address table)
Reboot Reboot NE
Swap Main and Backup Swap between the NE main and backup storage SW
Software
The Job wizard consists of max 7 steps. Depending on your choices, setting a task
may require two steps.
The table below highlights the wizard steps and provides reference to additional
information and instructions.
NE Selection Method Select the method that defines the nework elements (NEs).
Select an Action Define the task to execute from a list. Only tasks that apply to all
selected network elements can be selected. All others appar listed,
but are grayed out.
Validate an Action Appears only if a conflict occurs, for example one or more NEs do not
support the selected action.
Validate the Job Appears only if a conflict occurs, for example one or more NEs
Parameters support the job, but not the selected job parameters.
Schedule Define whether to execute the job now, at a later stage or frequently
according to defined intervals
Zero Touch
Zero Touch is a utility that allows creating rules to automatically locate and
configure devices on the system level. Rules are defined using a wizard that
consists of up to four steps.
The table below highlights the wizard steps and provides reference to additional
information and instructions.
General Parameters Assign a name to the rule and define a subnet and an IP address
range
NER Population Define the target loction in the network element repositry (NER)
and a naming convention for nodes found
Network Scan Configuation Specify criteria according to which the network is scanned, such as
scan interval, SNMP parameters, user credentials for access etc.
Maintenance Windows
RADview enables users to define maintenance windows that interrupt the
sampling by RADview-Performance Manager during maintenance tasks such as
software uploads, downloads etc in order to avoid statistic errors and failure
reports due to scheduled down times.
General Parameters Define the maintenance parameters for the maintenance window
and the resources that it applies to
Admin Console Provides log administration, fault services, Configuring the Network
security services, and changes attibutes Element Repository
for the network element repository (NER)
Provisioning Cleanup
Zero Touch Console Automatically adds and configures Adding and Configuring
network elements according to pre- Network Elements
defined rules Automatically
Log Viewer Customizes the list of logs displayed Viewing RADview Events in
the Log Viewer
License Manager Adds and maintains the licenses Managing and Modifying
Licenses
SNMPv3 Manager Modifies the SNMPv3 profile of SNMPv3- Configuring SNMPv3 Settings
enabled network entities using the SNMPv3 Manager
Event Browser Lists events, allows adding notes, sound Working with the Event
profiles etc Browser
SecFlow Invokes the SecFlow iSIM system SecFlow iSIM User Manual
Version Browser Displays the RADview package contents Viewing the RADview Package
Contents
Note The examples below are provided for Windows 7, but apply to all supported
Windows platforms.
• See Figure 3-130 for an example of a standalone unit that can be configured
only when connected to RADview. As the ports and LEDs are all on the front
panel, only the front panel is displayed in the shelf view.
• See Figure 3-131 for another example of a standalone unit that can be
configured only when connected to RADview. This unit has LEDs on the front
panel and ports on the rear panel therefore both panels are displayed.
• See Figure 3-132 for an example of a standalone unit with Edit and Agent
configurations
• See Figure 3-133 for an example of a chassis containing cards (modules),
with Edit and Agent configurations.
Figure 3-131. Shelf View of Standalone Unit, Front and Rear Panels
Figure 3-132. Shelf View of Standalone Unit, with Edit and Agent Views
Figure 3-133. Shelf View of Chassis, with Edit and Agent Views
Notes • If there is a shelf view already open for the device when you try to open the
shelf view, you are given the choice of opening the shelf view in read-only
mode or in read-write mode, or of canceling the open, since only one user at
a time can have the shelf view open in read-write mode (see Figure 3-134).
• If you choose to open the shelf view in read-write mode, the user that has it
already open receives a warning message that you have taken read-write
access. The other user now has read-only access (see Figure 3-135).
Figure 3-135. Warning That Other User Has Taken Read-Write Access
You can configure at the device level, card level (if applicable), and port level,
depending on what is selected in the shelf view. If there is an Edit and Agent
view, there may be multiple Edit configurations available.
In the case of the Megaplex and Kilomux devices, all parameters are soft
programmable for up to ten configurations for the Megaplex and two
configurations for the Kilomux (database). Alarm status and system configuration
are available through the Management System at all times
Note For especially complex configurations using certain modules and heavy payloads,
the Megaplex-2200, Megaplex-2100/4 storage capacity is limited to five
configurations.
Note If the device is disconnected, only the Edit view appears (see Figure 3-136).
• From the Window menu, select Agent View or click Agent View if
available in the toolbar.
Device Level
To perform operations at the device level, you must select the device in the shelf
view. The default selection is the device. For specific device-level operations,
refer to the RADview agent user's manual.
Card Level
In the case of a chassis, the Card level can be accessed for each preprogrammed
card, in the Edit or Agent views if applicable. The Card Level provides a graphical
representation of the selected card. The view includes ports and their operational
and communication status.
The toolbar includes Card level options, depending on the device and selected
card:
Port Level
The Port level includes ports and their operational and communication status. To
perform port operations, you must select a port. In the case of a chassis, the Port
level can be accessed for each preprogrammed card, in the Edit or Agent views if
applicable. For specific port-level operations, refer to the RADview agent user's
manual.
To select a port:
• If the device is standalone:
In the shelf view, click the port that you wish to select.
A blue border outlines the port, indicating it is selected.
The Port level is displayed within the Card view. The Port level toolbar includes
the following buttons for quick execution of specific tasks:
Alarms > Display - Display a list of current port active alarms (Agent
mode).
In the Port level, you can perform the following for Megaplex devices:
• View and set software parameters of a port.
• Copy a port configuration to a destination port in the current Megaplex or
another Megaplex.
• Display and set time slot assignments for MTML and HS-4 card ports.
• View the active port alarms of the selected port (Agent mode).
• View, start, and stop diagnostic tests in the selected port (Agent mode).
• View statistical information for the external-1 port of an MTML card.
Notes • The pop-up blocker should be turned off when working with devices via Web
browser
• If the web access is via HTTPS, you might receive a security warning. In this
case, choose the option to continue.
Using Telnet/PuTTY
The Telnet or PuTTY login window appears for the device as in Figure 3-141 and
Figure 3-142. For more information about configuring a particular device via
Telnet/PuTTY, refer to the device Installation and Operation manual.
Note If the access is via PuTTY, you might receive a security alert. In this case, click
<Yes> to open the PuTTY window.
You can view the following elements in the System Console window:
Servers on stations with EMS
EMS server process information
Services that can be monitored
Services that can be configured
Status of services (see Table 4-1).
Color Status
Note It is recommended to not run the polling indefinitely, as it increases the load on
the EMS server process.
Parameter Description
Info
Maximum memory Displays maximum amount of memory that is available to be allocated to the
EMS server process
Total memory Displays amount of memory that has been allocated to the EMS server
process
Free memory Displays amount of free memory available, from of the total memory
allocated to the EMS server process
Starting/Stopping/Managing Services
Unless noted otherwise, every service available in the system console can be
started or stopped by right-clicking the relevant service.
To start/stop a service:
• In the System Console, right-click the desired service or management item
and select Start or Stop from the shortcut menu (see Figure 4-5).
The service you selected starts or stops respectively.
Note Refer to Chapter 7 for information on the SNMP Spy parameters in the General
tab.
The server SMTP and security parameters are displayed (see Figure 4-7).
2. Enter information for any of the parameters (see Table 4-3).
3. Click <Set>.
Parameter Description
RMI
Initial Context Factory Accesses the real context implementation--the Context instance created by
the initial context factory class environment property. This factory class
implements the InitialContextFactory interface.
Read-only
Parameter Description
Provider URI The unique identifier for each service provider configured in a domain. Service
provider URIs are useful in that they allow a domain to distinguish between
two service providers that may share the same implementation (but not
configuration).
Read-only
SMTP Consult your system administrator for the values for these parameters
Mail Domain Mail server that sends email for event forwarding
Host Host name or IP address of mail server
Port Port for SMTP communications
User Name of user that sends event forwarding email
Password User password for mail
Security Connection (SSL) Secure Sockets Layer, when enabled (selected), ensures the security of data
sent via the Internet by using encryption.
Localization
First business day of the Specifies the first business day of the week. Can be set to any day of the
week week.
Default: Monday
Security
Internal Password This password protects access to the System Console itself. By default it is
set to the default RADview system password, root.
If you upgrade RADview from a version that did not have a default password
for the system console, after the upgrade the system console password is
set as follows:
• If the system console password was not defined before the upgrade, then
after the upgrade it is set to root
• If the system console password was defined before the upgrade, then
after the upgrade it remains the same.
Note: This password is not related to the Internal user listed in the EMS
Security Administrator.
Parameter Description
Parameter Description
User The name of the EMS Datasource Oracle Database server user
Password The user’s password used to gain access to the EMS Datasource
Note This service is always active and there is no option to stop it.
Parameter Description
Parameter Description
Event Channels Event channel files containing the event service settings
Parameter Description
Start Status Check Delay (min) The delay time (in minutes) until the status check is started
Read-only
Status Check Interval (min) The amount of idle time (in minutes) from the time the log service
stops until the time it will have to start again.
The Batch Size to use in DB The size of the batch specified for DB operations, e.g. – 50
Operations
Parameter Description
No. of Records Retrieved The number of records that can be retrieved for every request, e.g. –
per Request 1000
Unknown Notice
Normal Notice
Warning Warning
Minor Error
Major Critical
<Set> Select the new severity and click <Set> to save the setting
Parameter Description
Info
3. Expand the Servers tree, the <server name> tree and then the
Process1 tree.
All System Console options are available.
4. Select EMS License Service.
The EMS License Service parameters are displayed.
5. Enter the location of the new license server and the License Provider port
used to communicate with this server as explained in Table 4-10.
6. Click <Set>.
The settings take effect.
Parameter Description
Info
Description Describes the current service selected in the system console
Read-only
Version The version of the service
Read-only
Parameter Description
Info
Parameter Description
Parameter Description
Table 4-13. EMS Fault Management (Back End) Parameters – General Tab
Parameter Description
Info
Log Full Alarm Timeout (sec) The amount of time before the log is selected to see if it has reached
the maximum size
Fault Status Propagation Enables/disables auto checking of the status of each element in
the NER tree (internal database)
Parameter Description
Traps Buffering and Retransmission Traps defined as forwarded with retransmission are buffered (see the
forwarding policy configuration in the Admin Console.) Add the
destination of the forwarding to the OSS heartbeat service in order to
check if it is reachable using ping. If the destination becomes
unreachable for some period, then becomes reachable again, the
traps buffered during that period are retransmitted in groups.
Max Size of Traps Cache Size of traps cache in RAM (in traps). When cache size exceeds this
value, the oldest traps are removed from the RAM cache and stored
in the database.
Max Size of Traps Database Size of database storage for buffered traps (in traps). When database
size exceeds this value, the oldest traps are deleted.
Clear Database Delete all buffered traps, that are stored in database
Retransmission Group Size Number of traps sent without delay during retransmission
Inform Timeout (sec) Amount of time to wait for confirmation response to SNMP inform
traps
• In the system console ( ) select EMS Fault Management (Back End), then
select the Traps Synchronization tab.
The Traps Synchronization tab of the EMS Fault Management (Back End)
window appears, displaying the trap synchronization parameters. Refer to
Table 4-14 for information on the parameters.
Note • Enabling the trap synchronization spy worsens system performance. It should
be enabled only when necessary, and then disabled when no longer needed.
• Trap synchronization is not supported for non-Ethernet Access devices.
Table 4-14. EMS Fault Management (Back End) Parameters – Traps Synchronization Tab
Parameter Description
General
Algorithm
Trap Minimum Waiting Time (ms) Minimum amount of time to wait for trap
Waiting Time for Hard Resync Start Amount of time to wait before starting hard resynchronization
(ms)
Parameter Description
Max Size of Fault Management Queue Maximum size of fault management queue
Interval for Checking Ignored Agents Interval for checking ignored agents (When the fault management
(ms) queue is full, certain agents are ignored.)
Fill Threshold to Resync Ignored When the queue usage drops below this threshold, ignored agents
Agents (%) are resynchronized.
Spy
Parameter Description
Parameter Description
Parameter Description
Polling Threads Count Number of threads performing polling at once. This only affects
the polling duration.
NER Context Name of NER tree node level to be polled
Note: The name must contain at least one nonblank character
after the slash, for autodiscovery to function properly.
SNMPv3 Engine ID Polling Settings
SNMPv3 Engine ID Polling Threads Count Number of threads performing SNMPv3 polling at once. This
only affects the polling duration.
SNMPv3 Engine ID Polling Interval (hours) Interval for SNMPv3 polling
Parameter Description
Info
Parameter Description
Info
Discovery settings
Ner Context Name of NER tree node level where discovered nodes will be
added
Read Community One or more communities to use when accessing the device
via SNMP in this service
Note: When entering multiple communities, separate them
using a semicolon (;)
Timeout (msec) SNMP timeout when accessing the device via SNMP in this
service
Retries SNMP retries when accessing the device via SNMP in this
service
Parameter Description
Info
OSS Heartbeat Enabled Checked – OSS connectivity is checked with periodic ping
Cleared – OSS connectivity is not checked
OSSes IP Addresses IP address or host name of all OSS stations for which heartbeat
check should be performed
Notes:
• If the OSS station is listening for SNMP traps on a port other
than 162, you must enter the port after the
IP address/hostname, separated by a colon
• When entering multiple IP addresses/host names, separate
them with a semicolon.
Timer Interval (sec) Interval between periodic pings
Note: This should be a value greater than 0.
OSS Heartbeat Timeout (sec) Amount of time to wait for ping acknowledge, after which OSS
is considered to be disconnected
Note: This should be a value greater than 0.
Trap Community SNMP community for traps
Parameter Description
Info
Parameter Description
Info
MTSC FE Service
Memory Usage
Min. Free Memory Threshold (%) Amount of memory that must be available for Service Center
requests to be processed
Default: 10
Parameter Description
Current
Statistics
Parameter Description
Timeout
Parameter Description
Apache Server Host Click <Get> to retrieve the location of the Apache web server,
responsible for collecting the data displayed in the PM portal.
To specify a different location, enter the server name or IP
address and then click <Set>.
Default: The location of the RADview server
Parameter Description
Service Identifier Structure Only OAM services, not provisioned via SMS
Default: $[MD]-$[MA] $[Vlan].$[Pbit]
SMS Service Identifier Structure Only OAM services provisioned via SMS
Default: $[SMS Service]-$[SMS CoS]
Note This service is always active and there is no option to stop it.
Parameter Description
Info
Snapshot Settings
Maximum number of concurrent SNMP Maximum number of SNMP sessions for parallel reading of agent
sessions configurations
Maximum number of concurrent Maximum number of sessions for parallel processing of
database sessions application queries
Parameter Description
Info
operations to/from the NE. You have to configure three sets of parameters as
instructed in the sections below:
• General – Sets the number of concurrent NE tasks in the system (back-end
server).
• SFTP –Settings for the home directory, server host and port, user, and
password, as well as whether SFTP is the default file transfer protocol
• TFTP (default) –Settings for the home directory and server host.
Parameter Description
Info
Description Describes the current service selected in the system console
Read-only
Version The version of the service
Read-only
General settings
• In the system console ( ) select EMS Jobs Management (Back End) and
then click the SFTP tab.
The EMS Jobs Management (Back End) window appears, displaying the
SFTP tab. Refer to Table 4-29 for information on the parameters.
Parameter Description
SFTP Settings
• In the system console ( ) select EMS Jobs Management (Back End) and
then click the TFTP tab.
The EMS Jobs Management (Back End) window appears, displaying the
TFTP tab. Refer to Table 4-30 for information on the parameters.
Parameter Description
TFTP Settings
The EMS Jobs Management (Front End) window appears, displaying the
General tab. Refer to Table 4-31 for information on the parameters.
Parameter Description
Info
File Repository Home Directory Path of directory used as home root for EMS Jobs & Archive
management to store files (SW, configuration, user, script and log
files). See Table 4-32 for details on the structure of the file
repository.
(default location is
<EMS_installation_dir>\ems\udcm\fe_repository\, where
<EMS_installation_dir>= EMS installation directory, e.g. C:\RV32)
Notes:
• You should not add, remove, or change subdirectories and files
in the home root manually. Any manual alteration of the home
root content leads to data integrity loss and malfunction of the
whole EMS Jobs & Archive management.
• You should include the content of this directory as extra files in
the backup/restore procedure, and always back it up and
restore it synchronously with the database files.
Temporary Home Directory Path of directory used as a temporary storage root for EMS Jobs &
Archive management to store temporary files
(default location is <EMS_installation_ dir>\ems\udcm\temp\,
where <EMS_installation_dir>= EMS installation directory, e.g.
C:\RV32)
Notes:
• You should not add, remove, or change subdirectories and files
in the home root manually. Any manual alteration of the home
root content leads to data integrity loss and malfunction of the
whole EMS Jobs & Archive management.
• You should not include the content of this directory in the
backup/restore procedure.
Note
The <DB-ID> in the table is the file database ID, which is used by the database to
identify the file.
To configure the EMS Jobs Management (Front End) Archive Statistic parameters:
• In the system console ( ) select EMS Jobs Management (Front End) and
then click the Archive Statistics tab.
The EMS Jobs Management (Front End) window appears, displaying the
Archive Statistics tab. Refer to Table 4-33 for information on the
parameters.
Table 4-33. EMS Jobs Management (Front End) – Archive Statistic Parameters
Parameter Description
Summary
Files stored Number of files stored in EMS Jobs & Archive management file
repository
Space used Disk space (in kB) occupied by files stored in EMS Jobs & Archive
management file repository
SW Files
Files stored Number of SW files stored in EMS Jobs & Archive management file
repository
Space used Disk space (in kB) occupied by SW files stored in EMS Jobs &
Archive management file repository
Configuration Files
Files stored Number of configuration files stored in EMS Jobs & Archive
management file repository
Space used Disk space (in kB) occupied by configuration files stored in EMS
Jobs & Archive management file repository
User Files
Files stored Number of user files stored in EMS Jobs & Archive management file
repository
Space used Disk space (in kB) occupied by user files stored in EMS Jobs &
Archive management file repository
Script Files
Files stored Number of script files stored in EMS Jobs & Archive management
file repository
Space used Disk space (in kB) occupied by script files stored in EMS Jobs &
Archive management file repository
Log Files
Files stored Number of log files stored in EMS Jobs & Archive management file
repository
Space used Disk space (in kB) occupied by log files stored in EMS Jobs &
Archive management file repository
Files stored Number of data report files stored in EMS Jobs & Archive
management file repository
Space used Disk space (in kB) occupied by data report files stored in EMS Jobs
& Archive management file repository
To configure the EMS Jobs Management (Front End) Data Storage Monitoring
parameters:
• In the system console ( ) select EMS Jobs Management (Front End) and
then click the Data Storage Monitoring tab.
The EMS Jobs Management (Front End) window appears, displaying the
Data Storage Monitoring tab. Refer to Table 4-34 for information on the
parameters.
Table 4-34. EMS Jobs Management (Front End) – Data Storage Monitoring Parameters
Parameter Description
General Settings
Monitoring Interval (min) Time interval (in minutes) between space allocation monitoring (by
default 15 minutes)
Archive Settings
Automatically delete archive when Enable automatic archive deletion if archive size reaches limit
reached maximum allowed space
Currently used space (MB) Current disk space used for EMS Jobs & Archive management file
repository. Events are generated when the used space reaches
thresholds as specified by Warning Alert, Minor Alert, and
Major Alert
These events appear in the event browser (see Chapter 7).
Maximum allowed space (MB) Maximum disk space allocated for EMS Jobs & Archive management
file repository
Keep files marked as baseline If selected, files marked as baseline are kept during archive
compacting
Recent files to keep (per NE) Number of most recent files to keep (per single NE) during archive
compacting. Remaining older files are deleted
Warning Alert (%) When used space reaches the specified percentage of Maximum
allowed space (MB), RADview generates a warning event
Minor Alert (%) When used space reaches the specified percentage of Maximum
allowed space (MB), RADview generates a minor event
Major Alert (%) When used space reaches the specified percentage of Maximum
allowed space (MB), RADview generates a major event
Report Settings
Automatically delete reports when Enable automatic report deletion if number of reports reaches limit
reached Maximum No. of Reports
Current No. of Reports Current number of job reports
Maximum No. of Reports Maximum number of job reports
Old reports to remove (%) Percentage of reports to remove during report compacting
RADview while the availability of tasks depends on whether the specific network
element supports it:
• Discovering new units in pre-defined subnets and adding them to the map
• Automatically uploading software and configurations to newly discovered
units
• Uploading predefined CLI scripts, such as RADIUS, TACACS+, SYSLOG, etc to
newly discovered units.
• Adding a pre-defined RADview server’s IP address to the manager list of the
units added to the map.
• Discovering units on the map that have been replaced and handling the
replacement procedure according to a pre-defined rule.
Notes • Before you can configure and use the Zero Touch service, you may have to
start it as explained under Enabling and Viewing the Zero Touch Application
Service.
• Zero Touch is based on the Jobs. Devices that do not support certain Job
options do not support the respective task in Zero Touch as well.
• CLI commands are not supported for units whose Telnet/SSH/Terminal
interface is menu-driven.
• Sublevels can accommodate max 200 devices.
2. To configure the search and add criteria, use the Action menu or the toolbar
to select the desired option as outlined in Table 4-35.
Adding a new search and add rule for devices on the network For additional instructions,
refer to Adding and
Modifying Search and Add
Rules.
Enabling a search and add rule (after it has been disabled) Unavailable if the selected
rule(s) is (are) enabled
Disabling a search and add rule (after it has been enabled) Unavailable if the selected
rule(s) is (are) disabled
Moving selected search and add rules down in the list Unavailable if the selected
rules are already a the
bottom of the list
Moving selected search and add rules up in the list Unavailable if the selected
rules are already a the top
of the list
Now scanning for devices that comply with the search and add
rules in the list
1. From the menu, select Action > Add or, at the toolbar, click Add .
The Create New Rule wizard appears (Figure 4-9).
2. Assign a name to the rule and add a short description in the respective fields.
3. Define the criteria that the new rule has to comply with as explained in
Table 4-36.
4. Once you completed defining a criterion, click <Add Criterion>.
The new criterion is added to the list.
NE Type Equals. Only the device you choose is Click <…> to view a list of
part of the rule supported devices and
Contains. The device you choose is select the desired one from
also part of the rule. the list.
Figure 4-10. Specifying the Name of the Rule and the Level for the Devices to be Added
Table 4-37. Specifying the Name of the Rule and the Level for the Devices to be Added
Parameter Description
Target NER Location Path The level to which the devices are added, for example /ZT.
To add a new level, refer to Working with Levels in Chapter 3 for instructions.
Node Name
Hostname Check if you want the hostname to be displayed as part of the rule name
Parameter Description
IP Check if you want the IP address you entered in the pevious step displayed
as part of the rule name.
Preview Preview of the name accoding to the settings you choose (generic)
Parameter Description
First Time SW Upload Check to enable first time software upload to the unit as part of the search
and add rule.
Note: The availability of this option depends on your access rights and on
whether the unit supports it.
Software Version Select the desired software version from the list.
Reboot after Upload Check to reboot the unit once the new software has been donloaded.
First Time CFG Upload Check to enable upload a configuration file to the unit as part of the search
and add rule.
Note: The availability of this option depends on your access rights and on
whether the unit supports it.
File For New Device Click <…> and navigate to the relevant configuration file’s lcation and select
it.
Reboot after Upload Check to reboot the unit once the new configuration has been donloaded.
CLI Upload Check to enable uploading script elements to the unit as part of the rule.
Select Predefined Script Select the desired script elements from the list one by one. The following
script elements are available:
TACACS+, RADIUS, SNTP Server, Date, SysLog, Save Configuration
To enter the desired script element to be execute, click <Append>. The
scripts appears under Enter Script to Execute.
Add EMS to Manager List Check to add the EMS server to the manager lis of the unit.
EMS IP Address Enter the IP address of the station that hosts the RADview server.
Parameter Description
Handling Action Enter the desired option to the rule as a response to replacing a unit.
• No Action.
• As in First Time. The unit is handled like a newly added unit.
• Last Configuration and Matching SW. The unit is added and updated with
the last backed-up IP configuration file and the matching software version
(SW) file.
• Baseline Configuration and Matching SW. The unit is added and updated
with the baseline configuration file and the matching software version
(SW) file.
Parameter Description
Network Scanning Check this option to enable scanning according to the search and add rule
Scan Interval (Hours) Select one of the following intervals (hours): 6, 12, 24, 48
Discover non-RAD Devices Check this option to enable third-part (non-RAD) devices to be found,
Advanced Configuration Click <…> for additional parameters and refer to Table 4-40 for further
information and instructions.
Parameter Description
SNMP
Timeout Specify the SNMP timeout for the network element, in milliseconds
SNMP V1 Parameters
SNMP V3 Parameters
CLI/SSH Parameters
User Name Enter the user name for Telnet/SSH access, for example su
Password Enter the password for Telnet/SSH access, for example 1234.
Parameter Description
9. Click <Finish>.
The rule is added to the list in the Zero Touch Configuration dialog box.
2. From the menu, select Action > Change or, at the toolbar, click Change .
The Edit Rule wizard appears.
3. Follow the onscreen instructions in the wizard, which is identical to the
Create New Rule wizard (Figure 4-9).
Once the rule takes effect and scans were run accordingly, the map
displays the devices found as illustrated in Figure 4-16:
Figure 4-16. Part of RADview Map and NER - Devices Added According to Zero Touch Rule
2. From the menu, select Action > Delete or, at the toolbar, click Delete .
You are asked to confirm your request (Figure 4-17).
Adding an Entry
This operation is enabled when you select an entry in the hierarchy tree. The
selected node is the parent of the new entry.
Renaming an Entry
To rename an entry:
1. In the NER Explorer, select an object in the hierarchy tree (network element in
the middle pane).
2. In the NER Explorer toolbar, select Edit > Rename Entry.
Removing an Entry
To remove an entry:
1. In the NER Explorer, select an object in the hierarchy tree (network element in
the middle pane).
2. In the NER Explorer toolbar, select Edit > Remove Entry.
A confirmation dialog box is displayed.
Adding an Attribute
To add an attribute:
1. In the NER Explorer, select a node in the hierarchy tree (network element in
the middle pane).
2. In the NER Explorer toolbar, select Edit > Add Attribute.
The Add Attribute dialog box is displayed.
Parameter Function
Figure 4-25. NER Explorer – Add Attribute (Custom Attribute) Dialog Box
Modifying an Attribute
To modify an attribute:
1. In the NER Explorer, select a black row in the Attributes table (if the
respective row is blue, i.e., derived from the parent, you can modify it only
via Add Attribute).
2. In the NER Explorer toolbar, select Edit > Modify Attribute.
The Modify Attribute dialog box is displayed (see Figure 4-26).
3. Enter the new Attribute Value.
4. Click <Set>.
Removing an Attribute
To remove an Attribute:
1. In the NER Explorer, select a black row in the Attributes table (if the
respective row is colored in blue, i.e., attribute derived from the parent
object, it cannot be removed).
2. In the NER Explorer toolbar, select Edit > Remove Attribute.
A confirmation dialog box is displayed.
Refresh updates a subtree in the tree view starting with a selected node (e.g., a
selected node with all its subordinates). If no node is selected, refresh is
performed for the parent node.
If you intend to create users, you have to first create users associated with the
required encryption method at the desired security level via Telnet/SSH or the
terminal application. The SNMPv3 Manager creates additional users based on
existing users only.
Any new user is created with the same encryption method and at the same
security level or lower as the user on which he is based.
You can configure SNMPv3 defaults on the RADview map per device or per level
and then you can start modifying SNMPv3 settings for single or multiple devices.
To define the SNMPv3 defaults for an existing level and its sublevels:
1. Right-click the desired level of the NER or on the desired tab of the
respective level of the map and select Properties from the shortcut menu.
The Level Properties dialog box appears.
2. To modify the SNMP parameters, refer to Configuring Level Properties in
Chapter 3.
The RADview map functionality is fully supported. The utility responds to and
reflects all relevant map events. The SNMPv3 Manager stores map/agent
information in its database. When initiated with no map, the application retrieves
the information from the database.
Menu Bar
The menu bar provides access to the menus used for administrator account
configuration, initiating wizards, performing discovery, etc. The following table
lists the menu items and their functions.
Tool Bar
The toolbar provides easy access to the main functionalities of the application
that are otherwise available from the menus.
Button Function
Settings
Refresh
Discovery
Persist selected
Persist all
SNMPv3 Tables
The SNMPv3 tables can be used for adding, editing, and deleting user accounts,
their authorizations, and notifications. The tables are mapped directly from the
SNMPv3 MIB definitions (RFC 3413, RFC 3414, RFC 3415 and RFC 3584).
The tables are divided into three tabs:
• Users
• Authorization
• Notifications.
Output Viewer
The output viewer displays results of the administrative operations performed on
the SNMPv3 agents. You can enable or disable the Output Viewer via the Output
option in the View menu.
Note Before starting the SNMPv3 Manager, you must open RADview, to ensure that all
the SNMPv3 Manager functionalities are available.
Note You can also open the SNMPv3 Manager application by selecting from the
RADview Network Manager menu bar Tools > SNMPv3 Manager.
Note If there are configuration changes that will be lost by executing the discovery,
one of the following a messages appears:
• Configuration changes weren’t applied and will be lost if
discovery is executed
• Configuration changes weren’t saved to persistent storage.
To start the discovery and discard the changes, click <Ignore>.
To cancel starting the discovery, click <Cancel>.
2. Click <Continue in Background> to close the Discovery window and run the
discovery process in the background, or wait until the agent discovery is
completed, and then click <Close> to end the process.
The Agent Tree in the left pane of the main window (see Figure 4-29) is
updated with the located SNMPv3-enabled devices.
Override Map Defines if the SNMPv3 Manager retrieves access Selected – The SNMPv3 Manager
Settings attributes from the map, or overrides them. overrides the map settings
Note: If the option to override the map settings is Cleared – The SNMPv3 Manager
selected, the rest of the parameters are not uses the map settings
available. Default: Cleared
Sec. Model Global access security model for the user account. USM – User-based Security Model
When the USM (User-based Security Model) is (SNMPv3)
selected, you have to define its authentication and SNMPv2 – SNMP version 2
privacy protocols and passwords.
SNMPv1 – SNMP version 1
Note: Parameters that are irrelevant for the selected
Default: USM
SNMP option are unavailable.
Auth. Protocol Authentication protocol for the USM security model SHA – Secure Hash Algorithm
authentication
MD5 – MD5 authentication
No Auth. – User authentication is
disabled
Default: MD5
Priv. Protocol Privacy protocol for data encryption in the USM DES –DES privacy protocol
security model No Priv. – Data encryption is
disabled
Default: DES
Read Read community name for the SNMPv1 and SNMPv2 Up to 32 alphanumeric characters
Community security models
Write Write community name for the SNMPv1 and SNMPv2 Up to 32 alphanumeric characters
Community security models
You are now ready to create users, profiles etc as outlined under Managing
SNMPv3 Settings. The SNMPv3 Manager offers two ways of configuring an agent
for SNMPv3 Management:
• Wizard – Via a user-friendly step-by-step procedure providing all necessary
steps
• Native –By filling out standard SNMPv3 tables.
In addition, the standard SNMPv3 tables allow you to edit or delete user
accounts.
User Name
Authentication protocol and password
Privacy protocol and password.
User name and passwords can consist of up to 32 alphanumeric characters.
For additional information on authentication and privacy protocols, refer to
Table 4-44.
Note • For a single agent, the available authentication and privacy protocol values are
the settings of the master user account or lower (No Auth/No Priv).
• For multiple agents, the available authentication and privacy protocol values
are the settings of the master user accounts (if they are the same), and lower
(No Auth/No Priv). If the authentication and privacy protocol definitions in the
selected agents are different (for example MD5 and SHA authentication or DES
and No Priv privacy), the only available options are No Auth and No Priv.
4. Click <Next>.
The Assign Group dialog box is displayed.
5. Assign the new user to a group by choosing an existing group or create a new
user group by selecting Create Group and entering the desired name for it.
6. Click <Next>.
The Assign View dialog box is displayed.
Context SNMP context configured for the device Existing SNMP context
To remove a user account, group, or view via the standard SNMPv3 tables:
1. Display the necessary SNMPv3 table.
2. Select the desired table row by clicking the row number on the left side
of the table row.
3. Click <Remove> to delete the selected entry.
User Name Name of the user account to use the new Up to 32 alphanumeric characters
community name.
Context SNMP context configured for the device Existing SNMP context
6. Click <Next>.
The Assign View dialog box is displayed.
7. Select an existing view or create a new view by selecting Create View and
assigning a name to it, which may consist of up to 32 alphanumeric
characters.
8. Click <Finish>.
The view permissions are created.
Creating Notifications
The SNMPv3 Manager maintains a database of events that are mapped to the
traps sent by an agent to the NMS. You can select the events, specify their
destinations, and define the transmission methods.
3. From the left-hand event list, select one or several events and click to
move them to the right-hand list.
4. If you intend to create a new event, select Create Events, and then click
<Add>.
A new row is added to the event table.
In the Agent tree, select the desired agent(s), and then click Persist
Configuration on Selected Nodes or select Persist Selected from the
Persistency menu.
Note Only agents with the blue line around their status LED support persistent
storage. For unsupported agents the Persist options are unavailable.
Note If agents are refreshed before configuration changes are applied, the SNMPv3
Manager requires confirmation of the refresh procedure.
Note If configuration changes have not been applied or saved, one or more of the
following messages appear:
• Configuration changes weren’t applied and will be lost if
application is closed
• Configuration changes weren't saved to persistent storage
• There are procedures running and will be terminated if
application is closed.
To close the application, click <Exit>.
To return to the application, click <Cancel>.
Note If you are planning to collect statistics for the RADview Performance Portal, you
must install a TFTP server as collecting statistics does not support SFTP.
• Install a TFTP or SFTP server on the same station as the RADview server.
• Select a TFTP or SFTP server that supports a large number of concurrent
sessions. For additional TFTP/SFTP server requirements, refer to Software
Requirements in Chapter 1.
• Verify that the file transfer directory defined in the TFTP/SFTP server settings
is the same as the directory defined in the system console. For additional
information, refer to Configuring the EMS Jobs Management (Back End).
• Verify that the max number of concurrent sessions allowed by the TFTP/SFTP
server is compatible with the following:
The maximum number of concurrent NE tasks in the RADview system,
defined in the system console.
The maximum number of concurrent NE tasks per job, defined in the
Advanced Job Parameters dialog box.
For instructions on setting the max number of allowed jobs, TFTP ad SFTP settings
for uploads and downloads, refer to Setting Job Management Service Parameters.
Creating Jobs
You can start the process of creating a job as follows:
• With prior selection of NEs - To go fast, select one or more NEs and/or
groups by right-clicking them and then define the job starting the wizard with
defining the task (Step ).
• Without prior selection of NEs - To build a complex job library, start the
wizard without prior selecting the desired NE(s). The wizard starts with
selecting the desired NEs (Step ).
For an overview over the Jobs wizard, refer to Working with Wizards in Chapter 3.
1. In the Jobs Table Active tab, right-click and then select New Job from the
shortcut menu.
You are now able to select the NEs according to your choice (Step )
3. Select NE(s) according to the desired method (refer to Table 4-47).
Selecting NEs
This section explains how to select the NEs that apply to the desired job.
Note The examples of the dialogs below are provided for Windows 7, but apply to
Windows 2008 Server, Linux and Unix as well.
1. In the Jobs table, click New Job or start the wizard without prior selection
of NEs as explained above.
The Create New Job wizard appears with the NE Selection Method dialog
box (Step ).
2. Select the NE Selection Method and then click <Next>.
The Selection dialog box relevant to the selected method appears
(Step ).
3. Select the desired NEs according to one of the methods listed and explained
in Table 4-47
To discard the selection you made and choose different NEs or a
different selection method, click <Back> and repeat this procedure.
Method Instructions
4. After selecting the desired NEs, click <Next> to start selecting the job itself.
Selecting Tasks
In Step , you select the tasks. Tasks are usually referred to as ‘actions’ in the
user interface and the wizard. For some tasks, you may have to select additional
options at this step.
To select a task:
1. In Step (Figure 4-43), under Select an Action, select the desired task.
For some tasks, additional settings appear from which you have to
choose the ones required for the task.
2. Refer to Table 4-48 for additional information and instructions on these
additional settings.
3. To continue, click <Next>.
Note • In case of Upload Software or Upload Software to Backup, all NEs must be of
the same type. If NEs were selected by selecting a dynamic group or via
criteria, there must be only one criterion for a single NE type and the
condition must be set to Equals.
• Step is skipped unless at least one selected NE does not support the
selected task or you are not authorized to perform this task on them. For
additional information on Step , refer to Validating Tasks.
Figure 4-44. Job Wizard –Upload Configuration Selected (For a Group of NEs)
Allow only actions • Checked. Tasks that are unsupported by at least one If you selected a
supported by all of the selected NEs are listed, but grayed out and dynamic user group, this
selected NEs unavailable for selection. option does not appear
• Cleared. Tasks that are unsupported by at least one of and all the listed tasks
the selected NEs are listed and selectable. When can be selected.
moving on, the system returns a list of NEs that do
not support the task (step ). For further
information, refer to Validating Tasks
Activate congfig file • Checked. Acivates the configuration upon upload. Appears if Upload
upload • Cleared. Does not activate the configuration. Configuration is checked
as illustrated in
Default: Cleared
Figure 4-44
Install Software • Checked. Installs the software and resets the NE. Appears if Upload
• Cleared. Only uploads the software. Software is checked.
Default: Cleared
Note: Some NEs automatically reset after uploading
software, regardless of whether Install Software is
checked or not.
Reboot after Swap • Checked. Reboot the NE after swapping the main and Appears as selectable
backup software files. swap option when Swap
• Cleared. No reboot after swapping main and backup Main and Backup
software files. The swap takes effect only after Software is checked.
manually rebooting the NE.
Default: Cleared
Figure 4-46. Job Wizard – Select Upload License Action (For LA-210)
Validating Tasks
Step is a validation step that the system passes if the current user is not
authorized to perform the task on at least one NE or if at least one NE does not
support the task defined in Step as outlined below.
Activate operation is not The Activate config upload option was selected
supported but the operation is not supported by the NE
1. Click <Back> twice to return to Step and then modify the NE selection.
If all NEs are supported and none of the conditions above apply, Step
is skipped and the wizard moves straight to Step .
1. In Step , edit the name for the task if desired and add a description in the
optional Description field.
By default, the Description field is empty and the name is comprised of the
task name from the ‘Select an Action’ list and the following, dpending on the
number of NEs and whether they are of the same type:
1-2 NEs: <Task name><Name of NE>, <Name of NE>, for example
Execute Script – 172.17.151.209, 172.17.155.17
3 or more NEs of different types: <Task name> - <#> NEs, for example
Execute Script – 3 NEs
3 or more NEs of the same type: <Task name> - <NE type>, for example
Execute Script – LA-210
2. Select the various parameters according to the task you select. These tasks
are explained and illustrated in the sections outlined below.
Note If the job action is Generate Statistics Report, the dialog box Report Parameters
appears before Completing Adding the Job or Scheduling Jobs. Refer to Chapter 5
for details.
The sections below explain selecting and setting task parameters for every job.
Follow the respective link to get to the desired job.
• Collect Statistics
• Download Auxiliary File
• Download Configuration
• Download Log
• Download Software
• Download Software from Backup
• Download User File
• Execute Script
• Execute SNMP Script
• Generate Data Report
• Install Software
• Reboot
• Save Configuration
• Swap Main and Backup Software
• Upload Configuration
• Upload License
• Upload Software
• Upload Software to Backup
• Upload User File
Collect Statistics
For this task, Step sets the system to collect statistical data and store them
in the NMS database for a set period of time. The default is 90 days. For
scheduling options, refer to Scheduling Jobs.
This task is required to display statistical data in RADview-Performance Manager.
Note Before creating and activating this job, verify that your hard drive has sufficient
space to store the statistics data.
In step , you choose to download the MAC table or any other specified file
from the NE(s) to to a specified location on your work station as illustrated
below. The File Name within NE list box displays mac-table as the only available
option.
You specify the download location on your work station beforehand using the
TFTP or SFTP server you installed.
Download Configuration
startup-config Configuration file that resembles the state at the start of the device
Notes
• If some of the selected NEs do not support several configuration files, the
value selected in Source file name within NE is valid only for the NEs
supporting multiple configuration files.
• For the NEs that support a single configuration file, the configuration file that
resides in the NE is downloaded.
• If none of the selected NEs supports file name within NE, or a dynamic group
was not selected for the job, the parameter does not appear.
Download Log
In step , you choose to download the log file according to the label under
Source File Name within NE to a specified location on your work station.
You specify the download location on your work station beforehand using the
TFTP or SFTP server you installed. The example below is set to download the
alarm history.
Download Software
Note • If the parameter Source File Name within NE does not appear, the active
software is downloaded.
• If the Main software file is downloaded, the version attribute in the
configuration archive is obtained from the MIB parameter sysDescr.
In step , you choose to download the software file from the backup to a
specified location on your work station. You specify the download location on
your work station beforehand using the TFTP or SFTP server you installed.
The Source File within NE list box shows, if multiple software versions reside in
the backup of the relevant NE from which you select the desired one.
In step , you choose to download the user MAC address table to a specified
location on your work station. You specify the download location on your work
station beforehand using the TFTP or SFTP server you installed.
Under Source File within NE, the user file name (for example user.dat) is
displayed.
Execute Script
In step , you choose to execute scripts entered via the following three ways to
one or several NEs:
• Selecting built-in and pre-define scripts
• Importing scripts that are saved as text files (*.txt)
• Manually entering CLI commands.
The latter two options allow for running CLI command that are not supported by
a job, for example uploading a license file to a device that does not support the
Upload License job.
For more information on CLI commands, refer to the user manual associated with
the desired device.
Note Menu driven devices do not support the Execute Script job.
2. If required, edit the syntax to enter correct parameters (for example keys or
number of retries under TACAS+). These changes are preserved and take
effect for all selected NEs that support the respective feature when
completing the wizard.
Figure 4-54. Script Preview for ‘ETX-203AM Prepare for Service Config’
To import a script:
1. Click <Browse>.
The Select File dialog box appears.
2. Navigate to the desired file and then click <OK>.
The entire content of the text file appears under Select pre-defined script
and the Select File dialog box closes.
1. In the Execute Script: Job Parameters dialog box (Step ), click <Advanced>.
The Advanced Job Parameters dialog box becomes available as illustrated
under Setting Advanced Job Parameters.
2. In the Advanced Job Parameters dialog box, select Log all job tasks.
3. Once you completed the wizard, in the Jobs Report, click <More details> to
view the result of the script execution (see Viewing Report Details).
In steps and , you choose to generate SLA reports and export them to a
file. For additional information on SLA reports, refer to the RADview-Performance
Manager Manual section. For information on parameters to be set in Step ,
refer to the table below.
Format The available report and file formats depend on the report type you select.
Period Available time periods covered in the report depend on the type you select
CoS Select the service grades you want to include in the report.
Note: Available for ETH OAM only
Distribution
Per CoS Select to compile the service report per servicegrade (CoS)
Note: Unavailable for Daily Raw Data
Number of Months to keep Select the desired number of months from the list.
reports To keep them forever, select All.
In step , you choose to execute the scripts listed below for MP-2100/2104.
For instructions on verifying the execution of the commands, refer to Execute
Script.
Set Net Date and Time for MP- Synchronize the time and the date of
2100/2104 all selected MP-2100/2104 with the
network’s time and date.
Clear Net Alarms for MP-2100/2104 Clearing all current alarms for all
selected MP-2100/2104 devices.
Install Software
In step , you choose to install software that has already been uploaded to the
NE and stored there.
If the selected NE(s) support(s) multiple software files, you can activate a specific
software pack listed under Target File Name within NE.
Note Installing a previous software version may not be compatible with the device and
cause it to fail operating properly. Therefore, you have to verify that the desired
software version is compatible with your current hardware.
Reboot
Save Configuration
In step , you choose to swap main and backup software files in the NE.
Upload Configuration
Last running Use last running configuration file that was archived by a
download job. If such was not found, nothing is uploaded.
For NEs that do not support running configuration file, the
latest configuration file saved in the configuration archive is
loaded.
By Date Use file with the specified date. If such was not found, the
file with the closest earlier date is loaded. If the job action is
Upload Configuration, then for NEs that support running and
startup configuration files, if both running and startup files
have the same date, the file with the latest time is loaded.
Note If the selected task is Upload User File, By Date is the only available upload
option.
Figure 4-65. Upload Configuration File from Local File System to Single NE
2. Click <Browse>.
The Select Path dialog box appears.
3. Navigate to the desired file and click <OK>.
4. Under Target File Name within NE, select the target file name and type.
To upload a configuration file from the local files system to multiple NEs:
Note These instructions apply if you selected multiple NEs of the same type
specifically, for example multiple LA-210 devices.
Figure 4-66. Upload Configuration - From Local File System to Multiple NEs
2. Click <Browse>.
The Select Path dialog box appears.
Note The files are not displayed and the white field in the Select Path dialog box
remains empty.
Figure 4-68. Upload Configuration - From Local File System to Multiple NEs, Path Specified
Notes • If a file is not found for a particular NE, nothing is uploaded to it.
• For all Upload Configuration options, if at least one of the selected NEs
supports the target file name within NE or a dynamic group was selected for
the job, the Target file name within NE parameter is displayed in the dialog
box, with only the startup-config option available.
• In the case of Upload User file, the Target file name within NE parameter is
displayed in the dialog box as a text box that you can fill in.
Upload License
Note The Upload License job is currently supported by LA-210 units only.
To upload a license file from the local file system to a single NE:
Figure 4-69. Upload License File from Local File System to Single NE
2. Click <Browse>.
The Select Path dialog box appears.
3. Navigate to the desired file and click <OK>.
Figure 4-70. Upload License File from Local File System to Single NE – License File Selected
The license file names must include the MAC address of the device to which
the respective file is going to be uploaded. They are composed as follows:
LIC_<MAC address of the relevant LA-210 unit>.txt
If the MAC address is for example 00-20-D2-2A-60-37, the associated license
file name is LIC_0020D22A6037.txt
Note To identify the MAC address of the relevant device, open its shelf view and then
go to System Info or Device Info as explained in the respective RADview agent
manual.
To upload a license file from the local file system to multiple NEs:
Note License files are dedicated to specific devices and are identified by the MAC
address of the respective device as part of their file names. The file names are
composed as explained above.
1. Verify that all license files are stored in the same folder and match the
number and MAC addresses of the LA-210 you selected.
2. Under Load From:, select Local File System.
The Multiple Files option is selected and the Single File option is
unavailable.
Figure 4-71. Upload License Files - From Local File System to Multiple NEs
3. Click <Browse>.
The Select Path dialog box appears.
Note The files are not displayed and the white field in the Select Path dialog box
remains empty.
Figure 4-73. Upload Licenses - From Local File System to Multiple NEs, Path Specified
Note You can upload single and multiple license files from the archive.
Figure 4-74. Upload Multiple License Files via Archive – Selecting the File Option
2. Select the desired license file group. The following license file options are
available:
Note
If you select By Date and the file issued at the specified date is not found, the
file issued at the nearest date is uploaded instead.
Upload Software
Note If you select multiple NEs, all NEs must be of the same type, for example
ETX-203AX.
• Select the desired software version from the Software Version list as
illustrated in Figure 4-77 and Figure 4-78.
Note • If the desired software version does not appear, it is not listed in the RADview
Software File Management Table and must first be imported. For instructions
on importing the software version, refer to the instructions on importing a
software version below. For additional information on the Software File
Management Table, refer to Managing Software File Versions.
• If you upload the software file to multiple NEs and the NEs support multiple
software files, the dropdown list Target file name within NE appears, enabling
you to specify the SW pack as which you want to upload the software file.
• For NEs that support multiple software files, in order to activate the SW pack
you have to create a task to install software. For additional information, refer
to Generate Data Report.
• If multiple software files are not supported by an NE, the software file is
uploaded to the main software.
2. Click <Browse> to navigate to the location and the desired software file.
3. Under SW Version, enter the software version, for example 4.3.
4. Under Comments, add a comment if desired.
5. Click <OK>.
The software is imported and appears listed. It also appears in the
RADview Software File Management Table (explained under Managing
Software File Versions).
To set advanced job parameters and complete this step of the wizard:
3. Click <Next>.
You are moved to the next stop of the wizard.
Parameter Description
Send report to: When this is selected, a text box is available where you can enter one
or more email addresses, separated by semicolons (“;”), to which the
job report should be sent
By default, the text box contains the email address(es) entered in
previous job creations
If Send report to: is selected, you can select which type of report to
send – Summarized or Detailed (default), as well as to send email
only if job was unsuccessful
Parameter Description
Send report only if job fails When this is selected, job report is emailed only if job execution
completes with status not equal to OK
Note: Relevant only if Send report to: is selected
Maximum number of concurrent Specifies how many NE tasks (such as SNMP, xFTP, or Telnet session
NE Tasks for this job between NMS and an NE) can be opened for the specific job. For
Note: Does not appear for action example, if the job applies to 25 NEs, there are 25 NE tasks to
Generate Statistics Report. execute. If this parameter is set to 5, a maximum of five NE tasks can
be executed simultaneity. When one of the five NE tasks finishes, the
next task starts, and so on.
This parameter should be set to equal to or less than the value set in
the system console for the number of concurrent sessions allowed in
the entire system (refer to Configuring the EMS Jobs Management
(Back End)).
Values: 1–200 (default 100)
Set as default If selected, all future new jobs have the security domain of the
current job. Clear this option to cancel setting the security domain
for new jobs.
Clear Click to delete the list of previously defined security domain names
from the dropdown list (this applies to all jobs). This is useful if the
autocompletion feature prevents you from entering the desired
domain name.
Configuration Error Policy Determines the device behavior if an error occurs while NE is loading
Note: Appears only for action configuration file:
Configuration Upload for RAD-OS • Ignore errors and continue loading the file
devices. • Stop loading the configuration file if an error occurs
• Reject the file, reboot, and load the next configuration file in the
following sequence: startup, rollback, user default, or factory
default
Step lists the NEs that do not support at least one parameter you set as
explained under Validating Job Parameters.
The scheduling options in step vary with the selected job. Refer to
Scheduling Jobs to locate the parameters and complete setting up the task.
Note The Generate Statistics Report job uses two wizard steps to set parameters,
therefore the validation of job parameters and scheduling are performed in steps
and respectively.
Note • Unsupported/unauthorized NEs for the selected job and its parameters are not
included in the selection.
• The Job Scheduling dialog varies with available scheduling options, which
depend on the respective job. For additional information, refer to the next
page.
• f a group from the private group tree was selected for the job, only the option
Now appears
• The option Recurring appears only for the job actions Download Configuration,
Download Software, Download User File, Collect Statistics, and Generate
Statistics Report
• For job action Collect Statistics, only the option Recurring appears.
• For job action Generate Statistics Report, only the options Now and Once
appear if the report period is not the previous month; only the option
Recurring appears if the report period is the previous month
• For job action Generate Data Report, only the options Now and Once appear.
Scheduling Jobs
Depending on the specific task, up to three scheduling options are available:
• Running the job now
• Running the job once at a scheduled time.
• Running the job periodically according to a specified recurrence pattern.
Note Make sure that all selected NEs are connected and online at the time when the
task is scheduled to be executed.
Figure 4-83. Job Scheduling – Time Frequency for Collect Statistics and Generate Data Report
Figure 4-84. Job Scheduling – Recurring Pattern for all other Jobs
Parameter Description
Start Specifies the date when the job starts running, according to the recurrence
pattern. A combo-box is available where you can select the date, and a text
box is available where you can enter the time.
End after A text box is available where you can enter the number of recurrences
Default: 10
End by (default) A combo-box is available where you can select the date until when the job
runs
Default: one year later
<Recurence Options>
If a recurring job session is executing, and the next job session is about to
start, the default behavior is to skip the next session.
To stop the current session instead, select Stop current session in the
Recurrence Options dialog box.
Editing Jobs
You can edit jobs that are not running.
To edit a job:
• Select the job, then click Edit Job on the toolbar or right-click and select
Edit Job .
The job wizard opens at step . You can edit the job attributes as
desired, except for the job action, which cannot be changed.
Copying Jobs
You can create a new job with the same parameters as an existing job, except the
copied job has a new job ID.
To copy a job:
• Select the job, then click Copy Job on the toolbar or right-click and select
Copy Job .
• Select the job, then click Properties on the toolbar or right-click and
select Properties .
The Properties dialog box appears, displaying the General tab parameters,
which reflects the task you select and the schedule as explained under
Setting Job Parameters.
Parameter Description
Job Owner Each job has an owner, whose security profile is used for the job.
The default owner is the user that created the job. If you are viewing
properties for a job that you do not own, the job owner is displayed
as a dropdown list that contains the current owner of the job and
the current user. You can select your user name to become the job
owner if you have the relevant permission.
Refer to Job Security for more details.
Security Domain A dropdown list is provided for domain name. By default it is empty,
therefore all users can obtain this job. If you wish to control the
access to the job, you can add a domain name (the domain must be
defined in the user security profile with relevant permissions).
Refer to Job Security for more details.
Set as default If selected, all future new jobs have the security domain of the
current job. Clear this option to cancel setting the security domain
for new jobs.
Clear Click to delete the list of previously defined security domain names
from the dropdown list (this applies to all jobs). This is useful if the
autocompletion feature prevents you from entering the desired
domain name.
Running a Job
This operation is enabled only for a job with status Active, that is not currently
running.
To run a job:
• Select the job, then click Run Job on the toolbar or right-click it and select
Run Job .
The job runs immediately. The progress bar in the Status column is
updated accordingly.
• Select the job in the Jobs table, then click Show Progress on the toolbar,
Performing either of the above actions for a running job opens the job status
dialog box that shows the progress of the job for each NE associated with the
job. The information in the dialog box automatically updates as the job continues
to run.
The dialog box contains a progress bar for the whole job. Next to the progress
bar is the percentage of completion (70% in Figure 4-87), and the information
for how many NEs the job has completed and total number of NEs the job has to
process (four NEs have completed out of 10 total NEs in Figure 4-87). If the job
completes while the dialog box is open, Completed is displayed next to the
progress bar.
Additionally, the dialog box contains a table showing the status of each NE, with
the following parameters:
• NE Name
• IP Address
• Progression – Processing or Completed
• Status – Indicates the current status of the job (see Table 4-55)
• Error – Indicates error if applicable (see Table 4-55).
The following table shows the possible error and status messages.
[10] File is not transferred – no change since last Configuration or Software file has not been
transfer modified since last backup (upload)
[18] TFTP/SFTP server does not exist tftpStatus = error(7), tftpError = 0x0008
[34] NE is not responding after reboot timer NE is not responding after reboot time
expiration expiration
[36] Sanity check after upload failed For FCD-155 and FCD-155E:
sanityCheckTrap received with attached
sysSSanityCheckStatus = fail(2)
For MP-2100/2104:
sanityTrap received with attached
agnSSanityCheckStatus = fail(2)
[37] NE is busy with another TFTP/SFTP session Upon initiating a TFTP/SFTP Operation,
tftpStatus=3 or 4
[38] SNMP request failed SNMP Request Response was received and is
NOT OK (reject, Bad Value, No Such etc) This will
happen usually due to Agent Bug
[39] Reserved
[41] No file received or empty file received Timeout. In case of Download, where status =
ok, but no file received, or file is empty
[45] Reserved
[46] TFTP/SFTP root does not exist TFTP/SFTP Root does not exist (applicable only
for UNIX)
[48] Cannot open SSH session SSH session could not be established
agnSshAccess = disable (2)
[49] Cannot open Telnet session Telnet session could not be established
agnTelnetAccess = disable (2)
[50] Startup configuration file does not exist fileChangeStatus: startupConfigError = 1 and no
entry for startup-config in fileSystemTable
[56] No file with the specified date (or earlier) was On Upload operation
found for the NE
[57] No file with the specified Suffix and/or Prefix On Upload operation
was found for the NE
[59] Software file was not found in Archive for the On Upload operation
NE
[60] User file was not found in Archive for NE On Upload operation
Stopping Jobs
You can stop a job that is running, if it does not contain tasks that have started
processing. Tasks that have started processing cannot be aborted, but pending
tasks can be aborted.
To stop a job:
1. Select the job, then click Stop Job on the toolbar or right-click and select
Stop Job .
You are prompted for confirmation.
2. Click <OK>.
The job is stopped.
Cancelling Jobs
If a job is active and you want to prevent it from executing according to its
schedule, you can cancel it.
To cancel a job:
1. Select the job, then click Cancel Job on the toolbar or right-click and
select Cancel Job .
You are prompted for confirmation.
2. Click <OK>.
The job is moved from the Active tab to the History tab.
Deleting Jobs
You can completely remove a job that is not running, along with all its reports.
To delete a job:
1. Select the job, then click Delete Job on the toolbar or right-click the
desired job and select Delete Job .
You are prompted for confirmation.
2. Click <OK>.
The job and its reports are deleted.
• Select the job in the Jobs Table and click View Reports on the toolbar
button
• Select the job in the Jobs Table, then right-click and select View Reports .
The above actions open a tab in the Reports pane displaying a list of reports for
the job. The tab is named according to the job ID: “Job <ID>”.
By default the table rows are displayed sorted by time, from newer to older. You
can click column headings to sort by the columns.
Parameter Description
Job ID Job ID
Note: Appears only in Latest tab.
Job Name Job name
Note: Appears only in Latest tab.
Executed at Starting date and time, in the format: YYYY-MM-DD HH:MM:SS
Number of Entities Total number of NEs for which job was executed
Succeeded Entities Number of NEs for which operation succeeded
Note: Not visible by default.
Failed Entities Number of NEs for which operation failed
Duration Total time of job execution, in the format: HH:MM:SS
Report ID A number that is used to uniquely identify the report, set by the
Note: Not visible by default. management system at report creation
Report Operations
You can perform report operations via the toolbar, or via right-click menu in any
of the tabs.
Save Report Saves the report to a file in the local file system. You can select
which parts of the report to save, and select the type of file
(Comma Separated Values, HTML, or PDF)
Properties Displays a dialog box showing the contents of the report columns
[Not Show Latest Determines the number of displayed report summaries in the
applicable] Note: Appears only Latest tab. To change the value, enter the desired value and then
click <Enter>.
in Latest tab.
File type – csv for job action Generate Data Report, or pdf for job
action Generate Statistics Report
Error – Indicates error if applicable: Empty if no error occurred,
otherwise indicates failed to generate csv/pdf file
Result – Provides link to the report file if no error occurred, otherwise
provides link to log file if logging of all actions or logging of errors
was selected in the job parameters.
Note You can save (as CSV (Comma separated values)) or print the job report by
clicking <Save Report> or <Print Report>, respectively.
Job Security
Security profiles contain permission tags that control permission for particular
functions, specifying access as read, write, or not available. A security profile can
also contain permissions for access to particular NEs. Domains with subsets of
permissions can be created in security profiles. For detailed information on
Job Actions
Upon job creation the user security profile is checked as follows:
• Job action – Check if user has permission to perform the particular job action
(download, upload, etc.)
• NE access – Check if user has permission to perform this job action for each
NE.
If job action authorization fails, the job is not created. If NE authorization failed,
the job is created but when it runs, the actions are not performed for the failed
NEs.
The following apply when editing a job in the Job Properties dialog box and job
wizard:
• You can edit a job that has a security domain if the domain job_modify tag
has write permission
• You can edit a job that has no security domain if your user security profile
job_modify tag has write permission.
• You can change the job security domain according to the relevant
permissions, as shown in table Table 4-58.
• In the above cases if job_accessible tag does not have read or write
permission, a warning message is displayed:
Using current security domain may cause this job to be
inaccessible. Continue?
• If the new security domain is not defined in the user security profile and
job_modify tag has read permission, a message is displayed:
Access Denied. Check security domain.
Current Security Domain First Permission Checked New Security Domain Second Permission Checked
None OK only if user security profile None or not defined OK only if user security profile
job_modify tag has write job_modify tag has write
permission. permission.
Defined OK only if current job_modify None or Not Defined OK only if user security profile
tag has write permission. job_modify tag has write
permission.
Not Defined OK only if user security profile None or Not Defined OK only if user security profile
job_modify tag has write job_modify tag has write
permission. permission.
Note
If a job security domain is set to a domain _with job_accessible tag that has no
permission, the user has no more access to the job. Only the administrator or the
user with the new domain can change back the security domain of the job.
Refer to Chapter 6 for detailed examples of working with job security profiles.
Job NEs
Some NEs may be invisible to the user who created the job, according to the
relevant permissions. If a job includes NEs that are invisible to the creator, all NEs
are still displayed in the job wizard and in the job reports. Therefore you should
avoid this situation, and create only jobs that contain NEs visible to the user.
• New Job - User can’t use these NEs or groups, therefore can’t create a new
job with them
• Edit Job - Job that contains invisible NEs (for this user) can be edited by the
user. The NEs are visible to the user but can’t be removed from the job. In
the wizard step selecting NEs, the NEs are displayed on the selected list as
disabled and are not selectable. In the wizard step action validation, the
validation messages are displayed.
The following figure shows an example where the user profile does not allow
access to the subtree /ETX-203A.
In the Job Wizard step where NEs are selected, the sublevel is not visible.
Job Groups
If a job is created with a public or shared groups, all users can see this group, and
hence edit this job.
If a job is created with a private group, only the user who created the private
group can see it. If other users, including the administrator, attempt to edit the
job, the message Access Denied is displayed. If a job is created with a private
group, only the Now option is visible in the job wizard schedule step.
Job Execution
When a job executes, the following is checked, according to the user security
profile of the job owner:
• Job action – Check if job has permission to perform the particular job action
• NE authorization – Check if job has permission to perform this job action for
each NE (e.g.: U ser security profile may have only permission to download
from NE 1, and only permission to upload from NE 2.
Notes • ‘Download’ refers to file transfers from network elements to the NMS
• ‘Upload’ refers to file transfers from the NMS to network elements.
Column Description
IP Address NE IP address
Last Startup Changed Date and time when the NE configuration was last changed. The time
displayed is the time normalized to RADview time (refer to Normalizing
Date and Time).
Last Config Backup Date and time when the NE configuration was last backed up. If the NE
device maintains several configuration files, this applies to the
startup-config file.
Last Boot Time Date and time when the device last rebooted. The time displayed is the
time normalized to RADview time (refer to Normalizing Date and Time).
Note The above apply to NEs that support fileSytemTable. For NEs that do not support
it, RADview displays ‘--‘.
View Files Opens a tab in Archive Files pane Single row selected
Note: You can also displaying archive file information, if
double-click the any is available
row.
Note Files downloaded from the NE to the EMS server are stored in the file repository.
For information on the location and structure of the file repository, refer to
Table 4-31.
You can display archive file information for a particular NE, by doing any of the
following:
• Double-click the NE in the Configuration Status Table
• Select the NE in the Configuration Status Table and click on the toolbar
button
• Select the NE in the Configuration Status Table, then right-click and select
View Files.
The above actions cause a list of archive files for the selected NE to be displayed
in the Archive Files pane. The NE Name is displayed in the pane title.
Note If no files have been uploaded to or downloaded from the NE, the list does not
contain any entries.
The Archive Files table is a customizable table, meaning the following main
features:
• You can select which columns are visible. By default, the following columns
are visible:
Status
Executed at
Number of NEs
Scheduling
Active
Status.
• You can change the order of the table’s columns.
• You can sort the table according to the columns
• You can filter the table according to the columns.
Refer to Chapter 3 for more information on customizable tables.
Column Description
SW Version This field is relevant if File Type = software, and the file is the
main software file. If the file was loaded from backup, ( ) is
displayed before the SW version number to indicate that it was
user-defined, and can be edited via the Software File
Management dialog box (see Managing Software File Versions).
In all other cases ‘--‘ is displayed.
Date & Time Date and time when file was saved in archive, in format
YYYY-MM-DD HH:MM:SS
Column Description
User Name User name of the user that owns the job that loaded the file
from/to the NE
View File Opens a text viewer. Applicable only for the following types of Single row selected
files:
• User text file
• Startup configuration
• Running configuration
• CLI script.
This opens the job wizard (refer to Figure 4-42) at the Select Action step. The
parameters in the steps are preselected as follows:
• NE Selection Method step (see Selecting NEs):
Explicit option is selected.
• NE Selection step (see Table 4-47):
NE from the Archive File table row is selected. You can add any other NEs
to the list.
• Select Action step (see Selecting Tasks):
Only the following actions are available in the action list, and only if the
NE supports these actions:
If SW file was selected – Upload SW and Upload SW to Backup.
If configuration file was selected - Upload Configuration
If user file was selected – Upload User File.
• Job Parameters step (see Setting Job Parameters):
If SW file was selected, the Software Version field in the Job Parameters
dialog box displays only the version of the selected file.
If configuration file or user file was selected, Load from Archive is
selected in the Job Parameters dialog box, and the file that was selected
to upload is selected on the list. If more NEs were added in the NE
Selection step, you cannot select the file requested to upload.
Marking as Baseline
This action is applicable only for configuration files. You can mark a configuration
file as baseline, by selecting the row in the Archive File pane, then right-clicking
and selecting Mark as Baseline.
When the file is marked as baseline, the icon is displayed in the Baseline
column.
If a file is already marked as baseline, you can unmark it by selecting the row,
then right-clicking and selecting Unmark as Baseline.
Note If there are multiple occurrences of the same file, the file is marked as baseline in
only one of its occurrences. The file is identified according to its index (per NE) in
the file system by RADview.
The section for an external tool contains lines defining the following attributes:
Note A line for an attribute starts with <attribute> and ends with </attribute>.
• name – Specifies the name used for the external tool in the menus and
External Tools tab in the dialog boxes
• cmd – Specifies the beginning part of the external tool command line,
identifying application or shell command to execute
Notes • If the tool has no parameters, you can leave out the <param> line or define it
as empty: <param></param>
• The <param> attribute can be customized for a particular network element in
Command Parameters: in the External Tools tab of the Node Properties dialog
box (see Configuring Existing Network Elements). If this is done, the <param>
attribute is stored in the EMS database associated with the object for which
customization was done, and is used for command line generation for the
object rather than the original value defined in ntools.xml.
• icon – Specifies the icon to use for the external tool menu entry. The icon
should be in PNG/GIF/JPG format, 16x16 pixels with a transparent background.
It should be placed in c:\rv32\ems\images\ntm\tools.
Note The icon attribute is optional. If you do not specify it, a default tools icon is
used.
• securityTag – Specifies the external tool security tag label string (optional),
which can be configured later in security profile(s) to meet specific security
policies.
The new external tool appears in the External Tools submenu that is
displayed when you right-click a network in the navigation tree and select
External Tools.
Column Description
NE Type Type of NE
File-> Import Import Opens a dialog box to introduce a new SW file (see Always
Adding Software Files)
File> Export Export Opens a standard dialog box to save a selected SW Single row
file to client’s file system selected
File > Export Export Table Opens a dialog box to export the table to a format Always
Table such as CSV (Comma Separated Values), PDF, or
HTML
File > Print Print Table Opens a standard dialog box to print table Always
Table
File > Properties Opens a dialog box to display file properties (also Single row
Properties via double-click) selected
File > Close Closes the Software File Management dialog box Always
Edit > Mark as Mark as Marks the selected file(s) as obsolete. If a file is Any row(s)
Obsolete Obsolete marked as Obsolete, it is not displayed in the Job selected
Parameters dialog box (see Setting Job Parameters).
Edit > Mark as Mark as Valid Marks the selected file(s) as valid Any row(s)
Valid selected
Note Verify that the file being imported is a valid software file for the particular device
before you import it.
The Import SW Version dialog box appears. You can click the next to
SW Version to display an explanation of the SW version format.
Note The following figure shows the previous SW Version format, which is still
supported.
Parameter Description
File Software image file. You can enter the full path (including file name) or
click <Browse> to select the file from the local file system
NE Type You select the NE type, from the alphabetically ordered list of NE types
that are installed in RADview. You can type the initial letter(s) for
convenient navigation.
SW Version
SW version. Click to display a description of the SW version format
1. Select the software file entry, then click on the toolbar or from the main
toolbar select Properties.
The Properties dialog box appears. Refer to Table 4-63 for a description
of the parameters.
2. If desired, edit the following parameters:
Status
Comments
SW Version (editable only if SW file was downloaded from backup).
3. Click <OK> to save your changes.
1. Select the software file entry, then click on the toolbar or from the main
toolbar select Delete.
You are prompted for confirmation.
2. You can select the option Also delete all references in the Archive, if you
want to delete references to the software file from the configuration archive.
Note If you select the option to delete references in the archive, the archive file is not
deleted; only the reference to the SW file is deleted.
2. To view the RADview package contents, expand RADview EMS and EMS
Products.
3. To view jar files and their versions associated with a specific product, expand
the relevant product tree as illustrated below.
Figure 4-108. Version Browser – Product Tree Expanded to Display Jar Files
Notes • If the product name cannot be ‘expanded’, the associated device does not
have a RADview shelf view and therefore no jar files to display.
• If a product is indicated as Legacy, it has a legacy non-RADview shelf view. For
some of these legacy devices, the shelf view is supported only if the EMS
client station has direct SNMP connection to the device. For a complete list
refer to the RADview release note.
• If a product is indicated as RvLite, it can be accessed via Web and Telnet. The
web-based application is supported on Windows 7 or Windows Server 2008
only if you install Mozilla Firefox as your default web browser.
2. Choose the desired options for saving and then click <OK>.
3. Browse to the location in which to save the file and then click <Save>.
The table data is saved in the format Comma Separated Values (CSV),
which can be viewed in Microsoft Excel or any other compatible viewer.
2. Choose the desired options for printing and then click <OK>.
3. Select the desired printer and then click <OK>.
The table data is sent to the selected printer.
• EMS backup – Backs up the RADview (EMS) system files and PM (RADview-
Performance Manager) image files.
• License backup – Backs up the existing RADview license files.
Note There is no backup and restore support for Jobs and Configuration files. If you
would like to back up these types of files, refer to Defining Backup/Restore for
Additional Files.
You can perform both the backup and restore operations from the same
computer or from different computers.
Note Do not use the Backup and Restore tool with a RADview (EMS) station and a
non-RADview station.
• The source and destination stations require the same structure of the
RADview system with respect to clients and servers.
• The same version of the Backup/Restore tools should be used in the process
(the Restore script verifies this requirement)
• When backing up/restoring the database, the same database version should
be installed on the source and destination stations
• The same version, the same installation, and the same installation directory
should be used if Backup/Restore includes data from third-party products
used by RADview (e.g. Oracle).
Parameter Value
<dbtype_oracle> true
<dbtype_informix> false
Note You can back up files from hard drives other than the RADview installation drive,
but they are restored to the RADview installation drive; they are not restored to
the hard drive from which they were backed up.
Note If you schedule backups to be performed regularly, you have to closely monitor
the available space on your hard disk You may need to periodically delete older
backups.
After any backup operation finishes, these files are located in the relevant
directory according to the backup mode:
• Compressed file mng164_backup.zip containing backed-up data
• Compressed file mng164_backup_extra.zip containing additional backed-up
data if mng164_backup_extra.ini specified additional data to back up
• Backup log file (mng164_backup.log).
Read mng164_backup.log carefully to verify that there were no warnings/errors
during the backup process.
If the backup was successful, the WORKING directory is renamed to CURRENT.
Note Before running the restore tool, read the backup log file from the backup that
you intend to use for the restore, to verify that all the parts you want to restore
were backed up successfully. Otherwise, the tool exits with an error message.
The indicators appear for restore purposes. The last two rows are displayed once
the backup completed successfully.
informix_backup = false
oracle_backup = true
map_backup = false
security_backup = true
ems_backup = true
license_backup = true
BACKUP_REQUIRED_SPACE = 85104 Kbytes
2014/03/05 12:32:09 Archive file is created: mng164_backup.tar
Backup file is compressed
Backup completed 2014/03/05 12:32:10
WORKING directory renamed to CURRENT
Caution • If the restore process failed due to active RADview processes, you have to
close them and repeat the restore procedure. If you cannot close them, open
the Task Manager and end all mng164 processes manually.
• The restore process may take a few minutes. Let the process run until it
completes. Stopping the restore process while it is running may cause
database corruption and other problems
10. If RADview Server is installed on your station, you have to start it after the
restore process ends. You can do so by one of the following:
Reboot the system,
- or -
From Start > Control Panel > Administrative Tools > Services, select
RADview EMS Server and start the service.
Note Automatic Backup Restore is supported by Windows 2008 R2 Server and Windows
2012 R2 Server only.
Setup
Follow the procedure below at both the source and destination workstations, to
set up the autobackup/restore mechanism. If the FTP site does not exist yet on
the relevant station, you have to run a script provided by RAD to create it as
explained below.
• At the destination workstation, specify the following autobackup/restore
parameters in the file mng164_autobackup.xml in <RVPATH>\BackupRestore:
Enter the IP address of the destination workstation for the XML tag
<ftp_destination_ip>.
Enter the destination folder with the entire path on the destination
workstation for the XML tag <ftp_destination_path>.
Set the XML tag <keep_ems_running_after_restore> to
true for the source station and to false for the destination station
The content of mng164_autobackup.xml is illustrated in Figure 112. The FTP site
is set up, and the Backup and Restore configured using the command prompt at
the respective workstation.
Note • In order to configure Backup and Restore, you must be logged on as a user
with full Administrator rights.
• Do not use <RVPATH>\BackupRestore as destination folder. This folder is
reserved for the Backup and Restore script files. The default folder to use as
destination folder is C:\users\RV32\BackupRestore.
<configuration>
<auto_backup_restore_version>1.00</auto_backup_restore_version>
<!-- info of backup station, required for main station autobackup and
backup station config -->
<ftp_destination_ip>172.18.159.58</ftp_destination_ip>
<!-- info of backup station, required for autorestore and backup station
config -->
<ftp_destination_path>C:\users\rv32\BackupRestore</ftp_destination_path>
Note By default, <RVPATH> stands for C:\RV32, unless you selected a different drive
and/or folder name when installing RADview.
Note By default, <RVPATH> stands for C:\RV32, unless you selected a different drive
and/or folder name when installing RADview.
C:\users\RV32\BackupRestore\WORKING>c:\RV32\BackupRestore\zip.exe -r -u -q
C:\users\RV32\BackupRestore\WORKING\mng164_backup.zip *.*
=====================================
Backup finished 2014-01-23-13.36.36
WORKING directory will be renamed to CURRENT.WORKING directory renamed to
CURRENT
Figure 119. Example of mng164_backup.log (after Autobackup)
Scheduling Autobackup/Restore
4. To define the trigger that causes the task to run, open the Triggers tab.
The Triggers tab appears.
Net Inventory
The Net Inventory application allows you to display an inventory table
(see Figure 4-131) for all products that support the Entity MIB.
Note Refer to the list of supported products in Chapter 1 for information on which
products support the net inventory application.
When you start the Net Inventory application, it reads information from all nodes
representing agents on the map that support Entity MIB. The first time you start
the Net Inventory application, you may be prompted to confirm the data refresh,
as it is a potentially time-consuming operation.
The data refresh synchronizes the Net Inventory with the RADview map, and adds
all nodes on the map that support Entity MIB to the Net Inventory table. This
synchronization is not done automatically when nodes are added to the RADview
map. Therefore it is recommended to periodically synchronize via Refresh->
Synchronize All. To ensure that the Net Inventory table is updated when nodes
are added to the RADview map, use Refresh-> Add New Nodes From Map.
Note Any user other than root must have the legacy role function in the user profile in
order to have permission to open the Net Inventory application (refer to
Chapter 6 for details on user profiles).
The table is a hierarchical system. When you click the icon to the left of an entity,
the tree expands to display all entities that have the selected component ID in
their entPhysicalContainedIn MIB parameter. You can sort each column if the
left-hand tree is at the node level.
Note In order to save/print the entire display, verify that no rows are selected
(click <Ctrl> and the left mouse button to deselect any selected rows).
Parameter Function
<Edit…> Opens a dialog box to edit the parameters of the selected row
<Expand All> Expands all entities to display all subordinates down to the lowest
level
<Collapse All> Closes all tree entries to display node level only
<About> Displays info about the program, such as version and licensing
information
3. Click any parameters that you want to use as a filter, and enter the filter
criteria.
4. Click <OK>.
Only those Nodes that have entities matching all the filter criteria are
displayed.
Parameter Function
Class If selected, choose value from dropdown list for filtering: Modem,
Chassis, Back-Plane, Slot, PS, FAN, Sensor, Card, Port, Stack, CPU
Parameter Function
FRU If selected, choose Yes or No from dropdown list to filter for field
replaceable units or non-field replaceable units
Editing an Entity
To edit an entity:
1. In the Inventory Table, select an entity (row) and click <Edit>.
The Edit dialog box appears (see Figure 4-133).
2. Modify the desired parameters.
3. Click <Set>.
Expanding/Collapsing Sublevels
Maintenance Windows
In order to avoid error results on RADview-PM during scheduled down times of a
specific resource, RADview allows scheduling maintenance windows during which
RADview-PM does not receive data from the respective resource.
You can schedule maintenance windows as explained in the instructions below.
The interface to define maintenance windows is available from RADview Network
Manager.
3. Select the maintenance type from the list. The maintenance type is for
information only and does not have any effect on the maintenance window.
4. Click <Add>.
You are asked to link the maintenance window with the required resource
as illustrated below.
Figure 4-137. Defining New Maintenance Window – Specifying Name and Linking Resources
Figure 4-139. Maintenance Windows Dialog Box – New Maintenance Window Added
Licensing
The RADview licensing mechanism protects the system by restricting its
installation to the specific host for which the license was generated.
Product-specific licenses can be ordered in incremental license point sizes, to
allow optimal correlation between the types of managed devices and size of the
network, and the price of the management system.
Available Licenses
This section lists and explains the available licenses. There are two types of
licenses:
• ENW (Equivalent Node Weight) license – Entitles you to a certain amount of
license points that should be high enough to allow for the size and the type
of managed network elements, as well as the number of nodes in the
network. For additional information on license points for specific devices,
refer to your local distributor.
• Licenses for additional resources and modules – Some resources require a
separate license to be installed before you can activate and use them:
EMS-MAP – You must install a license for the RADview Network Manager
before you can log into it
EMS-Clients – If you want to have more than five users logged into
RADview simultaneously, you must install a license for multiple RADview
clients.
RV-LIC/SERVICE-MANAGEMENT – To use RADview-Service Manager (SM)
and/or RADview-Service Center (SC), you must have the Service-Manager
license installed. If you try to use these modules without this license, an
error message appears.
RV-LIC/PERFORMANCE-MANAGEMENT – To follow the performance using
the Performance Monitor (PM), you must have the Performance-
Monitoring license installed. If you try to access the Performance Monitor
without the proper license, an error message appears.
DXC-100 –A license must be installed before you can activate the DXC-
100 shelf view.
For an illustration of the licenses listed in the License Service Manager, refer to
Figure 4-140
and introduces its components. The License Service Manager has the following
two tabs:
• Genaral tab – Lists all the licenses and displays their status. For additional
information, refer to Table 4-67.
• Managed Element List tab – Lists all the devices that are managed by
RADview. For additional information, refer to Table 4-68.
• From the RADview Network Manager menu, select Tools > License
Manager.
The License Service Manager dialog box appears with the General tab
open as illustrated in Figure 4-140.
For information to what is listed in the General tab of the License Service
Manager, refer to Table 4-67.
Figure 4-140. License Service Manager – General Tab (Windows Client Connected to a Windows RV
Server)
Note If a temporary license has expired, it is displayed as a red line in the table.
Parameter Function
Total installed license points Total License Points to which the user is entitled (for all
valid licenses that have not expired)
Parameter Function
Consumed license points License Points that the user has already used (for
RADview managed elements)
This parameter allows uses to follow up on the growth
of their system.
For information on calculating license points required
for various devices, refer to Calculating License Points.
Parameter Function
Note • You can manage one agent from different RADview maps at the same station
without requiring an additional license. The RADview license service makes
sure that different logical representations of single network elements do not
require duplicate licenses.
• A managed element is deleted from the list when it is deleted from the map of
the client. If you delete it while this application is open, the change is not
reflected in the Managed Element List until you refresh the entry (File >
Refresh).
• By default, the list is ordered by IP address. You can sort the list by clicking on
any column and toggle between ascending and descending order.
Note • When the License Server is stopped and you try to log on, an error message
appears indicating that you do not have a sufficient license installed.
• If you are already logged on and you try to access and configure a network
element, an error message appears indicating that no valid license is available.
RADview logs off automatically after a several minutes.
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 500.
Required license points = Total Number of License points (for all types) −
RADview package bundled license points
The following is an example of calculating license points for a network to be
managed by RADview, with the following elements:
• Four Egate-100 units
• Eight ETX-202 units
• Ten FCD-E1E units
• Five FOMi-E3/T3 units.
Referring to the RADview License Calculator, we find that:
• Egate-100 = 130 ENW
• ETX-202 = 15 ENW
• FCD-E1E = 15 ENW
• FOMi-E3/T3 = 30 ENW.
Considering the bundled license points table (see Table 4–69), we find that:
• The RADview package includes a 300-point free-of-charge bundled license.
Thus, the license you need to order =
[(4x130) + (8x15) + (10x15) + (5x30)] – (300) = 640.
Explanation: since the actual license size that is needed to manage the given
network is 940, and 300 points are bundled free-of-charge within the RADview
package, you need to order only 640 license points.
Green Normal
Blue Warning
Orange Major
Red Critical
Red Disconnected
Interface Components
Supported Devices
Some RADview legacy devices do not support all the Resource features. The
following devices support all Resource features:
• ETX 203A version 3.0 and up
• ETX 203AM version 4.0 and up
• ETX 203AX version 4.0 and up
• ETX 204A version 3.0 and up
• ETX 204AW version 3.0 and up
• ETX 205A version 4.0 and up
• ETX 220A version 4.0 and up
• Resource
• Alarm Severity
• Resource ID
• IP Address
• Class
• Description
• NER Level
• Admin. Status
• Oper. Status
• HW Ver.
• SW Ver.
• Alias
• Sys Location
• Link to Node
• Customer.
Refer to Chapter 3 for more information on customizable table functions.
Parameter Description
Contained In Name of parent node, if the parent node Class is Device or Chassis, otherwise
blank
Description Description of the resource, , according to the description in the device
information
NER level Level of entity in map
Admin. status Administrative status of resource:
Up –Administratively enabled
Down –Administratively disabled
Testing – Test is running (applicable to class Port only)
Note: This is displayed only for fully supported devices (see Supported Devices), if
the class is Port or Card.
Oper. status Operational status of resource:
Up –Administratively enabled
Down –Administratively disabled
Not Present – Entity is not present in device
Testing – Test is running (applicable to class Port only)
Note: This is displayed only for fully supported devices (see Supported Devices), if
the class is Port or Card.
HW Ver. Hardware revision of the resource
SW Ver. Software revision of the resource
Alias Alias name for resource
Sys Location Location of resource, if Class is Device, according to the location in the device
information
Link to Node NE Name of device to which resource is connected on map, if Class is Port
Customer Customer associated with resource,if Class is Device, Chassis, or Port
To change the customer, click the browse button to display a list of customers,
then select the customer to which to assign the resource, and click <Select>.
FW Ver. Firmware revision of the resource
FRU Indicates whether entity is Field Replaceable Unit
True – This entity can be replaced in the field
False – This entity cannot be replaced in the field
Serial Number Resource serial number (usually read from the hardware)
Note: The serial number is unique for each device. It should be initialized only
once and not changed after that, because if the serial number is changed while
the device is connected to RADview EMS,then RADview EMS considers the device
to be a different device.
Asset ID Identification information added to the resource. It can be used to indicate the
Configuration Status Letter (CSL) of the unit component.
To edit a resource:
1. In the Resources workspace, select the resource that you wish to change,
then right-click and select Edit Resource.
The Edit Resource dialog box is displayed (see Figure 5-5).
2. Change the editable fields as necessary (refer to Table 5-2).
3. Click <Set>.
The changes to the resource are performed.
Description Filter
Options Filter
Parameter Description
Reconnecting
Click <Reconnect> to restart the SNMP Spy process according to the new settings.
Note Enabling the SNMP spy worsens system performance. It should be enabled only
when necessary, and then disabled when no longer needed.
Parameter Description
Info
Tracing
Global Level Level of message that appears in the main server tracing window
Debug Action Enables Technical Support personnel to insert debugging commands in the
EMS server; for use only by Technical Support
SNMP Spy Enabled When this option is selected, it enables monitoring of SNMP Spy messages
4. Edit the parameters as needed, then click <Set> to save your changes.
Notes • To add, edit and remove users, it is required to be logged on as a user with
Administrator rights.
• For security reasons, it is recommended to change the initial password that
has been set upon installing the RADview application.
Note Only users with Administrator rights can make and apply changes to settings in
the EMS Security Administrator.
1. From the RADview Manager menu, select Tools > Admin Console.
The Admin Console appears.
2. In the Admin Console’s navigation pane, select Security Service.
The Profiles tree appears with existing security profiles and users.
The Security Administrator displays the following:
• Profiles Tree: Lists all available security profiles as follows:
- Profile with one or more users assigned to it
Figure 6-3. Admin Console: EMS Security Administrator – With Default Profiles
Adding Users
This section explains how to add a new user and base it on an existing security
profile.
Note Only users with Administrator rights can make and apply changes to settings in
the EMS Security Administrator.
To add a user:
1. From the EMS Security Administrator window, select User > Add...
The Add User dialog box is displayed (see Figure 6-4).
2. Under User Name and Description, enter the desired user name and a
description (optional) respectively.
3. To base the new user on a security profile, select Profile and select the
desired user profile.
4. Under Password, enter the desired password.
Note If the Temporary Login option was enabled, the new user becomes invalid at the
specified expiry date and becomes. This might be useful for team members in the
lab who stay for a limited period of time.
Editing Users
This section explains how to change properties of existing users. For instructions
on changing the user’s password, refer to Changing User Passwords.
To edit a user:
1. Under User(s), select the desired user.
2. From the menu, select User > Edit…
The Edit User dialog box is displayed (see Figure 6-5).
3. Make the desired changes to User Name, Description, Profile and/or Lock.
4. Click <Set>.
The changes are applied.
Note • This entry is enabled only when an entry in the Users Table is selected.
• When Admin Lock is selected, the user cannot use the system until the
Administrator clears Admin Lock.
6. Click <Set>.
The new password is set and applies when logging with this user the next
time.
Removing Users
To remove a user:
1. Under User(s), select the desired user.
2. From the menu, select User > Remove.
The Confirm User Removal dialog box is displayed (see Figure 6-7).
3. Click <OK>.
The selected user is removed.
Note Only the Administrator can log out a user from this menu.
Overview
A security profile is a set of permission tags organized in a hierarchical tree as
illustrated in Figure 6-9. Permission tags may represent single permissions or
group permissions that consist of a set of single permissions. Single permissions
represent one operation in one of the EMS applications or in one of the shelf
view applications. For an overview of permission tags and available permissions,
refer to Table 6-2.
Table 6-2. Permission Tags – Types and Permission Levels
Icon Permission
Icon Permission
Note The RADview server automatically loads all permission files after
installation/upgrade. Therefore you do not need to load permission files before
assigning permissions to a profile.
Figure 6-9 shows the available permissions that have been uploaded from the
permission file in the right pane and the individual permissions that have been
assigned to a profile in the left pane.
The types of profiles are:
• Mandatory – Built-in profiles: Administrator, Operator, Monitor, Technician
• User-defined – Based on an existing profile or created “from scratch”.
• Through the All permission tag that functions as a group and includes all
Notes • The benefit of including group permissions is that if you load an updated
permission file in the future, all existing profiles that are included in this group
are updated automatically.
• Single labels that were included without their group label are not updated.
• Write
• Read
• No Access .
You can change the access rights by double-clicking the permission icon. This
select a single permission and drag the selected item to an empty space
in the profile tree.
The permission is added to the correct place together with the folder
item that it belongs to.
Note If you drag a permission to an incorrect place, a message appears indicating that
the selected place is inconsistent.
To delete a permission:
1. In the Profile view, select a permission or a folder item.
2. Click Delete.
The selected item is deleted.
Basic Permissions
Figure 6-14 shows the basic permissions displayed in the right pane of the
Security Administrator:
• audit_perm – Group of labels for audit functions
• global_perm – Group of labels for global functions
• admin – Tree of labels for Admin Console functions, including jobs and
configuration management, log, maintenance management, ner and pm
(RADview Performance Portal as illustrated in Figure 6-15).
• business_entity – Tree of labels for Business Entities workspace
• catalog – Tree of labels for the catalog functions, such as catalog creation,
catalog CoS view etc.
• config – Tree of labels for general configuration functions including SC-TDM
and device-specific functions. Each device tree contains labels for
device-specific functions, grouped for technician, monitor, and operator
profiles.
• fault – Tree of labels for Event Browser functions (see Figure 6-15)
• launchdesk – Labels for LaunchDesk/Network Element Manager functions
(see Figure 6-15)
• legacy_roles – Group of labels to allow access to legacy applications and
devices (see Figure 6-15)
• resources – Tree of labels for Resources workspaces
• service –Tree of labels for service creation, updating, provisioning,
unprovisioning, activation, deactivation
• topology – Tree of labels for Topology Entities workspace
• transport – Tree of labels for Transport workspace.
For further information on permission tags, refer to Table 6-3.
Note You can create permission files containing permission tags to provide security for
third-party applications such as external tools added to the RADview Network
Manager, by creating a file in C:\RV32\ems\admin\security (in the same format as
the existing files in the folder), and loading it as specified in Manually Loading
Security Profiles.
Figure 6-14. Edit Profile View with Profile and Basic Permissions
Permission Tags
The following table shows the functionality granted by the various permission
tags in the permission groups.
TOOLS_RADiflowIServer Opening the RADiflow iServer application (if SIS products are
installed)
TOOLS_RADiflowISIM Opening the RADiflow iSIM application (if SIS products are
installed)
maintenance_accessible
maintenance_create
maintenance_modify
maintenance_delete
maintenance_operate
maintenance_view
instances_view
instances_delete
Note
This section refers to EMS Maintenance, a functionality to be implemented in the
future.
Table 6-14. config Folder – Permission For Configuring Devices using Shelf View
Note
This table lists and explains general shelf view permission tags. In addition, this
folder contains all permission tags for configuring the agents. These tags are self-
explaining and therefore not listed here.
Table 6-15. fault Folder – Permission For Configuring Devices using Shelf View
Table 6-16. launchdesk Folder – Permission For Configuring Devices using Shelf View
SERVICE_provision Complete the service wizard with designing and provisioning the
service
Close -- --
• With read permission user can open the wizard to define a job, but can’t
create it. Pressing <Finish> is allowed only with write permission.
• Security is checked only upon pressing <Finish> in job wizard.
• With read permission user can open the wizard to view the job, but can’t
modify it. Pressing <Finish> is allowed only with write permission.
admin/jobs/Jobs_action_perm/download_software WRITE
admin/jobs/Jobs_action_perm/download_user_file WRITE
admin/jobs/Jobs_action_perm/upload_configuration WRITE
admin/jobs/Jobs_action_perm/upload_software WRITE
admin/jobs/Jobs_action_perm/upload_software_to_backup WRITE
admin/jobs/Jobs_action_perm/upload_user_file WRITE
admin/jobs/Jobs_action_perm/execute_script WRITE
admin/jobs/Jobs_action_perm/swap_main_and_backup_software WRITE
admin/jobs/Jobs_action_perm/reboot WRITE
admin/jobs/Jobs_action_perm/activate WRITE
admin/jobs/Jobs_action_perm/reboot_after_action WRITE
Properties -- --
Properties -- --
Note All permission files must be loaded before you perform the first Add/Edit Profile
or Add/Edit User.
Adding Profiles
You can add new security profiles based on existing security profiles and then
modify them. You can also add security profiles and assign permissions ‘from
scratch’.
In addition to a new profile, you have to add a new user based on the new
profile. This way, you may create a user group that has limited access based on
the permission granted to the new profile.
Figure 6-18. Add <New Profile Name> Profile Dialog Box – Base Profile Operator
To verify that the permissions from the base profile were adapted:
1. In the Add <New Profile Name> Profile dialog box, click launchdesk in the left
side column (Profile) and the right side column (Basic Permission).
The permissions displayed for the base profile and the new profile are
displayed and matching (see Figure 6-19).
Figure 6-19. Add <New Profile Name> Profile Dialog Box – Base Permissions
2. Change permissions as desired for the new profile on the left side as
explained under Working with Permissions.
3. Click <Set>.
The new profile is added under the associated base profile (in this case
Operator).
Base Profile Profiles can be used as a base for the new one. The list below shows and
explains the built-in (legacy) profiles:
• Administrator – Has unlimited access to all operations including User
Administration
• Operator – Has full Write mode and access to the Network Manager and
System Console. The Admin Console allows for editing only
• Technician – Has limited access to configuration operations, and
Read-only mode for Event Browser
• Monitor – Read-only mode for configuration operations, and no access to
other applications
• None
Note: Any existing profile can be used as a base for a new profile. You can
also select None to create a completely new profile.
<Continue…> Opens the Add <New Profile Name> Profile dialog box (see Figure 6-18)
Figure 6-22. Profile, not based on existing Profile – Profile Column Empty
Editing Profiles
To edit a profile:
1. From the EMS Security Administrator toolbar, select Profile > Edit.
The Edit Profile dialog box is displayed (see Figure 6-24).
2. Make the desired changes as explained under Working with Permissions.
3. Click <Set>.
The profile is updated.
Removing Profiles
Note Profiles can only be removed if a profile is selected in the profiles tree, if the
profile is not mandatory, and if the profile does not have any users attached.
To remove a profile:
1. In the EMS Security Administrator window, select Profile > Remove.
The Confirm Profile Removal dialog box is displayed (see Figure 6-25).
2. Click <OK>.
Example
Domains such as Group1, Group2 and Group3 can be set up and only certain
units are made visible to them according to pre-defined criteria. The names
Group# could stand for the names of companies who receive services from a
provider. The people from Group1, Group2 and Group 3 are able to see ‘their
parts’ of the network only. In addition, specific restrictions can be applied and
permissions granted for the Group1 and Group2 profiles respectively.
To set up a profile, you have to follow the checklist below compiled for Group3 as
example.
• Create a dynamic group called Group3 under Shared in the Groups tree and
specify the NEs that can be viewed.
• Create a new profile to view the NEs of Group3 only.
• Create a user based on Group3.
2. Right-click Shared and select New Dynamic Group from the shortcut menu
that appears.
You are asked to define criteria for the new group (see Figure 6-28).
Note • You cannot use wildcats and place holders such as the star (‘*’). To look for
NEs with a mutual section in the name, you have to always use Contain if the
mutual section is anywhere in the name or Start With if the mutual section
marks the beginning of the name.
• Names are case sensitive. Therefore, the relevant parts of the names must be
case sensitive when defining the criteria.
• Spaces and special characters are not allowed in names.
Figure 6-29. Devices Listed in the Dynamic Group – Group3 in this Example
Note In this section, dialogs are illustrated for Windows, but they are identical to the
ones for Linux and Unix except for the frame around them.
1. From the RADview Manager menu, select Tools > Admin Console .
The Admin Console appears.
2. In the Admin Console’s navigation pane, select Security Service.
The Profiles tree appears with existing security profiles listed as
illustrated in Figure 6-30.
Figure 6-30. EMS Admin Console: EMS Security Administrator – With Already Added Profiles
3. From the menu, select Profile > Add.
The Add Profile dialog box appears.
4. In the Add Profile dialog box, enter the following:
Under Profile Name, assign a name to your profile,
for example OnlyGroup3-Monitor.
Enter a description (optional).
Under Base Profile, select Monitor from the drop-down list to base the
new profile on the default Monitor profile.
Note This specific example bases the new profile on Monitor. You can base new
profiles on any built-in default profile or previously added profiles.
Note
The base profile is Monitor, therefore all permissions are set to Read
Figure 6-33. Adding a Profile – Permission Profile – launchdesk, admin, and ner Folders Expanded
2. Select Id_perm.
To add domains for levels that hold Group-3 NEs in the NER:
1. Under Profile on the left side, navigate to admin/ ner.
2. Right-click ner and select Add NEs Domain… from the shortcut menu.
The Select Domain dialog box appears.
3. In the Select Domain dialog box, click <…>.
The Select Source dialog box appears listing all the levels in the NER.
In the Select Source Domain dialog box, select 172.17.152.1. The level appears
listed under Source IP as illustrated in Figure 6-42.
7. Under Basic Permissions on the right side, under admin/ ner, select the
group permission Ner_perm.
9. Click <Set>.
The profile dialog closes and the new profile is now listed in the Profiles
Tree of the EMS Security Administrator as illustrated in Figure 6-44.
Figure 6-46. EMS Network Manager – Topology View for Group3 Profile and User ‘Group3-Monitor’
To create a profile:
1. Log in as root
2. Open the EMS Admin Console and create a new profile called WD_Operator.
Under Description, enter WD profile for this example. For instructions on
opening the EMS Admin Console and starting to create a profile, refer to
Creating a New Security Profile.
3. Once you assigned the name and entered a description, click <Continue>.
The Add WD_Operator Profile dialog box appears.
4. If the job group permission tags (highlighted yellow in the example below) are
not in the Profile pane, drag them to it from the Basic Permissions pane:
The admin/ jobs tree with the respective single labels appears in
the Profile pane.
5. Change the access for the single labels as follows:
2. In the EMS Security Administrator window (see Figure 6-3), right-click the
profile called WD_Profile you just created, and then select Edit to open the
Edit WD_Profile Profile dialog box.
3. Add a domain for the NE named 172.18.159.121:
a. In the Profile pane right-click the jobs folder and select Add Domain to
open the Select Domain dialog box.
b. In the Select Domain dialog box, click <...> and select the NE named
172.18.159.121 from the Select Source dialog box.
c. In the Select Source dialog box, click <Set> and in the Select Domain
dialog box, click again <Set> to create the domain.
d. In the Basic Permissions pane, select the group permission
Jobs_action_perm to display the list of its associated single
permissions in the ‘Jobs_action_perm’ Permissions pane.
e. From the ‘Jobs_action_perm’ Permissions pane, drag the
download_software permission tag to the /ETX-204A/172.18.159.121
domain.
f. Double-click the download_software tag in the domain to change its
permission to Read.
4. Add a domain for the /ETX-203A sublevel:
a. In the Profile pane right-click the jobs folder and select Add Domain to
open the Select Domain dialog box.
b. Click the browse button and in the Select Source dialog box, select the
/ETX-203A sublevel, then edit the Source IP field so that it contains
/ETX-203A/*.
c. Click <Set> in the Select Source dialog box and in the Select Domain
dialog box to create the domain.
d. In the Basic Permissions pane, click Jobs_action_perm so that a list of its
associated permissions appears.
e. From the ‘Jobs_action_perm’ Permissions pane, drag the
upload_configuration tag to the /ETX-203A/* domain.
f. Double-click the upload_configuration tag in the domain to change its
permission to Read.
The domains and the edited profile appears as illustrated in Figure 6-53.
5. Click <Set> to save the profile.
3. In the step where you select NEs, select the /ETX-204A/172.18.159.121 and
the sublevel /ETX-203A.
If you select Download Software as task, the task validation step
(Step ) indicates that the task is not authorized
for NE 172.18.159.121.
job_accessible – Read
Other job permissions –
see Figure 6-56
job_accessible – Read
job_accessible – Read
job_accessible – Read
Figure 6-56. Job Security Permissions for Users With No Figure 6-57. Global Job Security Permissions for Users
Domains With Domains
1 None
2 A_Team1
3 B_Team1
4 B_Team2
5 B_Team3
7 C_Team1 s
The following table shows which of the jobs in Table 6-35 the users in Table 6-34
can see (e.g. in the Jobs Table).
A
A1 × × × × ×
B × × × × × ×
B1 × × × × ×
B2 × × × × ×
B3 × × × × × ×
C × × × × × ×
C1 × × × × ×
The following table shows which of the jobs in Table 6-35 the users in Table 6-34
would be able to create.
A
1 2 2 2 2 2
A1 × × × × × ×
1 2 2 2 2 2 2
B × × × × × × ×
1 2 2 2 2 2
B1 × × × × × ×
1 2 2 2 2 2 2
B2 × × × × × × ×
1 2 2 2 4 2 2
B3 × × × × × ×
3 3 3 3 3 3 3
C × × × × × × ×
1 2 2 2 2 2 2
C1 × × × × × × ×
Note 1 – Job Wizard opens, but message box Access Denied is displayed when
<Finish> is clicked in last step, and status bar displays Access Denied.
Note 2 – Job Wizard opens, but message box Access Denied is displayed and
status bar displays Access Denied. Check Security Domain.
Note 3 – Job Wizard does not open; message box Access Denied is displayed if
user attempts to create job.
Note 4 –Job can be created but when <Finish> is clicked in last step, message box
Using current security domain may cause this job to be
inaccessible. Continue? is displayed. After the job is created, it is not visible
to the user in the Jobs Table.
The following table shows which of the jobs in Table 6-35 the users in Table 6-34
can modify (e.g. via Edit Job).
A
1 2
A1 × × Not applicable Not applicable Not applicable Not applicable Not applicable
3
B × Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable
1 4
B1 × Not applicable Not applicable Not applicable Not applicable Not applicable
1 2
B2 × Not applicable Not applicable × Not applicable Not applicable Not applicable
1
B3 × Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable
3
C × Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable
1 4
C1 × Not applicable Not applicable Not applicable Not applicable Not applicable
Note 1 –Message box Access Denied is displayed if user attempts to edit job.
Note 2 – Job wizard opens (e.g. via Edit Job) but message box Access Denied is
displayed when <Finish> is clicked in last step, and status bar displays Access
Denied. Check Security Domain.
Note 3 – Job wizard opens (e.g. via Edit Job) but message box Access Denied is
displayed when <Finish> is clicked in last step, and status bar displays Access
Denied.
Note 4 –The job can be modified, with the exception of the security domain. If
the domain is changed in the Advanced Job Parameters, then Note 2 applies.
Length Policy
Alphanumeric Policy
Expiration Policy
History Policy
Password Storage
Auto Lockout Policy Checked – Users are barred from logging on again after a specified number of
failed logon attempts for a specified period of time.
Cleared – Users are not barred from logging on again after failed logo
attempts.
Restrictions
Allow multiple logins per Checked – Users can log on multiple times.
user Cleared – Users can log on once only..
Logon and Logoff Success Checked – Successful logon and logoff is recorded in the log file
Note: Enabled only when Audit Policy is selected.
Logon and Logoff Failure Checked – Failure logon and logoff is recorded in the log file
Note: Enabled only when Audit Policy is selected.
Parameter Description
Info
Profiles Storage Directory The location of the directory where profiles are stored
Directory to Write Audits The location of the directory where audits can be written
Use file system for profile storage Enables/disables using the file system to store profiles. If
selected, the profiles are stored as a file in the Profiles Storage
Directory. If not selected, the profiles are stored in the RADview
database.
Note In this chapter, dialogs are illustrated for Windows platforms. These dialogs are
identical to the ones on Unix and Linux platforms except for the frame around
them.
Alarms
Alarms are divided into 5 levels that reflect their severity. Each alarm level is
categorized by a color. For additional information, refer to Chapter 3 on network
element icon colors.
Events
Events are displayed in the Event Browser in the Auxiliary section of the Network
Topology workspace. These events are categorized by the alarm color according
to the severity of the alarm that the respective event triggers.
Error Messages
Error messages pop up if certain tasks cannot be completed
Indications on the icons – color, symbol, Reference to Ch. 3 where icon colors
and links are covered.
Note You can open several Event Browser windows simultaneously. Each opened
window represents a list of events with a selected filter applied to it.
By default the Event Browser is displayed in the bottom pane, but you can open
multiple windows as mentioned above.
Note There are some cases where several events are combined into one event. In
these cases, an entry does not necessarily indicate one event.
The Event Browser can display up to 1000 events. If you click Page Up, another
1000 events are retrieved from the RADview database.
The bottom row displays the following for the current event filter:
• Total number of events, followed by the number of unacknowledged events
in parentheses.
• For each severity level, the total number of events followed by the number of
unacknowledged events in parentheses.
Time The Date and Time of the last arrival of the event to the Server
YYYY-MM-DD- hh:mm:ss
Instance The object in the Source where the event was initiated. This is
specific to the individual agent (see the specific product manual).
Toolbar Icons
The toolbar icons provide easy access to the main functions of the Event
Browser.
Button Function
Save As
Remove All
Acknowledge
Add Note
Notes
Locate on Map
Note: Appears only if Event
Browser is not opened
separately from Network
Manager
Shelf View
Note: Appears only if Event
Browser is not opened
separately from Network
Manager
Stop Refresh
Refresh
Pause
Button Function
Resume
Open Filter
Filter List
Export Filter
Import Filter
Scroll To Home
Scroll To End
Filtering Events
Filters allow you to view only the events that fit specified criteria. You can create
custom filters, or use the default filters.
The following default filters are available in the event browser:
• History Events – Displays all events from the current day, with severity
Critical, Major, Minor, Warning, or Normal
• Active Alarms – Displays all events from the current day that have not been
cleared or acknowledged, with severity Critical, Major, Minor, or Warning.
To open a filter:
• In the Event Browser window, click Open Filter and select the desired
filter from the list of filters
Or
Click Show List in the bottom right corner and select the desired filter
from the list of filters
Or
If the name of the filter appears on one of the tabs at the bottom of the
Event Browser, click the tab
The filtered events are displayed in a new tabbed window, and the filter
name is shown as selected in the tab on the bottom of the window.
Notes • You can create and open a filter named Active <device-name> to show the
active alarms for a particular device, by selecting the device on the map or
network element tree, and right-clicking Active Alarms
• You can create and open a filter named History <device-name> to show the
past alarms for a particular device, by selecting the device on the map or
network element tree, and right-clicking History Events.
You can add, change, or remove filters from the Filter List dialog box (see
Figure 7-2), which appears when you click Filter List in the toolbar.
To add a filter:
1. In the Filter List dialog box, click <Add>.
The Add Filter dialog box is displayed (see Figure 7-3 to filter by General
criteria, Figure 7-4 to filter by Sources, Figure 7-5 to filter by Event
Classes, and Figure 7-6 to filter Advanced).
2. Complete the fields according to Table 7-3.
3. Click <Set>.
Alarms
Alarms Only If this is selected, display events that are cleared by a different event, e.g.
Link Down is cleared by Link Up
Severity
Time Interval
Last, Days, Hours, Minutes Display only events received in the time period specified by the edit boxes
Interval, From, To Display only events received in the specified interval. The values are available
in ‘YYYY-MM-DD’ and ‘hh:mm:ss’ format and can be specified through the
dropdown boxes.
Cleared Events
Not Cleared Display only events that are marked as ‘Not Cleared’.
Acknowledged Events
Not Acknowledged Display only events that are marked as ‘Not Acknowledged’
Sources
Event Classes
Description Display only events according to a specific string in the event description field
Advanced
Show short node names Display names only as short node names
only
To change a filter:
1. In the Filter List dialog box, click <Change>.
The Change Filter dialog box is displayed (see Figure 7-7).
Note To change the current filter, you can click Edit Current Filter in the toolbar to
open the Change Filter dialog box.
To remove a filter:
1. In the Filter List dialog box, click <Remove>.
2. The Remove Filter confirmation dialog box is displayed (see Figure 7-8).
• In the Event Browser window, click Export Filter and select the filter from
the dropdown list.
A Save dialog box is displayed in which you can specify the location where
to save the filter definition.
Acknowledging Events
• Ack = Acknowledge (an event) – When you acknowledge an event, you mark
it as noticed.
To acknowledge events:
1. In the Event Browser window, select the event(s) to acknowledge.
To un-acknowledge events:
1. In the Event Browser window, select the event(s) to be unacknowledged.
Removing Events
You can remove selected events, all events, or all events before a certain
date/time.
2. Right-click and select Add Note, or on the toolbar click Add Note.
The Add Note dialog box is displayed (see Figure 7-16).
3. Enter the text of the note.
4. Click <Set>.
The note is added to the selected events, and the Add Note dialog box
closes. In the Event Browser line where the events are shown, the Notes
parameter is selected, to indicate that a note exists for the events.
2. Under Enable, check or clear the relevant check box to enable or disable the
respective sound profile for this RADview client.
To define the waiting time between issuing the event and playing he sound:
1. Under Time Window, select the currently set time window and enter the
desired new one.
The new value appears in blue and Italic as illustrated below.
2. Click <Apply>.
The value is set and the parameter setting’s formatting is adjusted to the
default.
• Event Policies to manage the display and handling of events in the Event
Browser (refer to Setting Event Policies). Default event policies are
predefined for generic and device event classes.
.
Search options appear as illustrated in Figure 7-23.
2. Select the desired search options as explained in Table 7-4.
The display is filtered to contain only the event policies with the search
string according to the search options you set. You need to expand the
groups to view the event policies.
Note From the Search Options dialog, you can select one option at the time. To select
additional options, you have to click again and select the next option.
Repeat this procedure until all desired options are selected.
All All policies are displayed for the search you entered.
For example, if you enter ETX as search term, all classes, policies etc are
displayed for ETX .
Event Class Display polices linked to specified event classes only. Refer to Table 7-5 for
additional information.
Description Display policies with descriptions added to them only. Refer to Table 7-5 for
additional information.
Source Display policies linked to a specific source only. Refer to Table 7-5 for
additional information.
Mask Policy Display policies linked to masked events. Refer to Masking an Event for
additional information.
Severity Policy Display policies linked to a specified severity. Refer to Setting the Severity for
additional information.
Duplication Policy Display policies linked to duplicated events. Refer to Duplicating Events for
additional information.
Forwarding Policy Display policies linked to forwarding events. Refer to Forwarding Events for
additional information.
Threshold Policy Display policies linked to threshold events. Refer to Setting the Threshold for
additional information.
Clearing Policy Display policies linked to clearing events. Refer to Clearing Events for
additional information.
Formatting Policy Display policies linked to formatting events. Refer to Formatting Events for
additional information.
Sound Policy Display policies with sounds defined to them. Refer to Defining Sounds for
additional information.
Case sensitive Only display items that match upper/lower case of the search item.
Use wild cards Display all policies that match the definition specified with wild cards.
Match from start Display all policies that match the beginning of the search item.
Match exactly Display all policies that match the search item exactly.
Match anywhere Display all policies that match anywhere in the search item.
Keep parent row if any of Display the upper level if a least one of the lower levels match.
the children match
Keep the children if any of Display all lower level entries if the upper level entry matches.
2. Choose the desired options for printing and then click <OK>.
3. Select the desired printer and then click <OK>.
The table data is sent to the selected printer.
Note Policies with old (prior version) event classes are not replaced. You must define
new policies using the new event classes.
Parameter Description
Figure 7-30. Select Event Dialog Box – Expanded Figure 7-31. Select Event Dialog Box – Event Class
Tree Selected
Figure 7-32. Add Event Policy Dialog Box after Event Class Selected
Masking an Event
To mask an event:
1. Click the Mask tab.
2. Select Mask.
3. Enter the Description of the Mask (only enabled when Mask is selected).
4. Select one of the following to specify when the event should be masked:
Always
Every Day –Specify the time and duration of the masking
On Date – Specify the date, time, and duration of the masking.
5. Click <Apply>.
Duplicating Events
Duplication refers to multiple appearances of the same event in a specific interval
of time. You can configure the option of only one appearance in the database
and in the Browser when the interval between two identical events is shorter
than a defined interval of time.
To configure duplication:
1. Click the Duplication tab (see Figure 7-37).
2. If you want to configure duplication of the event, select Duplication Policy.
3. Perform the following steps only if Duplication Policy is selected.
Enter the Description of the duplication.
Move the slider to select interval of time.
4. Click <Apply>.
The event is recorded and displayed only once if duplicate events occur
within the specified interval.
Forwarding Events
The Forwarding tab allows you to specify where to send notification of an event
when it occurs.
To set forwarding:
1. Click the Forwarding tab (see Figure 7-38).
2. Select Forwarding Policy and perform the following:
In the Description box, enter a description for the forwarding (only
enabled when Forwarding Policy is selected).
Perform one or more of the following:
Select E-Mail and enter one or more email addresses (separated by
semicolons)
Note To forward events to an email address, you must modify the EMS Server
parameters to provide SMTP information (refer to Chapter 4 for details).
Select Forward SNMP Trap to send the SNMP traps to another station.
Refer to Configuring Forwarding SNMP Traps for details on configuring
the forwarding of SNMP traps.
Note Before using the Forward SNMP Trap option, you must configure the SNMP trap
forwarding destinations as described in Defining SNMP Trap Forwarding
Destinations.
3. Click <Apply>.
Note Refer to Defining SNMP Trap Forwarding Destinations for a description of how to
define the SNMP trap forwarding destinations.
Clearing Events
You can set the clearing policy for clearing events. Clearing the event means
setting the event as cleared in the Event Browser (in the Cleared column), it does
not mean removing the event from the event log. This clearing procedure can be
useful for example to clear the Link Down event if the Link Up event arrives.
The event class appears at the bottom of the Select Event dialog box (see
Figure 7-31).
d. In the Select Event dialog box click <Set>.
The Select Event dialog box closes, and the selected event class appears
in the Event to Clear parameter.
4. Click <Apply>.
Formatting Events
Formatting determines the string to be displayed in the Event Browser for the
event.
Defining Sounds
You can assign sounds to specific events or group of events that are played once
these events occur.
Note Sound profiles are defined on the server level. Therefore, every client that
connects to the relevant serve hears these soun
Note If you select Retransmit and OSS Heartbeat service is enabled in the system
console (refer to the description of EMS services in Chapter 4), then when the
OSS server is down, RADview saves the event and resends to the OSS server
when it becomes available.
If OSS Heartbeat service is not being used, there is no need for the Retransmit
option.
3. For Event Class, Source, and Instance, you can use the default value of Any to
mean that the policy applies to all sources, all Instances, or all event classes,
respectively. If you want to use Any for event class, skip to step 4. The
following steps explain the procedure for selecting a specific event class:
a. Click […] next to Event Class to display the Select Event dialog box (see
Figure 7-29).
b. In the Select Event dialog box double-click the desired event class group
to expand it, then select the desired event class from the expanded event
class group (see Figure 7-30).
The event class appears at the bottom of the Select Event dialog box (see
Figure 7-31).
c. In the Select Event dialog box click <Set>.
The Select Event dialog box closes, and the selected event class appears
in the Add Fault Clearance Event dialog box (see Figure 7-53).
4. If you want to use Any for source, skip to step 5. The following steps explain
the procedure for selecting a specific source:
a. Click <Browse> next to Source.
The Select Node dialog box is displayed showing the nodes (see
Figure 7-33).
b. Select the desired node and click <OK> to close the Select Node dialog
box.
The node appears in the Add Fault Clearance Event dialog box (see
Figure 7-54).
5. In the Add Fault Clearance Event dialog box, click <Set>.
The Add Fault Clearance Event dialog box closes, and the Fault Clearance
Procedure dialog box displays the event, along with text boxes for the
probable cause and corrective actions (see Figure 7-55).
6. If you wish to specify a probable cause, enter text describing the probable
cause of the event in the Probable Cause text box.
7. If you wish to specify corrective measures, enter text describing corrective
actions for the event in the Corrective Measures text box.
8. Click <Apply> to complete the fault clearance specification for the event.
If you entered probable cause and/or corrective actions, the Probable
Cause and/or Correction options for the event are shown as selected (see
Figure 7-56).
9. When you have completed specifying fault clearance procedures, click
<Close> in the Fault Clearance Procedure dialog box.
The Fault Clearance Procedure dialog box closes. When an event occurs
for which you have specified a fault clearance procedure, you can see the
probable cause and corrective actions in the details of the event in the
Event Browser.
Figure 7-53. Add Fault Clearance Event Dialog Box – Event Class Selected
Figure 7-54. Add Fault Clearance Event Dialog Box – Node Selected
Figure 7-55. Fault Clearance Procedure Dialog Box, after Event Added
Figure 7-56. Fault Clearance Procedure Dialog Box, after Events Added with Probable Causes and
Corrective Actions
Parameters Function
Current No. of Log Records Displays the current number Log Records
Read-only
Max No. of Log Records Max No. of Log Records
Parameters Function
Cyclic
Old Records Remove Percentage of old log records to be removed when log
reaches the maximum size
Clear non-cleared events which Select to configure automatic event clearing. The
are in the system for the last automatic event clearing selects the Cleared parameter in
given days the Event Browser (see Figure 7-1) for events that meet
the criteria for automatic event clearing, as defined by the
next two parameters.
Checking time once a day Time of day when to check for events to automatically
clear, in hh:mm:ss format
Clear events older than (days) Enter the number of days that events should be older
than, to be automatically cleared.
Note Syslog servers do not install with RADview. They must be installed separately in a
location that is permanently accessible to the RADview server. For additional
information and instructions on installing a Syslog server, refer to the associated
documentation.
To configure the EMS log properties and define up to two Syslog servers:
1. Open the Admin Console. To do so, from the RADview Manager menu, select
Tools > Admin Console.
The Admin Console appears.
2. Click the + icon to expand the Admin Console and then select Log Admin
Console in the list of consoles.
The default logs appear listed.
3. Select the log that you wish to configure.
The EMS Log Administrator is displayed. For each EMS log it shows the
status, current size, and maximum size.
Parameter Function
Admin Status
Parameter Function
Wrap by Severity Entries with the lowest severity are deleted (enabled
only when Wrap is selected)
Max. Size Maximum size of the log. This can be any positive
number.
Record Life Time (Days) Number of days that the entries are saved in the log.
This can be any non-negative integer. Zero means
unlimited.
Parameter Function
Save to Log Files Check to save the event to the log files
Log Files Directory Enter the folder to save the log file
Log File Length (*1000 Lines) Define the max length of the log files
Parameter Function
Server 1, Server 2
Facility
Parameter Function
Minimum Severity Level Select the minimum severrity level of events sent to
the Syslog server.
Note: Syslog event severity levels are different and
are mapped to RADview event severity levels. To
customize the mapping, use the System Console as
explained under Configuring the EMS Log Service in
Chapter 4.
Note The codes in the Security log Description field can be used in case there is some
problem with system security, to allow RAD to identify the internal reason for a
problem.
Note If the dialog box does not display the list of EMS servers, click the EMS Servers
parameter to expand the list.
Severity Critical
Major
Minor
Warning
Normal
Unknown
To save a log:
1. Click a tab in the Log Viewer.
2. From the Action menu, select Save As.
To print a log:
1. Click a tab in the Log Viewer.
2. From the Action menu, select Print.
7.5 Troubleshooting
This section provides some troubleshooting information.
An error message appears indicating • A power saving scheme • Turn the power save option off. If a power
the that The RADview server is not may be active on the saver is still required for other resurces on
ready upon attempting to start relevant PC, which causes he PC, create a power plan for RADview as
RADview, although the server is started connectivity issues explained in Chapter 2 of the RADview
and appears as online and ready. between client and server system manual.
once the relevant PC • Uninstall RADview, remove the C:\RV32
went ‘to sleep’. folder and then reinstall RADview.
Note: For modified and added power plans to
persist, make sure to have the relevant PC
exempted from restrictions based on possible
company policies.
After a network element is created on • The corresponding • To check whether the product is installed,
the map, the icon is gray with a product was not selected open the Version Browser (Tools > Version
question mark when RADview was Browser) and expand the EMS Products
installed tree. If the desired product is not there,
• You do not have enough install RADview as an upgrade, keeping the
ENW license points existing database and selecting the
installed desired product.
• The product is not • To check the ENW license points, open the
supported by RADview License Manager (Tools > License
Manager), then verify that the total
• The product version is
number of installed license points is
not supported by
greater than the consumed license points
RADview
• To verify if the product is supported by
RADview, check the RADview release note
• To verify if the product version is
supported by RADview-EMS, check the
RADview release note
The RADview installation is terminated • You may have installed • Uninstall the Oracle database, restart your
because the Oracle database cannot be the Oracle database from PC and then re-install the Oracle database.
found, although it has been installed a network drive. In case of problems with uninstalling the
Oracle database, refer to the instructions
on manually uninstalling respective entry
on a procedure to manually uninstall the
Oracle database below.
Oracle server is not functioning See log files Check the following log files:
properly • C:\oracle\admin\mng164\bdump\alert_mng
164.log
• C:\oracle\ora10\network\log\listener.log
Oracle does not uninstall. The Oracle problem Perform the following to manually uninstall
uninstallation process stops Oracle:
somewhere between 10 and 20 per • Delete all folders whose name starts with
cent. oracle, in C:\ and C:\Program Files (if the
installation drive is not C, adjust the paths
accordingly)
• In some cases, files located under
C:\oracle\ora11\BIN are locked and cannot
be deleted.
To release them for deletion, go to
Services (via Control Panel > All Control
Panel Items > Administraive Tools) and
stop Distributed Transaction Coordinator.
• Use regedit to delete the entry
HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE
from the registry and then restart the
relevant PC.
• If this folder can sill not be deleted,
rename it, restart the PC again and then
delete it.
Note: Use extreme caution when editing the
registry. It is recommended to back up the
registry before editing it.
Unable to save User account control is set to Verify that the user account control is set to
C:\windows\system32\drivers\etc\hosts notify about changes, which Never notify (refer to Chapter 2 for details). If
after changing it blocks saving the file you change the user account control settings,
you must restart your workstation for the
change to take effect.
Certain end points cannot be used to A service may be listed in the 1. On the RADview Server station, navigate
create a service between two devices database, but not be visible to C:\Temp and create a new XML file
in RADview-Service Manager called deleteServices.xml.
2. Use an editor such as Notepad++ and
enter the following XML tags into that XML
file:
<script>
<services>
<name>service-1</name>
<name> service -2</name>
<name> service -3</name>
</services>
</script>
Replace service-# with the names of the
respective services.
3. To delete the specified services, run the
following string:
C:\rv32\ems\bin\mng164_script.exe
cmd=DeleteServices
xml=C:\temp\deleteServices.xml
log_filename=
C:\temp\deleteServices.log
Q I forgot my RADview user's password. How can I recover it? Also, is there a
default user name and password that I can use?
A The default user name and password for accessing RADview (via the
LaunchDesk or RADview Network Manager) are root for the user name and
root for the password. If the default password of the root user has changed
since the initial installation, then it is necessary to reset the password for
your specific user name.
8.1 Introduction
This tutorial covers the FCAPS functionalities of an application including:
• RADview Server
• RADview PC Client
• Devices
It includes the following features and functionalities in RADview as follows:
• Working with Links
• Viewing Link Status
• Resources
• Business Entities/Customers
• Performance Portal version 2 for ETX-203A and ETX-204A devices – refer to
Chapter 5.
4. Additional installations
Pre-Installation
RADview/PACK1 Client/Server PC
1. Verify that the PC/laptop has a unique name.
2. Allocate a static IP. If you need to use DHCP, refer to Chapter 2 for
instructions.
3. Disable TCP/IPv6.
4. Do not change the name of PC after installing Oracle.
5. Disable the Windows firewall.
6. Open the relevant ports on the network firewall. Refer to the diagram
showing all ports used by RADview in Chapter 2.
7. Enable Control Panel Item > Windows Firewall > Allowed Programs > SNMP
Trap.
8. Enable Telnet Client.
RADview/WIN/PACK1 Client PC
3. In General Information dialog box, leave Zone Name and Area Name fields
empty. Do not change Station Name field.
4. In the Database Settings dialog box, select (check) the Create new database
option only when you are performing the installation for the first time.
Note When upgrading, do not select the option to create a new database. Make sure
this option is not selected
5. The following dialog displays all product groups. Install all groups of devices
to avoid the need to upgrade in the future.
To activate and configure the TFTP SolarWinds on the server (in an actual
application):
1. In RADview go to Tools > System Console. (Enter the password root to open
the System Console).
2. Select Process1 > End Job Management (Back End) and select the TFTP tab.
6. Select the General tab, and verify and/or update the TFTP Server Root
Directory path is exactly as in Tools > System Console > Process1 > End Job
Management (Back End) > TFTP tab > TFTP Settings > Home Directory path.
Note Verify that TFTP Settings > Home Directory path is exactly the same as the path
defined in the TFTP Server Root Directory in the TFTP Server application.
Objectives
• Configuration via RADview (FCAPS)
• Installing RADview licenses
• Using the RADview network management GUI
Note When licenses are not loaded, the following Message box will appear.
RADview requires license points for each managed element and a license key to
activate the map.
Each management station requires two RADview licenses:
• MAP license - required for working with RADview Standalone map.
• ENW license - allows you to configure all RAD devices that exist on the map.
The Network Manager map opens, displaying its Network Element Repository,
Event Browser and the Topology Map pane.
Topology Map
The Topology workspace is divided into panes that contain the following
components:
• Network Element Repository – Displays a navigation tree of levels (submaps)
and nodes (network elements) in the RADview network.
• Groups – Displays a navigation tree of user-defined groups of network
elements, used for additional map viewing; also for working with
configuration and jobs.
2. In Link Name, enter as the link name “LinkGroup@”. It must be a unique name
that is not being used for any other link.
3. In Description, you may optionally enter a description.
4. To set the port for the link starting point, click the browse button […] for
EndPoint A.
The Select End Point dialog box opens, showing the ports available in the
Endpoint A device.
7. Expand your Group@ level, and expand the remote device to display its ports.
8. Select NET-ETH 1 port, and click Select.
9. In the New Link dialog box, click Set to create the link.
A line is drawn between the two devices to represent the link. The line is
wider if there is more than one link between the two devices.
10. Verify that a links is not Gray. If a link is Gray, delete it and create again
following carefully the below instructions.
Note For more information about Status, refer to the section “Viewing Device Status”
in the RADview User’s Manual.
Note If you see that the icon is orange, it means there are Active Major Alarms on this
device. RADview Network Manager GUI displays the alarm that is the most severe.
A major alarm commonly occurs when some of the ports of a device are not in
use while their administrative status is Up. As a result, these ports send a Link
Down event, and are colored in magenta. When the overall status of the device is
Major, it means the severity of the Link Down is Major.
Creating Groups
If you have many products, you can combine them into one group. You can then
run the same job on products associated with this group at the same time.
There are two kinds of groups:
• Dynamic group – Group members are defined by criteria that determine which
NEs belong to the group. NEs that meet the criteria are automatically
members of the group. When an NE is added to the map, and it matches the
specified criteria, it is automatically added to the group. When an NE is
changed, it is added or removed, according to the group criteria.
• Static group – Group members are defined by copy/paste of nodes/levels
from the tree/map. When levels are pasted to a static group, the
corresponding NEs are added to the group without the level hierarchy. You
can create levels in a static group.
You will also create jobs based on the group level you created.
Note Each group should run the job only on the devices that belong to the group level.
For example:
Overview
Configuration Archive
The configuration archive contains the configuration status and archived
configurations files, enabling you to track device configurations. The
configuration archive contains files uploaded/downloaded to/from devices via the
job mechanism (see below); these files can be uploaded to the devices when
necessary. The configuration files are tracked by date and time.
3. For the Name of the Job, type Upload software to Group@ (where @ is your
group number).
4. For the Description, type Upload software to all devices Group@
5. Click Import to import the software version.
Select Browse…, and go to Desktop to find the SW file.
6. Ask for your trainer for the exact file location and select the SW version file.
7. Fill SW version field with a SW version number.
Ask your trainer for the exact version number.
8. Click OK
From now on this version will be stored within the Software File
Management storage. See below for more information.
9. Click Next.
10. Select Now and click Finish.
The Job will start running.
11. When the job is finished, check the Reports pane to verify Status is OK.
12. In the Reports pane, double-click the job to see the status of the software
download job for each device. Notice a current status that might be
Rebooting, Verifying software version… etc according to a current Job status.
13. Click on More details … to view the report details (which can be either saved
and/or printed).
You will now see how to change the status of a specific software file from Valid
to Obsolete if necessary.
If new uploaded SW is the same as the existing previously, you will see a Warning
Informing that a SW was not changed.
2. Right-click on the specific version you need to change, and select Mark as
Obsolete.
Note Next time you will make SW upload, this version that was just signed as Obsolete
will not appear in the wizard combo-box.
Configuration Management
4. For the Name of the Job, type Download Configuration From Device$Group@
(where instead of $ write a device type and @=your group number).
5. Type a description.
6. Click Advanced.
7. For Report Logging, select Log All job tasks, and click <OK>.
Note The Advanced tab also allows you to configure several advanced features, such as
forwarding the report to an email address. (Refer to the product manual for more
information.)
8. Select Next, Now and Finish. The Job will start running.
9. When the job is finished, check the Reports pane to verify Status is OK .
10. In the Reports pane, double-click the job to see the status of the
configuration download job for each device.
11. Click on More details … to view the report details (which can be either saved
and/or printed).
In general, the status of the Job operation can be one of the following:
Fail –Job was not successful for at least one of the NEs. Check the
report details to see if the job succeeded for any of the NEs.
Warning – Job ended successfully, but there was some other error;
e.g., the CLI script was successfully sent to the agent, but the script contained
errors.
Configuration Archive
The configuration archive contains the configuration status and archived
configurations files, enabling you to track device configurations. The
configuration archive contains files uploaded/downloaded to/from devices via the
job mechanism; these files can be uploaded to the devices when necessary. The
configuration files are tracked by date and time.
The Configuration workspace is divided into panes that contain the following
components:
• Network Element Repository – Displays a navigation tree of levels (submaps)
and nodes (network elements) in the RADview network.
• Groups – Displays a navigation tree of user-defined groups of network
elements.
• Configuration Status – Shows device configuration information for NEs
selected from the Network Element Repository or from the Groups tree (NE
Baseline
This feature is applicable only for configuration files. When a file is marked as
baseline, the icon is displayed in the column. Only one baseline is possible
for each NE.
3. Right click on the relevant configuration file, and select Mark as Baseline.
4. Repeat this procedure for other devices in your group.
11. Click Next, select Now and Finish. The Job will start running.
12. You can verify the status of the job in the Jobs pane of the RADview window;
double-click on the specific job.
13. Click on More details … to view the report details (which can be either saved
and/or printed).
You will practice additional Job procedures, software upload and statistics
collection – in the last section of this tutorial.
This section is relevant only for devices supporting CLI.To send a CLI script to the
device:
1. In the Network Element Repository, right-click on the one of the devices in
your group that support CLI, and select New Job.
The job wizard opens.
2. Select Execute Script, and click Next.
5. Click Browse and select the OAM [email protected] file, which is located
in the Scripts directory on your desktop. Click OK.
The script will appear in the Enter script to execute field.
6. Click Next.
7. Select Next, Now and click Finish.
The Job will start running.
8. You can double-click on the Jobs Table to open the Jobs Status dialog box,
which shows the progress of the job for each NE associated with the job.
9. When the Job is finished you can open the report, and see the list of
commands that were executed on the device according to the script (see
below).
The information in the dialog box is automatically updated as the job continues to
run. Additionally the dialog box contains a table showing the status of each NE,
while the Error column indicates whether there is an error during the job process
that causes the job to fail. (In the event of an error, you can open a report that
details the cause of the failure).
10. Repeat the steps in this task for the second device.
Objectives
The transition to next generation packet network means that service providers
must be able to guarantee Service Level Agreements (SLA).
RADview Performance Monitoring (PM) Portal provides tools for real-time and
long term monitoring of Ethernet service performance and for creating monthly
SLA reports.
In this section you will learn how to configure RADview to collect OAM statistics,
generate monthly SLA reports, and view OAM statistic reports with the RADview
PM Portal.
Overview
RADview server collects OAM statistics from RADview devices that support it.
The statistic counters, referred to as Key Performance Indicators (Y.1731 KPIs)
are: frame delay (latency), frame delay variation (jitter), frame loss, network
availability, and throughput.
This chapter describes the operations required for configuring and viewing OAM
statistic reports, when the criteria for associating policies to services is by both
service grade and customer ranking.
RADview PM Configuration
After you have created a topology in the RADview map by creating sublevels and
network elements (NEs), you can begin configuration of RADview PM.
The upper pane Resources – Shows devices that have been defined in the
RADview Topology workspace.
The bottom pane containing Details, Active Alarms and History Alarms –
Displays the resource details, active alarms, and past alarms.
2. Select a resource in the Resources pane and note the information in the
Details pane.
3. Select the Active Alarms tab to display the active alarms of the resource.
4. Select the History Events tab to display the past alarms of the resource.
1. Select the Filter icon next to the Sort options in the Resources toolbar.
3. Select the (All) checkbox to clear all selections, and select Group@ where @ is
the number of your group.
4. Click OK. The Resources pane now displays only the devices belonging to your
group sublevel.
4. Click <Set>.
The resource/device was updated with its end-customer name.
5. Repeat Steps 1-4 for your second device.
Configuring PM Parameters
Each end-customer (group) has several defined OAM services, each of which
belongs to a different service grade.
Each end customer has a different SLA contract. This means that even if one end-
customer (e.g., CustomerGroup1) has a service based on pbit-7, exactly as
another end-customer (e.g., CustomerGroup2), they will have different SLA
contracts. Every SLA contract defines different threshold values.
For this reason, this tutorial teaches you how to configure and view OAM
statistics reports, with both service grade and customer ranking as the criteria for
associating policies to services.
2. Note the pre-defined Policies. Select any Policy in the table, and press
Change.
The Policy Details dialog box is displayed.
3. Press Next.
4. The KPI Selection dialog box is displayed. Note the pre-defined Threshold
values.
5. Press Cancel
Note Do not change any values, as they are shared by all RADview PC client users!
2. Click <Close>.
Collecting Statistics
OAM statistics are the statistic counters, referred to as Key Performance
Indicators (Y.1731 KPIs).
The RADview server collects the OAM statistics.
To obtain statistics, you need to set up a job for the devices from which you
want statistics, using the function Collect Statistics.
Once the statistics have been collected, they can be viewed via the web-based
RADview Performance Portal, described later in this section.
To Collect Statistics:
1. Select the Jobs workspace.
4. In Wizard Step 2 - Create New Job > Select Customer, select Explicitly, and
then select CustomerGroup@, where @ is a number of your group.
5. In Wizard Step 3 - Create New Job > Select an Action, select Collect Statistics,
and click Next.
6. In Wizard Step 5 - Create New Job > Collect Statistics: Job Parameters, for the
job Name, type: CollectStatisticsGroup@, where @ is a number of your
group.
7. Click Next.
Note
In the Job Parameters dialog box, the parameter Days to Save Statistics Data
specifies how long to keep the statistics data in the NMS database. If you want
to keep statistics for a longer period, verify that your hard drive has enough
space for the stored statistics data.
8. In Wizard Step 7 - Create New Job > Schedule, select Recurring Every 15
Minutes and No end date.
9. Click Finish.
10. To start collecting the data now, click the green Play button.
The Job will start running.
11. Verify the status of the job in the Jobs pane of the RADview window; double-
click on the specific job.
4. In Wizard Step 5 – Create New Job > Generate Statistics Report: Job
Parameters, for Name, type CreateReportGroup@ (where @=your group
number), and click Next.
5. In Wizard Step 6 – Create New Job > Report Parameters, for the Title, type
OAM Statistics Report Group @ (where @=your group number). This is the
title that you want to appear in the statistics report.
6. Select all other parameters as shown in the screen below, and click Next.
8. Press Finish
9. To start generating the Statistics Report now, click the green Play button.
The Job will start running.
10. After the job completes, you can view the job report details by double-clicking
the job in the Reports pane.
7. The bottom part of the window appears according to the link that is clicked in
the navigation pane. When the portal is opened, the Dashboards window is
displayed by default.
The segment protrudes slightly from the circle, and the tooltip is
displayed.
The tooltip displays number of services corresponding to the segment.
Note In this tutorial we do not have real traffic; therefore all values of FLR, Frame
Delay are 0. As a result the entire pie chart is green.
Note
If you see numbers in yellow, it means that the Warning Threshold was crossed. If
you see numbers in red, it means that Error threshold was crossed.
The right pane displays the Eth Report corresponding to the previously
selected filter in the left pane. If you selected the NER tab in the left
pane, you will see information relevant to NE. If you selected the
Customers tab, the right pane called Eth Reports will be upated
accordingly.
2. Select the Customers tab, and select CustomerGroup@, where @ is a number
of your group.
As a result, the title of the report will be changed to Eth Reports (Filtered
by Customers) and the information displayed in the table is updated.
5. Note the different Report Filters in the Eth Reports in the right pane
Name Description
Customer Ranking Specifies for which customer ranking(s) to show data. You can select a single value
or all customer ranking values
Service Grade Specifies for which service grade(s) to show data. You can select a single value or
all service grade values
Threshold Level Specifies for which crossed thresholds to show data. You can select a single
threshold or all thresholds.
Note: This field is enabled only if SLA Report is selected in Report Type.
Name Description
Report Period Indicates the period of time for the report. The possible values differ according to
the report type.
The values for aggregation reports are: 1 Hour, 1 Day , 1 Week, 1 Month
The only allowed value for SLA reports is 1 Month.
Select Specific Indicates the specific period of time, according to the value selected in Report
Period Period. Click Select Specific Period to open a popup calendar to select the period of
time.
To change the date, click inside the date text box to open a calendar.
Default: Current date
Hour If 1 Hour was selected in Report Period, this field contains a list of hour values,
from which you can select the desired hour.
<Refresh Reports> / Click <Refresh Reports> to refresh the report data. If changes are made in the
<Update Reports> toolbar or tabs, the name of the button changes to Update Reports. After it is
clicked to show the report according to the filtering, the name changes back to
Refresh Reports
To monitor services:
For monitoring services, this tutorial uses the following example of an SLA report
with the warning and error threshold crossings shown in yellow and red,
respectively. The large red segment in the pie charts in the Dashboards pane of
RADview Performance Portal.
Since Error Threshold Level was selected in the Eth Reports Service Filters,
in the table you will see only services with the Error threshold level.
2. Select Normal in the Threshold Level combo-box, and press Update Reports in
Actions.
You will now see only services that have Normal status; that is, services
that do not violate the SLA contract.
6. You can change the display and display one of the following: Loss or Delay
Measurements Messages: LMMs, LMRs, DMMs, DMRs, Far/Near End Tx/Rx
Frames, Far/Near End Lost Frames, Far/Near End Frame Loss Ratio, Far/Near
End Availability, Average Two Way Delay, Average Two Way Delay Var.
7. To display Frame Loss Ratio, click Select Chart, select Frame Loss Ratio, and
click Show Charts to display a graph. See the example below.
Overview
RADview Fault Management allows you to view and control the SNMP traps
(events) received by the management station from the managed elements.
The Event Browser (located at the bottom of the RADview Network Manager
screen) allows you to view and control the display of SNMP traps (events)
received by the management station from the managed elements.
The Fault Administrator allows you to configure the Event Browser log
parameters, SNMP trap forwarding destinations, and fault clearance, and to
define Event Policies for managing the display and handling of events in the Event
Browser .
To create a filter:
5. Press Set.
6. A new filter was created.
7. In the Event Browser toolbar, click (Open Filter) and select the new filter
from the list of filters.
Now you will see only the Event Browser events that were sent by the NEs in
your sublevel Group@.
The General Tab provides the following options:
• Select which trap Severity to display within the specific tab
• Select the traps that were sent only in a specific time Interval
• Select to display Cleared alarms, Not Cleared alarms or All
• Select whether or not to display Acknowledged traps.
4. Select Generic and scroll down until you see the event policy
Generic_nodeConnected.
5. This policy was automatically preconfigured by the system.
6. It means that every time a Node Connected event arrives, a previously sent
Node Disconnected event is signed as “CLR” in the Event Browser.
4. On the Topology map, right-click your device, and select Properties > Poll.
5. Right-click your device. Change Read Community back to public. Then perform
polling again by selecting Properties > Poll.
This time, RADview will get response from a device, and the node will be
colored in green again.
In the Event Browser you will see the Normal event Node Connected.
Note that the Critical event Node Disconnected was signed as cleared.
“CLR” now appears next to it in the Event Browser.
7. Click <Continue…>.
8. In the Add Event Policy dialog box, select the Mask tab and select Mask.
9. Click <Set>
Once these steps are completed, the event policy is defined.
You can now see that this new policy was added in the Fault Administrator dialog
box and appears in Event Class list.
Before continuing to the next step, change the SNMP Read community back to
public.
Overview
For the very first login (before users are defined) you used the default user:
Username=root, Password=root
You will now create new users accounts and define security profiles using the
Security Administrator.
Note A user is assigned to only one role (profile); however one role (profile) may be
assigned to many users.
4. After your Login fails, you will see a message “Login denied. Account
temporarily disabled.” You will not be able to login for the time defined in
Configuration > Account Tab.
Write
Read
Not Available
6. Press Continue. The Add <New Profile Name> Profile dialog box appears.
10. In the Select Domain dialog box, click the browse (…) button.
11. In the Select Source dialog box, select Group@. (If your group is Group 1,
select Group1, etc.)
12. In the Select Domain dialog box, type an asterisks (*) in the Domain field
after Group@ to ensure that the domain includes everything in Group@.
13. You will now see a folder /Group@* under the ner folder.
14. In the Basic Permissions pane, double-click the admin folder. Then double-
click ner folder to display a list of permissions in the Ner_perm folder.
15. In the Ner_perm Permissions list select ENTRY_accessible, and drag it to the
/Group@* folder in the Profile pane .
Note A user is assigned to only one role (profile); however one role (profile) may be
assigned to many users.
6. Press Set.
7. The Admin Console now includes a new user assigned to the Operator@
profile, meaning that this user has the permissions you previously defined for
this specific profile.
Log Viewer
The Log Viewer enables tracking of successful and/or failed logons and logoffs.
The Log Viewer System tab lets you track all operations performed in the
RADview map.
3. The Log Viewer Application tab displays all operations performed in the shelf-
view applications.
A.1 Introduction
In some cases, a patch is inserted into the RADview server, to be distributed to
its RADview clients. When this is necessary, RAD Technical Support provides the
patch file(s) and procedure for inserting a patch on the RADview server.
B.1 Introduction
The automatic update mechanism described in Appendix A is used for scenarios
where it is necessary to define a primary and secondary server. RAD Technical
Support provides the necessary files and procedure for installing them in the
server. The following files are provided:
• ems_servers.xml – Contains the definitions for the primary and secondary
servers
• emsupdate.xml – Contains the patch.
When the timer displayed in the status bar expires, the client connects to
an RADview server if one is available. If one is not available, the timer is
restarted.
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail [email protected]
www.rad.com