polyview release notes - n6.6.1

PolyView

Release Notes

N6.6.1.0.0. 1129

Document Version

November 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

Ceragon Networks®, FibeAir

®, 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,

CeraMonTM

, EtherAirTM

, and MicroWave FiberTM

, are trademarks of Ceragon Networks Ltd.

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

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.

Corporate Headquarters:

Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email: [email protected]

European Headquarters:

Ceragon Networks (UK) Ltd. 4 Oak Tree Park, Burnt Meadow Road North Moons Moat, Redditch, Worcestershire B98 9NZ, UK Tel: 44-(0)-1527-591900 Fax: 44-(0)-1527-591903 Email: [email protected]

North American Headquarters:

Ceragon Networks Inc. 10 Forest Avenue, Paramus, NJ 07652, USA Tel: 1-201-845-6955 Toll Free: 1-877-FIBEAIR Fax: 1-201-845-5665 Email: [email protected]

www.ceragon.com

APAC Headquarters:

Ceragon Networks APAC (S'pore) Pte Ltd 100 Beach Road #27-01/03 Shaw Towers Singapore 189702 Tel.: 65 65724170 Fax: 65 65724199

PolyView™

N6.6.1 Release Notes iii

Contents 1 PolyView - NMS for Wireless Backhaul Networks ........................................................... 1

1.1 PolyView and CeraMap Main Features ................................................................... 1

2 Components .................................................................................................................... 3

3 New Features .................................................................................................................. 4

3.1 IP-10 Support ......................................................................................................... 4

3.2 MySQL Database Upgrade ..................................................................................... 4

3.3 Licensing Report .................................................................................................... 5

3.4 Radio Channel PMs ................................................................................................ 6

3.5 IP-10G - Floating IP Support .................................................................................. 7

3.5.1 Auto-discovery ............................................................................................... 7

3.5.2 Adding an NE ................................................................................................. 7

3.5.3 Inventory Reports .......................................................................................... 7

3.5.4 Floating IP Administrative State Change ........................................................ 7

3.5.5 Disabling Floating IP Procedure ..................................................................... 8

3.5.6 Enable Floating IP Procedure ........................................................................ 8

3.5.7 Deleting an NE ............................................................................................... 8

3.6 Configuration Broadcast – GUI Update................................................................... 9

3.7 Radio Report – Additional Columns ...................................................................... 10

3.7.1 PM Report – Additional Columns ................................................................. 10

3.8 Client Auto Upgrade ............................................................................................. 10

3.9 TDM Trail Operational Status Alarm Logging........................................................ 11

3.10 Server Redundancy – Enhancement .................................................................... 11

3.10.1 Three New Parameters on the Redundancy Tab of the Server .................... 11

3.11 Radio PM – Time in Green Mode ......................................................................... 14

3.12 New RFU Support – RFU-HP ............................................................................... 15

3.13 Radio Disable Support for IP-10G ........................................................................ 15

4 Resolved Issues ............................................................................................................ 16

5 Open Issues .................................................................................................................. 18

6 Known Issues ................................................................................................................ 20

7 Supported Network Elements ........................................................................................ 22

7.1 IP-10 .................................................................................................................... 22

PolyView™

N6.6.1 Release Notes iv

7.2 IP-10G .................................................................................................................. 22

7.3 FibeAir 1500 Family .............................................................................................. 22

7.4 FibeAir 2000/4800 family ...................................................................................... 23

7.5 3rd Party Supported Elements ............................................................................... 23

8 Supported Operating Systems ...................................................................................... 24

PolyView™

N6.6.1 Release Notes v

List of Figures FIGURE 1: POLYVIEW SYSTEM NETWORK INTEGRATION ................................................................ 3

FIGURE 2: LICENSE MODEL COLUMNS ......................................................................................... 5

FIGURE 3: FLOATING IP REPORT ................................................................................................. 7

FIGURE 4: UPDATED CONFIGURATION BROADCAST GUI ............................................................... 9

FIGURE 5: ADDITIONAL COLUMNS RADIO REPORT ...................................................................... 10

FIGURE 6: ADDITIONAL COLUMNS XPIC PM REPORT .................................................................. 10

FIGURE 7: ALARM LOG – TDM OPERATIONAL STATUS ................................................................ 11

FIGURE 8: STANDBY SERVER SWITCHING MESSAGE ................................................................... 12

FIGURE 9: ENABLING AUTO-ACTIVATE FOR THE STANDBY SERVER .............................................. 13

FIGURE 10: GREEN MODE PERFORMANCE MONITORING ............................................................. 14

PolyView™

N6.6.1 Release Notes vi

List of Tables TABLE 1: RADIO CHANNELS PM REPORT ..................................................................................... 6

TABLE 2: FLOATING IP ADMINISTRATIVE STATE CHANGE TRAPS AND ALARMS ............................... 8

TABLE 3: NEW PARAMETERS FOR SERVER REDUNDANCY ........................................................... 11

-- Company Confidential --

PolyView™

N6.6.1 Release Notes Page 1

1 PolyView - NMS for Wireless Backhaul Networks

PolyView™ is Ceragon‟s innovative, user-friendly Network Management System (NMS) designed for

managing large scale wireless backhaul networks. Built on a powerful platform that offers users a

comprehensive set of management functions at the network level PolyView provides enhanced system

functionality and comprehensive network management.

Optimized for centralized operation and maintenance of a complete network, PolyView provides network

operators and service providers with straightforward remote access to all NMS functions. PolyView‟s powerful

and intuitive graphical interface enables users to easily manage and maintain the network, including

functionality for managing faults, performance, end-to-end configuration, and system security.

PolyView provides an easy to comprehend and easy-to-use network view with unique, up-to-date NMS features

presented in a user-friendly GUI. It provides a range of system functionalities, including an easy auto-discovery

feature, intuitive configuration procedure, daily maintenance with advanced report interface, software download

capabilities, and simple methods to investigate system faults.

PolyView supports Ceragon FibeAir products such as the FibeAir IP-10 family and FibeAir 1500R. It

complements Ceragon‟s Element Management System (EMS) by providing management support at the network

level. PolyView‟s unique user interface, CeraMap™, enables fast and easy design of multi-layered network

element maps, and helps manage the network from the initial deployment stage through ongoing maintenance

and configuration procedures.

1.1 PolyView and CeraMap Main Features

User-friendly interface used to build graphic element network, manage element configuration, and

perform maintenance functions

Enables fast and easy hierarchical multi-layered network map design

Supports multiple maps, groups, and links

Extensive reporting capabilities

Enables saving/loading of configuration data (automatically)

Supports inter-element graphical connection

Supports active graphic element status indication

Supports global configuration changes through top-level elements

Database information can be exported for use in other applications (backup)

Supports top-most severity display and current alarms in near real-time (with alarm synchronization)

Alarm log is maintained in the database for up to one year.

Supports near real-time current alarm list and alarm log (with alarm synchronization)

Supports alarm triggers

Software download to multiple elements, with optional delayed download and network element (NE)

restart

User-selected background maps

Support for active and hot standby servers

Automation of tasks using CLI (Command Line Interface)

Trap forwarding service

Integrates with other NMS platforms (such as NSN NetAct)


PolyView™


HTTP/S proxy servers

Trail configuration and management

Configuration Broadcast (trap configuration, NTP, thresholds, security and more)

Multilinks between NEs (2+0, 3+0 …)

Large number of NMS clients


PolyView™


2 Components

The PolyView NMS system consists of the following main components:

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

PolyView database - a centralized internal MySQL database

NMS pluggable API Interface - the connection between PolyView and the NMS it is integrating

PolyView applications

CeraMap application - Ceragon‟s NMS GUI

Optional components:

o End to end trail management

o NSN's NetAct ESYMAC interface

o Redundancy support

The following illustration shows the PolyView system and how it integrates with other NMS platforms and the

network.

Figure 1: PolyView System Network Integration


PolyView™


3 New Features

3.1 IP-10 Support

PolyView now offers support of the following IP-10 software versions,

Full support of:

o IP-10G I6.6.1 SW release (I6.6.1.0.0.60)

o IP-10 I6.3 SW release (2.9.6)

Partial support of :

o IP-10G I6.6.2 (I6.6.2.0.0.22)

3.2 MySQL Database Upgrade

MySQL has declared that MySQL database version 4.1.7 is now obsolete. This is the version which was previously used by PolyView.

In PolyView version N6.6.1.0.0 Ceragon introduces the use of MySQL database Enterprise Server v5.1, the

most updated MySQL database version. With the new MySQL database version, PolyView version N6.6.1.0.0

introduces the use of the “InnoDB” storage engine. This storage engine will enable PolyView to achieve better

performance, scalability, and data integrity.

The use of the “InnoDB” storage engine also enables PolyView to use hibernate for data persistency purposes.

Hibernate is the de-facto industry standard ORM (Object Relational Mapping) tool for Java application data

persistency.

PolyView version N6.6.1 also contains the installer of the new MySQL DB version.

For the detailed upgrade procedures and information, refer to PolyView Upgrade Procedure to N6.6.1.


PolyView™


3.3 Licensing Report

License report structure was changed, licenses are no longer in columns and instead are in differnet rows per

licensed feature. Additional support was added to the IP-10G NE (I6.6.1) for the following licenses:

Sync Unit (SyncU)

Resiliency

TDM License

In addition, Polyview now supports the ability to show the usage of each licensed feature.

License model column was added and displays the marketing name for that license.

Figure 2: License Model Columns


PolyView™


3.4 Radio Channel PMs

Radio Channel PMs (Performance Monitors) were added to the PM radio report.

PolyView creates a new sub-node under „Slot‟ under „Radio-1‟ (for IP-10G only) called Radio channels.

Per channel (1 up to Max number of channels) - the PolyView presents one PM “Channel UAS” PM +

“integrity” column (two columns per radio channel).

The value in seconds is: 0 - 900 (per 15 minutes).

Radio channel UAS PM is added to the CLI reports (Radio report)

Table 1: Radio Channels PM Report


PolyView™


3.5 IP-10G - Floating IP Support

The Floating IP is an additional IP address that is added to an NE configured with 1+1 HSB (hot-standby). The

NE has three IP addresses as follows: two addresses - one IP for each unit (slot) and another floating IP that is

for the current active unit.

PV supports IP-10G with configured Floating IP (to be used in case of 1+1 slot protection).

The NE is discovered via its Floating IP using either Auto Discovery process, or by manually adding the

NE

Protection report is updated (first column is the Floating IP column)

All communication with the NE is via the Floating IP

NOTE: Floating IP configuration requires discover node process for that NE. An alarm is sent if the

discover node process was not performed.

Figure 3: Floating IP Report

3.5.1 Auto-discovery

An NE may be found by one of its three IP addresses. PolyView is able to identify that all of these IP addresses

refer to the same NE (one icon).

NOTE: IP-10G standalone does not support Floating IP.

3.5.2 Adding an NE

Manually adding an NE can be done while adding one of the IPs supported by the NE (3 options including the

Floating IP). PolyView does not support configuring or changing the IP in the NE, only discovering it is

supported.

3.5.3 Inventory Reports

In all inventory reports the Floating IP will be the main IP address of the NE (the IP address column).

3.5.4 Floating IP Administrative State Change

NOTE: After changing the configuration of the Floating IP administrative state parameter

(enable/disable) at the NE, the user must perform Discover Node on this NE in PolyView.

If the user did not perform Discover Node on the NE in PolyView after changing the Floating IP admin state in

the NE, an alarm is raised (Floating IP added, severity Minor).

The alarm should be cleared after the performance of the Discover Node on the NE in PolyView.


PolyView™


Table 2: Floating IP Administrative State Change Traps and Alarms

Trap Name Alarm Description Trap Number Severity

nmsFloatingIPAdded Floating IP added 419 Minor

nmsFloatingIpCleared Floating IP cleared 519 Minor

3.5.5 Disabling Floating IP Procedure

To disable Floating IP:

1) Disable Floating IP in the NE. Do not use the floating IP in another NE before discovering the

