PolyView system N6.7.0.0.

0
Technical Description

Rev A 14 June 2011
Copyright © 2011 by Ceragon Networks Ltd. All rights reserved.

PolyView system N6.7.0.0.0

Technical Description

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® is a registered trademark of Ceragon Networks Ltd. FibeAir® is a registered trademark of Ceragon Networks Ltd. CeraView® is a registered trademark of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

Trademarks
CeraMap™, ConfigAir™, PolyView™, EncryptAir™, and CeraMon™ 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.

Open source statement
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://www.gnu.org/licenses/.

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.

Revision history
Rev Date
1.0

Author

Description

Approved by

Date
14 June 2011

14 June 2011 Mika Yehezkeli Product description of PolyView N6.7 Nir Gasko

Ceragon Proprietary and Confidential

Page 2 of 42

PolyView system N6.7.0.0.0

Technical Description

Table of Contents
PolyView Network Management System (NMS) System overview .....................6
PolyView features overview.................................................................................................. 7 Automatic discovery of network topology ............................................................................ 7 Global fault management ................................................................................................... 8 Network element configuration management ...................................................................... 9 Network performance management.................................................................................. 10 End-to-End Ethernet services management ..................................................................... 11 End-to-End TDM trail management .................................................................................. 12 Network security management ......................................................................................... 13 System administration ...................................................................................................... 14

System architecture .......................................................................................... 15
PolyView server components ............................................................................................. 16 MySQL database ............................................................................................................. 16 FTP/ TFTP server ............................................................................................................ 16 XML & HTTP proxy .......................................................................................................... 16 Server redundancy........................................................................................................... 16 CeraMap client GUI............................................................................................................ 17 Network topology maps .................................................................................................... 17 Navigator panel topology tree ........................................................................................... 17 Management interfaces ...................................................................................................... 18 Northbound interfaces ...................................................................................................... 18 CLI report interface .......................................................................................................... 18 SNMP southbound interface ............................................................................................. 18

PolyView features.............................................................................................. 19
GUI based network management ....................................................................................... 19 Adding network elements to a network topology map ....................................................... 19 Network auto discovery .................................................................................................... 19 Network rediscovery......................................................................................................... 20 Grouping and linking network elements ............................................................................ 20 Network hierarchy and the Navigator topology tree ........................................................... 20 Fault and alarms management ........................................................................................... 21 Network entity alarms ....................................................................................................... 21 PolyView’s alarms interface.............................................................................................. 21 Viewing top most alarm severity ....................................................................................... 21 Viewing alarm history ....................................................................................................... 21 Network management alarms ........................................................................................... 22 Alarm triggers .................................................................................................................. 22 Configuration management ................................................................................................ 22 Network element configuration backup & restore .............................................................. 22 Mass configuration broadcast ........................................................................................... 22 Mass software downloads ................................................................................................ 23 NMS client auto upgrade .................................................................................................. 23 Traffic services management ............................................................................................. 23 End-to-end Ethernet services management ...................................................................... 23 GUI based service management ................................................................................. 23 Wizard based provisioning .......................................................................................... 24
Ceragon Proprietary and Confidential Page 3 of 42

PolyView system N6.7.0.0.0

Technical Description

xSTP status maps ....................................................................................................... 24 End-to-end TDM trail management................................................................................... 24 GUI based TDM trail management .............................................................................. 24 Automatic provisioning of TDM trails............................................................................ 25 Performance management ................................................................................................. 25 Inventory management..................................................................................................... 25 Performance monitoring ................................................................................................... 25 Security.............................................................................................................................. 25 User access control.......................................................................................................... 26 Personalize view per user ........................................................................................... 26 Domain based group permissions and subnet based access rights .............................. 26 Password security configuration .................................................................................. 26 Single sign-on to EMS web clients............................................................................... 27 Remote user authentication ......................................................................................... 27 Audit logging .................................................................................................................... 27 Monitoring and managing connected NMS users ......................................................... 27 User action log ............................................................................................................ 27 System administration ........................................................................................................ 27 Task scheduler................................................................................................................. 27 Database management .................................................................................................... 28 Server redundancy and synchronization ........................................................................... 28

System specifications ....................................................................................... 28
Minimum hardware requirements ....................................................................................... 28 Hardware capacity recommendations ................................................................................. 29 Supported operating systems ............................................................................................. 29 Supported protocols ........................................................................................................... 29 Supported network elements .............................................................................................. 30 IP-10 ................................................................................................................................ 30 IP-10G ............................................................................................................................. 30 IP-10E ............................................................................................................................. 30 FibeAir 1500 family .......................................................................................................... 31 FibeAir 2000/4800 family.................................................................................................. 31 3rd party supported elements ............................................................................................ 31 License requirements ......................................................................................................... 32

