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 CeraMap , ConfigAir , PolyView , EncryptAir trademarks of Ceragon Networks Ltd. TM TM TM TM, CeraMon , EtherAir , and MicroWave Fiber , are TM TM TM 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] 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 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 Contents 1 2 3 PolyView - NMS for Wireless Backhaul Networks ........................................................... 1 1.1 PolyView and CeraMap Main Features................................................................... 1 Components.................................................................................................................... 3 New Features .................................................................................................................. 4 3.1 3.2 3.3 3.4 3.5 IP-10 Support ......................................................................................................... 4 MySQL Database Upgrade..................................................................................... 4 Licensing Report .................................................................................................... 5 Radio Channel PMs................................................................................................ 6 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 3.7 3.8 3.9 Configuration Broadcast – GUI Update................................................................... 9 Radio Report – Additional Columns ...................................................................... 10 3.7.1 PM Report – Additional Columns ................................................................. 10 Client Auto Upgrade ............................................................................................. 10 TDM Trail Operational Status Alarm Logging........................................................ 11 3.10.1Three 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 5 6 7 Resolved Issues ............................................................................................................ 16 Open Issues .................................................................................................................. 18 Known Issues ................................................................................................................ 20 Supported Network Elements ........................................................................................ 22 7.1 IP-10 .................................................................................................................... 22 ™ 3.10 Server Redundancy – Enhancement .................................................................... 11 PolyView N6.6.1 Release Notes iii ..................... 22 FibeAir 1500 Family.................................... 23 3rd Party Supported Elements ....6...................4 7..........................5 8 IP-10G ........................................................................ 24 PolyView N6.............................................................7................. 22 FibeAir 2000/4800 family ..........................................1 Release Notes ™ iv .................... 23 Supported Operating Systems ..................................................3 7..................2 7................................................................................ .........................................................................................................................................1 Release Notes ™ v .............................. 10 FIGURE 6: ADDITIONAL COLUMNS XPIC PM REPORT............................................7 FIGURE 4: UPDATED CONFIGURATION BROADCAST GUI .................................................................. 13 FIGURE 10: GREEN MODE PERFORMANCE MONITORING ...........................................................................................................................................................6............................................................................................................ 14 PolyView N6.... 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 ..............3 FIGURE 2: LICENSE MODEL COLUMNS .............................5 FIGURE 3: FLOATING IP REPORT .............9 FIGURE 5: ADDITIONAL COLUMNS RADIO REPORT ..........................List of Figures FIGURE 1: POLYVIEW SYSTEM NETWORK INTEGRATION ..... ....List of Tables TABLE 1: RADIO CHANNELS PM REPORT ............................................................... 11 PolyView N6........................6..........1 Release Notes ™ vi ......................................................6 TABLE 2: FLOATING IP ADMINISTRATIVE STATE CHANGE TRAPS AND ALARMS .................8 TABLE 3: NEW PARAMETERS FOR SERVER REDUNDANCY ...... 6.-. CeraMap™. and helps manage the network from the initial deployment stage through ongoing maintenance and configuration procedures. up-to-date NMS features presented in a user-friendly GUI. Supports near real-time current alarm list and alarm log (with alarm synchronization) Supports alarm triggers Software download to multiple elements. and system security. software download capabilities.NMS for Wireless Backhaul Networks PolyView™ is Ceragon‟s innovative. PolyView provides network operators and service providers with straightforward remote access to all NMS functions. end-to-end configuration. PolyView provides an easy to comprehend and easy-to-use network view with unique. PolyView‟s unique user interface. It provides a range of system functionalities. PolyView supports Ceragon FibeAir products such as the FibeAir IP-10 family and FibeAir 1500R. 1. Optimized for centralized operation and maintenance of a complete network. It complements Ceragon‟s Element Management System (EMS) by providing management support at the network level. 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 N6. 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. and simple methods to investigate system faults. 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. user-friendly Network Management System (NMS) designed for managing large scale wireless backhaul networks.1 Release Notes ™ Page 1 . performance. groups. including functionality for managing faults. daily maintenance with advanced report interface. enables fast and easy design of multi-layered network element maps. and perform maintenance functions Enables fast and easy hierarchical multi-layered network map design Supports multiple maps.1 PolyView and CeraMap Main Features User-friendly interface used to build graphic element network.Company Confidential -- 1 PolyView . including an easy auto-discovery feature. PolyView‟s powerful and intuitive graphical interface enables users to easily manage and maintain the network. manage element configuration. intuitive configuration procedure. NTP. 3+0 …) Large number of NMS clients PolyView N6.6. security and more) Multilinks between NEs (2+0. thresholds.-.1 Release Notes ™ Page 2 .Company Confidential -- HTTP/S proxy servers Trail configuration and management Configuration Broadcast (trap configuration. 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 N6.the foundation on which all PolyView applications and services run PolyView database .1 Release Notes ™ Page 3 .Company Confidential -- 2 Components The PolyView NMS system consists of the following main components: PolyView framework .6.-.the connection between PolyView and the NMS it is integrating PolyView applications CeraMap application .a centralized internal MySQL database NMS pluggable API Interface . 0. the most updated MySQL database version.1.6. PolyView version N6. refer to PolyView Upgrade Procedure to N6. The use of the “InnoDB” storage engine also enables PolyView to use hibernate for data persistency purposes.6. PolyView N6.3 SW release (2. With the new MySQL database version.1. This is the version which was previously used by PolyView.6. PolyView version N6.6.1 SW release (I6.1.2 (I6. In PolyView version N6.2.0.1.1.0 introduces the use of the “InnoDB” storage engine.0.-.6. scalability. Full support of: o IP-10G I6.9. Hibernate is the de-facto industry standard ORM (Object Relational Mapping) tool for Java application data persistency.0 Ceragon introduces the use of MySQL database Enterprise Server v5.6.0.7 is now obsolete. For the detailed upgrade procedures and information.0. This storage engine will enable PolyView to achieve better performance.1 also contains the installer of the new MySQL DB version.22) 3.1 Release Notes ™ Page 4 .1 IP-10 Support PolyView now offers support of the following IP-10 software versions.6) Partial support of : o IP-10G I6.6.6.6. and data integrity.0.2 MySQL Database Upgrade MySQL has declared that MySQL database version 4.60) o IP-10 I6.1.Company Confidential -- 3 New Features 3. 6.-. Figure 2: License Model Columns PolyView N6. licenses are no longer in columns and instead are in differnet rows per licensed feature.6. License model column was added and displays the marketing name for that license.1 Release Notes ™ Page 5 .Company Confidential -- 3. Additional support was added to the IP-10G NE (I6.3 Licensing Report License report structure was changed. Polyview now supports the ability to show the usage of each licensed feature.1) for the following licenses: Sync Unit (SyncU) Resiliency TDM License In addition. 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) .4 Radio Channel PMs Radio Channel PMs (Performance Monitors) were added to the PM radio report.6.-.the PolyView presents one PM “Channel UAS” PM + “integrity” column (two columns per radio channel).900 (per 15 minutes). The value in seconds is: 0 . Radio channel UAS PM is added to the CLI reports (Radio report) Table 1: Radio Channels PM Report PolyView N6.1 Release Notes ™ Page 6 .Company Confidential -- 3. Company Confidential -- 3. the user must perform Discover Node on this NE in PolyView. 3.5. only discovering it is supported. PolyView is able to identify that all of these IP addresses refer to the same NE (one icon).5 IP-10G . The NE has three IP addresses as follows: two addresses . PolyView N6. PolyView does not support configuring or changing the IP in the NE. NOTE: IP-10G standalone does not support Floating IP.5. 3.3 Inventory Reports In all inventory reports the Floating IP will be the main IP address of the NE (the IP address column). If the user did not perform Discover Node on the NE in PolyView after changing the Floating IP admin state in the NE. 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. severity Minor). 3. PV supports IP-10G with configured Floating IP (to be used in case of 1+1 slot protection).Floating IP Support The Floating IP is an additional IP address that is added to an NE configured with 1+1 HSB (hot-standby). An alarm is sent if the discover node process was not performed.5.one IP for each unit (slot) and another floating IP that is for the current active unit. The alarm should be cleared after the performance of the Discover Node on the NE in PolyView. an alarm is raised (Floating IP added.6.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).1 Auto-discovery An NE may be found by one of its three IP addresses.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 NE is discovered via its Floating IP using either Auto Discovery process.1 Release Notes ™ Page 7 . Figure 3: Floating IP Report 3. 3. will cause the NE to be unreachable (if discover node was not done). the NE will not be discovered. if the user deletes an NE from the map then the NE configuration and history still exist in the DB. 2) Perform discover node. Disabling the Floating IP in the NE. 2) Perform discover node.-. 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.5 Disabling Floating IP Procedure To disable Floating IP: 1) Disable Floating IP in the NE. while the NE is not connected to slot 1. 3. Do not use the floating IP in another NE before discovering the node.5.6.1 Release Notes ™ Page 8 .5.Company Confidential -- Table 2: Floating IP Administrative State Change Traps and Alarms Trap Name nmsFloatingIPAdded nmsFloatingIpCleared Alarm Description Floating IP added Floating IP cleared Trap Number 419 519 Severity Minor Minor 3.5.6 Enable Floating IP Procedure To enable Floating IP: 1) Enable Floating IP in the NE. alarm will be raised (as defined above). If discover node was not done and PolyView polled the inventory. When Floating IP is enabled.7 Deleting an NE Generally in PolyView. The correct way to delete an NE is to perform “Discover Node” and not delete the NE from the map. NOTE: If the user performs discover node. PolyView N6. 1 Release Notes ™ Page 9 .6. Figure 4: Updated Configuration Broadcast GUI PolyView N6. if IP-10 was selected.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.Company Confidential -- 3. 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. 1500R/3200T).-. or specific to a kind of NE (IP-10. the configuration broadcast is done only for IP-10 NEs. 1 PM Report – Additional Columns There are three new columns for XPIC PM Report: Min XPI.-.7 Radio Report – Additional Columns New columns were added to the Radio Report: XPIC .Admin state (to support radio disable) Figure 5: Additional Columns Radio Report 3.7. when upgrading the server. Disable or Enable) State . These columns are only supported for IP-10G NE. Figure 6: Additional Columns XPIC PM Report 3. afterwards this feature is available to the client (the client also needs to update its SW to install this new feature). The client must initially be upgraded to the next version. 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. Max XPI and Excessive XPI.XPIC support (NA.Company Confidential -- 3. PolyView N6. Upgrading the client can cause a lot of operational effort when there are several clients on many platforms spread out in several locations.8 Client Auto Upgrade In previous version of PolyView.1 Release Notes ™ Page 10 .6. the user needed to upgrade the client as well. The following parameters have been added to the Standby server in the Redundant window. Value Default Configurable Auto-activate the Standby server.9 TDM Trail Operational Status Alarm Logging Trails status alarms were added to the alarm log.10 Server Redundancy – Enhancement In case of redundancy. NOTE: The Main server and the Standby server will be active. Trail status changes are sent per trail from the NE. Disable Disable In Standby only PolyView N6. and is added to the alarm log.Company Confidential -- 3. the Standby server will become Active. Enable.10.6. 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.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. Events are sent for each trail when there is an alarm status change from the IP-10G.-. Table 3: New Parameters for Server Redundancy Parameter Description Configures an Admin state where the Main server activates the Standby server if the threshold of an unreachable NE was crossed. Figure 7: Alarm Log – TDM Operational Status 3. 3.1 Release Notes ™ Page 11 . Value Default Configurable Main server management threshold (of unreachable NE) (0-100) in percentage 80 In Standby only Standby server management threshold (of unreachable NE) (0-100) in percentage 50 In Standby only.Company Confidential -- Parameter Description When the threshold of an unreachable NE in the Main server is crossed.and vice versa.6. 80%) and Standby threshold is below the limit (i.e. 1) The Standby server performs the decision to become active. while the Standby server has 49% of the unreachable NE.-. When the threshold of an unreachable NE in the Standby server is crossed.then the Standby server is Mute. the Standby server performs a force switch to Mute state only if the Main server management threshold is not crossed (below the threshold) . it informs the Main server.e. NOTE: The Main server and the Standby server are active.1 Release Notes ™ Page 12 . 50%). For example (assuming default configuration): if the Main server has 78% of the unreachable NE. if main threshold above the limit (i. while the Standby server has 52% of the unreachable NE . PolyView N6. 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. When the Standby server becomes Active. the Standby server performs a force switch to Active state only if the Standby server management threshold is not crossed (below the threshold). For example (assuming a default configuration): if the Main server has 82% of the unreachable NE. then the Standby server is Active. as shown in Figure 8.1 Release Notes ™ Page 13 .refer to alarm list (417.6. New clients on the Main server also receive this message. b. 517). Figure 9: Enabling Auto-Activate for the Standby Server PolyView N6. Active Client on the Main server receives a message.-.Company Confidential -- 2) When the Standby server becomes active the following occurs: a. c. Alarms are raised in the both the Main and Standby servers . if the Standby server is active. The Standby server only returns to the Mute state when the number of NEs is the same in both Main and Standby. 1 Release Notes ™ Page 14 . 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). while cutting operational expenditure.6.Company Confidential -- 3. Figure 10: Green Mode Performance Monitoring PolyView N6. This PM column is hidden by default.-. 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. PolyView is able to count and present green mode levels from TSL threshold PM (values 0-900 seconds). Ceragon‟s Green Mode RFU-HP offers automatic control of both the power consumption as well as the transmission power.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. The new column is called Green % and an NE that does not support green mode has the value 0 in the entry. This mode ensures that no excess energy is used while the network operates in “steady state”. 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. 12 New RFU Support – RFU-HP RFU-HP is now supported by PolyView. 3. NOTE: Changing the radio from disable to enable. requires performing a “Discover Node” action on the NE.-. including SW download and retrieving RFU inventory.6.Company Confidential -- 3. an additional column is added to the Radio report.1 Release Notes ™ Page 15 .13 Radio Disable Support for IP-10G In order to support the radio disable feature for IP-10G. PolyView N6. there are slots that may not display after network auto-discovery Try to perform SWD on any element type (1500R/IP10/IP10G etc. and therefore in the first 24 hours the number of PM intervals from the STM-1 is less than 96.1 Release Notes ™ Page 16 .x: Configuration failed .-.x.) In Add New Trail. while the number of PM intervals from E1s is 96.Company Confidential -- 4 Resolved Issues Class Configuration Broadcast ID 22995 Description Configuration Broadcast configures traps and General tabs simultaneously.x..6. The process will succeed but an error message appears. when the main slot is Down (no power). it is impossible to perform all the actions on the standby slot Defined users could not add or remove NEs Sending a cleared trap with zero severity option does not work Two rows of the same day appear in the PM report Applied filters only filter on the first slot Comment 24475 3rd Party 25056 TDM Trails 26130 26873 SW Download 30166 Inventory Report 26108 FTP 19859 23474 Protection 27350 User Management Trap Notifications PM Reports 28979 28876 27915 24805 PolyView N6. (STM-1 T-card was inserted to the device. "x.).. This causes an incorrect behavior in PolyView when parsing the time stamp of each interval. The SWD process becomes stuck in "waiting" status and does not continue Neighbor report – configuring column manually produces inconsistent behavior Filezilla is not configured for PV servers (only on Vista and Windows 2008 server) HighCap system does not configure the Filezilla to the correct FTP path In case of protected IP-10G slots.Unknown error" Configuration Broadcast log sometimes a message of "failed" appears although the operation succeeded. Sagem ADR2500. ADR155 – the PV imports the alarm log instead of the current alarm table There are no PMs on STM-1 links in the first 24 hours. 1 Release Notes ™ Page 17 .Company Confidential -- Class PV Languages ID 29897 Description PV does not support UMLAUT German. Swedish.6.-. and Hungarian languages PV server keeps history for longer than configured PV restarts due to DBCheck process 1500R Quad support Comment PM History PV Restart Discovery 29397 30844 30960 PolyView N6. Comment Workaround – Configure threshold manually 28951 Discovery 15951 Workaround – Restart PV server 30525 Add links manually 23093 Workaround – The NE can be added manually to the map 29613 31836 Client Auto-upgrade PV Installation 27241 16301 TDM Trails 24579 SW Download 25589 24981/ 25591/ 26346/ 26004 29725 When the server and the client are installed on Solaris.1 Release Notes ™ Page 18 . (2) After new alarm raising in FA4800. when the flag is enabled. radio) Configuration Broadcast does not apply on 3200T When pressing abort during auto-discovery (of large amount of NEs) . the PV may not add it automatically to the map. (Trap FW Options > Advance > Auto Add NE > Enable) Discover node has no effect on ADM Trail mechanism Discover FA4800 with no active alarms as unreachable and not colored in green.Company Confidential -- 5 Open Issues Class Configuration Broadcast ID 24332 Description In 1500P. it update the NE color in PV Manually install the new version of the client on Solaris Workaround – Add the icons manually PolyView N6. the client auto-upgrade feature does not work Installer installs wrong Desktop icons for Solaris 10 (both CDE and Java Desktop) PolyView does not support dual homing with the second endpoint pass via port of NE that has the first endpoint PolyView performs SW upgrade on a unit and may mark it as cancelled even though the SW upgrades succeed SW download can be falsely reported as successful Work around : (1) Alarm could be hidden manually from the PV.-. not all thresholds are configured via Configuration Broadcast (STM-1.6. the links disappear When receiving a trap from unknown NE.the process always aborts at the same point When adding Floating IP to IP-10G and performing discover node. -. Use User Defined Name Interface Report 28956 Current Alarm Table 30150 User definition 31796 Work around – define admin users in specific subnet groups. while 1500R NE shows the connector type Some events may be displayed in the current alarm table in large networks for a couple of hours and then eventually disappear Admin user that was defined in a specific subnet group cannot perform all processes according to his permissions. Comment Workaround – Restart PV server Multilink (2+0) 26272 Alarm Log 30936 Reports 30832 System contact should be less than 64 characters Topology Redundancy 30562 29930 Alarms 24932 SNMP 29132 Work around: 1.Company Confidential -- Class Security .1 Release Notes ™ Page 19 . The Main server does not send a raised trap of percentage of unreachable elements and indicate that the Main server is over threshold No current alarms are shown in aggregated link (2 radio links between 2 NEs) on IP-10G 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” IP-10 NE shows the Admin state of the WS port. PolyView N6. changed NE locations are not saved 80/20 redundancy feature. Insert the name from the web or 2.Radius ID 24897 Description 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 Protected trails on 2+0 links are only partially supported (only on one 2+0 link) When enabling protection between slots of IP-10G. but with permissions to all the network.6. the same IP address is used for Active and for Standby slots in protection switch event When the "System Contact" is larger than 64 characters there is no "Network element” report When importing a topology. on Internet Explorer (windows) may close the PV client. through the open window.Company Confidential -- 6 Known Issues Class Discovery ID 25766 24520 Description Rarely. there is a problem with opening CeraMap after pvstart. the E1 loopback dialog opens and is empty BG20/30 (ECI) – Changing alarm severity in the EMS of the BG doesn‟t reflect in PV Workaround – Re-open the client ADM Trail Management 3rd Party 4070 Workaround – Re-open the window Workaround . but through the window that is already open. after auto discovery.6.do?bug_id=6457572 In ADM Trail Management (1500AL. It is possible to open it from an icon on the desktop or other means. http://bugs.Perform discover node after changing the severity of the alarm in the EMS of the BG. when clicking the refresh button.com/bugdatabase/view_ bug. 1500A product line). traps not recognized in PV (SNMP V2c) Sometimes. only if it was done after server restart.sun.-.1 Release Notes ™ Page 20 . the user cannot close the "Refreshing…" dialog Workaround – Re-open CeraMap PolyView N6. in Unix. CeraMap refuses to open There are situations when the icon disappear from the system tray (Windows only) Performing “single sign on” on NE from CeraMap. FibeAir 3200T links may not be discovered correctly via auto-discovery process Comment Workaround – delete those links Requires discover node 29717 Workarounds: (1) Configured the management slots as neighbors (in the middle floor) (2) Perform discover node PV Server 14067 3625 Other 24639 On rare occasions. 24451 24479 24536 CeraMap 4132 Sagem linkF – Current alarm cannot be read Nokia FIU-19E. The bug is a known JAVA bug: Bug ID: 6457572. non-existent links appear in the map Changing NE interfaces (for example adding or removing daughter-board) cannot be retrieved via poll node. the PV in this case will present two alarms.1 Release Notes ™ Page 21 .sec) directly. PolyView N6. alarm that are raise from a one side of the link.-. solve the problem. MySQL DB NA Alarms 31833 Any manual configuration of MySQL database may harm PolyView functionality.Company Confidential -- Class User Management ID 17786 Description Empty user groups are not restored after export/import. is being sent from both sides FA4800. Workaround. Comment Workaround – Whenever one need to copy security privileges from one server to another. It is located under config directory. In FA4800.6. Poll node from PV. copy security file (nms. 1.0.5ca1 I6.33.2 2.00c3.50e2.0.32 2.2. S5.6ga I6.6 T5.0.41 6.10 S6.5.95 5.sfd SFD_5.2.12 2.-.0 4.40 6.1.0 S6.6ca1 I6.6. 7.6ca1 I6.0.0.6.2 SW Version 3.6.2 IP-10G Marketing Version I6.5ca1 I6.00a71a PolyView N6.5 I6.0.8.0 I6.4.0 2.0.99 6.0.6.1 I6.10n1 SFD_6.0.sfd SFD_6.6.1 I6.8. G5) 1500R 1500R 1500R 3200T 640P Marketing Version SW Version I5.28 I-528f 4.60 6.6.6 I6.53 6.2 I6.97 3.0.1.Company Confidential -- 7 Supported Network Elements 7.3 FibeAir 1500 Family Product 1500 1528 1500A 1500AL 1528A 1500P (I5.2.0.60c3.3 SW Version 1.6 Remarks Upgrade only.9.1.22 Remarks Upgrade only Upgrade only 7.5 S6.95s19 5.1 IP-10 Marketing Version I6.6. G5) 1500P (I5.8.7.sfd SFD_6.6.1 Release Notes ™ Page 22 .0. S5.25 2.2. 4.9.4 1.-.1.1 Release Notes ™ Page 23 .9 25152321512 Requires embedded Sagem SW version 035 or higher Notes PolyView N6.5 3rd Party Supported Elements Manufacturer ECI ECI NSN Sagem Sagem Sagem Product BG-20B BG-30B FIU-19E ADR-155 ADR-2500 Link-F SW Version V10.30 SW Version 2.4 FibeAir 2000/4800 family Product FA2000 FA4800 Marketing Version 2.4 1.10B V10.30 7.1.9.10B 252476907AC-lo P 2.6.Company Confidential -- 7. 2000/2003(32 & 64 bit)/XP/2008(32 bit) o UNIX .Solaris 10.-.6. Sun SPARC servers Client only support o Windows 7/XP/Vista PolyView N6.Company Confidential -- 8 Supported Operating Systems Server & Client OS support o Windows .1 Release Notes ™ Page 24 .