node.

2) Perform discover node.

NOTE: If the user performs discover node, while the NE is not connected to slot 1, the NE will not be

discovered.

Disabling the Floating IP in the NE, will cause the NE to be unreachable (if discover node was

not done).

If discover node was not done and PolyView polled the inventory, alarm will be raised (as

defined above).

3.5.6 Enable Floating IP Procedure

To enable Floating IP:

1) Enable Floating IP in the NE.

2) Perform discover node.

3.5.7 Deleting an NE

Generally in PolyView, if the user deletes an NE from the map then the NE configuration and history still exist

in the DB. When Floating IP is enabled, if the user adds the NE again with the Floating IP the server will leave

the DB of the “old” NE and build a new DB for the “new” NE. The correct way to delete an NE is to perform

“Discover Node” and not delete the NE from the map.


PolyView™


3.6 Configuration Broadcast – GUI Update

There is a new user interface which enables the user to choose either to broadcast parameters that are similar for

all the NEs, or specific to a kind of NE (IP-10, 1500R/3200T).

The Select drop-down menu was added to the upper left corner of the Configuration Broadcast window with the

following options:

a) General – for parameters that are suitable for all Ceragon‟s products

b) 1500R/3200T/IP-MAX – for parameters for one of these IDUs

c) IP-10 – only for IP-10 specific parameters