Appendix A – PolyView’s server redundancy ................................................... 33
PolyView’s redundant server configuration ......................................................................... 33 Synchronizing server databases ......................................................................................... 33 Activation conditions for a standby server ........................................................................... 33 Activation operations for a standby server .......................................................................... 33

Appendix B – PolyView predefined report types .............................................. 35
Performance reports .......................................................................................................... 35 Interface performance reports .......................................................................................... 35 Radio Ethernet performance report .................................................................................. 35 TDM trail performance reports .......................................................................................... 36
Ceragon Proprietary and Confidential Page 4 of 42

....................................... 39 Neighbors report ..............................................................................................................................................................................................................................................................................................................................................................................................................................PolyView system N6........ 40 Radio report ......... 38 Licensing report .................................................................................................................................................................... 39 Network element report ..................................................................................... 37 Interface availability report........0 Technical Description Inventory reports .................................................................................................................................................................................................................0....................................................... 36 In-band report ...................................................................................................................................................................0.................................................................................................... 42 Ceragon Proprietary and Confidential Page 5 of 42 ........................................... 41 Versions report... 38 Link report................................................................... 39 Protection report ........................................ 37 Interface report..... 40 Serial numbers report ..............................7...................................... 42 xSTP report............................................................................... 36 Available interfaces for PM report ..................... 41 Slot population report ..................................................

PolyView’s broadcast configuration and software download utilities help the NMS user to manage groups of network elements. including the alarm type and severity. and services. Optimized for centralized operation and maintenance of a complete network. all map entities. Performance reports provide information about radio. configuration. Configuration management PolyView simplifies network elements configuration management. provides centralized. Service view provides Wizard based provisioning. Performance management Scheduled polling allows users to monitor network activity in real time and to keep historical performance monitoring information for future usage.0 Technical Description PolyView Network Management System (NMS) System overview PolyView is a Network Management System (NMS) designed for managing large scale wireless backhaul networks. and management of Ethernet service and TDM trails. CeraMap’s reporting interface is designed to help users identify activity patterns and anticipate problems before they occur. Inventory and performance reports can be generated for the entire network. and GUI driven configuration of service paths and trails. including network elements. PolyView’s client interface. User access rights determine which parts of the network a user can view. or for a selected subnet. trails. Network security PolyView is a secure system that enables administrators to control who uses the system. End-to-end traffic service management PolyView includes a service management GUI for provisioning. and which parts of the system can be accessed. or service. For a more in-depth understanding of network performance. interface. and trail performance. and which operations users can perform for each subnet. audit logging. service topology maps. probable causes and corrective actions. GUI based access to all network management functionality.PolyView system N6. The alarms interface provides details of each alarm.7.0. with centralized configuration file backup and rollback. links. PolyView offers users a comprehensive set of management functions to simplify network management work. monitoring.0. Permissions are assigned to groups on a feature by feature basis. CeraMap. trail. Security is maintained by a combination of user access control features. Ceragon Proprietary and Confidential Page 6 of 42 . are color coded. and secured interfaces. Additionally. Fault management PolyView enables global management of network entity alarms with comprehensive alarm reporting. Inventory reports provide information about Ceragon interfaces and links in the system. raise and clear time. with the color indicating the status of the most current alarm. group.

Ceragon Proprietary and Confidential Page 7 of 42 . multi radio.7. Multi link map discovery and display. and protected links. Flexible discovery scope configuration options.0. multi-line.PolyView system N6. subnets.0 Technical Description PolyView features overview Automatic discovery of network topology    Auto discovery of network entities.0. including network elements.

0. Alarm history including raise/clear time and actions performed on an alarm. including dedicated management. Alarm details include probable causes and suggestions for corrective actions. trail. Alarm history and user action logs show performed on alarms.0 Technical Description Global fault management        Comprehensive alarm interface. and service alarms. Configurable alarm filtering.7. Alarm synchronization toward southbound and northbound interfaces.PolyView system N6. Graphic representation of alarm severity levels. Ceragon Proprietary and Confidential Page 8 of 42 .0.

reports.0 Technical Description Network element configuration management      Global network element administration Single sign-on with network element managers via CeraMap topology maps. or alarms. Network elements configuration file backup & rollback Mass configuration broadcasts Batch software downloads Ceragon Proprietary and Confidential Page 9 of 42 .0. service maps.PolyView system N6.7.0.

7. and TDM trails performance monitoring and reporting Scheduled report generation via PolyView’s command line report interface. radio.PolyView system N6. Sophisticated report filtering for customized views of network status and performance data Interface. or groups of elements to retrieve real time performance and inventory status. Generate reports performance and inventory reports for the entire network or selected groups. subnets or specific network elements.0.0. Ceragon Proprietary and Confidential Page 10 of 42 .0 Technical Description Network performance management      Scheduled polling of discovered network elements.

