polyview user guide - 12-2010.pdf

PolyView™

with CeraMap™

User Interface

User Guide

Part ID: BM-0077-0 Doc ID: DOC-00007966 Rev. R

December 2010

Notice

This document contains information that is proprietary to Ceragon Networks Ltd.

No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd.

This document is provided as is, without warranty of any kind.

Registered TradeMarks

FibeAir®, Ceragon Networks®, and CeraView® are registered trademarks of Ceragon Networks Ltd.

Other names mentioned in this publication are owned by their respective holders.

TradeMarks

CeraMapTM, ConfigAirTM, PolyViewTM, EncryptAirTM, and CeraMonTM are trademarks of Ceragon Networks Ltd.

Other names mentioned in this publication are owned by their respective holders.

Open Source Information

The Product may use open source software, among them O/S software released under the GPL or GPL alike license ("GPL License"). Inasmuch that such software is being used, it is released under the GPL License, accordingly. Some Software might have changed. The complete list of the software being used in this product including their respective license and the aforementioned public available changes is accessible on http://nms-open-source.license-system.com/.

Statement of Conditions

The information contained in this document is subject to change without notice.

Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.

Information to User

Any changes or modifications of equipment not expressly approved by the manufacturer could void the user’s authority to operate the equipment and the warranty for such equipment.

Copyright © 2010 by Ceragon Networks Ltd. All rights reserved.

Contents Introduction ................................................................................................................. 1

Installing PolyView ...................................................................................................... 7

Getting Started ............................................................................................................ 9

Working with the Client ............................................................................................ 17

PolyView Security ..................................................................................................... 29

Server Configuration ................................................................................................ 38

Client Configuration .................................................................................................. 51

Trap Forwarding Configuration ............................................................................... 55

Configuration Broadcast .......................................................................................... 59

Viewing Alarms ......................................................................................................... 71

End to End Trail Management .................................................................................. 82

Software Download ................................................................................................... 91

Configuration File Download ................................................................................... 95

Management Reports ................................................................................................ 98

Administration & Maintenance .............................................................................. 109

Appendix A: PolyView CLI (Command Line Interface) ........................................ 125

Appendix B: PolyView License Information ......................................................... 137

Appendix C: PolyView Server Installation and Testing ....................................... 141

Appendix D: HTTP Proxy Installation and Configuration .................................... 154

Appendix E: DCN Sizing ......................................................................................... 164

Appendix F: PolyView Ordering ............................................................................ 167

Appendix G: SNMP MIB Support ........................................................................... 176

Appendix H: Trail Management for FibeAir 1500A ............................................... 187

Appendix I: PolyView Support for Floating IP Address....................................... 194

Appendix J: Port List .............................................................................................. 196

PolyView™ User Guide 1

Introduction PolyView™ is Ceragon’s powerful yet user-friendly NMS (Network Management System) that integrates with other NMS platforms and systems in which no NMS is used. It provides management functions for Ceragon’s FibeAir® systems at the network level, as well as at the individual network element level.

Using PolyView, you can perform the following for Ceragon elements in the network:

Auto Network Element Discovery

End-toEnd Trail Management

Performance Reporting

Inventory Reporting

Software Download

Trap Forwarding

Broadcast Configuration

View Current Alarms (with alarm synchronization)

View an Alarm and User Action Logs

Create Alarm Triggers

User Management

Schedule Tasks

PolyView's user interface, CeraMap™, enables fast and easy design of multi-layered network element maps. CeraMap helps manage the network from its building stage to its ongoing maintenance and configuration procedures.

PolyView supports all Ceragon FibeAir products, and compliments Ceragon’s CeraView® and CeraWeb by providing a higher (network) level of management support.

PolyView is implemented in Java, which enables it to run on different operating systems.

PolyView is security-protected, whereby configuration and software download operations can only be performed by authorized system administrators.


Features End-to-end trail management

CeraMap user-friendly interface used to build graphic element network, and manage element configuration and maintenance.

Launched by clicking on elements in the map

Automatic detection of network elements

Supports multiple maps, groups, and links

Extensive reporting capabilities

Enables saving/loading of configuration data

Supports inter-element graphic connection

Supports active graphic element status indication

Supports global configuration changes through top-level elements

PolyView version updates do not affect the database

PolyView™ database information can be exported for use in other applications

Integrates with other NMS platforms

System Overview The PolyView system consists of the following main components:

PolyView framework - the foundation on which all PolyView applications and services run

PolyView database - a centralized SQL-based database

NMS plugable API Interface - the connection between PolyView and the NMS it integrates with

PolyView applications


The following illustrations show how PolyView is integrated in the overall management process.

Integrated PolyView Management

A note about operating systems and platforms:

PolyView runs on Windows 2003/XP/Vista and Sun Solaris systems, and can integrate with higher level NMS platforms.

PolyView supports 32-bit Windows OS versions (not 64-bit versions).

Although the screens shown in this guide relate to PolyView running on a Windows system, the screens are identical in function to those that appear in other operating systems.

A note about PolyView upgrades:

The PolyView server performs auto upgrades for clients. The client will receive a notification that an upgrade should be done, and upon acceptance the upgrade procedure will start on the client, based on the software sent from the server. The server will send only the updated files. PolyView supports only the last two released versions for backward compatibility. Older clients (three or more releases back) will be blocked from upgrades.


System Requirements To run PolyView, your system requires the following specifications:

For Windows:

Specification Minimum (up to 7000 elements)

Hardware Type Any type

Processor Core 2, 2.0 GHz

Memory (RAM) 2 GB

Available Drive Space 120 GB

Operating System Windows 2003 Server/XP/Vista

Display Monitor 1280x1024 True Color

Ethernet Ports 1

For UNIX:

Specification Minimum (up to 7000 elements)

Hardware Type SF T5220

Memory (RAM) 8 GB

Available Drive Space 73 GB x 2

Operating System Solaris 10

Display Monitor 1280x1024 True Color

Ethernet Ports 1


Hierachical Approach PolyView operates in a hierarchical manner, whereby some operations will apply to selected network elements and all sub-elements included in the one that was selected.

For example, consider the following network element map.

If the Root is selected, for some operations (such as software download), all relevant Ceragon elements in the system will be affected by the specified operation.

If element A is selected, the operation will apply to A, A1, and A2. It will not apply to B, B1, and B2. For the operation to apply to B and its sub-elements, both A and B must be selected.

If A1 or B1 are selected, the operation will include only A1 or B1 and all sub-elements related to them.


About this Guide This guide describes the PolyView Management System, and explains how it is used.

The body of this guide explains each of the PolyView menu items and options.

The appendixes at the end of the guide provide additional information concerning the system.


Installing PolyView This section provides the PolyView installation procedure and pre-installation instructions.

Important: Note that firewalls may hinder PolyView installation. It is recommended to remove firewall restrictions when installing the PolyView software.

Important: Note that for Windows, you must first install an FTP application; otherwise the installation will fail.

Pre-Installation Before you install PolyView, perform/check the following steps:

Close all applications.

An anti-virus program may inhibit the installation. If you experience a problem installing PolyView, try disabling the anti-virus program for the duration of the installation.

Make sure you have administrator rights on the machine (root on UNIX).

Important! PolyView database is kept when upgrading from PolyView N6.1 release and above. Upgrading from PolyView N6.01 or an older release will erase all previous data in the database. It is highly recommended to backup the database before upgrading.

Restart the computer after the installation is complete.

Installation Procedure PolyView and its related software is installed in the following order:

Install CeraView

Install MySQL

Note that PolyView can be operated only with its internal SQL database (MySQL DB). The MySQL DB is provided as part of the basic PolyView installation but needs to be purchased separately (different software license).

Install PolyView


Install CeraView

1. In Windows, restart the computer after the installation is complete.

Install MySQL

1. If a previous version of MySQL is installed, uninstall it.

2. Install MySQL.

Do not change the default installation location (Windows: c:\mysql, UNIX: /opt/mysql).

3. In Windows, restart the computer after MySQL is installed.

Install PolyView Server and CeraMap

1. If a previous version of PolyView is installed, uninstall it. - Open a DOS command window, type pvstop, and press Enter. - Uninstall PolyView via the Control Panel using Add/Remove Programs.

2. Install PolyView with the Server mode. (See Appendix C at the end of this user guide.)

Note: On Vista systems, right click the install program and select Run as Administrator.

Note: PolyView does not support Vista's User Access Control (UAC). If the server is intsalled on Vista, open the Control Panel, double-click User Accounts, select Turn User Account Control On or Off, and make sure that UAC is not selected.

3. In Windows, restart the computer after the installation is complete.

4. In the PolyView configuration file (located in the Config directory in the PolyView installation directory), configure the Mail server.

If you are setting up a PolyView server, configure the TFTP server address and the full TFTP files directory path. You must configure CeraView to use the same directory for TFTP files.

5. Licensing:

When you install the PolyView server for the first time, it is installed with a “demo” license that will give you one month of work with PolyView.

To obtain a permanent PolyView license, do the following: a. Install PolyView (as explained above) and restart the machine. b. Start CeraMap, and select Help, About. c. Write down the Host ID number. d. Contact Ceragon customer support and report the Host ID number. e. When customer support sends you the license file, copy it to the PolyView/config directory f. Restart the server. g. Start CeraMap, select Help, About, and confirm the updated license information.


Getting Started PolyView is operated through its CeraMap interface. All network element definitions, configurations, and maintenance procedures are performed through the CeraMap interface.

Starting CeraMap

Start CeraMap by double-clicking the CeraMap icon on the desktop.

In the CeraMap Login window, enter your user name and password, and click OK.

The main CeraMap window appears.

Main CeraMap Window


Or, for multi link configurations, the map will include mutli link icons:

PolyView supports multi link map presentation and discovery for the FibeAir® IP-10 G-Series.

Multi Link consists of more than 1 radio link aggregated together, or more than 1 STM-1/OC-3 link aggregated together. The links are established between two neighboring network elements.

Note that current alarms and inventory reports are presented for both links.

Map Icon Colors

If a network element is unreachable (no DCN connection), it will appear on the map with a line across it.

An undiscovered element will appear grey.

A reachable element will appear in the color of its top-most alarm.


Creating the Map The graphic map is built by creating icons that represent elements in your network, or groups that include one or more elements.

Creating an Individual Element

To create an element:

1. On the left side of the CeraMap window, click the right mouse button on the icon of the group to which you want the element to belong (or the root icon, whereby the element will belong to the root list, and not to a particular group), and select Add Network Element.

You can also select the root icon or a group, and, in the menu bar, select Edit, Add network element.

Add Element Window


2. Specify the IP address of the element you want to add, and select User Defined Name if you want to give it a name.

Note about IP Addresses for FibeAir IP-10 G-Series:

While each protected IP-10 G-Series network element represents two IP addresses, in PolyView each one is displayed and treated as one IP address, of slot 1. Due to this convention, all NMS functionality related to this protected node (reports, alarms, etc.) is done on behalf of the slot-1 IP address.

3. If you want to change the default SNMP parameters for the element, click the SNMP tab,and set the parameter values you want, as shown in the example window above.

For IP-10 G-Series elements, select the IP-10 icon and click the Parameters tab to set the correct HTTP communication protocol (HTTP or HTTPS), as shown in the following example window.


4. Click OK.

An icon representing the element you defined will appear on the map with the element's name and IP address. The element will also appear in the list on the left side of the window.

In the following example, several elements were defined in the map.

Elements in the Main CeraMap Window

Note that the color of the element's icon represents the level of its most severe alarm.

For example, green means that the element is operating with no alarms; light red means that the element is operating with one or more major alarms.

In the element list on the left side of the CeraMap window, the color of the icons will also reflect their alarm status. The color of upper level groups and the root level will always be the color of the element in the list with the most severe alarm.


Creating a Group of Elements

To create a group of elements:

1. On the left side of the CeraMap window, click the right mouse button on the root icon, or on the group to which you want to add another group, and select Add Group.

You can also select the root icon or a group, and, in the menu bar, select Edit, Add Group.

Add Group Element Window

2. Specify the name of the group, and select a site level (you can create an unlimited number of levels in the map), or a different icon representing the type of group you want to create.

3. If you want to change the background of the map, select Define background, and click Select.

4. If you defined a background, you can also change the transparency of the background using the Opacity slider.

5. Click OK.

The group you defined will appear on the map and in the element list on the left side of the window.

The following example shows two groups that were created under the root group.


Groups Created under the Root Group

Creating a Symbol

Symbols are icons that represent different items (equipment, logos, etc.), but are not treated as network elements by PolyView (for example, no polling is performed for symbols).

To add a symbol to the map:

1. Select Edit, Add Symbol.


Add Symbol Window

2. You must specify a name for the symbol in the Name field.

3. Select Show name on map if you want the name you specified to appear on the map under the symbol.

4. Select a symbol from symbol icon area and click OK.

Notes:

- If you want to add a symbol that does not appear in the window, you must copy the graphic file (in GIF or JPG format) to the symbol folder in installdir/image/symbols, whereby installdir is the name of the directory in which PolyView was installed. Symbol files can be grouped in sub-folders in the symbols directory.

- Symbol file and sub-folder names cannot include spaces. If you want to include spaces in symbol file or sub-folder names, use underscores (_). For example, the file Ethernet_Bridge.gif, will appear as "Ethernet Bridge".

- Add symbol files only to the PolyView server. All media files are automatically copied to all CeraMap clients.

- Links can be defined between symbols and other symbols or network elements.

- You can delete and move symbols the same as with other elements in the map.


Working with the Client This section explains how to work with elements and groups in the CeraMap interface.

Finding an Element or Group If your map includes a large number of elements, you can find a specific element or group using the Find option.

Click the right button on an element or a group, and select Find.

or

Select Edit, Find in the menu bar.

or

Click the Find icon in the tool bar .

Find Element or Group Window

Enter the text you assigned to the element, or its IP address, choose the desired options, and click Find.


Deleting an Element or Group To delete an element or a group, click the right button on the element or group you want to delete (in the element list on the left side of the window, or in the map itself), and select Delete elements.

You can also select an element or a group, and then select Edit, Delete elements in the menu bar.

To select more than one element, hold the Ctrl key down and click the select mouse button.

Note that you cannot delete the root element or the element that represents the PolyView server.

Moving an Element or Group To move an element or a group to another group, or to the root list, click the right button on the element or group you want to move, and select Move element.

You can also select an element or a group, and then select Edit, Move element in the menu bar.

Move Element or Group Window

Select the group to which you want to move the element or group, and click OK.

To select more than one element to move, press the Ctrl key and click the select mouse button.

If the elements you want to move have links between them, the links will be moved as well.

If the elements have links to other elements that are not to be moved, the links will be deleted.

You can also use drag & drop by selecting the element and then dragging it to its new location.


Element/Group Properties To view the properties of an element or a group, click the right button on an element or a group, and select Properties.

You can also select an element or a group, and then select Edit, Properties in the menu bar.

Element/Group Properties Window

In this window, you can specify the element’s IP address, system name, location, and contact person.

You can also specify a name for the element by clicking Define name and entering the name in the field. The name you enter will appear in the icon representing the element in the map. You can use the name you defined to search for the element in the map using the Find option described earlier in this online help section.

Use the SNMP Parameters and HTTP areas to configure SNMP or HTTP access per network element.


Creating a Link Links in the map show how elements and groups are connected in the network.

To create a link, select two elements or groups, click the right button on one of them, and select Add Link.

You can also select two elements or groups, and then select Edit, Add Link in the menu bar.

Link Properties Window


First, select the width of the graphic line that will connect the elements on the map. Then select the type of connection - Radio, Multi Radio, Line, Multi Line, Protected, or Generic, and click OK.

The following example shows three linked elements in the map.

Three Linked Elements in the CeraMap Window

The following example shows two linked groups in the map.

Two Linked Groups in the CeraMap Window

The alarm severity level indicated by the connection line is calculated by CeraMap. The level will be that of the most severe alarm that exists in a link between elements of the first group with elements of the second group.

Note that you can add a name to a link. By default, the link name appears only as a tool tip (when the mouse cursor is placed over the link). You can change the default in the Displayed link name on map field in the CeraMap Configuration Utility, so that the link name will always appear in the map. (The field is explained in the CeraMap Configuration section.)


Creating a Text Element To add a text element to the network map:

1. Place the cursor at the desired location in the map, click the right mouse button, and select Add Text. You can also select Edit, Add Text in the menu bar.

Add Text Window

2. In the Text field, enter the text you want to appear in the map. Each element can include up to 80 symbols.

3. After you specify the text, you can customize it by selecting the desired attributes in the different fields.

Note that the font you select must exist on all computers running CeraMap. If the font you select does not exist on a computer running CeraMap, the text will appear in a different font.

In addition, note that the Sample area may display only part of the actual text. The level of opacity is not shown in the sample, and for border size, only the simple border style will be displayed.


Moving One Level Back

To move one level back in the map, click the Up Level icon in the tool bar , or select Edit, Map Up One Level in the menu bar.

Updating the Map To update the map with the latest information from the PolyView server, click the Refresh icon in the tool

bar , or select File, Refresh in the menu bar.

Exporting CeraMap Data You can export CeraMap data (topology and trigger information) to an external file by selecting File, Export Data.

Export Data Window

After you export CeraMap data, the exported file can be imported back into PolyView (for example, after a server upgrade), or to another PolyView server.

You can export an entire tree if you select the root element and then select File, Export Data. Using the same method, you can export a single sub-tree, by selecting the sub-tree root before the export.

For an export operation, you can select the file you want to export the data to, and the data types you want to export.


Importing CeraMap Data To import a CeraMap data file select File, Import Data.

Import Data Window

The import will be done under the currently selected group.

For an import operation, you can select the file to import, which data types you want to import from the file, and whether or not to update duplicated items.