Only one option can be selected, if IP-10 was selected, the configuration broadcast is done only for IP-10 NEs.

Figure 4: Updated Configuration Broadcast GUI


PolyView™


3.7 Radio Report – Additional Columns

New columns were added to the Radio Report:

XPIC - XPIC support (NA, Disable or Enable)

State - Admin state (to support radio disable)

Figure 5: Additional Columns Radio Report

3.7.1 PM Report – Additional Columns

There are three new columns for XPIC PM Report: Min XPI, Max XPI and Excessive XPI. These columns are

only supported for IP-10G NE.

Figure 6: Additional Columns XPIC PM Report

3.8 Client Auto Upgrade

In previous version of PolyView, when upgrading the server, the user needed to upgrade the client as well.

Upgrading the client can cause a lot of operational effort when there are several clients on many platforms

spread out in several locations.

This version of PolyView adds the ability to automatically upgrade the client SW via the server when the

specific client first connects to the server. The client must initially be upgraded to the next version, afterwards

this feature is available to the client (the client also needs to update its SW to install this new feature).


PolyView™


3.9 TDM Trail Operational Status Alarm Logging

Trails status alarms were added to the alarm log.

Events are sent for each trail when there is an alarm status change from the IP-10G, and is added to the alarm

log. Trail status changes are sent per trail from the NE.