7. Ethernet service topology maps. Automatic. xSTP status map.0. View current Ethernet service related alarms.0 Technical Description End-to-End Ethernet services management        GUI based Ethernet service management.PolyView system N6.0. wizard based provisioning of Ethernet services. Ceragon Proprietary and Confidential Page 11 of 42 . Multiple property based views. Automatic discovery of all Ethernet service paths.

TDM trail topology maps.0 Technical Description End-to-End TDM trail management       GUI based TDM trail management.PolyView system N6. and dual ended protection. including ABR protection. Automated. TDM trail performance monitoring and reporting. wizard based TDM trail provisioning.0.7. protected SNCP links. Automatic discovery of primary and secondary TDM trails between two end points. Ceragon Proprietary and Confidential Page 12 of 42 .0. Manage trail protection.

Secure authentication and security protocols for all management interfaces. Configure customizable network access.7. Password encryption and rules enforcing.0.0.0 Technical Description Network security management         Feature based permissions. Subnet based access.PolyView system N6. Single sign on with network element managers. Ceragon Proprietary and Confidential Page 13 of 42 . Passwords retry ceilings and timeout blocking. External user authentication.

7. Database backup. repair. GUI or command line scheduling of recurring tasks. Ceragon Proprietary and Confidential Page 14 of 42 .0 Technical Description System administration      Comprehensive server configuration options.0. & restore. Server redundancy and synchronization.PolyView system N6.0. Server CPU & memory usage monitoring and alarming.

0.7.0.a centralized internal MySQL database CeraMap application .the foundation on which all PolyView applications and services run The PolyView server PolyView database .0 Technical Description System architecture The PolyView NMS system includes: PolyView framework .PolyView system N6.Ceragon’s NMS GUI PolyView System network integration Ceragon Proprietary and Confidential Page 15 of 42 .

The MySQL license must be purchased as part of the purchase order of the PolyView system from Ceragon.0. Server redundancy PolyView has built-in support for redundancy configuration.1.0. XML & HTTP proxy PolyView has an embedded XML & HTTP proxy that enables connection between network elements and the CeraMap client when direct connection between is unavailable.  For Windows servers.7 works with embedded MySQL Enterprise Server 5. and doesn’t require FileZilla.PolyView system N6. The database is provided as part of the basic PolyView installation. or to upload software updates. With two PolyView servers.0 Technical Description PolyView server components MySQL database PolyView N6. one is configured as the primary server. NMS users can use the FTP server to download configuration files from the network elements.7. PolyView uses the Solaris FTP client. FTP/ TFTP server PolyView uses an external FTP server to backup network element configuration files and to manage software uploads and downloads. PolyView expects to find the FileZilla FTP client installed in its default location (C:\ProgramFiles\FileZilla Server\)  For UNIX servers. Ceragon Proprietary and Confidential Page 16 of 42 . with the secondary server configured for standby mode.

planning and design. Network topology maps The topology map shows both physical and logical links between network entities.  Double clicking an icon opens the Element Manager of a single network element. with information about the network element: its user defined name. actions will be applied to all the sub-elements that are included in the selection. Logical links can be configured for Ethernet traffic. CeraMap.  Mousing over a network element displays its tooltip. PolyView’s network management GUI enables maximum flexibility in network operation. IP. CeraMap treats them all as separate links. When there are multiple physical links between two networkelements.0. For most operations. its system name.0 Technical Description CeraMap client GUI PolyView’s network management GUI. Navigator panel topology tree CeraMap’s topology tree provides a logical view of network topology.  Double clicking a group of network elements opens a map of the group. NMS users can drill down to see all the subnets in their view of network. Ceragon Proprietary and Confidential Page 17 of 42 .0. with a topology tree in the Navigator panel on the left.PolyView system N6. and alarm severity.  The main window presents a map of the network topology. With full support for today’s mixed network topologies. and all of the elements in each subnet.7.  Alarm severity of map entities is represented by color. 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.  Actions are performed on the current selection.

