Documente Academic
Documente Profesional
Documente Cultură
1129
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,
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 users 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: info@ceragon.com
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: infoeuro@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
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: infous@ceragon.com
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
iii
IP-10G .................................................................................................................. 22 FibeAir 1500 Family.............................................................................................. 22 FibeAir 2000/4800 family ...................................................................................... 23 3rd Party Supported Elements ............................................................................... 23
iv
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
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
vi
-- Company Confidential --
Page 1
-- Company Confidential --
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
Page 2
-- Company Confidential --
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 - Ceragons 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.
Page 3
-- Company Confidential --
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)
Page 4
-- Company Confidential --
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.
Page 5
-- Company Confidential --
Page 6
-- Company Confidential --
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.
Page 7
-- 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.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.
Page 8
-- Company Confidential --
Page 9
-- Company Confidential --
Page 10
-- Company Confidential --
Enable, Disable
Disable
In Standby only
Page 11
-- Company Confidential --
Parameter
Description 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. 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.
Value
Default
Configurable
(0-100) in percentage
80
In Standby only
(0-100) in percentage
50
In Standby only.
The following message is presented to the client when the Standby server is automatically activated:
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.
Page 12
-- Company Confidential --
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.
Page 13
-- Company Confidential --
Page 14
-- Company Confidential --
Page 15
-- Company Confidential --
4 Resolved Issues
Class Configuration Broadcast ID 22995 Description 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" 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. (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.) In Add New Trail, there are slots that may not display after network auto-discovery Try to perform SWD on any element type (1500R/IP10/IP10G etc...). 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, 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
Page 16
-- Company Confidential --
Class PV Languages
ID 29897
Description PV does not support UMLAUT German, Swedish, and Hungarian languages PV server keeps history for longer than configured PV restarts due to DBCheck process 1500R Quad support
Comment
Page 17
-- Company Confidential --
5 Open Issues
Class Configuration Broadcast ID 24332 Description In 1500P, not all thresholds are configured via Configuration Broadcast (STM-1, radio) Configuration Broadcast does not apply on 3200T When pressing abort during auto-discovery (of large amount of NEs) - the process always aborts at the same point When adding Floating IP to IP-10G and performing discover node, the links disappear 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) Discover node has no effect on ADM Trail mechanism Discover FA4800 with no active alarms as unreachable and not colored in green. Comment Workaround Configure threshold manually
30525
23093
29613 31836
27241
16301
TDM Trails
24579
SW Download
25589
When the server and the client are installed on Solaris, 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. (2) After new alarm raising in FA4800, it update the NE color in PV Manually install the new version of the client on Solaris Workaround Add the icons manually
Page 18
-- Company Confidential --
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, 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, changed NE locations are not saved 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 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, 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.
Multilink (2+0)
26272
Alarm Log
30936
Reports
30832
Topology Redundancy
30562 29930
Alarms
24932
SNMP
29132
Work around: 1. Insert the name from the web or 2. Use User Defined Name
Interface Report
28956
30150
User definition
31796
Work around define admin users in specific subnet groups, but with permissions to all the network.
Page 19
-- Company Confidential --
6 Known Issues
Class Discovery ID 25766 24520 Description Rarely, after auto discovery, non-existent links appear in the map Changing NE interfaces (for example adding or removing daughter-board) cannot be retrieved via poll node. 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, 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 There are situations when the icon disappear from the system tray (Windows only) 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 In ADM Trail Management (1500AL, 1500A product line), the E1 loopback dialog opens and is empty BG20/30 (ECI) Changing alarm severity in the EMS of the BG doesnt reflect in PV
4070
Workaround Re-open the window Workaround - Perform discover node after changing the severity of the alarm in the EMS of the BG.
24451
Sagem linkF Current alarm cannot be read Nokia FIU-19E, traps not recognized in PV (SNMP V2c) Sometimes, when clicking the refresh button, the user cannot close the "Refreshing" dialog
Page 20
-- Company Confidential --
ID 17786
Comment 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
Alarms
31833
Any manual configuration of MySQL database may harm PolyView functionality. 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.
Page 21
-- Company Confidential --
7.2 IP-10G
Marketing Version I6.5ca1 I6.5ca1 I6.6ca1 I6.6ca1 I6.6ga I6.6.1 I6.6.2 SW Version 3.0.97 3.0.99 6.6.0.0.1.40 6.6.0.0.1.41 6.6.0.0.2.53 6.6.1.0.0.60 6.6.2.0.0.22 Remarks Upgrade only Upgrade only
I5.28 I-528f 4.95 5.10 S6.0 S6.5 S6.6 T5.0 4.95s19 5.10n1 SFD_6.00c3.sfd SFD_6.50e2.sfd SFD_6.60c3.sfd SFD_5.00a71a
Page 22
-- Company Confidential --
7.4
Page 23
-- Company Confidential --
Page 24