Figure 7: Alarm Log – TDM Operational Status

3.10 Server Redundancy – Enhancement

In case of redundancy, the PolyView server has added a new ability to switch to the Standby server if the Main

server crosses a pre-configured threshold of unreachable NE.

3.10.1 Three New Parameters on the Redundancy Tab of the Server

The default setting is that when the Main server does not reach more than 80% of the NEs, the Standby server

will become Active.

The following parameters have been added to the Standby server in the Redundant window.

Table 3: New Parameters for Server Redundancy

Parameter Description Value Default Configurable

Auto-activate the

Standby server.

Configures an Admin state

where the Main server

activates the Standby server if

the threshold of an unreachable

NE was crossed.

NOTE: The Main server and

the Standby server will

be active.

Enable,

Disable Disable In Standby only


PolyView™


Parameter Description Value Default Configurable

Main server

management

threshold (of

unreachable NE)

When the threshold of an

unreachable NE in the Main

server is crossed, the Standby

server performs a force switch

to Active state only if the

Standby server management

threshold is not crossed (below

the threshold).

NOTE: The Main server and

the Standby server are

active.

For example (assuming a

default configuration): if the

Main server has 82% of the

unreachable NE, while the

Standby server has 49% of the

unreachable NE, then the

Standby server is Active.

(0-100) in

percentage 80 In Standby only

Standby server

management

threshold (of

unreachable NE)