The CLI interface can be used to generate performance monitoring and inventory data reports for higher level OSS usage.0. Ceragon Proprietary and Confidential Page 18 of 42 . PolyView can be configured to forward network elements server management traps to a predefined server IP address (OSS server). faults. PolyView includes an alarm synchronization mechanism that automatically creates and generates traps for alarms that were sent by the network element but didn't reach the PolyView server. NetAct ESYMAC) Reports interface – CLI reports interface Southbound interface (SNMP. such as starting or stopping the server. topology. Via this interface. exporting and importing data. The CLI also allows access to the PolyView system for specific tasks.0 Technical Description Management interfaces PolyView supports three different management interfaces for network management access:    Northbound interface (SNMP. NetAct ESYMAC PolyView supports the NSN open OAM interface for integration with OSS level network management systems. In addition to logging alarms which have been received through SNMP traps. SNMP southbound interface PolyView’s NMS supports monitoring and configuring of network elements via the SNMP interface. CLI report interface PolyView allows system administrators to perform many server related tasks via the command line. XML over HTTP) Northbound interfaces SNMP Interface toward OSS / Other NMS platforms PolyView’s SNMP agent provides a system-wide active alarm table.0. which the northbound OSSs can poll when needed. and performance data can be sent to the northbound OSS. or scheduling recurring reports. An external OSS can poll the alarms counter and the current alarm table through SNMP. Northbound alarm synchronization towards a higher level NMS / OSS is available.PolyView system N6.7.

including network elements. multi-line. Using auto discovery Auto discovery finds existing network elements.0. Ceragon Proprietary and Confidential Page 19 of 42 . including third party elements and elements with floating IP addresses. Note that importing map data will overwrite any changes that were made after exporting the map data. Open network element EMS from CeraMap topology maps. or reports to configure parameters for a selected network element. Network auto discovery The CeraMap client provides auto discovery of network entities. Manage network traffic services. or a combination of both. Manually adding network elements NMS users can manually add network elements to a group or subnet. This is useful for adding specific units to a discovered topology. provides centralized.7. feature based access to network elements. The auto discovery utility is able to identify any network entity with an IP address. All map entities are color coded according to alarm severity.PolyView system N6. Monitor network element status and performance. the map entity will display the color of the most severe alarm. and for designing changes to network topology. Importing map data NMS users can also import saved network topology. CeraMap allows users to choose between different protocols and authentication methods for each type of discovery scope.0 Technical Description PolyView features GUI based network management PolyView’s client interface. Define customized. If there is more than one alarm configured for a network entity. GUI based access to all network management functionality. links. CeraMap. Current alarm status is built into the topology GUI. subnets. multi radio. auto discovery is the recommended way to initialize network topology maps.      Adding network elements to a network topology map There are three ways to add network elements to a network topology map: Each method is appropriate for different stages of network management. and protected links. As PolyView is designed to manage large networks. Users can define the range of the discovery scope according to IP range or subnet. Perform global configuration operations such as configuration broadcasts and software downloads.0. alarm lists.   View and manage network entity alarms. and alarms.

such as multi-radio links. Groups that are added to the map will also be added to the topology panel on the left. Ceragon Proprietary and Confidential Page 20 of 42 . PolyView operates in a hierarchical manner.PolyView system N6. PolyView automatically reads the element’s static information. If the elements have links to other elements that are not to be moved. If more than two elements are found to be linked.0 Technical Description Network rediscovery When an element is first added to the map. Users can drill down to see all the subnets in the network. Users can differentiate between groups by establishing logical naming conventions.  Users can perform a Poll node operation for a selection of discovered network elements to retrieve current performance and availability status. Each discovery feature has a distinct purpose. There are a number of rediscovery options that will update the network topology map with current data. choosing the appropriate icon to represent each group.  Users can also Refresh topology maps to display the most current data from the server. aggregated links. including stored reports. PolyView also searches for connectivity between elements. When connections are found. During the Auto discovery process. including all the sub-elements in the selection.0. Network hierarchy and the Navigator topology tree CeraMap's Navigator panel displays a hierarchical view of network topology. and by defining group backgrounds. and 2+2 configurations. and all of the sub-elements of on that subnet. the links will be deleted instead. the links between them will be moved as well. Grouping and linking network elements Users can create an unlimited number of levels in the map by grouping network elements. PolyView automatically identifies the type of link and adds links the connected elements on the topology map. Links in the map show how elements and groups are connected in the network.7.  Users can perform a Discover node operation to re-discover the element's properties. with the new data. Discover node replaces existing information. Most operations apply to the selected network elements. If a user moves linked network elements or groups.0. are represented by corresponding link types. Network entities are automatically arranged on the topology tree according to subnet. Multiple link configurations. and moves the linked elements to that sub-group. PolyView supports up to seven levels of hierarchy. PolyView automatically creates a sub-group.