Updating duplicated items means that when you import an entity that already exists (a network element with the same IP, or a group with the same name), you can request that PolyView update the element attributes from the imported file (for example, an element's name).

Network Auto Discovery PolyView can scan the network and automatically and add supported elements to its map.

To start scanning:

1. In the map list on the left side of the window, select a group to which all newly discovered elements will be added.

2. Select File, Network Auto Discovery.


Network Auto Discovery Window

3. The Discovery Scope area shows a list of existing Discovery Scope definitions.

Click Add to define a new scope.


Scope Settings IP Range Window

Select the type of scope you want, IP Range or IP Subnet.

If you selected IP Range, in the First IP and Last IP fields, specify the range of IPs to which the network scan will apply.

If you selected Subnet, in the IP field enter the subnet IP, and in the Mask field enter the subnet mask to which the network scan will apply.

If network elements within the subnet or IP range do not use the default SNMP settings, click the SNMP Parameters tab, and set the correct values.

Scope Settings SNMP Parameters Window


In the Version field, select the SNMP version of the network elements you want to include in the scan. The supported SNMP versions are V1, V2c, and V3.

For Port, use the up/down buttons to select the port number of the element you want to include in the scan.

For Retries, select the amount of retries the system will perform, before sending an error message.

For Timeout, select the amount of time the system will wait before timing out.

For Read/Write Community enter the community names in their respective fields, to include those filters in the scan.

Click the HTTP Parameters tab to to set the desired HTTP communication protocol (HTTP or HTTPS).

Scope Settings HTTP Parameters Window

Click OK.

Note: If you want, you can add more than one range or subnet, by clicking the Add button in the Network Auto Discovery window.

4. Click Discover to start the discovery process.

The Discovery Status area shows the progress of the scan. To view information about errors that may have been detected during the scan, click the Error Log tab.


Notes:

- The duration of the discovery process depends on the network size and the connection speed. The time may vary from several minutes to several hours.

- Newly discovered elements will be added to the group you selected. If a discovered element already exists in the target group or in one of its sub-groups, the original element will be retained, and the discovered one will not be added.

- During the process, PolyView will also search for connectivity between elements. If a connection between elements is found, a link will automatically be generated for them and will appear in the map.

- If more than two elements are found to be linked, PolyView will create a sub-group for them, and all the linked elements will be moved to that sub-group.


PolyView Security This section explains how to set up PolyView security.

Note: For security reasons, security settings can only be run locally on the PolyView server machine.

Starting the Security Application To start the PolyView Security application, select Start, Programs, PolyView, PolyView Security.

or

In CeraMap, select Settings, Security Settings.

The Security application main window appears.

PolyView Security Application Main Window


Using the Security Application Security for PolyView is obtained by creating users and user groups with designated access rights to the different PolyView components.

Note that upon installation, two users and two groups are created, as follows:

Users:

Admin - Always placed in the Admin group

Viewer - Initially placed in the Observer group

Groups:

Admin - Full access

Observer - Read-only access

The administrator can add new users and groups, and modify existing ones, but cannot rename or delete the Admin user or group.

Creating a New User To create a new PolyView user:

1. In the main window (shown above), click Users, and select Add User.

The User Configuration window appears

PolyView Security Application User Configuration Window

2. Enter the new user’s name and password in the fields at the top of the window.


3. In the Access by Subnet area, you can assign different access rights to the new user according to subnet. For example, you can give the user Administrator rights on one subnet and Observer rights on another.

To define the user's rights category, double-click the line that you want to define.

The Web EMS User and Password columns are used when you double-click an icon of a device in the topology map. For IP-10, an internet browser window opens with the Web EMS of that device.

Generally, the first page of the Web EMS prompts you for user name and password, but when you provide values in the Web EMS columns, the system uses the values you provide to automatically log in (known as “silent login”).

Notes:

* You cannot enter the same subnet twice for the same user.

* If none of the subnets you entered match an IP the user tries to connect to, the user will be denied access to that IP.

* If more than one subnet matches an IP the user tries to connect to, the group that belongs to the subnet that matches the IP the closest will be used for the IP access. For example, you created the user “Joe” with the following rights: 172.24.0.0 : Observer, and 172.24.30.0 : Administrator. If Joe requests access to 172.24.30.5, he will be granted Administrator rights for that IP. Even though both subnets you assigned to Joe match the IP he requested, the subnet 172.24.30.0 is closer to the IP than the other one.

In order to obtain default Observer rights for IP addresses that do not match any of the subnets in the list, you need to assign the subnet 0.0.0.0 : Observer to the user, and the subnet mask must also be 0.0.0.0.

* Whenever a user performs an operation that is not applicable to a specific network element (such as changing the security configuration) access permissions will be calculated by the "Default Access" line (which contains the Subnet IP and Mask equal to 0.0.0.0). If a "Default Access" line does not exist for a user, that user will not be able to access general network features.


Working with Users Once you create users, you can perform several user-related operations.

To perform a user-related operation:

1. In the main window, expand the Users list, and click the name of a user you want to work with.

PolyView Security Application User Options

2. Select Configure User to modify the user configuration as described in the section Creating a New User above. The User Configuration window will appear for you to make changes.

3. Select Copy User if you want to duplicate the user you selected. The Copy User window appears.

PolyView Security Application Copy User Window


Enter the new user’s name and password, and click OK. A new user will be created with the same access rights as the user you chose to copy.

4. Select Delete User if you want to delete the user you selected.

Note that you cannot delete the Admin user.

5. To import users from an external file to your current PolyView session, in the main security window select File, Import Users.

To export users from your current PolyView session for the CeraView Security application or a different PolyView session, in the main security window select File, Export Users.

Creating a New User Group

User groups can be assigned collective rights to different PolyView components.

To create a new group of users:

1. In the main window, click Groups, and select Add read-only Group or Add read-write Group.

PolyView Security Application Create User Group

If you select Read-Only Group, initially the group will only have read-only access rights. If you select Read-Write Group, initially the group will have read-write access rights.

2. In the Enter Group Name window that appears, enter a name for the new group, and click OK.


Working with Groups Once you create groups, you can perform several group-related operations.

To perform a group-related operation:

1. In the main window, expand the Groups list, and click the name of the group you want to work with.

PolyView Security Application Group Options

2. Select Configure Group to rename the group. Note that you cannot rename the Admin group.

Note that you cannot rename the Admin group.

3. Select Copy Group if you want to duplicate the group you selected. The Copy Group window appears.

Enter the group’s name, and click OK. A new group will be created with the same access rights as the group you chose to copy.

4. Select Delete Group if you want to delete the group you selected.

Note that you cannot delete the Admin group.

5. For each group, to configure access rights for specific PolyView components, double-click the key icon beside the component name. The Access Rights window appears.


PolyView Security Application Access Rights Window

Mark the checkboxes of each PolyView component you want the group to have access to, and click OK.

Security Settings To configure security PolyView security, select File, Settings.

PolyView Security Settings Window


The administrator can select the following options:

- Enable users to change their own passwords (otherwise, only the administrator can change user passwords).

- Users must create a password upon their initial login to PolyView.

- Expiration time of passwords (after which the user must enter a different password).

- Minimum password length.

- Password complexity (whether or not the password must also contain numbers).

If users can change their own passwords, a new menu item will appear in the main window.

Select File, Change user password to change the current password.

Change User Password Window

In this window, you must enter the existing password, and then the new password twice.

When you click Apply, PolyView changes the password in its security database, and will try to change the password in the element manager. Note that for this to work, the "Users can change their passwords" option must also be enabled in the element manager security application.


Updating the Server

After you make changes in the security settings, you can dynamically update the PolyView server with the changes you made, without restarting the server. To do so, select File, Update PolyView Server.

Note that changing the settings will not affect operations that were already defined before a security change was made. For example, if you configured a delayed software download, and then your permission to perform software download was revoked, the software download you defined before your permission was revoked, will still be executed.

PolyView Database Access

To ensure a more secure PolyView database, in the Main window, click the Database tab.

Provide a user name and password for access to the database, and click Apply.


Server Configuration This section explains how to use the Server Configuration Utility.

Note: For security purposes, this utility can only be run locally on the PolyView server.

Starting the Utility To configure PolyView, select Start, Programs, PolyView, PolyView Config.

Or, in CeraMap, you can select Settings, Server Options.

The PolyView Configuration Utility appears.

PolyView Server Configuration Utility General Window


The following sections are available by clicking the appropriate icons on the left side of the window:

Used to set general parameters, such as server addresses and port numbers.

Used to set polling values.

Used to set TFTP server parameters.

Used to set security-related parameters.

Used to configure main and standby server operation.

Used to set alarm-related parameters,

Used to set advanced parameters, such as SNMP related values and others.

Using the Utility The following are instructions for working with the PolyView Configuration utility.

1. Click the General Parameters icon .

In the General section (shown above in Starting the Utility), select or enter values for the PolyView Server port, SMTP (Simple Mail Transfer Protocol) server, and User Actions Logger port.

The "Sent By" Email Address will be used when the server sends reports by email.

The Keep Actions History field is used to specify the number of days PolyView will keep records of user actions in its database.

In the Enable ENM Proxy field, select True if you want the ENM client to connect to an element via PolyView. Note that to use this option, the ENM must be capable of working via a proxy.


If you selected True for this option, in the ENM Proxy Port Number field, specify the number of the port from which PolyView will receive proxy requests.

For Enable HTTP(S) Proxy, whenever the web browser does not have direct access to the network element, the NMS server can act as a proxy to connect the web browser to that network element. Note that the specific web browser must support the mode of working with the NMS server as proxy.

For HTTP Proxy Port Number, enter the default port number on which the server will listen for proxy requests from the web browser. The minimum allowed value is 1024, the maximum is 65536.

To reset the parameters to their original values, click Restore Defaults.

To reload the page with the last saved values, click Reload Page.

2. Click the Polling Configuration icon to set polling values.

PolyView Configuration Utility Polling Window


Note: The polling values that you set in this window relate to all network elements.

Set Dynamic Polling Interval to the interval that PolyView will use to poll dynamic inventory information from the network elements. The value will be rounded to the nearest quarter of an hour.

Set Static Polling Interval to the interval that PolyView will use to poll static inventory information from the network elements. The value will be rounded to the nearest quarter of an hour.

Set Reports Polling Interval to the interval that PolyView will use to poll performance information from the network elements. The value will be rounded to the nearest quarter of an hour.

Set Config Upload Interval to the interval that PolyView will use to upload the configuration file from the network elements. The value will be rounded to the nearest quarter of an hour.

Set Alarms Polling Interval to the time (in minutes) that PolyView will use to poll current alarms from the network elements.

Set Keep PM History to the amount of time (in days) PolyView will keep Performance Reports.



3. Click the File Transfer icon to set TFTP server values.


PolyView Configuration Utility File Transfer Window

In the TFTP Server Address field, specify the Trivial File Transfer Protocol server IP. If you leave this field empty, PolyView will try to detect which IP address to use, via the PC routing tables.

In the TFTP Files Location field, specify the directory in which the element software files are located.

In the TFTP Timeout field, select the amount of time (in seconds) the system will wait after a TFTP command before timing out.

In the TFTP Retries field, select the number of times a TFTP request will be made after a timeout.

FTP Server Protocol defines the FTP (File Transfer Protocol) mode of the external FTP server, FTP or SFTP.

FTP Server Address defines the FTP (File Transfer Protocol) address of the network element.


FTP Server Username defines the FTP (File Transfer Protocol) user name assigned to the network element.

FTP Server Password defines the FTP (File Transfer Protocol) password assigned to the network element.



4. Click the Security icon to set PolyView security-related values.

PolyView Configuration Utility Security Window


For Inactive Client Disconnect Time, specify the time (in minutes) of inactivity, after which the server will disconnect the client. The value 0 means that an inactive client will not be disconnected. The minimum value is 0; the maximum value is 30000.

For Allowed Consecutive Failed Logins, specify the number of times a user can attempt to login. After the specified number of times, a management trap will be issued, and the user will not be able to log in again for the amount of time specified by the Block User Period option.

For Block User Period, specify the number of minutes a user will not be able to log in after failing to log in correctly the amount of times specified by the Allowed Consecutive Failed Logins option.

For Secured Client Connection, select True for a secure connection between the client and server. In this configuration, the server will reject non-secure connections. In Secure mode, CeraMap and CeraView (when using PolyView as a proxy) will automatically be set for secure communication.

Radius Authentication - PolyView supports the Radius client for remote authentication of users. Select On to enable user authentication using the Radius client, or Off to disable this option. If Radius is enabled, the user is authenticated via the Radius server and locally as well. If the password was authenticated by the Radius server and locally, the user will be accepted in the system. If Radius authentication is Off, the user will be authenticated only locally. PolyView supports the PAP authentication method (as defined in the Radius standard).

Radius server host - the IP of the Radius server.

Radius server number of login retries - the number of seconds between the authentication messages that PolyView will continuously send if the reply did not arrive.

Radius server retry timeout - the number of seconds between the times PolyView sends an authentication message, after a timeout occured.

Radius server secret - a shared security secret configured in PolyView and the Radius server.

Notes Concerning Radius

The admin needs to add a user in PolyView and in the Radius server. The privileges of the user should be configured only in the Radius server. The user should configure only the user name and password in the Radius server. Using PolyView’s advanced privilege mechanism, you can define several groups and users per group. Since the user can have a set of admin privileges for some subnets, and viewer privileges for others, privileges must therefore be defined also in the PolyView server.

When the Radius server is enabled, but not available, the user will not be authenticated.

When the user password is not the same in both the Radius server and in PolyView, the user will not be authenticated.


5. Click the Redundancy icon to configure a secondary server to back up the main server.

PolyView Configuration Utility Redundancy Window

PolyView has built-in support for redundancy configuration. This configuration includes two PolyView servers: a main server, which is generally active, and a secondary server, which is generally located at a remote location and is in standby mode.

If the main server is down, the standby server can be configured to automatically take over. When the main server starts again after a failure, the secondary server returns to standby mode. In standby mode, the secondary server does not send traps or triggers.

In the Server Role field, select one of the following modes of operation:

Stand Alone - The default setting. No redundancy is configured.


Main Server - The main server, which will be connected to a secondary server. If no secondary server exists, an alarm will be raised.

Standby - Auto Switch - The server is configured as a secondary server. After disconnection from the main server for x minutes (user-defined), it will automatically take over from the main server. When a connection to the main server is re-established, it will return to its standby state.

Main Server Host Address is used only if you selected Standby in the Server Role field. (The port number is configured in the General section of the window.)

Connection Timeout to Standby Server is used only if you selected Main Server in the Server Role field. Specify the amount of time, in minutes, after which the main server will generate an alarm if it was disconnected from the standby server.

Standby Activate Time is used only if you selected Standby - Auto Switch in the Server Role field. Specify the amount of time, in minutes, after which the standby server will take over from the main server if a failure occurred in the connection between them.

Standby Deactivate Time is used only if you selected Standby - Auto Switch in the Server Role field. Specify the amount of time, in minutes, after which the standby server will be muted (stops sending traps and triggers) when the main server resumes operation.

For Main - Standby Synchronization, select one of the following options:

Disabled - disables the synchronization feature.

Full (both directions) - causes changes in one server (main or standby) to be made in the other server as well.

Only from Main to Standby - (recommended setting for normal system operation) causes changes in the main server (for example, a new element is added), to be made in the standby server as well, but not vice versa.

Only from Standby to Main - causes changes in the standby server to be made in the main server as well, but not vice versa.

The following data will be included in the synchronization:

- Topology changes

- Trigger definitions

- Security settings

- Media files (images and sound files)

Note that configuration files are not synchronized, since they contain settings that may be different in the main and standby servers.

For Sync Interval, specify the amount of time, in minutes, between synchronization updates.

Mute Standby Server Poll Mode is used only if you selected Standby in the Server Role field. The options in this field are used to save network bandwidth.

Select one of the following options:


No Data Polled - When the secondary server is in standby mode, polling of data from network elements will be disabled. When the server becomes active, polling will resume.

Poll Only Alarms - This is the recommended and default setting. When the secondary server is in standby mode, only alarm information will be polled from network elements.

Poll Alarms and Inventory - When the secondary server is in standby mode, only alarm and inventory information will be polled from network elements.

Poll All Data - When the secondary server is in standby, all data will be polled from elements.

Additional Server-Related Notes

• If no connection is detected between the main and standby servers for more than x minutes (user defined):

- It will raise the alarm “No Connection with Standby Server”

- In Auto mode, the secondary (standby) server becomes active, and will:

* start sending traps and triggers

* start accepting client connections

* raise the management alarm “No Connection with Main Server”

* start polling network elements

When the connection is resumed and is stable for y amount of time (user defined):

- The main server clears the “No Connection with Standby Server” alarm.

- If in Auto mode, the secondary (standby) server will go to standby mode, and will:

* clear the management alarm “No Connection with Main Server”

* notify about new client connections, and send the message “Main server (IP) is active” to connected clients

* stop sending traps and triggers

* limit polling (by default, will only poll alarms)

• When a security file is updated, the standby server reloads the file, and immediately begins to use it.

• Network elements should be configured to send traps to both servers.


6. Click the Alarms icon to set PolyView alarm-related values.

PolyView Configuration Utility Alarms Window

In the Email Format field, click the drop-down list and select the format you want for email messages triggered by alarms, or generated by offline reports using the CLI. If you select, HTML, you can use HTML tags to control the way the messages appear. For Max Initial Number of Alarms, specify the maximum number of alarms that will appear in the alarm log when the window is open. By system’s minimum is 1000 and the maximum is 50000.

In the Ignore Heartbeat field, select True to cause PolyView to disable the heartbeat feature. The heartbeat is a trap that is sent by a network element every x amount of time (user defined). By default, the trap is ignored by PolyView (it is not stored in the server database, not added to the alarm log, and does not activate a trigger). However, if you configure trap forwarding, the heartbeat trap will be forwarded, as is, regardless of the value you select for the Ignore Heartbeat parameter.


For Keep Alarms History, specify the number of days you want PolyView to keep alarm log information. Note tha alarms that are open (raised) will be kept until they are closed, regardless of the value you set for this option. The minimum value allowed is 5; the maximum value allowed is 365.

7. Click the Advanced Configuration icon to set advanced PolyView parameters.

PolyView Configuration Utility Advanced Parameters Window

In the Max Concurrent Tasks field, specify the amount of tasks you want PolyView to run simultaneously.

The VC Calculation from KLM field is for ADM tributary paths. This parameter defines the formula used to calculate the VC (Virtual Container) from the KLM values.


In the Select Interface Language field, select the language in which you want user interface to appear. Note that this feature requires a separate software license.

In the Max Memory Allocation (MB) field, specify the maximum amount of memory the application can allocate. The minimum is 256 MB, the maximum is 8192 MB.

In the Application Time Zone field, specify the time zone to be used. Normally you should leave this field empty. Specify the zone only if the application time is not calculated correctly.The format is GMT+/-<Offset>, with no spaces between the parameters. For example: GMT+2.

In the Threshold of Free Disk Space field, specify the amount of free disk space below which an alarm will be generated.

In the Threshold of Average CPU Load field, specify the system load average above which an alarm will be generated.


Client Configuration The Client (CeraMap) Configuration Utility lets you configure different parameters that control the way the client operates.

Starting the Utility To configure CeraMap, select Start, Programs, PolyView, CeraMap Config.

Or, in CeraMap, you can select Settings, User Settings.

The CeraMap Configuration Utility appears.

CeraMap Configuration Utility General Window


The following sections are available by clicking the appropriate icons on the left side of the window:

Used to set general parameters, such as entity name format.

Used to set host server parameters.

Used to set advanced parameters, such as the connection check interval.

Using the Utility

1. Click the General parameters icon .

In the General section (shown in the figure under Starting the Utility above), you can configure the following:

In the Displayed Entity Name Format field, select the format you want for the element name. The name appears in the icon that represents the element in the map.

In the Display Link Name on Map field, select Show Link Name if you want the name of the link to appear on the map. By default, link names are hidden.

In the Default Link Width field, specify the default width of the line that will represent a link between two elements in the map.

In the Map Background Color field, click the button to the right of the field and select the color you want for the map background.

In the Max Number of Trigger Messages field, specify the maximum number of trigger messages that may be displayed for the user.

In the Max PM Report Lines field, specify the maximum number of entries the server will retrieve when a performance monitoring report is requested.


To reload the page with the updated information, click Reload Page.


2. Click the Remote Hosts parameters icon .

CeraMap Configuration Utility Remote Hosts Window

In the Primary NMS Server Host Address field, specify the name of the primary host server.

In the Primary NMS Server Port Number field, use the up/down arrows to select the primary server port.

In the Secondary NMS Server Host Address field, specify the name of the secondary host server (if one is being used).

In the Secondary NMS Server Host Address field, use the up/down arrows to select the secondary server port (if one is being used).




3. Click the Advanced parameters icon .

CeraMap Configuration Utility Advanced Parameters Window

In the Play Sound Minimal Gap field, specify the minimal time (in seconds) between sounds for a triggered alarm.

In the Windows Refresh Interval field, use the up/down arrows to select the amount of time (in seconds) between information updates in CeraMap windows.

In the Media Files Update Interval field, use the up/down arrows to select the amount of time (in minutes) PolyView will wait between media file updates. Media files are stored in the PolyView directory, and include graphic map background files and audio files.

In the Connection Check Interval field, use the up/down arrows to select the amount of time (in seconds) between connection verifications, whereby CeraMap verifies its connection with the PolyView host server.

In the Select Interface Language field, select the language in which you want the CeraMap interface to appear. Note that this feature requires a separate software license.

In the Application Time Zone field, specify the time zone to be used. Normally you should leave this field empty. Specify the zone only if the application time is not calculated correctly.The format is GMT+/-<Offset>, with no spaces between the parameters. For example: GMT+2.




Trap Forwarding Configuration Trap forwarding parameters determine how PolyView will work with traps.

Note: For security purposes, trap forwarding can only be configured locally on the PolyView server.

Important: For trap forwarding to operate properly, configure the trap options in all network elements, as follows:

Report traps of far end IDU - de-select

Use different alarm ID for each alarm type - select

Send traps with extended alarm information - select

To configure trap forwarding:

1. On the desktop, select Start, Programs, PolyView, Trap Forwarding Config. Or, in CeraMap, select Settings, Trap Forwarding Options.

Trap Forwarding Configuration General Window


The following sections are available by clicking on the appropriate icon on the left side of the window:

Used to set general trap forwarding parameters, such as the forwarding mode, trap listening port number, and others.

Used to set trap forwarding parameters specific to NSN’s NetAct application.

Used to set advanced trap forwarding parameters, such as receive trap logger disable/enable, and others.

2. Click the General Trap Forwarding Configuration icon . The General section of the Trap Forwarding Configuration window appears (shown in step 2 above).

In the Trap Forwarding Mode field, select one of the following options:

Off Disables trap forwarding.

Regular Forwards the trap exactly as it was received.

NSN Translates the trap for NSN’s NetAct application.

NSN Alarm Synchronization - Supports incoming alarm translation and NSN's NE3S agent.

Note: If the mode is set to Regular or NSN, all network elements must send the traps to the port specified in the Trap Listening Port field. If the mode is set to Off, all network elements must send traps directly to PolyView (the port specified in the Management Alarms Port field in the Advanced section of the utility (the default value is 1621).

In the Trap Listening Port Number field, select the trap listening port. The standard port is 162. Change this number if it is already being used by another SNMP service. In addition, remember to configure the network elements to send traps to the correct port.

In the Local Host Address field, enter the IP address or name of the local host. Leave the value 0.0.0.0 to bind all IP addresses.

In the Forward Traps to Hosts field, enter a list of host names and port numbers to which traps will be forwarded. Use the format <host IP>:<port>.




3. Click the NSN NetAct Trap Configuration icon to set NetAct-related trap forwarding parameters.

Trap Forwarding Configuration NSN NetAct Window

In the SNMP Agent Address field, enter the NetAct agent IP address.

In the SNMP Agent Port Number field, enter the NetAct agent port.

Note that for NSN Netact, the following additional parameter is required:

In the NMS Server ID field, you may want to change the value if multiple NMS servers are connected to the same NSN server. In such a case, make sure that each NMS server has a unique ID.




4. Click the Advanced Trap Forwarding Configuration icon to set advanced trap forwarding parameters.

Trap Forwarding Configuration Advanced Parameters Window

In the Heartbeat Interval field, if you specify a value, a heartbeat trap will be generated every x minutes (the number you enter in the field) to tell your system that the trap mechanism is working. The value 0 means that a heartbeat trap will never be sent.

In the Management Alarms Port field, specify the internal port used to send management alarms to the trap forwarding mechanism.

In the Auto Add Network Element field, select Enable if you want an undefined network element in the map to be added to the PolyView server automatically as soon as a trap is received from that element.

In the Send Cleared Traps with Zero Severity field, select Enable if you want cleared traps generated by the NMS server to be sent with zero severity. If you select Disable, they will be sent with the severity of their raised alarm. This parameter does not affect cleared traps that arrive from the units and are forwarded via the Trap Forwarding mechanism.




Configuration Broadcast Various network settings can be configured using PolyView.

To configure network settings:

1. In CeraMap, select one or more elements you want to work with.

2. Select Tools, Configuration Broadcast, or click the Configuration Broadcast icon .

The Configuration Broadcast window appears.

While working in the window, you can use the following buttons:

Click Set to implement the settings for the network elements. After you click Set, the Configuration Log area displays the results of the operation.

Click Abort to cancel the configuration process that begins after you click Set.

Click Load to load configuration settings from a file.

Click Save to save the current configuration in a file.

3. Choose the product you want to work with using the Select drop down list, either IP-10 or 1500R/3200T/IP-MAX. The General group relates to all products.

To enable the options in a window, on the left side of the window click the checkboxes beside each option group you want to enable.

IP-10 Options

The IP-10 options appear when you choose IP-10 from the Select drop down list.

1. For IP-10, the Traps window appears as follows:


Select the Send traps on operational status change only option if you want traps to be sent only when the system status changes.

In the Send Traps for Alarms with Severity area, you determine which alarm severity levels will be sent as SNMP traps to each manager. In each manager column, select the alarm severity levels you want to include for each manager.

2. The General window appears as follows:


In the GMT Time Zone area, set the offset amount from the GMT.

For Daylight Saving Time, set the start and end dates and the offset.

3. The Thresholds window appears as follows:


Click the E1/DS1 checkbox on the left side to enable the interface options.

Set the Excessive Error and Signal Degrade thresholds to the values you want.

4. The Security window appears as follows:


In this window you can set the Web Protocol and activate the Telnet Protocol.

In the SNMP Parameters area, configure the way SNMP works. Select the version, and specify the Read/Write communities.

5. The Users window appears as follows:


At the top of the rigt side of the window, select the Add User or Delete User option.

For Add User, select the desired privilege, and enter the user name and password.

Note: If you add a new user, the password sent to the element is temporary. Upon your first login to the element, you will need to change the password.

For Delete User, enter the user name and click Set.

For Password Aging select the value you want, and specify when the user account will expire, or choose Never Expired for an ongoing account.

General Options

The General options appear when you choose General from the Select drop down list.

1. The Traps window appears as follows:


In the Managers IP address area, specify the IP addresses of the managers to which you want traps to be forwarded.

In the Trap Port area, specify the number of the port through which the traps will be communicated.

2. The General window appears as follows:


Set the current date and time.



Click the checkboxes on the left side to enable the interface options.

For each interface your system includes, set the Excessive Error and Signal Degrade thresholds to the values you want.

1500R/3200T/IP-MAX Options

The 1500R/3200T/IP-MAX options appear when you choose those products from the Select drop down list.

1. The Traps window appears as follows:


In the Send Traps for Alarms of Group area, you determine which alarms will be sent as SNMP traps to each manager. In each manager column, select the alarm types you want to include for that manager.

Standard traps include serial number - select this option if you want trap messages to include the IDU serial number.

Report traps of far end IDU - select this option if you want remote IDU trap messages to be reported locally.

Use different trap ID for each alarm type - select this option if you want each alarm type to be reported with a unique ID.

Send “clear” traps with zero severity - when enabled, Clear traps are sent with a severity of 0. When disabled, Clear traps are sent with the same severity as the equivalent Raised trap.

Send traps with extended alarm information - select this option if you want additional alarm details, such as alarm ID, origin, and unit from the current alarm table to be added to the end of each radio-related trap.


Trap heartbeat period - if you select this option, a heartbeat trap will be generated every x minutes (the number you enter in the field) to tell your system that the trap mechanism is working.

In the Send Traps for Alarms with Severity area, you determine which alarm severity levels will be sent as SNMP traps to each manager. In each manager column, select the alarm severity levels you want to include for each manager.

2. The Network window appears as follows:

To enable the options in the window, on the left side of the window click the checkboxes beside each option you want to enable.

For NTP Server IP, specify the IP address of NTP server you want to use.

For NTP Update Interval, specify the interval you want the system to wait before checking the NTP server to update system synchronization.

For Router IP, specify the IP address of the router you are using.

In the GMT Time Zone area, set the offset amount from the GMT.


For Daylight Saving Time, set the start and end dates and the offset.


Click the checkboxes on the left side to enable the interface options.

For each interface your system includes, set the Excessive Error and Signal Degrade thresholds to the values you want.


Viewing Alarms PolyView enables current and historical alarm displays. Current alarms can be filtered and acknowledged, and you can choose to launch CeraView (Ceragon's element management software) due to a particular alarm.

Current Alarms To view and work with current alarms:

1. Select one or more elements in the map, click the right button in the map, and select Current Alarms.

You can also select Reports, Current Alarms in the menu bar, or click the Current Alarms icon in the tool bar.

The following is an example of current alarms for elements in the network.

Example of Current Alarms Window

2. To acknowledge an alarm, select it in the list, and click the Acknowledge icon . (You can also select more than one alarm and perform a collective acknowledgment for all of them.)

You will be prompted to add a note about the acknowledgement. If you don't want to add a note, click


OK without entering text in the field.

After you acknowledge an alarm, a check mark will appear beside it in the Ack column.

You can also add a note for an alarm without acknowledging it, by selecting the alarm and clicking the

Add Note icon .

3. To hide an alarm from the visible list, select the alarm (or several alarms) and click the Hide icon .

You will be prompted to add a note about the hidden alarm. If you don't want to add a note, click OK without entering text in the field.

The alarm you chose to hide will be removed from the list, and placed in the hidden alarms list. To view all hidden alarms, select Action, Show Hidden. When you select this command, the window displays all alarms that are normally hidden. To make them visible again, select one or more of the alarms, and

click the Show icon .

4. For each alarm listed, you can view its probable cause and corrective actions by placing the cursor on the line of the alarm, as shown in the example above.

5. To view the details of a particular alarm, select the alarm, and click the Alarm Details icon .


Alarm Details Window

Use the buttons at the bottom of the window to acknowledge the alarm (if it wasn't already acknowledged), add a note to describe it, or hide it from the main alarm list.

Click the User Actions History tab to view a log of the actions performed for the alarm.

The Advanced tab is used by technical support personnel to view additional alarm information.

6. To filter the alarms in the list, select Report, Filter in the menu bar.


Alarm Filter Definition Window

Click Add to define a filter.

Add Filter Window

Click the drop down lists and select the Field, the Operator, and the Value. Then click OK.

The filter you defined will operate on the alarms in the Current Alarms list, and will remove any alarm that does not meet the filter criteria.

To edit a filter you defined, select the filter and click Edit.

To delete a filter you defined, select the filter and click Delete.

To terminate a filter, select Report, Clear Filter in the Current Alarms menu.

7. If, due to a particular alarm, you want to launch CeraView, select the alarm, and click Actions, Launch CeraView. CeraView will be launched for the unit with the associated alarm.

8. To save the current alarm list to a text file, select File, Save As in the menu bar.


Historical Alarm Log To view a report of historical alarms:

1. Select Reports, Alarm Log in the menu bar, or click the Alarm Log icon in the tool bar.

Select Alarm Log Interval Window

2. Specify the start and end dates of the alarm report, and click OK.

The following is an example of an historical alarm report.

Example of Alarm Log Window

Note: By default, the alarm log is a logical view, meaning that Raise and Clear commands generate a single alarm, and are shown on the same line. At times, it may be easier to view the Alarm Log in a chronological view (with Raise and Clear generated alarms on different lines).


To open a chronological view window, in the Alarm Log window, select Report, Chronological View.

Example of Alarm Log Chronological View

3. To acknowledge an alarm, select it in the list, and click the Acknowledge icon . (You can also select more than one alarm and perform a collective acknowledgment for all of them.)

You will be prompted to add a note about the acknowledgement. If you don't want to add a note, click OK without entering text in the field.

After you acknowledge an alarm, a check mark will appear beside it in the Ack column.

You can also add a note for an alarm without acknowledging it, by selecting the alarm and clicking the

Add Note icon .

4. To hide an alarm from the visible list, select the alarm (or several alarms) and click the Hide icon .

You will be prompted to add a note about the hidden alarm. If you don't want to add a note, click OK without entering text in the field.

The alarm you chose to hide will be removed from the list, and placed in the hidden alarms list. To view all hidden alarms, select Action, Show Hidden. When you select this command, the window displays all alarms that are normally hidden. To make them visible again, select one or more of the alarms, and

click the Show icon .


Alarm Triggers Triggers are actions taken whenever alarms are generated due to criteria that you define.

To create alarm triggers:

1. Select Tools, Trigger Configuration.

Alarm Trigger Definition Window

2. Click Add to define a trigger.


Trigger Definition Window

3. In the Trigger Name field, enter a name for the trigger you want to define.

4. In the Activation Conditions area, you can define a trigger based on the following options:

- Trap ID - if you know the ID of the trap you want to use, select this option, click the drop-down list, and select the trap.

- Severity - select one or more alarm severities that will trigger the action you specify when received.

- Description - select this option if you want an action to be triggered when specific characters are detected in the alarm text. You can filter the text trigger using the Ignore case and Exact match options.

- If not ack in - select this option if you want an action to be triggered if the trap type or severity is not acknowledged.


5. In the Activated Operation area, select the operation you want to activate when the alarm occurs, as follows:

- For Display Message, you can specify the sound that will be heard when the alarm occurs, and the text that will appear in the message. Click the three dots button beside the Content field to select predefined variables that you can insert in the text.

- For Send Mail, you can specify the address to which the mail will be sent, the subject of the mail, and the content.

You can send emails using HTML tags to format the email message text.

For example:

<H1> text </H1> - create a header <B> text </B> - bold text <I> text </I> - italic text <BR> - insert a new line

Make sure that in the PolyView Configuration utility, the “Email Format” option is set to HTML.

- For Run Executable, you must specify the path of the executable file you want to run whenever the alarm occurs. You can also specify parameters that will be passed to the specified executable.

- Use Auto Hide or Auto Delete to hide or delete alarms you do not want to view, such as low level ADM alarms. Note that using one of these options will not prevent relevant traps from being generated and forwarded.

- Use Forward Trap to filter the alarms to be forwarded. If you select this option, you need to specify all the servers to which the traps will be sent, in the format <host IP>:<port> with a space between each entry. Note that this mechanism is slower than PolyView's standard trap forwarding mechanism and should be used only when filtering is required.

6. Additional trigger operations:

- To edit an existing trigger, select the trigger and click Edit .

- To delete an existing trigger, select the trigger and click Delete .

- To save the trigger list in a file, select File, Save as.

Note: A trigger only applies to alarms generated after the trigger was defined.

The following example shows messages that were displayed for alarms that activated a trigger.


Example of Messages that were Displayed due to Alarm Triggers

In the Trigger Messages window, you can click Clear All to clear the list of messages.

Select an alarm in the list, and click Alarm Details to view information about the alarm.

Continuous Alarm Sound It is possible to configure a sound that will be played when triggered by an alarm. The sound will be played continuously until the user acknowledges the alarm.

In the PolyView installation directory, an application called "playsound" enables you to configure the sound to be played.

You can run playsound in a command window, using the format:

playsound <sound file name> <message to the user> <severity>

where:

sound file name is the name of the file that contains the sound. The value can be a specific path, or a path relative to the PolyView installation folder. Several sound files were included with the PolyView installation in the sound directory in the installation folder.

message to the user is a text message that will be displayed for the user in a window that opens.

severity is used to organize the playing of sounds, according to their severity. If a sound with severity X is triggered by an alarm, and another sound is triggered by an alarm with severity Y, if Y's severity is greater than that of X (for example, Y is Major and X is Warning), Y will be played instead of the X. If Y is not greater than X, X will be played.


Example:

An example of the usage of the playsound application would be to define different sounds for Major alarms and Critical alarms, as follows:

1. Create a trigger.

- For Severity in the Activate Conditions area, select Major.

- In the Activation Operation field, select the following:

Type: “Run Executable”

Path: playsound

Parameters: sound/bark.au “%SEVERITY: %DESCR” %#SEVERITY

Execute On: Connected Clients

2. Create an additional trigger.

- For Severity in the Activate Conditions area, select Critical.

- In the Activation Operation area, select the following:

Type: “Run Executable”

Path: playsound

Parameters: sound/bong.au “%SEVERITY: %DESCR” %#SEVERITY

Execute On: Connected Clients

Management Alarms PolyView management alarms are provided in Appendix G: SNMP MIB Support, at the end of this guide.

Alarm Synchronization The following method is used for an OSS to synchronize all the current alarm tables:

The OSS must periodically obtain the nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1) from PolyView.

This is a counter that advances every change of the current alarm table and compares it with the OSS alarms/traps counter. If the value is not the same, the OSS must poll the current PolyView alarm table, nmsCurrentAlarmTable (which contains all FibeAir IP-10, 1500R, PolyView, and 3rd party current alarms). This will synchronize all alarms in the current alarm table.


End to End Trail Management This feature enables you to define End to End trails and modify existing ones.

End to End trail management is supported for the IP-10 G Series family.

Note: Before you define an End to End trail, you should first add neighboring elements in the IP tables of each element you want to appear in the trail. If you do not add the elements in the tables, PolyView will not be able to generate the End to End path.

To define an End to End trail:

1. In the Main CeraMap window, click the Trails icon, or, in the menu bar, select Trail, TDM Trails.

Main CeraMap window:

The following window appears:


In this window, you can view all the defined TDM trails, and peform trail related operations.

The information for each trail in the list includes:

Trail ID - the trail identification.

Trail Completed - whether or not the trail was found to be complete, from one endpoint to the other.

Trail Severity - the most severe alarm of the element trails that comprise the network trail.

Protected - whether or not the trail is a protected.

Trail Description - a basic description of the trail.

Trail Endpoints - the end points which include the element, the slot, port type (Line or STM-1) and port number.

To delete a trail, select the trail in the list and click the Delete icon , or, in the menu bar, select Actions, Delete.

To print the trail list, click the Print icon .

To save the trail list to a file, click the Save icon .

To filter the trail list, click the Filter icon , and select either Filter by Values or Show/Hide Columns.

Filter by Values:

For Filter by Values, the following window appears:


The Field Name column shows the field to which the filter applies. The OP column shows the filter operation (which can be >, >=, <, <=, =, or <>). The Filter Value column shows the numerical value of the filter.

Select a row and click Edit to modify the filter definition.

Select a row and click Delete to delete that particular filter.

Click Add to add a single filter for a particular field.

The Add Filter window appears.

For Field, click the drop-down list and select the field you want to filter.

For Op, click the drop-down list and select the operator for the filter.

For Value, enter the values you want for the filter.

Click OK.

Show/Hide Columns

If you select Filter, Show/Hide Columns, the following window appears:


Mark the checkboxes beside the columns that you want to appear in the trail list window, and click OK.

2. To define a new trail, click the Add New Trail icon , or, in the menu bar, select Actions, Add New Trail.

When protected slots are used, the Slot field will appear as follows:


In the case of protection for any two consecutive slots (such as 1-2, 3-4, 5-6), PolyView will display the main IP of the device (or the name), and instead of one of the slots (presented in the past), it will present the slot as “1-2”, “3-4”, or “5-6”.

The example window above shows a trail that starts (end point 1) at IP 172.24.30.205, whereby both slots 1 and 2 are protected, and ends at (end point 2) IP 172.24.30.206, whereby slots 5-6 are protected as well.

Create Protected Trail - Check this option if you want to configure the trail for protection.

Endpoints - Select IP to define the endpoints by the IPs of the elements, or Name to define the endpoints by their names. Then select their slots, the type of interface used, and their port numbers.

Dual Ended Protection - select this option only if you want an alternative trail to be defined for protection. If you select this option, fill in the same information for Endpoint 3 as for the previous endpoints.

3. Click OK to process the trail.

The following window appears for an unprotected trail:


The following window appears for a protected trail:

In this window, you can determine how and if the trail will operate, and provide trail related information.

For Trail ID and Description, add the trails ID and a short description.

Protected is read-only and shows if you selected protection or not in the previous window.


For Operational Status, select Operational to activate the trail, or Reserved if you want create the trail in reserved mode. In this mode, the trail will exist but will not be operational, meaning traffic will not pass and alarms will not be generated.

For ACM Priority select the level of priority you want for the ACM (Adaptive Coding & Modulation). ACM employs the highest possible modulation during changing environmental conditions, which may be from QPSK to 256 QAM.

In the Trail Graphic View area, use the Zooming buttons to enlarge or reduce the view of the elements in the trail you are defining.

In the Graphic Presentation area, you can select Icon Positioning, click an element in the graphic display, and re-position it. If you do so, click the Start Redraw button to render the changes you made in the trail map.

For Multi Links, if you click on the link, you can choose Select Link to determine which trail route will be used.

To change the trail path, click Path Selection, and select the elements you want for the trail.

Click Set Trail, to save the information of the trail you defined. The trail will then appear in the Trail List window.

About the VCs

Note that along the element link lines, the VC# Low/High has the following meaning:

Example: VC#1 - Low/High (X,Y,Z)

Low/High - the priority of the VC on the radio

X - Minimum number of VCs on the radio link (according to the lowest allowed modulation)

Y - Maximum number of VCs on the radio link (according to the highest allowed modulation)

Z - Number of defined VCs on the radio link

4. Once you finish defining a trail, you can see its properties by clicking the Trail Properties icon , or by selecting in the menu bar Actions, Properties.

The following window appears:


In this window, you can view the trail information, and perform additional trail related operations.

In the Actions area, you can click Set Reserved to change the status of the trail from Operational to Reserved, or vice versa.

Click Poll Trail to refresh the status of the trail elements.

Click Delete Trail to delete the trail.

In the Trail Graphic View area, use the Zoom buttons to enlarge or reduce the view of the elements in the trail you are defining.

Click the Start Redraw button to render the changes you made in the trail map.

Click Save to save the latest changes you made to the element positions in the trail.

Click Load to load new element locations in the trail.


Software Download The software download items allow you to configure software downloads and view the status of the downloads you configured.

If an element you selected for software download configuration includes other sub-elements, the configuration will apply to all relevant sub-elements.

Note: The software is located in the following directories:

FibeAir 1500x <PolyView installation folder>\data

FibeAir IP-10 <PolyView installation folder>\polyview\data\IDU

FibeAir IP-10 G-Series <PolyView installation folder>\polyview\data\IDU-G

Software Download Configuration To configure software downloads:

1. In CeraMap, select the element(s) you want to work with.

2. Select Tool, Software Download.


Software Download Configuration Window

If the element you selected is a group that includes other elements, the different types appear at the top of the window.

3. Select the tab of the element to which you want the software download to apply. Then, click the line that contains the version you want to download, and click Add.

Important: The IDU, MUX, and ODU/RFU files you choose to download must be located in the TFTP server directory (as specified in the PolyView Configuration Utility).

4. For FibeAir 1500P, in the Perform ODC internal download for field, select the Left shelf, the Right shelf, or both.

5. For Download Time, select Now if you want the download to occur immediately, or click Date Config and set the time and date you want the download to occur.

6. In the Reset Time area, mark the checkbox beside Enable if you want the system to perform a reset. Then, either select After Download to perform a reset after the software download ends, or click Date Config and set the time and date you want the reset to occur.


7. Click Apply to save and implement the changes.

8. You can click Status Log to view the current software download status (described in the following section).

Important Notes:

* When downloading software to a FibeAir IP-10 unit, the Upgrade command automatically initiates a Reset immediately after the download is complete.

* Don't forget to verify that the following parameters are defined in the PolyView Server Options utility:

- The TFTP server address should contain the IP address of the PolyView server. Network elements should have access to this IP (you should be able to ping from the network element to the server using this address).

- Specify the folder name that contains the files to be downloaded. Note that the name can be a specific path, or a path relative to the PolyView installation directory. The default software file folder is polyview installation folder/data.

- Remember, the TFTP folder name (and path) cannot contain spaces.

Software Download Configuration for IP-10 Radios For IP-10 radios, the procedure is as above, but the downloaded files must be placed in the following directories:

For IP-10 - ...\polyview\data\ip10

For IP-10-G - ...\polyview\data\ip10g

Software Download Status To view the current software download status:

1. In CeraMap, select the element(s) you want to work with.

2. Select Tools, Software Download Status, or click Status Log in the Software Download Configuration window described above.


Software Download Status Window

3. The window lists the IP addresses of the elements that were configured for software download, the type of software set for download, the software files (versions) to be downloaded, whether or not the elements are scheduled for reset, and the current status of the downloads.

To remove from the log lines that are not active (not in the middle of a download), select the line and click Remove.

The values that may appear in the IDU, MUX, and ODU Status columns include Download %, Waiting, Succeeded, Failed, or Cancelled.

Note that software will be downloaded in the order of IDU first, then MUX, and then ODU. If you chose all three and the IDU software download failed, the other downloads will be cancelled.


Configuration File Download PolyView periodically reads configuration information from network elements, and stores the information in its database. If necessary, you can download the saved configuration to the network element (such as a case in which a unit is replaced, and you want the new unit to have the same configuration as the previous one).

PolyView stores up to four configuration files in the mysql database. Only the recent file from each element is stored on the disk. FibeAir files (except for FibeAir IP-10) are named according to the element IP: <element IP>.cfg and are stored in the folder <PV Installation path>/data.

FibeAir IP-10 configuration files have the same name: aidc_cfg.tar.gz and each file is stored in its own folder: <PV Installation path>/data/<element IP>/.

Only the most recent file for each element can be viewed.

To download a saved configuration to a network element:

1. In CeraMap, select Tools, Configuration Download from the menu bar.

Configuration File Download Window

2. By default, the last configuration file that was stored in the database will be the one that will be restored to the unit. If a prior version is needed, either double-click the line of the element in the list, or select the line and click Select File.

The following window appears for you to select a file stored in the database.


Select Configuration File for Download

Notes:

- Up to four configuration files are stored in PolyView for each network element. If this number is exceeded, the newest configuration file will replace the oldest.

- PolyView will upload and store new configurations from the unit only if they differ from the ones already stored in the database.

3. If you don't want to download the configuration for a specific element, select the element in the list, and click Remove.

4. Click Download All to begin the process.

During the process, the Download Status column displays the status of the operation.

Configuration File Download Progress Window

To terminate the operation, click Abort All.


Note that Configuration Upload from an IP-10 G-Series network element is done per slot during polling (manual or scheduled).

Configuration Download to an IP-10 G-Series network element is done per slot using the Configuration Download window, as shown below.

Configuration File Download for FibeAir IP-10 G-Series

File Locations

The files are downloaded to the following directories:

For FibeAir products other than IP-10 - ...\polyview\data, and will have the suffix cfg.

For IP-10 products - ...\polyview\data\ip10(or ip10g), and the name of the file will be the same as the IP of the network element.


Management Reports PolyView reports include inventory and performance reports. Inventory reports provide information about Ceragon interfaces and links in the system. Performance reports provide information about Ceragon element communication performance.

Performance Reports Performance reports provide information about the way an element is performing in the system.

There are two types of performance reports:

Radio

Interface

To generate a performance report:

1. In CeraMap, select one or more elements for which you want to generate a report.

2. Select Reports, Performance Reports, in the menu bar, or click the Performance Report icon .

The following are examples of radio performance report windows.


Example 1 - Radio Performance Report


Example 2 - Radio Cross-Connect Performace Report

3. In the window that appears, select the interfaces for which you want performance data by marking the box beside their names.

To select all the interfaces of a unit, mark the box beside the icon of the unit itself.

To select all interfaces in the system, marking the "root" box.

4. Click the Get Report icon to obtain data for the interfaces you selected.

5. Click the Report Date Range icon to specify the dates you want to include in the report.

When you open the report window, the default date range is the last 24 hours.

After you change the date range, CeraMap automatically retrieves the specified data from the server, so that you do not need to click the Get Report icon.

6. Click the Filter icon to filter the report data.

Note that once you define a filter, the definition will apply to all the interfaces.


Report Filter Definition Window

The Field Name column shows the field to which the filter applies. The OP column shows the filter operation (which can be >, >=, <, <=, =, or <>). The Filter Value column shows the numerical value of the filter.

Select a row and click Edit to modify the filter definition.

Select a row and click Delete to delete that particular filter.

Click Add to add a single filter for a particular field.

The Add Filter window appears.

Add Single Filter Window

For Field, click the drop-down list and select the field you want to filter.

For Op, click the drop-down list and select the operator for the filter.

For Value, enter the values you want for the filter.

Click OK.

To clear the filter, select Clear Filter in the Report menu.


7. Click the Print icon to print a performance report for the currently selected interface.

8. Click the Save As icon to save the report in .csv text format (used in Excel).

9. Click the Help icon to open the PolyView help file.

Note that the maximum number of entries that can be retrieved is limited. The amount of entries can be configured in the user settings, whereby the default is 50,000). During report generation, you will be notified when the maximum number of entries is reached. If this happens, try to select less interfaces to be included in the report, or further limit the report date range.

Additional Report Operations

In addition to the operations mentioned above, you can also perform the following:

You can export the report data to a text file, or to an Microsoft Excel formatted file. To do so, select File, Save as.

You can launch CeraView from a report. To do so, select a line, and then select Actions, Launch Element Manager.

You can locate the element in the map by selecting Actions, Find in Topology Tree.

You can open an Inventory report. To do so, select a line, and then select Actions, Inventory Report.

You can automatically generate and send reports via the CLI (Command Line Interface). (For more information about the CLI, see Appendix A at the end of this guide).

In the Report menu, you can select either 15-Minute Report, Daily Report, Weekly Report, or Monthly Report for a summarized report based on the specified period.

Select Missing Interval Report to display the periods of time in which no activity was recorded.

In the Report menu, you can select Filter Zeros to exclude all zero values from the table.


Inventory Reports Inventory reports provide information about the selected elements. The different inventory report types cover different aspects of the Ceragon equipment operating at the site, such as element type, radio information, link information, ADM information, and others.

The following types of inventory reports are available:

Slot Population

Network Element

Radio

Link

Neighbors

Interface

Inband

ADM

ADM Connection

Versions

Serial Numbers

IP-10 G-Series Licensing Report

IP-10 G-Series Slot Protection

To generate an inventory report:

1. In CeraMap, select one or more elements for which you want to generate a report.

2. Select Reports, Inventory Reports, or click the Inventory Reports icon .

Inventory Report Selection Window


3. Click the drop-down list, and select the type of report you want to generate.

4. Click Run Report.

The following are examples of network element inventory reports.

Inventory Report - Network Element

Inventory Report - Cross Connect


Inventory Report - Radio

Inventory Report - IP-10 G-Series Slot Protection

Inventory Report - IP-10 G-Series Licensing


Explanation of Licensing Report

The License Model column defines the marketing name for the license (hidden by default).

Network Resiliency License

The Resiliency License calculation for the Usage Configuration column is as follows:

STP Protocol Protected Trails Usage Configuration No (disable) No Disable No (disable) Yes SNCP

Yes (not disabled) No <stp protocol value> Yes (not disabled) Yes SNCP, <stp protocol value>

TDM License

The license value is calculated as follows: if the license is not available, the value is “not allowed”. If it is available the value is the number of TDM trails allowed (16, 32, 48, 64, 75). The usage value is the actual number of configured trails in the radio link.

Feature Usage (Value) License Model

ACM Enableb IP10-SL-ACM Disabled NA

Switch Single-Pipe NA Managed-Switch IP10-SL-Metro Metro-Switch IP10-SL-Metro

Resiliency

Disabled NA SNCP (and license is not default license) IP10-SL-Network-Resiliency

<stp protocol value>, (and license is not default license)

IP10-SL-Network-Resiliency

SNCP, <stp protocol value> (and license is not default license)

IP10-SL-Network-Resiliency

Sync Unit Local NA Sync IP10-SL-Sync-Unit

Enhanced QoS

Disabled NA Enabled IP10-SL-Enhanced-QoS


Feature Usage (Value) License Model

Capacity

Capacity <= 10.5 NA (default license is used) < 10.5 Capacity <= 25 IP10-SL-CAP-25 25 < Capacity <= 50 IP10-SL-CAP-50 50 < Capacity <= 100 IP10-SL-CAP-100 100 < Capacity <= 150 IP10-SL-CAP-150 150 < Capacity<= 200 IP10-SL-CAP-200 200 < Capacity<= 300 IP10-SL-CAP-300 300 < Capacity IP10-SL-CAP-ALL

TDM Capacity

XX: TDM capacity license = not-allowed, or license-per-usage = allowed

NA

Capacity <= 16 (and not XX) IP10-SL-CAP-16E1

16 < Capacity <= 32 (and not XX) IP10-SL-CAP-32E1




Additional Report Operations

In addition to the operations mentioned above, you can also perform the following:

You can export the report data to a text file, or to a Microsoft Excel formatted file. To do so, select File, Save as.

You can locate the element in the map by selecting Actions, Find in Topology Tree.

You can launch CeraView from a report. To do so, select a line, and then select Actions, Launch Element Manager.

You can open a Performance report. To do so, select a line, and then select Actions, Performance Report.

You can automatically generate and send reports via the CLI (Command Line Interface). (For more information about the CLI, see Appendix A at the end of this guide).


Sorting Data In a report generated by PolyView, you can sort the data in a column by clicking on the column title.

When you click on a column title, the data in the column is sorted as follows:

Alphabetically for string value columns

Numerically for number value columns

By date for date value columns

By IP address for columns with IP address values

This is useful when it is important to group the data according to type or date.

In Performance reports, sorting some columns provides valuable grouped information, such as days on which the most errors were detected.


Administration & Maintenance Discovering Nodes When an element is first added to the map, PolyView automatically “discovers” it (reads the element’s static information, such as its interfaces).

To force PolyView to re-discover an element (such as in the case of an interface type that was changed for the element), select the element, and then select and then select Tools, Discover Node.

In the Discover Node window, click Apply.

Before performing a Discover Node operation, note the following:

When Discover Node is executed, all existing information about the element (stored reports) is deleted.

After PolyView performs Discover Node, it will automatically perform Poll Node (described below).

Polling Nodes To force PolyView to retrieve updated information from network elements (PolyView automatically polls all elements every few hours, depending on the user configuration), select element(s) in CeraMap, and then select Tools, Poll Node.


Click Apply.

Note that when Poll Node is executed, all existing information about the element (stored reports) is deleted.

Database Backup and Restore PolyView uses an internal SQL database called MySQL. It is highly recommended that you back up this database regularly.

Backup can be done using the tools provided with the database. However, to make this task easier, a backup script called pvdbbackup can be found in the directory in which PolyView was installed.

The format of the script is provided in the CLI section of this help file.

Note that backup can be performed while PolyView is running (known as "hot backup"). However, before running a restore backup operation, PolyView must be terminated by typing pvstop in a command window.

Viewing Connected Users An administrator can view users currently connected to the server, their computer IDs, and since when they were connected.

To view connected user information, in the main PolyView window, select File, Show Connected Users.


Connected Users Window

To disconnect a user from the PolyView server, select the line with the user name, and click the Disconnect

User icon .

To view a single user's action information, select a user in the window, and click the Show User Actions

icon . A user action log appears with a list of actions the user you selected performed within the last day. In the window, you can filter the information by selecting Report, Filter. Note that actions performed after the window was opened will automatically be added to the window.

To send a message to a user, click the User Message icon .

To view an action log for more than one user, over a longer range of time, see the Viewing User Actions section below.

Sending Messages to Users Click Send a Message to User in the Connected Users window to relay important information to users connected to the server.

Send Message to User Window

Enter the message you want to send, and click OK.


Viewing User Actions Each action that changes a parameter in the NMS system is recorded in the PolyView server database, and can be viewed by the administrator.

Examples of such actions include:

- Changes in network element parameters.

- Topology modifications (add/remove/modify/etc elements in the topology).

- Changes in the PolyView security configuration.

- Configuration changes (using PolyView or the Trap Forwarding Configuration utility).

To view a list of actions for all users, select Reports, Users Action Log in the main CeraMap window.

In the window that appears, select the start and end dates for the report, and click OK.

Users Action Log Window

Each action recorded in the database contains information about the user, the time the action was performed, the application name (such as CeraView, CeraMap, PolyView Security, etc.), and the name of the action (such as Software Download).

To filter the information in the report, select Report, Filter.

In most cases, double-clicking a line will provide details of that action, as shown in the following example.


User Action Details Window

If CeraView is connected to the network elements via PolyView (PolyView acts as a proxy), all user actions in CeraView are automatically recorded in the PolyView server database.

If CeraView is not connected via PolyView, but the administrator nonetheless wants user actions to be logged, CeraView can be configured to route the actions to the PolyView server.

Scheduling Tasks The task scheduler enables you to create recurring tasks.

To define a scheduled task, select Tools, Schedule Task Configuration.

Schedule Task Configuration Window

The icons in the toolbar are as follows:

Saves the task list to a file.

Prints the task list.


Creates a new task (see explanation below).

Edits a selected task (see explanation below).

Deletes the selected tasks.

Runs the selected task. This option enables you to test if the task is configured properly, without having to wait for the scheduled time to arrive.

Enables/disables the selected task.

To add a new task, click the Add icon, or select a line in the list and click the Edit icon.

The tasks that you can create and edit include the following:

Offline Report

DB Backup

DB Check

Conf Backup

Execute

Offline Report

Select this option to define an automatic offline report.


At the top of the window, specify a unique name for the task, the type of report you want to generate, and the report sub-type (if relevant). For a performance report, select the interval as well.

On the left side of the window, select the elements you want to include in the report.

In the Recurrence area, for Daily, specify the time of day you want the report to be generated.

For Weekly, specify if the report is to be generated each week, every two weeks, etc. In addition, specify which days of the week, and the time during the day.

For Monthly, specify the day of the month, and the time during the day.

In the Report Period area, select Unlimited for all available data, or specify the Last # days to generate a report based on data from the previous specified amount of days.

In the Output area, for File Name, you can use variables embedded in the name. The variables will be replaced with the actual text upon file generation. For example, %D will be replaced with the day of the month (01 to 31), %X will be replaced with the name of the month (Jan, Feb, ...), and so on.

To view a list of all possible variables, click the list button on the right side of the field.

The Sample Name field shows how the actual name will appear.

In the Report Format field, select Textual or CSV (Comma Separated Values).

For the output destination, select one of the following:

File - Enter the path of the file.

FTP - Enter the FTP server address. If you are accessing the server with a defined identification, enter your user name and password. In addition, specify where on the FTP server the files will be stored.

Email - Enter the email address.

In the Filter area, you can filter the report using any report field. To add additional criteria, click Add.


DB Backup

Select this option to define an automatic backup for the PolyView database.

At the top of the window, specify a unique name for the task.




In the Output area, for File Name, specify the name of the report you want to generate.





DB Check

Select this option to define an automatic check for the PolyView database.






Configuration Backup

Select this option to define an automatic backup for the PolyView configuration.

Note that this task will result in the backup of the PolyView configuration, databases, and zipped logs.





In the Output area, for File Name, specify the name of the report you want to generate.





Execute

Select this option to define an automatic task execution schedule.





For Executable, specify any executable program you want to run (related or not related to PolyView).

For Parameters, you can specify parameters you want for the executable.


Redundancy Support PolyView has built-in support for redundancy configuration. The configuration includes two PolyView servers: a primary server, which is generally active, and a secondary server, which is generally located at a geographically remote site and is in standby mode. By default, data required for proper server operation (such as topology and security information) is synchronized from the primary to the secondary server. The administrator can also set the synchronization for both ways, or disable it altogether.

When the main server is down (disconnected from the secondary server), the secondary server automatically (by default) takes over, begins polling the network, sends triggers, forwards traps to north-bound systems, and so on. When the main server is up again, the secondary server automatically resumes standby mode.

If required, the administrator can also force the secondary server to enter active or standby mode.

By default, to conserve network bandwidth, while in standby mode, the secondary server only synchronizes alarm information (if needed). The administrator can change this behavior and set the secondary server, in standby mode, to poll inventory and performance monitoring information as well.

For more information about configuring PolyView redundancy, see PolyView Configuration Utility.

PolyView clients, such as CeraView (when working via PolyView) and CeraMap, have built-in support for redundancy. When PolyView clients are activated, they will try to connect to the primary server first, and, if unsuccessful, they will automatically try to connect to the secondary server (if one was configured).

When working with redundant servers, CeraView and CeraMap should be configured with the addresses of the primary and secondary servers. For more information, see the section CeraMap Configuration Utility and the CeraView Online Help.

Note that network elements should be configured to send traps to both servers.

The following illustration shows the built-in redundancy system.

PolyView Redundancy System


Ping and Trace Route Ping and Trace Route are used to test connectivity between the PolyView server and the network element.

To start a Ping operation, select an element in CeraMap, and then select Tools, Ping.

Ping Window

The Ping window lists the attempts made by the server to connect with the element, and other connectivity information, such as the connection speed.

To start a Trace Route operation, select an element in CeraMap, and then select Tools, Trace Route.

Trace Route Window


The Trace Route window displays the routing connectivity to the element (the path the packet takes on its way to the element).

Migration Steps for New Platform The following procedure must be performed when a PolyView server is to be moved to a new hardware platform.

1. Install

- Install MySQL and PolyView on the new hardware platform.

Note that the PolyView version must be the same as that of the previous platform.

- After installation, you will have 30 days to obtain a new PolyView license for the new platform.

2. Configure

- Copy the files in the PolyView configuration folder (*.cfg and *.sec) to the new platform.

- On the new platform, open the PolyView Configuration Utility and update the new IP in the TFTP Server Address settings.

3. Transfer Database

- On the old platform, run the command pvdbbackup backup <target filename>

- Copy the <target filename> to the new platform.

- On the new platform, run the command pvdbbackup restore <target filename>

4. Configure Clients

- Configure CeraMap clients (and CeraView, if applicable) to access the new server.


Repairing the MySQL Database In situations such as an unexpected power outage, PolyView’s MySQL database may become corrupted.

The last solution for this should be to recreate the database table using the following command:

createdb create

However, in most cases, only the database index files will be corrupt (the index is a separate smaller file with records that point to the main data file). Fixing most of these lighter forms of corruption is relatively easy.

For checking and repairing the database, you can use one of the following methods:

Run the mysqlcheck command (the MySQL server can run during this command)

or

Run the myisamchk command (the MySQL server cannot run during this command)

Since repairing a table requires twice as much disk space as the original table (a copy of the data is made), verify that there is enough free disk space before you run the repair command.

Important: Shut down the PolyView server before you start. To shut down the server, use the pvstop command.

Repairing Tables with mysqlcheck

The mysqlcheck command can be used while the MySQL database server is running.

The syntax is:

mysqlcheck -rf PolyView -uroot -ppvroot

Repairing Tables with myisamchk

Before running this command, shut down the MySQL server as follows:

mysqladmin shutdown -uroot -ppvroot

The syntax of the myisamchk command is:

myisamchk [options][tablenames]

Note that you must specify the full path of the database files.

For example, for Windows systems the command may be:

myisamchk -fr c:\mysql\data\polyview\*.MYI

When the check is done, restart the server.


Appendix A: PolyView CLI (Command Line Interface) This appendix describes PolyView commands that you can implement via a text-based command line.

Report Generation Commands PolyView reports can be generated via the CLI interface. This document describes the commands used to generate the different reports, and the resulting report columns.

Using the PolyView CLI interface, you can generate reports such as Current Alarms, Alarm Log, Performance Management, Inventory, and User Actions. The reports can be forwarded to the northbound OSS automatically and periodically (in accordance with user preference) in plain text or CSV format.

CLI Functionality

CLI executables are a part of the PolyView installation (both client and server) and therefore the CLI can be activated from any machine on which PolyView client or server is installed. There are two common working modes.

Mode 1 - CLI Runs Locally on the Server

The report file is saved in the server machine under a known FTP directory. Assuming the FTP server is enabled on the PolyView server machine, a remote machine should fetch the file using an FTP/SFTP client.

Advantage: The file can be copied via a known protocol (FTP/SFTP) which is sometimes the only option when dealing with firewalls.

Mode 2 - CLI Runs on a Remote Machine

CLI runs as a remote client towards the server. The report is saved on the remote machine and there is no need for FTP.

Advantages: No need for FTP, the client application copies the file.

CLI Scheduling Instructions

For Windows, create a batch file containing the desired CLI command. Schedule it via the Windows scheduler ("Scheduled Task" built-in Windows application).

For Solaris, create a shell script containing the desired CLI command. Schedule it via the Unix "crontab" application.


Inventory Reports This section describes the CLI interface for inventory reports.

Note: To integrate inventory report data in a north bound radio, all inventory data or the required relevant sections can be saved as a csv or txt file. Using the PolyView FTP client, you can configure the system to automatically send the inventory data file to the north bound computer (which needs to have an FTP server).

CLI Command Format inreport -CLI -IP <IP list> -OFN "<file name>" -RT “<report type>" –MAIL <target-email> -SD “<date>” –ED “<date> -USER <user-name> -PASSWORD <password>

CLI: Command line input, tells inreport to work in command line mode.

IP: List of elements IP in the format of: <IP> <IP>,… For example: -IP 172.24.30.100 172.24.30.101 Or: ALL (for all elements in the database) For example: -IP ALL

MAIL: Mail target to send the report to (optional) For example: -MAIL “[email protected]”

SD: Start date of the report, in the format of: "dd/MM/yy HH:mm" (optional)

ED: End date of the report, in the format of: "dd/MM/yy HH:mm" (optional)

RT: Report type, one of: "Network Element” "Radio Report" "Link Report" "Interface Report" "Inband Report” "ADM Report" "ADM Connection Report” “Versions” "CLI Network Element" "CLI B Network Element" "CLI Radio Report" "CLI B Radio Report" "CLI Link Report" "CLI B Link Report" "CLI Neighbors Report" "CLI B Neighbors Report" "CLI Interface Report" "CLI B Interface Report" "CLI Inband Report" "CLI B Inband Report" "CLI Versions" "CLI B Versions"

Note: The report types starting with CLI contain all elements and all columns. Slot ID columns are shifted to the right (end of table). Reports starting with CLI B contain all elements except for the FibeAir IP-10 family elements, whereby the Slot ID column does not appear.


OFN: Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV (Comma Separated Values) format.

USER: The name of the user with read access to the target elements.

PASSWORD: The user’s password.

Example inreport -CLI -IP 172.24.30.100 -OFN "file_test.txt" -RT " Network Element " -USER reportUser -PASSWORD viewer

Available Interfaces Report

The Available Interfaces Inventory Report includes the following columns:

IP Address

Name

Product Type

Is Radio Interface Available

Is Non-Radio Interface Available

XC Slot Number

Link Report

The Link Report includes the following columns:

IP Address

Name

Transmit Frequency (MHz)

Receive Frequency (MHz)

ATPC

XC Slot Number

Slot Population Report

The Slot Population Report includes the following columns:

Name

Slot 1 to Slot 6


Network Element Report

The Network Element Report includes the following columns:

IP Address

Name

System Name

System Location

System Contact

Product Type

Wayside Channel

Radio Report

The Radio Report includes the following columns:

IP Address

Name

Slot

RFU Type

Modem Type

Transmit Frequency (MHz)

Receive Frequency (MHz)

Min Transmit Frequency (MHz)

Max Transmit Frequency (MHz)

Channel Spacing (MHz)

Transmit Level

ATPC

ATPC Reference Level

Link ID

XC Slot Number


Neighbors Report

The Neighbors Report includes the following columns:

IP Address

Name

Interface

IP Address

Name

XC Slot Number

Interface Report

The Interface Report includes the following columns:

IP Address

Name

Slot

Interface

XC Slot Number

In-band Report

The In-band Report includes the following columns:

IP Address

Name

In-band Status

Element Type

Channel

TTL

Subnet Address

Subnet Mask

Network ID

Ethernet Mask

Default Router Address

XC Slot Number


Versions Report

The Versions Report includes the following columns:

IP Address

Name

Slot

Type

Version

Post Reset Version

XC Slot Number

Serial Numbers Report

The Serial Numbers Report includes the following columns:

IP address

Name

Slot

Type

Serial number

XC Slot Number


Performance Monitoring Reports This section describes the CLI interface for performance monitoring reports.

Note: The examples shown in this section were taken from a FibeAir IP-10 system. The windows may vary in accordance with the FibeAir system used.

CLI Command Format pmreport -CLI -IP <IP list> -FFILTER “<filter>” -OFN "<file name>" -RT “<report type>" –MAIL <target-email> -SD “<date>” –ED “<date>” -FILTER <value> -USER <user-name> -PASSWORD <password>

CLI: Command line input, tells pmreport to work in command line mode.

IP: List of elements IP in the format of: <IP> <IP>,… For example: -IP 172.24.30.100 172.24.30.101 Or: ALL (for all elements in the database) For example: -IP ALL


SD: Start date of the report, in the format of: "dd/MM/yy HH:mm" (optional)

ED: End date of the report, in the format of: "dd/MM/yy HH:mm" (optional)

RT: Report type, one of: - "Radio Performance Report"

- "Interface Performance Report"

SDAY: Outputs a summarized daily report.

SWEEK: Outputs a summarized weekly report.

SMONTH: Outputs a summarized monthly report.


FILTER: Only fields that exceed the specified value are presented. For example: -FILTER 0 - Don’t show zero value fields.

FFILTER: Filter the report by specific field value. The format of this parameter is: "<field-name><operator><value><boolean-op><field-name><operator> <value><boolean op>..." where: operator is one of the following: > >= < <= = <> boolean-op is the sign | for OR between the expressions, or & for AND between them. field name is the name as it appears in the report header: such as UAS or “Max. RSL"

Note: You cannot have FILTER and FFILTER in the same command.

USER: The name of the user that has read access for the target elements.


Example pmreport –CLI -IP 172.24.30.100 -FFILTER "UAS>0,UAS<900,Max. RSL>-99" -OFN "file_test.txt" -RT "Radio Performance Report" -USER reportUser -PASSWORD viewer


Radio Performance Report

The Radio Performance Report includes the following columns:

Interface

- UAS

- ES

- SES

- BBE

- Integrity

RSL

- Min RSL

- Max RSL

- RSL Thresh 1

- RSL Thresh 2

TSL

- Min TSL

- Max TSL

- TSL Thresh

ACM

- Lowest ACM Profile

- Highest ACM Profile

- Lowest Bitrate

- Highest Bitrate

- Lowest Number of TDM Interfaces

- Highest Number of TDM Interfaces

MSE

- Min MSE

- Max MSE

- MSE Threshold Exceeded

General

- Date

Interface Performance Report

The Interface Performance Report includes the following columns:

Interface


- UAS

- ES

- SES

- BBE

- Radio UAS

- Integrity

General

- Date

Alarms Report This section describes the CLI interface for performance monitoring reports.

CLI Command Format alarmreport -CLI -IP <IP list> -FFILTER “<filter>” -OFN “<file name>" -RT “<report type>" –MAIL <target-email> -SD “<date>” –ED “<date> -USER <user-name> -PASSWORD <password>

CLI: Command line input. Tells alarmreport to work in command line mode.

IP: List of element IPs in the format: <IP> <IP> … For example: -IP 172.24.30.100 172.24.30.101 or: ALL (for all elements in the database) For example: -IP ALL


SD: Start date of the report, in the format "dd/MM/yy HH:mm" (optional)

ED: End date of the report, in the format "dd/MM/yy HH:mm" (optional)

RT: Report type, either "Alarm Log" or "Current Alarms"


FFILTER: Filter the report using a specific field value. The format is: "<field-name><operator><value><boolean-op><field-name><operator> <value><boolean op>..." where: operator is one of: > >= < <= = <> boolean-op is the sign | for OR between the expressions, or & for AND between them. In the Description field, you can also use "contains". field name is the name that appears in the report header: such as "Ack" or "Severity"

USER: The name of the user that has read access for the target elements.


Example alarmreport -CLI -IP ALL -RT "Alarm Log" -OFN c:\temp\alarm.txt -user admin -password admin


Report Columns

The Alarms Report includes the following columns:

Ack

Raise Time

IP

Slot ID

Name

Severity

Module

Description

Export Data Report This section describes the CLI interface for export data reports.

The Export Report is used to export topology and/or trigger data to a file.

CLI Command Format pvexport -CLI -TYPE {TOPOLOGY | TRIGGERS | ALL} -GROUP <GROUP NAME>

-OFN <TARGET FILE> -USER <user-name> -PASSWORD <password>

CLI: Command line input - tells pvexport to work in command line mode.

TYPE: Type of data to export: TOPOLOGY will export only topology data, TRIGGERS will export only trigger data, ALL will export all data.

GROUP: The root group to start the export with. If there is more than one group with the specified name, the first one that will be found will be used.

OFN: Name of the output file in which the data will be saved.

USER: The name of the user that has read access to CeraMap.


Example pvexport -CLI -TYPE ALL -GROUP root -OFN c:\pvdata.exp -USER admin -PASSWORD admin

Report Columns

The Export Data Report includes the following columns:

Description

IP

SNMP Version


SNMP Read Community

SNMP Write Community

Import Data Import data is used to import topology and/or trigger data from a file.

Synopsis pvimport -CLI -TYPE {TOPOLOGY | TRIGGERS | ALL} -GROUP <GROUP NAME>

-IFN <TARGET FILE> -IP <IP list> -USER <user-name> -PASSWORD <password> -NO_UPDATE

Parameters CLI: Command line input - tells pvimport to work in command line mode.

TYPE: Type of data to export: TOPOLOGY will export only topology data, TRIGGERS will export only trigger data, ALL will export all data.

GROUP: The root group to start the export with. If there is more than one group with the specified name, the first one that will be found will be used. If the Group does not exist, it will be created under the root object.

IP: An optional list of network element IPs in the format: <IP> <IP> … For example: -IP 172.24.30.100 172.24.30.101

The entities in this list will be added to the topology under the group designated by the -GROUP parameter.

IFN: The name of the file from which the data will be imported.

USER: The name of the user that has write access to CeraMap.

NO_UPDATE: Optional parameter. If set, the existing element will not be updated if the same element is imported.


Example

pvimport -CLI – TYPE ALL – GROUP root -IFN c:\pvdata.exp -USER admin -PASSWORD admin


Database Backup and Restore PolyView uses an internal SQL database called MySQL. It is highly recommended that you back up this database regularly.

Backup can be done using the tools provided with the database. However, to make this task easier, a backup script called pvdbbackup can be found in the directory in which PolyView was installed.

The format of the script is as follows:

Synopsis

pvdbbackup {backup|restore} <target path name\target file name>

Parameters

BACKUP/RESTORE Command used to tell the MySQL database to perform either backup or restore.

FILE NAME Path of the file to backup or restore.

Example

The script for creating a backup and saving it in the file c:\temp\bkfile.dat would be as follows:

pvdbbackup backup c:\temp\bkfile.dat

To restore the backup from that file, the script would be:

pvdbbackup restore c:\temp\bkfile.dat

Note that backup can be performed while PolyView is running (known as "hot backup"). However, before running a restore backup operation, the PolyView server must be terminated by typing pvstop in a command window.

Other Commands pvstart Manually starts the PolyView server.

pvstop Manually stops the PolyView server.

pvstatus Displays the current state of the PolyView server.

createdb create Clears the PolyView database, and creates empty tables.

Warning: If you use this command, all data in the database will be erased. You will NOT be able to recover the data.


Appendix B: PolyView License Information This appendix provides information about PolyView licenses, including number of elements, redundancy, TDM Trails, ordering, and other relevant information.

Introduction

PolyView software can be purchased from Ceragon. The software consists of a built-in license for 20 Network Elements (NEs), meaning it can manage up to 20 elements.

In order to manage more than 20 NEs, an additional license should be purchased from Ceragon.

PolyView Ordering Information

In order to manage the network, customers should purchase the PolyView software and the appropriate license based on the number of managed network elements.

PolyView software is available on a CD that will be delivered to the client, or downloaded via Ceragon's customer support FTP.

In order to obtain a permanent license, contact Ceragon customer support and request the type of license you want, as listed in the following table.

Description Model # Part # PolyView Software (Win/Unix) + License for 20 NEs PolyView NMS SP-0028-x* License for 21-100 NEs: per NE PV_21-100_NE SR-0038-0 License for 101-500 NEs: per NE PV_101-500_NE SR-0039-0 License for 501-1000 NEs: per NE PV_501-1000_NE SR-0040-0 License for 1001 or more NEs: per NE PV_>1000_NE SR-0041-0

SP-0028-x* - whereby "x" represents the latest released version of PolyView

Examples:

Management of 130 NEs:

Description Model # Quantity PolyView Software + License for 20 NEs PolyView NMS 1 License for 21-100 NEs: per NE PV_21-100_NE 80 License for 101-500 NEs: per NE PV_101-500_NE 30


Upgrade of existing license from 60 NEs to 130 NEs:

Description Model # Quantity License for 21-100 NEs: per NE PV_21-100_NE 40 License for 101-500 NEs: per NE PV_101-500_NE 30

License Components

The following license components are limited, based on the purchase order.

Managed NE Limit - limits the number of managed elements (number of IP addresses on the network map). There is no limit on the number of groups or symbols the user can add.

Feature Set and Enabled Features - limits the features enabled by PolyView. Two feature sets are currently defined (default is Pro):

Pro: all features are enabled, except the following which require a specific license.

Enabled Features: specific proposal for the following features that require a specific license:

- End to End TDM trails provisioning

- Redundant server support

- GUI foreign language support

- PolyView software upgrade

- NSN NetAct interface

Expiry Date - no expiry (permanent license), or expiry date of license (for trials/demos)

Example:

Management of 130 NEs, redundant server configuration:

Description Model # Quantity per Server

Quantity for Redundant Server

Solution PolyView Software + License for 20 NEs PolyView NMS 1 2

License for 21-100 NEs: per NE PV_21-100_NE 80 160

License for 101-500 NEs: per NE PV_101-500_NE 30 60

License for redundant PolyView support

PV_Redundant_Support 1 2


Temporary Demo License

When the user installs the PolyView server for the first time, it is installed with a “demo” license that will enable 30 days of work with all features enabled, and no limitation on the number of managed NEs.

PolyView will provide 14 days of notification before the license expires. The notification will appear upon each login to remind the customer to contact Ceragon to obtain a permanent license.

If a permanent license was not obtained within 30 days, the demo license will expire and the user will no longer be able to log in. An error message will advise the customer to contact Ceragon to obtain a permanent license.

The demo license will be activated once per station. Uninstalling and reinstalling the PolyView software will not grant a new demo license.

Obtaining a Permanent License

A permanent PolyView license will be issued when the relevant order is processed by Ceragon, after PolyView is installed on the customer station.

Once an order is placed and processed, the customer must send the "PolyView License Request Form" to Ceragon Customer Support, with all the relevant information.

Ceragon Customer Support will verify that the necessary information was provided, and that the order was properly made. The license will then be generated and emailed to the customer, together with license installation instructions.

An invoice will be issued when the license is generated.


PolyView License Request Form

Please fill in this form and email it to [email protected].

Company Name

Ceragon Order #

Host ID (* see below)

User Name (full name of primary customer contact)

Email Address (email address of the primary contact to which the license file will be sent)

Managed NEs Limit (according to the order placed)

Feature Set - Pro

Enabled Features (according to the order placed)


- Redundancy server

- GUI foreign language support

- PolyView software, upgrade only

- End to End TDM trail provisioning

Expiration Date (relevant for demo/trials only)

- Permanent license (no expiry)

- Expiration date:

Remarks (additional information or special request)

* Host ID 1. Install PolyView, and restart the server. As part of the installation process, the server gets a unique number called

"Host ID” that is used for the license generation. The Host ID cannot be used on a different server.

2. Start CeraMap and select Help, About.

3. Write down the Host ID number.

For additional information, please contact us at [email protected].


Appendix C: PolyView Server Installation and Testing This appendix explains how the PolyView server is installed and tested.

PolyView Server Installation

To install the PolyView server:

1. Copy Mysql installation file to / folder.

2. Run "chmod 775 <Mysql installation file>"

3. Run "./< Mysql installation file >"

4. Go through the installation by choosing default (always next).

5. Copy CeraView installation file to / folder.

6. Run "chmod 775 <CeraView installation file>"

7. Run "./< CeraView installation file >"


9. Copy the PolyView installation file to / folder

10. Run "chmod 775 <installation filename>".

11. Run "./<installation filename>".


13. Make sure server installation is chosen in the following screen.


PolyView Standalone Server Testing

After installation, open the Terminal and do the following:

1. Run "pvstart &" and make sure that the following messages appear:

2. Run CeraView, see that the following login screen appears, and click Cancel.


3. Make sure that PolyView icons appear in the menu bar as follows:

4. Run "pvmap &".

5. When the Login screen appears, enter the following - User Name: admin, Password: ceragon.


6. Make sure the map is loaded properly, the server appears on the map, and it is colored green.

7. Run "cmconfig" and select the Advanced tab.

8. Make sure that "/usr/sfw/bin/mozilla" appears in the web browser.


PolyView Redundancy Server Testing

1. Perform the PolyView Server Installation procedure (provided earlier in this Appendix) for each of the servers.

2. Perform the PolyView Standalone Server Testing procedure (provided earlier in this Appendix) for each the servers.

3. On the main server, run "pvconfig".

4. Click the Redundancy tab, and for the main server, select the Server role.


5. Click Apply, and then Close.

6. In the terminal, run "pvstop", and then "pvstart &".

7. On the Standbyserver, run "pvconfig".

8. Click the Redundancy tab, and for the Standby-Auto Switch, select the Server role.

9. For Main Server Host Address, enter the main server’s IP address.

10. For Main-Standby Synchronization, select Full.


11. Click Apply, and then Close.

12. In the terminal, run "pvstop", and then "pvstart &".

13. On the Main server, run "pvmap".



15. Right click anywhere on the map and select Add Group.


16. Choose a name for the group and click OK.


17. Make sure that the group is added to the map.


18. On the Standby server, run "pvmap".


20. Make sure that the group you added on the Main server appears in the map.


Appendix D: HTTP Proxy Installation and Configuration This appendix explains how the HTTP proxy for PolyView is installed and configured on the Microsoft Windows and Sun Solaris operating systems.

HTTP Proxy Installation on Microsoft Windows Systems

• Buy and download Sun Java System Web Proxy Server 4.0.8 from the following web site:

https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJPrxySrv-4.0.8-OTH-G-F@CDS-CDS_SMI

• Unzip the “sun-web-proxy-server-4.0.8-win.zip” file.

• Run setup.exe to install the web proxy.

• Start the server by running <installation path>\proxy-admserv\startsvr.

• Access the proxy admin server via the following URL: http://<machine name>:8082.

• In the web proxy admin go to Servers -> Manage Servers (the default opening location), and click the server1 instance.


• In “Preferences” -> “Start/Stop Server” (the default opening location), click “On”.

The server can also be started by running:

<installation path>\proxy-server1 \startsvr

• Make sure the server is running (via the proxy-admin, as in the example above, or via the computer

services list).


• Go to “Routing” -> “Enable/Disable Proxying”, select the “Enable Proxying of this Resource”

option, and click OK.


HTTP Proxy Installation on Sun Solaris Systems

• Buy and download Sun Java System Web Proxy Server 4.0.8 from the following web site: https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJPrxySrv-4.0.8-OTH-G-F@CDS-CDS_SMI

• Put the downloaded file in the / folder. • Open terminal and run "cd /". • Run "gzip -d sun-web-proxy-server-4.0.8-sparc.tar.gz". • Run "tar -xvf sun-web-proxy-server-4.0.8-sparc.tar". • Run "chmod 775 setup". • Run "./setup".

In the following window make sure that "startup on boot" is checked.


Start the server by running "/opt/sun/proxyserver40/proxy-admserv/start". • Run "/usr/sfw/bin/mozilla"

Access the proxy admin server via the following URL: http://<machine name>:8081. • In the web proxy admin go to Servers -> Manage Servers (the default opening location), and click

the server1 instance.


• In “Preferences” -> “Start/Stop Server” (the default opening location), click “On”.

Make sure the server is running (via the proxy-admin, as in the example above, or via the computer services list).


• Go to “Routing” -> “Enable/Disable Proxying”, select the “Enable Proxying of this Resource” option, and click OK.


Client-Browser Configuration For each browser that will access the web interface, configure the following:

• Open a browser window.

• In the Tools menu, select Internet Options.

• Select the Connections tab.

• Click LAN Settings.


• In the Proxy Server area, select Use a proxy server for your LAN.

• In the address area, specify the address of the machine on which the web proxy server is installed.

• For Port, enter 8080 (or a different port number if configured otherwise in the web proxy server).


Appendix E: DCN Sizing This appendix describes how to determine the required bandwidth between the network elements and the centralized network management system.

PolyView Server - CeraMap Client (#1)

The NMS should have IP connectivity to the NEs network. The PolyView clients can be locally installed on the Sever or remotely installed on a separate PC.

The Client PCs can be directly connected to the NE network. If no DCN connection is available between the PolyView clients and the NE network, the PolyView server can be used as a proxy server. Requests (SNMP or HTTP) from the client will be sent to the network through the PolyView server.

The minimum recommended bandwidth between the PolyView server and any remote connected PolyView client user (CeraMap) is 2 Mbps.


DCN Sizing, Server-Client

Recommended bandwidth between PolyView server and active connected PolyView clients is as follows:

Number of Clients 1 2 5 10 20

Recommended DCN Bandwidth towards the PolyView Server

2048 Kbps 2048 Kbps 4096 Kbps 10 Mbps 20 Mbps

PolyView Server - Network Element Network (#2)

The recommended bandwidth between the PolyView server and the first network element on the NE network is driven by the number of NEs that need to be managed on this single DCN connection and the application in use.

For one NE Telnet/SSH CLI connection, a 128 Kbps connection suffices.

For a typical CeraView Web or PolyView connection 1 Mbps is recommended (where 512 Kbps is the minimum).

2 Mbps is recommended for larger networks.

Local Connection to the Network Element (#3)

Users can directly connect to the NE using a local connection, via the CLI or the CeraView Web EMS. The recommended bandwidth for directly connected users with a CLI connection is 128 Kbps. The CeraView Web user will need a minimum of 512 bps bandwidth connection.

PolyView Northbound Interface (#4)

Northbound interfaces should be treated as Client connections. This means that the sizing rules of the PolyView Server - Client should be used here as well (see the section PolyView Server - CeraMap Client (#1)).


Redundant Server Solution - PolyView (#5)

PolyView includes built-in support for redundancy configuration. This configuration includes two PolyView servers: a primary server, which is generally active, and a secondary server, which is generally located at a geographically remote site, and is in standby mode. To keep the information on both servers synchronized, an Ethernet connection should be available between the two servers.

The recommended bandwidth between the Main Server and the Standby server is 2 Mbps.

Note: The PolyView standby server may have lower bandwidth connection depending on the configuration in case the main server it up. The standby server may be configured not to poll any info from the NE, while synchronizing only from the main server; however, if the Main server is down, the standby server need to have the same bandwidth as the main server.


Appendix F: PolyView Ordering The intent of this Network Management Ordering Guide is to assist customers and sales when quoting the management product. This appendix is intended as a guide to the NMS HW and SW platform and should be used to supplement the existing sales configurator.

Hardware Selection for PolyView Server

Determining System Parameters

When ordering NMS HW, the following basic parameters must be known:

• Maximum number of managed network elements.

• Maximum number of potential parallel connected NMS clients (CeraMap) users.

• Operating system – UNIX or Windows.

• PolyView SW version or Generic version (HighCap Radio NMS). UNIX-Solaris OS Platforms Important remarks regarding UNIX OS:

• UNIX servers are supplied with PolyView or HighCap Radio NMS already installed.

• Ceragon doesn’t support UNIX servers that were not purchased through Ceragon and were not installed by Ceragon.

• All NMS Software licenses and MySQL database SW should be purchased separately.

• Oracle servers HW (former - SUN Microsystems company) are delivered with one year standard warranty of Sun (NBD). Yearly warranty extensions are available.

• PolyView supports Solaris 10 version only.


Number of Managed NEs

Number of Parallel

Connected Clients Processor Memory Hard

Drive Model Ceragon

Marketing Model

Part Number

Up to 7,000 Network Elements

Up to 10 NMS Clients

UltraSPARC T2 8G 300 GB Sun Fire

T5220

PV KIT-SW&HW,

Medium,Unix SU-0001-X

HighCap-SW&HW,Medi

um,Unix SU-0004-X




T5220

PV KIT-SW&HW, High,Unix

SU-0002-X

HighCap-SW&HW,High,

Unix SU-0005-X




T5220

PV KIT-SW&HW,Ultra

High,Unix SU-0003-X

HighCap-SW&HW,Ultra

High,Unix SU-0006-X

Unix Server, Network Elements <7,000, up to 10 clients

Marketing Model Item Description Part Number PV KIT-SW&HW, Medium,Unix Unix HW with PolyView SW (Medium, NE<7K, up to 10

clients) SU-0001-X

HighCap-SW&HW,Medium,Unix UNIX HW with HighCap Radio SW (Medium, NE<7K, up to 10 clients)

SU-0004-X

“PV KIT-SW&HW, Medium,Unix” and “HighCap-SW&HW,Medium,Unix” are kits that includes T5220 4core, 8GB, 4x146GB Hardware and PolyView/Generic SW installation.

T5220 4core, 8GB, 4x146GB, Unix Sun Part # Qty Full Description

SEDAA143Z 1

Sun SPARC Enterprise T5220 Server Base, 1 * 4 Core 1.2GHz UltraSPARC T2 processor, 2nd Generation Chassis, no memory, no disk backplane, no disks, no DVD, 4 10/100/1000 Ethernet ports, 1 serial port, 4 USB ports, 4 dedicated PCI-E low profile slot, 2 PCI-E low profile or XAUI (10Gb ethernet) slots, no power supplies, RoHS-6 compliant. (For Factory Integration Only)

SESY9DV2Z 1 SATA DVD drive assembly with 8x DVD+/-RW, slot load, slimline. For use with Sun SPARC Enterprise T5xx0. RoHS-6. ATO option.

SEDY9PS32Z 2 AC power supply unit, Climate Saver Compliant 750W, for use with the Sun SPARC Enterprise T5220. (For Factory Integration Only) RoHS-6.


T5220 4core, 8GB, 4x146GB, Unix

Sun Part # Qty Full Description

SESY3C11Z 4 146GB 10K RPM 2.5" SAS disk drive with bracket (Qty 1). For use with Sun SPARC Enterprise T5120, T5220, T5140 & T5240. RoHS-6 For Factory Integration Only

SESY9MF1Z 4 Hard Disk Filler Panel

SESY9SF1Z 1 Sun SPARC Enterprise Software Preinstall, including Solaris 10 05/09 (Update 7), Sun Studio 12, GCC, Ldoms 1.2 Manager, and CMT Tools, Factory Integration

SEDY9BB2Z 1 8 disk capacity 2nd Generation disk backplane. For use with the Sun SPARC Enterprise T5220. RoHS-6. (For Factory Integration Only)

SEDY9LS1Z 1 Standard agency label for SPARC Enterprise T5220 AC 8 HDD (For Factory Integration Only)

SESY2B2Z 2 4 GB Memory Expansion (2 x 2GB) low-profile FBDIMMs, Gen 2, 1.8 V, for Sun SPARC Enterprise, RoHS 6. (For Factory Integration Only)

SESY9BC1Z 1 Shipping box used for 2U AC Power Supply Units

X3000A 1 XVR-300 2D Graphics Frame Buffer. 24-bit color, high resolution 2D graphics accelerator. PCI Express x8 interface and dual DVI-I. RoHS-6.

X333A-25-10-IL 2 Localized Power Cord Kit Israel, SI-32 plug, IEC60320-C13 connector 10A, 250VAC rated, 2.5meter/ This Product is Hazard Class Y, RoHS compliant.

SESX9RK2Z 1 Express Rail (tool-less) slide rail kit for rack mounting of the Sun SPARC Enterprise T5120, T5220, T5140 & T5240. RoHS-6. Xoption

SESX9CA1Z 1 Cable management arm, compatible with either screw mounted slide rails or Express Rails. For use with Sun SPARC Enterprise T5120, T5220, T5140 &T5240. RoHS-6. Xoption

X3731A 1 Type 7 U.S./Canada Universal (PC) Country Kit. RoHS-6 (Lead-Free) Compliant.


Marketing Model Item Description Part NumberPV KIT-SW&HW, High,Unix Unix HW with PolyView SW (High, NE<10K, up to 20

clients) SU-0002-X

HighCap-SW&HW,High,Unix

UNIX HW with HighCap Radio SW (High, NE<10K, up to 20 clients)

SU-0005-X

“PV KIT-SW&HW, High,Unix” and “HighCap-KIT-SW&HW, High,Unix” are kits that includes T5220 4core, 16GB, 4x146GB Hardware and PolyView/Generic SW installation.


T5220 8Core 16GB, 4x146GB, Unix


SEDAC143Z 1









SESY2B2Z 4 4 GB Memory Expansion (2 x 2GB) low-profile FBDIMMs, Gen 2, 1.8 V, for Sun SPARC Enterprise, RoHS 6. (For Factory Integration Only)



X333A-25-10-IL 2 Localized Power Cord Kit Israel, SI-32 plug, IEC60320-C13 connector 10A,

250VAC rated, 2.5meter RoHS-6 compliant.





Marketing Model Item Description Part Number PV KIT-SW&HW,Ultra High,Unix Unix HW with PolyView SW (Ultra High,

NE<10K, up to 40 clients) SU-0003-X

HighCap-SW&HW,Ultra High,Unix UNIX HW with HighCap Radio SW (Ultra High, NE<10K, up to 40 clients)

SU-0006-X

“PV KIT-SW&HW, Ultra High,Unix” and “HighCap-KIT-SW&HW, Ultra High,Unix” are kits that includes T5220 4core, 32GB, 4x146GB Hardware and PolyView/Generic SW installation.


T5220 8Core 32GB, 4x146GB, Unix


SEDAC143Z 1









SESY2C1Z 4 8GB RoHS-6 Memory Expansion Kit (2*4GB)Comprised of two low-profile FBDIMMs. For use with Sun SPARC Enterprise T5120, T5220, T5440, Netra T5220 and Netra T5440.For Factory Integration Only



X333A-25-10-IL 4 Localized Power Cord Kit Israel, SI-32 plug, IEC60320-C13 connector 10A, 250VAC rated, 2.5meter RoHS-6 compliant.





Windows OS Platforms

Windows PC, Network Elements <600, up to 3 Clients

Important remarks regarding Windows OS –

• Unlike UNIX servers, Windows PCs can be purchased separately from the with PolyView SW. Installation can be done by the customer.

• All NMS Software licenses and MySQL database SW should be purchased separately.

• With 2Gb memory PC, maximum of 2-3 parallel NMS clients usage is recommended. Minimum Windows PC requirements are - Hardware Type Any type Processor Core 2, 2.0 GHz Memory (RAM) 2 GB Available Drive Space 120 GB

Operating System Recommended -Windows 2008 Server/XP Optional (EOL) – Windows 2003, Vista

Min Ethernet Ports 1 Display Monitor 1280x1024 True Color

My SQL Database

Ceragon PolyView SW uses internal MySQL SW database. The following Item should be purchased on every new server HW (UNIX or Windows) purchasing. Marketing Model Item Description Part Number

MYSQL-LICENSE MySQL software License for Windows/Unix platform. SL-0003-X

Hardware Selection for PolyView Client

It is recommended to use for the PolyView Client the same configuration as the PolyView PC for server.

It is possible to use the UNIX servers for clients too. Hardware Type Any type Processor Core 2, 2.0 GHz Memory (RAM) 2 GB Available Drive Space 120 GB

Operating System Recommended -Windows 2008 Server/XP/Win7 Optional (EOL) – Windows 2003, Vista

Min Ethernet Ports 1 Display Monitor 1280x1024 True Color


NMS Software Selection

Introduction

PolyView™ software can be purchased from Ceragon. The basic software item consists a built-in license for 20 Network Elements (NEs), meaning it can manage up to 20 managed elements.

In order to manage more than 20 NEs, additional license should be purchased from Ceragon.

PolyView™ Software Ordering Information

In order to manage the network, customers should purchase the PolyView™ software and the appropriate license based on the number of managed Network Elements.

PolyView™ software is available on a CD that will be delivered to the client, or downloaded via Ceragon's customer support FTP.

Two basic NMS SWs are available (with the same set of features) –

• PolyView (with “Ceragon” naming)

• HighCap Radio NMS (Generic version of the PolyView- without Ceragon Name)

In order to obtain a permanent license, contact Ceragon customer support and request the type of license you want, as listed in the following table.

It is possible (and preferable) to order from Ceragon the NMS servers including the PolyView/HCR NMS SW installation as a package.

Marketing Model Item Description Part Number

PolyView NMS PolyView Software (Win/Unix) + License for 20 NEs SP-0028-x* HighCap Radio NMS SW HighCap Radio NMS Software + License for 20 NEs SP-0077-x* PV_21-100_NE License for 21-100 NEs: per NE SR-0038-0 PV_101-500_NE License for 101-500 NEs: per NE SR-0039-0 PV_501-1000_NE License for 501-1000 NEs: per NE SR-0040-0 PV_>1000_NE License for 1001 or more NEs: per NE SR-0041-0

(*) SP-0028-x* & SP-0077-x*- whereby "x" represents the latest released version of PolyView


Examples:

1. Management of 130 NEs:

Description Model # Quantity PolyView Software + License for 20 NEs PolyView NMS 1

License for 21-100 NEs: per NE PV_21-100_NE 80 License for 101-500 NEs: per NE PV_101-500_NE 30

2. Upgrade of existing license from 60 NEs to 130 NEs:

Description Model # Quantity License for 21-100 NEs: per NE PV_21-100_NE 40 License for 101-500 NEs: per NE PV_101-500_NE 30

License Components The following license components are limited, based on the purchase order.

Managed NE Limit - limits the number of managed elements (number of IP addresses on the network map). There is no limit on the number of groups or symbols the user can add.

Feature Set and Enabled Features - limits the features enabled by PolyView™. Two feature sets are currently defined (default is Pro):

o Pro: all features are enabled, except the following which require a specific license.

o Enabled Features: specific proposal for the following features that require a specific license:


- Redundant server support

- PolyView software upgrade

- End to end TDM trails provisioning

Expiry Date - no expiry (permanent license), or expiry date of license (for trials/demos)

Example:

Management of 130 NEs, redundant servers configuration:

Description Model # Quantity per server

Quantity for redundant servers

solution PolyView Software + License for 20 NEs PolyView NMS 1 2 License for 21-100 NEs: per NE PV_21-100_NE 80 160 License for 101-500 NEs: per NE PV_101-500_NE 30 60 License for redundant PolyView support PV_Redundant_Support 1 2


Temporary Demo License

When the user installs the PolyView server for the first time, it is installed with a “demo” license that will enable 30 days of work with all features enabled, and no limitation on the number of managed NEs.

PolyView will provide 14 days of notification before the license expires. The notification will appear upon each login to remind the customer to contact Ceragon to obtain a permanent license.

If a permanent license was not obtained within 30 days, the demo license will expire and the user will no longer be able to log in. An error message will advise the customer to contact Ceragon to obtain a permanent license.

The demo license will be activated once per station. Uninstalling and reinstalling the PolyView software will not grant a new demo license.

Obtaining a Permanent License A permanent PolyView license will be issued when the relevant order is processed by Ceragon, after PolyView is installed on the customer station.

Once an order is placed and processed, the customer must send the "PolyView License Request Form" to Ceragon Customer Support, with all the relevant information.

Ceragon Customer Support will verify that the necessary information was provided, and that the order was properly made. The license will then be generated and emailed to the customer, together with license installation instructions.

An invoice will be issued when the license is generated.


Appendix G: SNMP MIB Support The NMS doesn’t support any standard SNMP MIB (like RFC-1213, or other). The NMS supported SNMP private MIB which called CERAGON-NMS-MIB, and requires CERAGON-MIB to be compiled with.

MMS MIB Location


Ceragon NMS-MIB Functionalities

The main functionality of the MIB is the current alarm table.

The current alarm table includes:

• NMS server alarms

• All NE alarms (including for IP-10 and 1500R, 3200T, and IP-MAX)

In addition to the current alarms there are two scalars:

• nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1 )– a counter that advance every change of the current alarm table.

• nmsMostSevereAlarm (1.3.6.1.4.1.2281.2.2.15.1.3 ) - the most severe alarm within the current alarm table.

NMS Current Alarm Table (nmsCurrentAlarmTable)

The NMS current alarm table is based on the 1500R/3200T current alarm, that defined in CERAGON-MIB. IP-10G traps and current alarms are a bit different, for mapping refer to the next section. Note the following:

‐ Only SNMP V.1 is supported.

‐ The default Server SNMP port number is 1610 (configurable).

‐ The community string for “Read only” is “public”.

‐ There are no write permissions for the MIB.

NMS Current Alarm Table Columns

• nmsCurrentAlarmCounter - A running counter of open alarm, the counter is incremented on every new RAISED trap. It is cleared after reset.

• nmsIpAddress – The IP address of the NE that the alarm is raised upon. It could be the NMS server’s IP for NMS alarms, or a NE IP for any NE alarm.

• nmsCurrentAlarmSeverity – The severity of the alarm. The following severities can be for the alarms

o event (1)

o warning (3)

o minor (7)


o major (15)

o critical (31)

o node down (63) - this is for unreachable NEs raised by the NMS server only.

• nmsCurrentAlarmId - Alarm Identifier (contains alarm type and interface). Same AlarmId for raise and clear alarms.

• nmsCurrentAlarmIfIndex- Interface Index where the alarm occurred, alarms that are not associated with specific interface will have the following value (in case of 1500R/3200T/IP-MAX):

o For IDC related alarms the value is: 65001

o For drawer1 related alarms the value is: 65003

o For drawer2 related alarms the value is: 65004

o If Alarm's origin is bigger than 256, it will be 65000 + the origin

• nmsCurrentAlarmOrigin- The origin drawer of the alarm (if applicable, otherwise it will be idc(2)) other possible values are based on gnAgnCurrentAlarmOrigin:

o Interfaces(1), idc(2), drawer1(3), drawer2(4), unKnown(5), tIdc1(257), tIdc2(258), tIdc3(259), tIdc4(260), tIdc5(261), tIdc6(262), tIdc7(263), tIdc8(264), tIdc9(265), tDrawer1(513), tDrawer2(514), tDrawer3(515), tDrawer4(516), tDrawer5(517), tDrawer6(518), tDrawer7(519), tDrawer8(520), tDrawer9(521), tDrawer10(522), tDrawer11(523), tDrawer12(524), tDrawer13(525), tDrawer14(526), tDrawer15(527), tXC1(769), tXC2(770), tXC3(771), tXC4(772), tXC5(773), tXC6(774)

• nmsCurrentAlarmUnit- The unit of the alarm, possible values are:

o idc(2), odu(3), mux(4), modem(5), drawer(6), unKnown(7), xc(9)

o rfu (101)

• nmsCurrentAlarmTrapID- The trap ID of the RAISED trap that was sent when this alarm was raised.

• nmsCurrentAlarmTimeT– Timestamp of this alarm, this number is the seconds from midnight 1.1.1970

• nmsCurrentAlarmText- The alarm display text (same as the text in the sent trap).


IP-10/IP10G Current Alarm Column Mapping to the NMS Current Alarms

Var-Bind Mapping: IP-10 to NMS Current Alarms

IP-10 Trap Var-Bind/Current

Alarm Column IP-10 Var-Bind NMS Var-Bind Comments

Trap var-bind & current alarm column genEquipCurrentAlarmCounter nmsCurrentAlarmCounter

No mapping. The NMS counter is different from the NE counter.

Trap var-bind & current alarm column

genEquipCurrentAlarmRaisedTimeT nmsCurrentAlarmTimeT Mapping 1:1


genEquipCurrentAlarmId nmsCurrentAlarmId Mapping 1:1


genEquipCurrentAlarmSlotId nmsCurrentAlarmOrigin

Current support No mapping. Fixed to ‘-1’ (Future) 1000 – SA Ip-10 1001 –Ip-10G slot 1 1002 –Ip-10G slot 2 1003 –Ip-10G slot 3 1004 –Ip-10G slot 4 1005 –Ip-10G slot 5 1006 –Ip-10G slot 6


genEquipCurrentAlarmInstance NA No mapping


genEquipCurrentAlarmSeverity nmsCurrentAlarmSeverity Mapping 1:1


genEquipCurrentAlarmIfIndex nmsCurrentAlarmIfIndex Mapping 1:1


genEquipCurrentAlarmModule nmsCurrentAlarmUnit Mapping “IDU “: 101 “RFU” : 3 (odu)


Traps

NMS Traps

The list of NMS traps are defined in Ceragon NMS MIB, and in the alarm chapter.

NMS traps are sent with the following var-binds

gnGenCfgTrapSeverity: Severity of the trap (nmsCurrentAlarmSeverity)

gnGenCfgAlarmText: Alarm text (nmsCurrentAlarmText)

gnGenCfgCLLI: Fixed empty string will be sent ("") - not supported

gnAgnCurrentAlarmOrigin: 400 (fixed number) will be sent - not supported

gnAgnCurrentAlarmUnit: 400 (fixed number) will be sent - not supported

IP-10 Trap Var-Bind/Current

Alarm Column IP-10 Var-Bind NMS Var-Bind Comments


genEquipCurrentAlarmDesc nmsCurrentAlarmText Mapping 1:1

Trap var-bind only genEquipMostSevereAlarm NA No mapping

Trap var-bind only genEquipNetworkAgentIp nmsIpAddress Mapping 1:1

Trap var-bind & current alarm column genEquipCurrentAlarmState NA

No mapping (no need, as only the raised traps will be in the table)

Trap var-bind only genEquipTrapCfgMgrCLLI NA No mapping

Trap id NA nmsCurrentAlarmTrapID The trap ID of the alarm (SNMP v.1)

Current alarm column only

genEquipCurrentAlarmName (the parameter and entity in the CLI) for example 'radio/framer/radio-lof')

NA No mapping

Current alarm column only genEquipCurrentAlarmProbableCause NA No mapping

Current alarm column only genEquipCurrentAlarmCorrectiveActions NA No mapping


gnAgnCurrentAlarmTimeT: Timestamp of this alarm, nmsCurrentAlarmTimeT will be sent.

gnAgnCurrentAlarmID: For event - 0 (integer), for alarm it will be equal to the trap ID of the raise alarm (400+).Trap-ids starting from 500 are always clearing raise alarms starting in 400. There is a difference of 100 between raise and clear alarms, for example, Trap 401 is a raise alarm, while 501 is the clear alarm for it.

NBI Trap (in SNMPv1) Example - Event 402: Security Failure


Management Traps

The following tables list thePolyView management traps and MIB definitions.

Management Alarms - Raise Traps

Trap Name Alarm Description Trap # Severity

nmsNodeDown Management Trap: This Trap is sent when the NMS loses connection with a network element.

401 Node Down

nmsSecurityFailure Management Trap: This Trap is sent when the user failed login the NMS system three times sequentially.

402 Event

nmsPrimaryServerConfigMismatch Management Trap: This Trap is sent when a Secondary Standby server tries to connect to Stand-alone server.

403 Major

nmsSecondaryServerNotConnected

Management Trap: This Trap is sent by a Primary server when it loses connection to the Secondary Standby server.

404 Major

nmsLicenseExpiresInLessThanTwoWeeks Management Trap: This Trap is sent by a Main server when License File expires in less than two weeks.

405 Warning

nmsLicenseExpired Management Trap: This Trap is sent by a Main server when License File expired.

406 Major

nmsNetworkElementsNumExceedsLimit

Management Trap: This Trap is sent by a Main server when Network Elements number exceeds the license limit.

407 Major

nmsFailedLoadingLicenseFile Management Trap: This Trap is sent by a Main server when it Failed loading license file.

408 Major

nmsTftpServerAlreadyRunning Management Trap: This Trap is sent when Tftp port (69) bind by another process.

409 Major

userDisconnected Management Trap: This Trap is sent when a user is disconnected by another user.

410 Event

nmsPrimaryServerVerMismatch

Management Trap: This Trap is sent when a Secondary Standby server tries to connect to Main server with different version.

411 Major

nmsEsymacNotConnected Management Trap: This Trap is sent when the server cannot communicate with ESYMAC services.

412 Major

nmsPrimaryServerNotConnected

Management Trap: This Trap is sent by a Secondary Standby server when it loses connection to the Primary server.

413 Major



nmsEnabledFeatureSetNotLicensed Management Trap: This Trap is sent when an Enabled feature set not licensed.

414 Major

nmsFreeDiskSpaceTooLow

Management Trap: This Trap is sent when the free disk space on the main disk is too low (below the configured threshold).

415 Major

nmsCpuLoadTooHigh Management Trap: This Trap is sent when average system load is too high (above the configured threshold).

416 Major

nmsProtectionSwitchOccurred

Management Trap: This Trap is an event that sent when a protection switch occurs between the main slots in a network element The trap description includes the IP of the active and standby slots in the following format: 'Protection switch, active:<IP>, standby:<IP>'

417 Major

nmsPrimaryAndSecondaryServersAreActive

Management Trap: This Trap is sent by a Primary server (Main) and by the secondary server (Standby) when both servers are in active mode in case the percentage of unreachable NE in the main server crossed the configured threshold. The trap description includes the following format: 'Percentage of unreachable elements in main server is over threshold Raised'

418 Major

nmsFloatingIpAdded

Management Trap: This Trap is sent when a floating IP was added to a network element. The trap description includes the main (non floating) IP of the NE in the following format: 'Alarm from ip <IP>: Floating IP added'

419 Minor

nmsNoTrustedCertificateFound

Management Trap: This Trap is sent when no trusted certificate was found for a network element. This trap is OBSOLETE, and not in use.

420 Warning



nmsConfigurationChange

Management trap: NMS configuration change event: For each configuration change, The description of the event shall be the same description that being logged in the Users Action Log concatenated with the three fields - Application - User name - Connected From - Description + Details (in { …}) For example Adding NE will send a trap with the description field like this: “Application=CeraMap, User Name=admin, Connected From=10.10.11.113, Description=Topology:Add Network Element, Details {Type=Network Element, IP=10.10.10.10, Name=aaaaa, Path=root->aaaaa, SNMP port=161, SNMP version=V1”

421 Warning


Management Alarms - Clear Traps

Trap Name Alarm Description Trap #

nmsNodeUp

Management Trap: This Trap is sent when the NMS resumes connection with a previously disconnected network element.

501

nmsPrimaryServerConfigOk

Management Trap: This Trap is sent when a secondary standby server connects to a main server.

503

nmsSecondaryServerConnected

Management Trap: This Trap is sent by a Primary server when it reconnects to the Secondary Standby server.

504

nmsLicenseExpiresInMoreThanTwoWeeks

Management Trap: This Trap is sent by a Main server when License File expires in more than two weeks.

505

nmsLicenseDoesNotExpire Management Trap: This Trap is sent by a Main server when License File does not expire.

506

nmsNetworkElementsNumWithinLimit

Management Trap: This Trap is sent by a Main server when Network Elements number within the license limit.

507

nmsSucceededLoadingLicenseFile Management Trap: This Trap is sent by a Main server when it Succeeded loading license file.

508

nmsTftpServerStartRunning Management Trap: This Trap is sent when the TFTP server succeeded bind Tftp port (69) .

509

nmsPrimaryServerVerMismatchOk

Management Trap: This Trap is sent when a secondary standby server connects to a Main server.

511

nmsEsymacConnected

Management Trap: This Trap is sent when server can communicate with ESYMAC services.

512

nmsPrimaryServerConnected

Management Trap: This Trap is sent by a Secondary Standby server when it reconnects to the Primary server.

513

nmsLicenseConfigurationMismatchRemoved

Management Trap: This Trap is sent when a License Configuration mismatch is removed.

514


Trap Name Alarm Description Trap #

nmsFreeDiskSpaceOK

Management Trap: This Trap clears the free free disk space alert. It is sent when the free disk space of the main disk is OK (above the configured threshold).

515

nmsCpuLoadOK

Management Trap: This Trap clears the high CPU load alert. It is sent when average system load is normal (below the configured threshold).

516

nmsPrimaryAndSecondaryServersAreNotActive

This Trap is sent by a Primary server (Main) and by the secondary server (Standby) when both servers are nor in active mode.

518

nmsFloatingIpCleared

Management Trap: This Trap clears the alert that was sent when a floating IP was added to a network element.

519

nmsTrustedCertificateFound

Management Trap: This Trap clears the alert that was sent when no trusted certificate was found for a network element.

520


Appendix H: Trail Management for FibeAir 1500A End-to-end Trail Management enables you to define the communication path between one FibeAir 1500A unit and another.

Using end-to-end trail management, once you determine the trail source and destination end point, PolyView automatically selects the optimal route, as follows:

For a protected trail, the shortest path will be defined as the main path.

For an non-protected trail, the least loaded path will be chosen as the main path.

In a ring configuration, each trail can be defined as Protected or Non-Protected, if the VC is avilable for both directions.

In addition to determining the optimal path from one Ceragon ADM unit to another, the advantages of defining and managing an end-to-end trail include the following:

Trails are tracked in the network map and in a table with sorting features.

PolyView maintains a performance monitoring log database collected for the trail termination points of each trail in the system.

Users can view the top-most trail alarms and current alarms.

Users can activate/disable trails and initiate a switch to the protection path.

Defining a Trail To define an end-to-end trail:

1. In CeraMap, select two Ceragon ADM elements at each end of the trail.

Note the following:

All trail-relevant data for all the elements that are part of the sub-map must be updated in the database. Note that if a change in the trail was made via CeraView, the PolyView database may not be updated.

PolyView automatically updates the database every few hours, depending on the system settings. You can perform a manual update of the database by selecting all entities in the trail, and running the Poll Node PolyView command (described later in this guide).

End point #2 must be reachable from end point #1 (at least one path).


The radio direction, East-West, must be valid. To verify this, run the validation utility by selecting Trail, East-West Validation in the CeraMap menu bar.

Trail East-West Validation Window

In this window, select the group of radios you want to correct, and click Apply.

PolyView will check radio directions and correct them to enable a working trail.

There must be at least one unmapped port at each end point.

There must be at least one KLM (VC) not in use in at least one path.

2. In the menu bar, select Trail, Create New Trail, or click the Create New Trail icon .

The Create Trail window appears.


Trail Definition Window

The information that appears in the window is based on the path you selected in the network map.

3. In the Trail End Point area, select Drop if the unit will serve as an end-point in the trail without being able to transmit data to sources outside the ring, or Pass-through if the unit will serve as an end-point in the trail with the ability to transmit data to sources outside the ring.

If you selected Drop, click Select and choose the desired port.

4. In the Trail Details area, select Enable Trail to activate the trail path.

5. In the Name field, enter a unique name you want to assign to the trail. (It is recommended to use the name that PolyView automatically generates.)

6. To change the Virtual Container for the trail, click Select.


VC Selection Window

Note the following:

- The two end points of the trail are mapped to a selected VC.

- The selected VC for ADMs in the middle of the trail are set to Pass through and appear in dark gray.

- VCs in dark gray are in use and cannot be selected.

7. For Main Path, click the drop-down list and select the direction relative to the port at end point #1.

The direction for the port at end point #2 is determined by that of end point #1 (meaning that if the direction at end point #1 is East, the direction at end point #2 is West).

8. Select Protection to enable the protection mode for the trail (only if this mode is relevant, and the VC is available also on the protected side).

9. After you complete the Create Trail window and click OK, the trail is validated.

Trail Validation Results Window


Managing a Trail To manage a defined end-to-end trail:

1. Select one or more elements in the map.

If you select only part of the map, you will only see the trails that start or end in the selected elements. To see all trails, select all the elements in the map.

2. Select Trail, View and Edit Trail List, or click the View and Edit Trail List icon .

The Trail List window appears.

Trail Management Window

3. The window displays a list of defined trails between the elements that were selected in the sub map. To perform a trail management operation, select the row that represents the trail you want, and click the icon that represents the operation you want to perform, as follows:

Used to refresh trail information.

Used to create a new trail. The trail will be added between the endpoints of the selected trail.

Used to edit the selected trail’s information.

Used to perform a loopback for the selected trail.


Used for advanced trail configuration.

Used to delete the selected trail.

Used to switch the trail’s current active direction.

Used to open the Performance Monitoring window for the selected trail.

Used to open the Current Alarms window.

4. Advanced Configuration

In the window that appears when you select this option, you can specify the transport identification code, and set operation mode parameters.

5. Viewing Trail Alarms

To view trail alarms, click the Trail Alarms icon.

The Trail Alarms window displays the following information:

The current state of the specified end point unit, its number, name, and port

The severity of the alarm. From highest to lowest, the severity levels are:

Critical - dark red

Major - light red

Minor - orange

Warning - yellow

Event - blue

Normal (no alarm) - green

Unknown (the element is not responding) - grey (question mark)

The path direction

The alarm’s source

A brief description of the alarm


6. Viewing a Trail Performance Monitoring Report

To view a trail’s performance monitoring report, select a trail, and click the Trail PM Report icon.

The report displays performance monitoring information for the ADMs included in the trail you selected. To view performance values for a particular ADM, click the tab of the ADM at the top of the window.

Note that the Integrity column indicates whether or not the values received at that time and date are reliable. A red x icon in the column indicates that the values are not reliable due to a possible power surge or power failure event that occurred at that time.


Appendix I: PolyView Support for Floating IP Address The network element can be configured to enable a floating IP address in a 1+1 slot protection configuration.

The Floating IP is an additional IP added to an element configured for 1+1 HSB (hot standby). The element has three IP addresses as follows:

• One IP for each unit (slot, altogether two)

• Another floating IP for the current active unit

Auto Discovery

The network element can be found by one of its three IP addresses. PolyView can identify that it is the same network element (one icon).

Note: IP-10G standalone does not support a floating IP.

Add Network Element

Adding an element manually can be done while adding one of the IPs supported by the element (three options, including the floating IP).

Note that PolyView does not support IP configuration or change in the element; it can only be discovered.

Inventory Reports

In all inventory reports, the floating IP will be the main IP of the element (the IP address column).

Using the Floating IP Address

Network Element Configuration

Any configuration of the element (that is using a floating IP) will be done via its floating IP.

IP-10G specifically supports the ability to configure the active slot in a 1+1 configuration via the extensions.

Network Element Notifications

Traps (from active or standby) will be sent with the floating IP address.

The slot number inside the trap will be the slot that was sending the trap.


(1) Alarms should be saved in the current alarm log as usual (with the floating IP).

(2) Events should be saved in the event log.

(3) Trail status events should be handled when they are sending via the floating IP.

Enable/Disable Floating IP

Note: Enabling or disabling floating IP requires a new discover node of the element.

When polling inventory from the element, if PolyView understands that the element was configured with a floating IP, If the user did not discover the node after enabling or disabling, an alarm will be raised (“Floating IP added”, severity Minor). See the alarm table below.

The alarm should be cleared after the discovered node process.

Trap Name Description Trap # Severity

nmsFloatingIPAdded Floating IP added 419 Minor

nmsFloatingIpCleared Floating IP cleared 519 Minor

Disable Floating IP Procedure

(1) When you disable a Floating IP in the element, do not use the floating IP in another element before discovering the node.

(2) Perform discover node.

Note: If discover node is run while the element does not have a slot 1 connection, the element will not be discovered.

Note: Disabling the floating IP in the element, will cause the element to be unreachable (if discover node was not done).

Note: if discover node was not done, and the PolyView polled the inventory, an alarm will be raised (as defined above).

Enable Floating IP Procedure

(1) Enable Floating IP in the element.

(2) Perform discover node.

Delete Network Element

Deleting an element and adding it again using a floating IP will cause the abandonment of the database of the “old” element, and the building of a new database for the “new” element. This option is not advised.


Appendix J: Port List This appendix details the ports used by PolyView. The notation Optional means that the port may be blocked if the service it supplies is not needed. The notation Configurable means that the port number may be configured. Note that if you change a port number of the server, you should make sure that the client that accesses that server also uses the same port number.

Ports used for Sending from PolyView Server

Port Number Protocol Packet Structure Details

161 SNMP UDP Sending SNMP Requests to the network elements

162

Configurable SNMP (traps) UDP

Sending SNMP traps forwarding. Optional

25 SMTP (mail) TCP

To send PolyView reports & triggers by email. Optional

69 TFTP UDP To upload/download configuration files. Optional

80 HTTP TCP To manage IP-10 devices

443 HTTPS TCP To manage IP-10 devices Optional

From 21 port to any remote port (>1023) FTP Control Port TCP

To download software and configuration files. (FTP Server responds to client's control port) Optional

From Any port (>1023) to any remote port (>1023) FTP Server random port range can be limited according to needed configuration (number of parallel configuration uploads).

FTP Data Port TCP

To download software and configuration files. (FTP Server sends ACKs (and data) to client's data port) Optional


Ports used for Receiving to PolyView Server


162

Configurable SNMP (traps) UDP Recieve SNMP traps from network

elements

1610 SNMP UDP Recieve SNMP traps from NBI

4001

Configurable Propriety TCP

CeraMap Server Used for connected clients and the redundant Standby server.

69 TFTP UDP To download software and files. Optional

21 FTP

Control Port

TCP To download software and configuration files. (FTP client initiates a connection) Optional

To any port (>1023) from any Port (>1023) FTP Server random port range can be limited according to needed configuration (number of parallel configuration uploads).

FTP Data Port TCP

To download software and configuration files. (FTP Client initiates data connection to random port specified by server) Optional

9205

Configurable Propriety TCP User Actions Logger server.

Optional

9207

Configurable Propriety TCP CeraView Proxy

Optional


Ports used for Sending from CeraView


161 SNMP UDP Sending SNMP requests to the network elements

69 TFTP UDP To upload/download configuration files. Optional

9205


User Actions Logger server. Optional

9207

Configurable Propriety TCP CeraView Proxy

Optional

9106


CeraView security server. the security server can run locally. Optional

Ports used for Receiving to CeraView


69 TFTP UDP To download software files. Optional

9106


CeraView security server. the security server can run locally. Optional

Ports used for Sending from the Web Based Management


80 HTTP TCP To manage device

443 HTTPS TCP To manage device. Optional


Ports used for Receiving to the Web Based Management


21 FTP TCP To download software files. Optional

Data port FTP TCP To download software files. Optional

In addition (optional), for telnet access to the network element, open TCP port 23. For SSH access to the network element, open TCP port 22.

polyview user guide - 12-2010.pdf

Documents