When the threshold of an

unreachable NE in the

Standby server is crossed, the

Standby server performs a

force switch to Mute state only

if the Main server management

threshold is not crossed (below

the threshold) - and vice versa.

For example (assuming default

configuration): if the Main

server has 78% of the

unreachable NE, while the

Standby server has 52% of the

unreachable NE - then the

Standby server is Mute.

(0-100) in

percentage 50 In Standby only.

The following message is presented to the client when the Standby server is automatically activated:

Figure 8: Standby Server Switching Message

NOTE: The Main server and the Standby server are active.

1) The Standby server performs the decision to become active, if main threshold above the limit (i.e.

80%) and Standby threshold is below the limit (i.e. 50%). When the Standby server becomes

Active, it informs the Main server.


PolyView™


2) When the Standby server becomes active the following occurs:

a. Active Client on the Main server receives a message, as shown in Figure 8.

b. New clients on the Main server also receive this message, if the Standby server is active.

c. Alarms are raised in the both the Main and Standby servers - refer to alarm list (417, 517).

The Standby server only returns to the Mute state when the number of NEs is the same in both Main and

Standby.

Figure 9: Enabling Auto-Activate for the Standby Server


PolyView™


3.11 Radio PM – Time in Green Mode

A critical design issue is the need to efficiently reduce power consumption and thereby increase the operational

lifetime of the network, while cutting operational expenditure. Ceragon‟s Green Mode RFU-HP offers

automatic control of both the power consumption as well as the transmission power. This mode ensures that no

excess energy is used while the network operates in “steady state”. Under fading conditions the power is

automatically increased to compensate for signal loss and to ensure that the link continues to meet the required

performance level.

Green mode is only supported on the RFU-HP ODU

Green mode is supported for IP-10G

A new PM was added to count the percentage of NE usage which is “green” time. PolyView is able to count and

present green mode levels from TSL threshold PM (values 0-900 seconds).

PolyView calculates the seconds (per NE) that the NE was in green mode and displays the percentage (table

view). It is added to the PM report for Radio Interface (in a new column). The new column is called Green %

and an NE that does not support green mode has the value 0 in the entry.

This PM column is hidden by default.

Figure 10: Green Mode Performance Monitoring


PolyView™


3.12 New RFU Support – RFU-HP

RFU-HP is now supported by PolyView, including SW download and retrieving RFU inventory.

3.13 Radio Disable Support for IP-10G

In order to support the radio disable feature for IP-10G, an additional column is added to the Radio report.

NOTE: Changing the radio from disable to enable, requires performing a “Discover Node” action on

the NE.


PolyView™


4 Resolved Issues

Class ID Description Comment

Configuration

Broadcast

22995 Configuration Broadcast configures

traps and General tabs simultaneously.

The process will succeed but an error

message appears, "x.x.x.x:

Configuration failed - Unknown error"

24475 Configuration Broadcast log -

sometimes a message of "failed"

appears although the operation

succeeded.

3rd

Party 25056 Sagem ADR2500, ADR155 – the PV

imports the alarm log instead of the

current alarm table

TDM Trails 26130 There are no PMs on STM-1 links in

the first 24 hours.

(STM-1 T-card was inserted to the

device, and therefore in the first 24

hours the number of PM intervals from

the STM-1 is less than 96, while the

number of PM intervals from E1s is 96.

This causes an incorrect behavior in

PolyView when parsing the time stamp

of each interval.)

26873 In Add New Trail, there are slots that

may not display after network

auto-discovery

SW Download 30166 Try to perform SWD on any element

type (1500R/IP10/IP10G etc...). The

SWD process becomes stuck in

"waiting" status and does not continue

Inventory Report 26108 Neighbor report – configuring column

manually produces inconsistent

behavior

FTP 19859 Filezilla is not configured for PV

servers (only on Vista and Windows

2008 server)

23474 HighCap system does not configure the

Filezilla to the correct FTP path

Protection 27350 In case of protected IP-10G slots, when

the main slot is Down (no power), it is

impossible to perform all the actions on

the standby slot

User

Management