Network administrators can specify how long to keep alarm log information. alarm triggers. including the alarm type and severity. and alarm messages can all be used to help find the alarm when viewing the alarm or user actions logs. all map entities. The alarms interface provides details of each alarm.  Show hidden alarms. links. an NMS user may:  Acknowledge the alarm.  Set the alarm to hidden so that it will no longer appear in the alarm lists.7. Users can view. raise and clear time. After viewing an alarm’s details. and corrective actions. and corrective actions. filter. with the exception of raised alarms which are kept in the alarm history log until they are cleared. network element.PolyView system N6. PolyView’s alarms interface The alarms interface provides details of each alarm. including network elements. Viewing top most alarm severity Additionally.0.  Reset an acknowledged alarm to unacknowledged. Ceragon Proprietary and Confidential Page 21 of 42 . The acknowledge state of an alarm. and services. without acknowledging the alarm. or to perform a collective acknowledgement for a selection of alarms. and the alarm history logs. or for the entire network. Viewing alarm history The list of current alarms helps users to identify which items require immediate action. In terms of functionality. Users will be prompted to add a note about the hidden alarm. recurring events that may require preventative measures. are color coded. with the color indicating the status of the top most current alarm. for example.0 Technical Description Fault and alarms management PolyView enables global management of network entity alarms with comprehensive alarm reporting. Network entity alarms Network operators can view current or historical alarms for a group. raise and clear time. subnet. probable causes.  Add a note to the alarm. or remove hidden status from an alarm. print. and save the current alarms. trails. alarm descriptions. including the alarm type and severity.0. the alarm lists are similar to the network element EMS reports. probable causes.

Network administrators can use these files to restore network elements to the latest functioned configuration. alarm type.0. surpassing capacity thresholds and network element level issues that affect network services. Configuration management PolyView simplifies management of network elements by enabling global administration of network element configuration. providing real time alerts about loss of radio frames. sound alarms. if the server is running low on disk space. sending email.0. Trigger configuration allows users to define activation conditions and activation operations for raising alarms. Mass configuration broadcast PolyView’s broadcast configuration and software download utilities help the NMS user to manage groups of network elements. Network element configuration backup & restore PolyView reads network element configuration data during its user defined polling intervals. Network element configuration data is stored in configuration files on the NMS database. subnet.PolyView system N6. users can enable a Severity trigger by selecting one or more alarm severities or activate a trigger when specific characters are detected in the alarm text. alarm description. forwarding traps. with centralized configuration file backup and rollback. PolyView’s broadcast configuration utility allows users to set attributes or modify configuration parameters for selections of network elements according to type of element. Activation operations include displaying messages. PolyView simplifies network elements configuration management. network management alarms will forward a trap if the NMS loses connectivity with a network element. or acknowledged status.7. if the network is unable to switch to a standby server. Ceragon Proprietary and Confidential Page 22 of 42 . For example. PolyView’s broadcast configuration and software download utilities help the NMS user to manage groups of network elements. Alarm triggers Alarm triggers and trap generation complement scheduled polling intervals. or other common feature. and customized executables. For example. or if a license is about to expire.0 Technical Description Network management alarms Management alarms keep users informed about the state of their networks. Activation conditions can be based on alarm severity.

Service view provides Wizard based provisioning. PolyView uses a customized version of its software download utility to provide automatic client upgrades.0 Technical Description Mass software downloads PolyView’s smart software download utility allows users to perform simultaneous upgrades of multiple units. View and manage service related alarms for network elements along the service path.7 and higher.7. Ethernet level connectivity must be preconfigured manually. otherwise PolyView will not recognize the Ethernet ports neighbors. Additionally. Update service status. PolyView’s smart upgrade utility will find all CeraMap clients on the network.7 or higher. and will perform automatic upgrades from the previous two releases. broken. Service view provides GUI based access to all service attributes:         Provision and configure new Ethernet services. View real time operational status of xSTP rings. Edit service access points and service network point parameters. NMS client auto upgrade When upgrading from N6. or partially configured. Repair services whose operational status is unknown. Traffic services management PolyView includes a service management GUI for provisioning. As with mass configuration broadcast. service topology maps. Page 23 of 42 Ceragon Proprietary and Confidential .0. ports must be enabled and configured for all the network elements for the target service.7 and above. if a selection includes sub-elements. for clients running versions N6. Remove services. Poll a service to update the service topology map with the current status and alarms. GUI based service management The Ethernet services GUI simplifies configuration and management of Ethernet service paths. PolyView’s end to end Ethernet service management is available for IP-10 release I6.PolyView system N6. configuration. and GUI driven configuration of service paths and trails.0. monitoring and management of Ethernet service and TDM trails. End-to-end Ethernet services management Note that the IP tables for target service access points must be pre-configured through the network element web EMS or CLI. the download will apply to all the sub-elements as well.