28979 Defined users could not add or remove

NEs

Trap

Notifications

28876 Sending a cleared trap with zero

severity option does not work

PM Reports 27915 Two rows of the same day appear in the

PM report

24805 Applied filters only filter on the first

slot


PolyView™



PV Languages 29897 PV does not support UMLAUT -

German, Swedish, and Hungarian

languages

PM History 29397 PV server keeps history for longer than

configured

PV Restart 30844 PV restarts due to DBCheck process

Discovery 30960 1500R Quad support


PolyView™


5 Open Issues


Configuration

Broadcast

24332 In 1500P, not all thresholds are

configured via Configuration Broadcast

(STM-1, radio)

Workaround –

Configure threshold

manually

28951 Configuration Broadcast does not apply

on 3200T

Discovery 15951 When pressing abort during

auto-discovery (of large amount of

NEs) - the process always aborts at the

same point

Workaround –

Restart PV server

30525 When adding Floating IP to IP-10G and

performing discover node, the links

disappear

Add links manually

23093 When receiving a trap from unknown

NE, the PV may not add it

automatically to the map, when the flag

is enabled, (Trap FW Options >

Advance > Auto Add NE > Enable)

Workaround – The NE

can be added manually

to the map

29613 Discover node has no effect on ADM

Trail mechanism

31836 Discover FA4800 with no active alarms

as unreachable and not colored in

green.

Work around :

(1) Alarm could be

hidden manually from

the PV.

(2) After new alarm

raising in FA4800, it

update the NE color in

PV

Client

Auto-upgrade

27241 When the server and the client are

installed on Solaris, the client

auto-upgrade feature does not work

Manually install the

new version of the

client on Solaris

PV Installation 16301 Installer installs wrong Desktop icons

for Solaris 10 (both CDE and Java

Desktop)

Workaround – Add the

icons manually

TDM Trails 24579 PolyView does not support dual

homing with the second endpoint pass

via port of NE that has the first

endpoint

SW Download 25589 PolyView performs SW upgrade on a

unit and may mark it as cancelled even

though the SW upgrades succeed

24981/

25591/

26346/

26004

29725

SW download can be falsely reported

as successful


PolyView™



Security - Radius 24897 When Radius is enabled with more than

one user (PolyView client) – the

second user cannot access the server

even though it was accepted by Radius

server

Workaround – Restart

PV server

Multilink (2+0) 26272 Protected trails on 2+0 links are only

partially supported (only on one 2+0

link)

Alarm Log 30936 When enabling protection between

slots of IP-10G, the same IP address is

used for Active and for Standby slots in

protection switch event

Reports 30832 When the "System Contact" is larger

than 64 characters there is no "Network

element” report

System contact should

be less than 64

characters

Topology 30562 When importing a topology, changed

NE locations are not saved

Redundancy 29930 80/20 redundancy feature. The Main

server does not send a raised trap of

percentage of unreachable elements and

indicate that the Main server is over

threshold

Alarms 24932

No current alarms are shown in

aggregated link (2 radio links between

2 NEs) on IP-10G

SNMP 29132 When inserting a name with multiple

spaces from PolyView to IP-10 the

second space and on are replaced with

"+"

For example:

Inserted name: “Link From A to B”

Final name: “Link From+A+to+B”

Work around:

1. Insert the name from

the web

or

2. Use User Defined

Name

Interface Report 28956 IP-10 NE shows the Admin state of the

WS port, while 1500R NE shows the

connector type

Current Alarm

Table

30150

Some events may be displayed in the

current alarm table in large networks

for a couple of hours and then

eventually disappear

User definition 31796 Admin user that was defined in a

specific subnet group cannot perform

all processes according to his

permissions.

Work around – define

admin users in specific

subnet groups, but with

permissions to all the

network.


PolyView™


6 Known Issues


Discovery 25766 Rarely, after auto discovery,

non-existent links appear in the map

Workaround – delete

those links

24520 Changing NE interfaces (for example

adding or removing daughter-board) -

cannot be retrieved via poll node.

Requires discover node

29717 FibeAir 3200T links may not be