Users can choose between the Fast Ring RSTP and the standard RSTP protocols as defined in IEEE 802. Spanning Tree allows a network design to include spare (redundant) links for automatic backup paths. operational status and performance monitoring. The backup paths can be included with no danger of bridge loops. End-to-end TDM trail management PolyView’s end-to-end trail management allows comprehensive trail definitions and configuration of trail properties and status information such as alarms.   Ceragon Proprietary and Confidential Page 24 of 42 .0. needed for cases in which an active link fails. Manage trail protection by specifying which will be the primary trail and which will be the secondary trail. Generate trail performance reports from the CeraMap client GUI.7. Poll trails to update the trail map with current availability and alarm status data. Bridge loops must be avoided since they result in network “flooding”. View trail related alarms.PolyView system N6.0. RSTP and Ring RSTP algorithms are designed to create loop-free topologies in any network design. which makes it sub-optimal to ring topologies. providing access to all trail parameters:    Add trail protection to an unprotected trail.1D. or schedule recurring reports using PolyView’s command line report interface. or the need for manual enabling/disabling of the backup links. GUI based TDM trail management The TDM trail GUI simplifies configuration and management of TDM trails.0 Technical Description Wizard based provisioning Wizard based provisioning wizard automates configuration of Ethernet service paths. The Ethernet services wizard automates provisioning of E-LINE and E-LAN services. PolyView’s auto discovery searches for paths between two or more selected service access point. xSTP status maps STP ensures a loop-free topology for any bridged LAN.

PolyView system N6. and which operations users can perform for each subnet. Report specific filters allow for customized report generation. Performance reports provide information about radio. group. Performance monitoring Comprehensive PMs for network entities are available via the built in Performance reports. Security PolyView is a secure system that enables administrators to control who uses the system. CeraMap reporting interface is designed to help users identify activity patterns and anticipate problems before they occur. Links between network elements along the target trail must be discovered and TDM enabled for the system to automatically provision a TDM trail.7. Inventory reports provide information about Ceragon interfaces and links in the system. Ceragon Proprietary and Confidential Page 25 of 42 . In addition to the built-in reports. or service. PolyView’s auto discovery searches for the most efficient trail between two selected end points. PolyView calculates the trail path using information from the network elements. trail. Inventory data is available to users via 14 built-in predefined reports. or for a selected subnet. and which parts of the system can be accessed. Inventory management PolyView retrieves inventory information from all managed network elements. audit logging.0. and secured interfaces. User access rights determine which parts of the network a user can view. Performance management Scheduled polling allows users to store historical data and to monitor network level activity in near real time. Inventory and performance reports can be generated for the entire network.0.0 Technical Description Automatic provisioning of TDM trails Wizard based provisioning wizard automates configuration of TDM trails. and trail performance. the Service view reporting interface displays Ethernet service and TDM trail status information. interface. Permissions are assigned to groups on a feature by feature basis. Security is maintained by a combination of user access control features.

and reports are all limited to the IP range and subnets where users have access rights. they see only the map for the network where they’ve been granted access. For example. and password aging. Discovery and configuration scope. Personalize view per user Network topology and service maps are saved in the database per user. user access rights create a personalized view of the network for each user. PolyView will not accept a user password that does not meet all the configured restrictions.0 Technical Description User access control User access configuration determines which parts of the network a user can view. they may be assigned to a different group – with different permissions – for each subnet. passwords must be at least eight characters long and must include a mix of alphanumeric characters and case. Permissions are configured on a feature by feature basis for each group. New passwords cannot repeat any of the previous five passwords. traffic service management. alarm lists. The default interval for password expiry is one month. Domain based group permissions and subnet based access rights The set of operations that network operator may perform within their allowed subnets is further limited by the permissions that are defined for each group. however. password complexity. and which operations users can perform for each subnet.PolyView system N6. Ceragon Proprietary and Confidential Page 26 of 42 . Password compliance is enforced. Password security configuration Administrators can enforce password security by enabling minimum password length.0. the list of current alarms that a network operator sees is actually only a subset of the list of alarms that will be displayed to an Admin-Security user who has access rights to the entire network. By default. Users are assigned to one group per subnet.7. Passwords information is encrypted on the database. Password rule settings can be modified by an Admin network administrator. When network operators open their clients.0. In effect.

Ceragon recommends adding database and configuration backup as daily tasks. Login information to EMS users is assigned to groups that define which operations users will be able to perform on managed network elements. users must be granted access rights to the subnet where the network element is located. Remote user authentication PolyView uses RADIUS protocol for remote user authentication. the IP address of network element on which an action is being performed. The log records details about each operation performed by every system user. While PolyView’s command line interface only allows specific. The User action log displays the username.7. as a user of a group with silent login privileges. users must be authenticated by RADIUS server by using the embedded RADIUS client on the PolyView server. For single sign-on with network elements. When CeraWeb is connected to the network elements via PolyView. CeraMap’s task schedule allows users to set up customized executables as recurring tasks. When enabled.0 Technical Description Single sign-on to EMS web clients PolyView supports single sign-on with IP-10 CeraWeb EMS. Ceragon Proprietary and Confidential Page 27 of 42 . Database backup and repair can also be performed using PolyView’s command line interface. and details about the operation that was performed. CeraWeb operations will be included in the user action log. location. and the protocol used to connect to the network element. The network administrator can send messages or disconnect connected users. User action log PolyView records all user actions performed over the past day.0. The connected users report displays the user name. User name and password for single sign-on are assigned to groups. PolyView supported executables. Audit logging Monitoring and managing connected NMS users Admin users can view actions performed by connected users. System administration Task scheduler PolyView’s task scheduler allows network administrators to set up recurring tasks such as database checks and automatic database backup.PolyView system N6.0.

user definitions. alarm triggers.  Network map topology. and configuration backups for all network entities. network element inventory.  Polling data. or disable it altogether. 2. The system is preconfigured with recommended – but customizable . and scheduled tasks are saved per user.  Configuration backup saves the four most recent snapshots.log limits. alarm and user action history. System specifications Minimum hardware requirements Component Hardware type Processor Memory (RAM) Available drive space Operating system Ethernet ports Windows requirements Any type Core 2.PolyView system N6. When redundancy is enabled.0.0 GHz 2 GB 120 GB Windows server 2003 and 2008 (32 bit) /XP 1 Unix requirements T2/T3 Sun SPARC 8 GB 73 GB x 2 Solaris 10 1 Ceragon Proprietary and Confidential Page 28 of 42 . By default. map topology. data is synchronized from the primary to the secondary server.0. alarm history and user action logs are stored for a userspecified period of time in the server database. The administrator can also set the synchronization for both ways.0 Technical Description Database management PolyView stores performance monitoring data. network operators can configure redundancy thresholds and synchronization options. Server redundancy and synchronization PolyView has built-in support for server redundancy.7.

0.7.0 Technical Description Hardware capacity recommendations Number of managed network elements Up to 5.000 network elements Up to 7.PolyView system N6.000 network elements Number of parallel connected Hard Processor Memory clients drive Up to 10 NMS Clients Up to 20 NMS Clients Up to 40 NMS Clients SPARC T3 8G SPARC T3 16G SPARC T3 32G 300 GB 600 GB 600 GB Supported operating systems Server & client OS support Windows Server 2003 (32 & 64 bit) Windows Server 2008 (32 & 64 bit) Windows Server 2008 64 bit on a VMware server Windows Server 2008 R2 (32 & 64 bit) Windows XP Solaris 10.000 network elements Up to 7.0. Oracle (Sun) SPARC server Client only support Windows 7 Supported protocols SNMP V1 / V2C / V3 CLI / SSH-2 HTTP / HTTPS FTP / SFTP Ceragon Proprietary and Confidential Page 29 of 42 .

0.2.0.3.53 6.0.2.6.8.0.6.2.0.6ca1 I6.6ca1 I6.0.7.0.12 2.6.0.41 6.6.0.0 Technical Description Supported network elements IP-10 Marketing version I6.0.9.32 2.7.1.7 Software version 3.97 3.5ca1 I6.1.0.5.5ca1 I6.6.0.7.4.60 6.0.PolyView system N6.6ga I6.0. IP-10G Marketing version I6.40 6.2 2.0.1.6.93 Remarks Upgrade only Upgrade only IP-10E Marketing version I6.1 I6.0 2.5 I6.6.33.8.0.3 I6.99 6.22 6.0.0.6 I6.2 I6.1 I6.9.9 Remarks Upgrade only.93 Remarks Ceragon Proprietary and Confidential Page 30 of 42 .25 2.7.8.2 I6.1 Software version 1.2.0.0.6 2.7 Software version 6.0 I6.