discovered correctly via auto-discovery

process

Workarounds:

(1) Configured the

management slots as

neighbors (in the

middle floor)

(2) Perform discover

node

PV Server 14067 On rare occasions, in Unix, there is a

problem with opening CeraMap after

pvstart, through the open window. It is

possible to open it from an icon on the

desktop or other means, but through the

window that is already open, CeraMap

refuses to open

3625 There are situations when the icon

disappear from the system tray

(Windows only)

Other 24639 Performing “single sign on” on NE

from CeraMap, on Internet Explorer

(windows) may close the PV client,

only if it was done after server restart.

The bug is a known JAVA bug: Bug

ID: 6457572.

http://bugs.sun.com/bugdatabase/view_

bug.do?bug_id=6457572

Workaround – Re-open

the client

ADM Trail

Management

4070 In ADM Trail Management (1500AL,

1500A product line), the E1 loopback

dialog opens and is empty

Workaround –

Re-open the window

3rd

Party 24451 BG20/30 (ECI) – Changing alarm

severity in the EMS of the BG doesn‟t

reflect in PV

Workaround - Perform

discover node after

changing the severity of

the alarm in the EMS of

the BG.

24479 Sagem linkF – Current alarm cannot be

read

24536 Nokia FIU-19E, traps not recognized in

PV (SNMP V2c)

CeraMap 4132 Sometimes, when clicking the refresh

button, the user cannot close the

"Refreshing…" dialog

Workaround –

Re-open CeraMap

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6457572

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6457572


PolyView™



User

Management

17786 Empty user groups are not restored

after export/import.

Workaround –

Whenever one need to

copy security privileges

from one server to

another, copy security

file (nms.sec) directly.

It is located under

config directory.

MySQL DB NA Any manual configuration of MySQL

database may harm PolyView

functionality.

Alarms 31833 In FA4800, alarm that are raise from a

one side of the link, is being sent from

both sides FA4800, the PV in this case

will present two alarms.

Workaround, Poll node

from PV, solve the

problem.


PolyView™


7 Supported Network Elements

7.1 IP-10

Marketing

Version SW Version Remarks

I6.0 1.4.5.2 Upgrade only.

I6.1.1 2.7.12

I6.2 2.8.25

I6.2.5 2.8.32

I6.2.6 2.8.33.0

I6.3 2.9.6

7.2 IP-10G

Marketing

Version SW Version Remarks

I6.5ca1 3.0.97 Upgrade only

I6.5ca1 3.0.99 Upgrade only

I6.6ca1 6.6.0.0.1.40

I6.6ca1 6.6.0.0.1.41

I6.6ga 6.6.0.0.2.53

I6.6.1 6.6.1.0.0.60

I6.6.2 6.6.2.0.0.22

7.3 FibeAir 1500 Family

Product Marketing

Version SW Version

1500

1528

1500A I5.28

1500AL I-528f

1528A

1500P (I5, S5,

G5) 4.95 4.95s19

1500P (I5, S5,

G5) 5.10 5.10n1

1500R S6.0 SFD_6.00c3.sfd

1500R S6.5 SFD_6.50e2.sfd

1500R S6.6 SFD_6.60c3.sfd

3200T T5.0 SFD_5.00a71a

640P


PolyView™


7.4 FibeAir 2000/4800 family

Product Marketing

Version SW Version

FA2000 2.4 2.4

FA4800 1.9.30 1.9.30

7.5 3rd Party Supported Elements

Manufacturer Product SW Version Notes

ECI BG-20B V10.1.10B

ECI BG-30B V10.1.10B

NSN FIU-19E

Sagem ADR-155 252476907AC-lo

Sagem ADR-2500 P 2.4.9

Sagem Link-F 25152321512 Requires embedded Sagem

SW version 035 or higher


PolyView™


8 Supported Operating Systems

Server & Client OS support

o Windows - 2000/2003(32 & 64 bit)/XP/2008(32 bit)

o UNIX - Solaris 10, Sun SPARC servers

Client only support

o Windows 7/XP/Vista

polyview release notes - n6.6.1

Documents