7.00_b2650 1.95 5.45 Ceragon Proprietary and Confidential Page 31 of 42 . S5.9.5 S6.60c3.95s19 5.60c3.0 S6.28 I-528f Marketing version Software version FibeAir 2000/4800 family Product FA2000 FA4800 Marketing version 2.6 S6.sfd SFD_6.sfd SFD_6.00c3.0.6 T5. G5) 1500P (I5.35_b1845 3rd party supported elements Manufacturer Product ECI BG-20B Software version V12.0.5.PolyView system N6.50e2.0 Technical Description FibeAir 1500 family Product 1500 1528 1500A 1500AL 1528A 1500P (I5.9.0 4.sfd SFD_5. S5.35 Software version 2.00a71a I5.5 1.10n1 SFD_6.sfd SFD_6.10 S6.0. S5 Quad G5) 1500R 1500R 1500R 1500R Quad 3200T 640P 4.

1 TDM trails Ethernet services PolyView software release upgrade Model # PolyView NMS Quantity per server 1 Quantity for redundant servers solution 2 PV_21-100_NE 80 160 PV_101-500_NE 30 60 PV_Redundant_Support MySQL-License-PV PV_TDM_Provisioning PV_Ethernet_Provisioning PV_SW_upgrade 1 1 1 1 1 2 2 2 2 2 Ceragon Proprietary and Confidential Page 32 of 42 .0.7.0 Technical Description License requirements Description PolyView Software + License for 20 network elements License for 21-100 network elements.PolyView system N6. per NE License for 101-500 network elements: per NE License for redundant PolyView support mySQL Enterprise Server 5.0.

The standby server becomes active when the main server crosses user specified thresholds. Start polling network elements. A redundant configuration includes two PolyView servers: a primary server. When the synchronization mode is from main to standby. including adding and deleting network elements. the main server will get the current topology map from the standby server.7. Activation conditions for a standby server If the main server is down. Raise the management alarm “No Connection with Main Server”.0. but it could also create a situation where both will become active. By default. If the synchronization mode is both ways. and will: Start sending traps and triggers. Lost connectivity between the two servers could mean that the main server is unavailable. Ceragon Proprietary and Confidential Page 33 of 42 . and a secondary server. the secondary server returns to standby mode. no synchronization action will be performed when the main server becomes active again. When the main server starts again after a failure. the standby server can be configured to automatically take over. data is synchronized from the primary to the secondary server. Synchronizing server databases Redundancy requires that databases in both servers remain synchronized: topology changes. the secondary (standby) server becomes active. when connectivity is restored.PolyView system N6. The administrator can also set the synchronization for both ways. which is generally located at a geographically remote site and is in standby mode. must be synchronized across both databases. In all cases. or disable it altogether. Start accepting client connections. or if it loses connectivity with the main server. which is generally active. switching to the standby server raises an alarm. Activation operations for a standby server If no connection is detected between the main and standby servers for more than the user defined loss of connectivity threshold:   It will raise the alarm “No Connection with Standby Server” In Auto mode.0. and gives users the option to switch back to the primary server.0 Technical Description Appendix A – PolyView’s server redundancy PolyView’s redundant server configuration PolyView has built-in support for redundancy configuration.

and will: Clear the management alarm “No Connection with Main Server” Notify about new client connections. in standby mode.PolyView system N6. the secondary (standby) server will go to standby mode. the standby server reloads the file.0 Technical Description When the connection is resumed and is stable:   The main server clears the “No Connection with Standby Server” alarm. Network elements should be configured to send traps to both servers.0. If in Auto mode. Resume limited polling (by default. the secondary server polls only alarms). When a security file is updated. and send the message “Main server (IP) is active” to connected clients.7. Stop sending traps and triggers. and immediately begins to use it.   Ceragon Proprietary and Confidential Page 34 of 42 .0.

7. Ceragon Proprietary and Confidential Page 35 of 42 . Radio Ethernet performance report Displays Ethernet service performance parameters.PolyView system N6.0 Technical Description Appendix B – PolyView predefined report types Performance reports Interface performance reports Shows performance parameters for line (E1 / DS1/ STM-1 / OC-3) interfaces.0.0.

0. Inventory reports Available interfaces for PM report Shows which network element interfaces are enabled for performance monitoring. If TDM trail path protection is enabled.0 Technical Description TDM trail performance reports Displays performance data for TDM trails.7.PolyView system N6. the system performs measurement on both the primary and secondary paths.0. Ceragon Proprietary and Confidential Page 36 of 42 .

Interface report Displays information about all the interfaces on the unit. Ceragon Proprietary and Confidential Page 37 of 42 .0 Technical Description In-band report In-band status is a way to manage the network.0.0.7.PolyView system N6.

0. Ceragon Proprietary and Confidential Page 38 of 42 .PolyView system N6.0 Technical Description Interface availability report Shows which network element interfaces are enabled. Licensing report Provides data about which licenses are enabled for each network element.7.0.

0.7. Neighbors report Provides data about the IP addresses of the units on a link. Network element report Provides status information and data about indoor units. such as transmit and receive frequencies and slot number locations.PolyView system N6. Ceragon Proprietary and Confidential Page 39 of 42 .0 Technical Description Link report Provides data about links.0.

Radio report Provides status information of outdoor units.0.PolyView system N6. Ceragon Proprietary and Confidential Page 40 of 42 .0 Technical Description Protection report Provides data about protected configurations in the network.0.7.

0.0.PolyView system N6.7.0 Technical Description Serial numbers report Shows the serial number for each network element. Slot population report Reports which IDUs are inserted in each slot. Ceragon Proprietary and Confidential Page 41 of 42 .

xSTP report Provides data about active and inactive xSTP paths.0.7.PolyView system N6.0. Ceragon Proprietary and Confidential Page 42 of 42 .0 Technical Description Versions report Provides data about which software versions are installed on network elements.