PolyView Technical Description N6 7 (Rev A)

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
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 users 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
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 PolyViews 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
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 PolyViews server redundancy ................................................... 33

PolyViews 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
Inventory reports ................................................................................................................ 36 Available interfaces for PM report ..................................................................................... 36 In-band report .................................................................................................................. 37 Interface report................................................................................................................. 37 Interface availability report................................................................................................ 38 Licensing report ............................................................................................................... 38 Link report........................................................................................................................ 39 Neighbors report .............................................................................................................. 39 Network element report .................................................................................................... 39 Protection report .............................................................................................................. 40 Radio report ..................................................................................................................... 40 Serial numbers report ....................................................................................................... 41 Slot population report ....................................................................................................... 41 Versions report................................................................................................................. 42 xSTP report...................................................................................................................... 42
Page 5 of 42
PolyView Network Management System (NMS) System overview

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

Automatic discovery of network topology
Auto discovery of network entities, including network elements, subnets, multi-line, multi radio, and protected links. Flexible discovery scope configuration options. Multi link map discovery and display.
Page 7 of 42
Global fault management
Comprehensive alarm interface, including dedicated management, trail, and service alarms. Alarm details include probable causes and suggestions for corrective actions. Graphic representation of alarm severity levels. Alarm history and user action logs show performed on alarms. Configurable alarm filtering. Alarm synchronization toward southbound and northbound interfaces. Alarm history including raise/clear time and actions performed on an alarm.
Page 8 of 42
Network element configuration management
Global network element administration Single sign-on with network element managers via CeraMap topology maps, service maps, reports, or alarms. Network elements configuration file backup & rollback Mass configuration broadcasts Batch software downloads
Page 9 of 42
Network performance management
Scheduled polling of discovered network elements, 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. Sophisticated report filtering for customized views of network status and performance data Interface, radio, and TDM trails performance monitoring and reporting Scheduled report generation via PolyViews command line report interface.
Page 10 of 42
End-to-End Ethernet services management
GUI based Ethernet service management, Automatic, wizard based provisioning of Ethernet services. Ethernet service topology maps. Automatic discovery of all Ethernet service paths. Multiple property based views. View current Ethernet service related alarms. xSTP status map.
Page 11 of 42
End-to-End TDM trail management
GUI based TDM trail management. Automated, wizard based TDM trail provisioning. TDM trail topology maps. Automatic discovery of primary and secondary TDM trails between two end points. TDM trail performance monitoring and reporting. Manage trail protection, including ABR protection, protected SNCP links, and dual ended protection.
Page 12 of 42
Network security management
Feature based permissions. Subnet based access. Password encryption and rules enforcing. Passwords retry ceilings and timeout blocking. Single sign on with network element managers. Configure customizable network access. External user authentication. Secure authentication and security protocols for all management interfaces.
Page 13 of 42
System administration
Comprehensive server configuration options. GUI or command line scheduling of recurring tasks. Database backup, repair, & restore. Server redundancy and synchronization. Server CPU & memory usage monitoring and alarming.
Page 14 of 42
System architecture
The PolyView NMS system includes: PolyView framework - the foundation on which all PolyView applications and services run The PolyView server PolyView database - a centralized internal MySQL database CeraMap application - Ceragons NMS GUI
PolyView System network integration
Page 15 of 42
PolyView server components

MySQL database
PolyView N6.7 works with embedded MySQL Enterprise Server 5.1. The database is provided as part of the basic PolyView installation. The MySQL license must be purchased as part of the purchase order of the PolyView system from Ceragon.
FTP/ TFTP server

PolyView uses an external FTP server to backup network element configuration files and to manage software uploads and downloads. NMS users can use the FTP server to download configuration files from the network elements, or to upload software updates. For Windows servers, PolyView expects to find the FileZilla FTP client installed in its default location (C:\ProgramFiles\FileZilla Server\) For UNIX servers, PolyView uses the Solaris FTP client, and doesnt require FileZilla.
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.
Server redundancy
PolyView has built-in support for redundancy configuration. With two PolyView servers, one is configured as the primary server, with the secondary server configured for standby mode.
Page 16 of 42
CeraMap client GUI

PolyViews network management GUI, CeraMap, enables fast and easy design of multi-layered network element maps, and helps manage the network from the initial deployment stage through ongoing maintenance and configuration procedures. With full support for todays mixed network topologies, PolyViews network management GUI enables maximum flexibility in network operation, planning and design.
Network topology maps

The topology map shows both physical and logical links between network entities. When there are multiple physical links between two networkelements, CeraMap treats them all as separate links. Logical links can be configured for Ethernet traffic. Actions are performed on the current selection. For most operations, actions will be applied to all the sub-elements that are included in the selection. The main window presents a map of the network topology, with a topology tree in the Navigator panel on the left. Alarm severity of map entities is represented by color. Mousing over a network element displays its tooltip, with information about the network element: its user defined name, its system name, IP, and alarm severity. Double clicking an icon opens the Element Manager of a single network element. Double clicking a group of network elements opens a map of the group.
Navigator panel topology tree

CeraMaps topology tree provides a logical view of network topology. NMS users can drill down to see all the subnets in their view of network, and all of the elements in each subnet.
Page 17 of 42
Management interfaces
PolyView supports three different management interfaces for network management access: Northbound interface (SNMP, NetAct ESYMAC) Reports interface CLI reports interface Southbound interface (SNMP, XML over HTTP)
Northbound interfaces
SNMP Interface toward OSS / Other NMS platforms PolyViews SNMP agent provides a system-wide active alarm table, which the northbound OSSs can poll when needed. PolyView can be configured to forward network elements server management traps to a predefined server IP address (OSS server). Northbound alarm synchronization towards a higher level NMS / OSS is available. An external OSS can poll the alarms counter and the current alarm table through SNMP. NetAct ESYMAC PolyView supports the NSN open OAM interface for integration with OSS level network management systems. Via this interface, faults, topology, and performance data can be sent to the northbound OSS.
CLI report interface

PolyView allows system administrators to perform many server related tasks via the command line. The CLI interface can be used to generate performance monitoring and inventory data reports for higher level OSS usage. The CLI also allows access to the PolyView system for specific tasks, such as starting or stopping the server, exporting and importing data, or scheduling recurring reports.
SNMP southbound interface

PolyViews NMS supports monitoring and configuring of network elements via the SNMP interface. In addition to logging alarms which have been received through SNMP traps, 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.
Page 18 of 42
PolyView features
GUI based network management
PolyViews client interface, CeraMap, provides centralized, GUI based access to all network management functionality. View and manage network entity alarms. Current alarm status is built into the topology GUI. All map entities are color coded according to alarm severity. If there is more than one alarm configured for a network entity, the map entity will display the color of the most severe alarm. Perform global configuration operations such as configuration broadcasts and software downloads. Monitor network element status and performance. Define customized, feature based access to network elements. Manage network traffic services. Open network element EMS from CeraMap topology maps, alarm lists, or reports to configure parameters for a selected network element.
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. Using auto discovery Auto discovery finds existing network elements, links, and alarms. As PolyView is designed to manage large networks, auto discovery is the recommended way to initialize network topology maps. 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, and for designing changes to network topology. Importing map data NMS users can also import saved network topology. Note that importing map data will overwrite any changes that were made after exporting the map data.
Network auto discovery

The CeraMap client provides auto discovery of network entities, including network elements, subnets, multi-line, multi radio, and protected links. Users can define the range of the discovery scope according to IP range or subnet, or a combination of both. CeraMap allows users to choose between different protocols and authentication methods for each type of discovery scope. The auto discovery utility is able to identify any network entity with an IP address, including third party elements and elements with floating IP addresses.
Page 19 of 42
Network rediscovery
When an element is first added to the map, PolyView automatically reads the elements static information. There are a number of rediscovery options that will update the network topology map with current data. Each discovery feature has a distinct purpose. Users can perform a Discover node operation to re-discover the element's properties. Discover node replaces existing information, including stored reports, with the new data. Users can perform a Poll node operation for a selection of discovered network elements to retrieve current performance and availability status. Users can also Refresh topology maps to display the most current data from the server.
Grouping and linking network elements

Users can create an unlimited number of levels in the map by grouping network elements. Groups that are added to the map will also be added to the topology panel on the left. Users can differentiate between groups by establishing logical naming conventions, choosing the appropriate icon to represent each group, and by defining group backgrounds. Links in the map show how elements and groups are connected in the network. Multiple link configurations, such as multi-radio links, aggregated links, and 2+2 configurations, are represented by corresponding link types. During the Auto discovery process, PolyView also searches for connectivity between elements. When connections are found, PolyView automatically identifies the type of link and adds links the connected elements on the topology map. If more than two elements are found to be linked, PolyView automatically creates a sub-group, and moves the linked elements to that sub-group. If a user moves linked network elements or groups, the links between them will be moved as well. If the elements have links to other elements that are not to be moved, the links will be deleted instead.
Network hierarchy and the Navigator topology tree

CeraMap's Navigator panel displays a hierarchical view of network topology. Network entities are automatically arranged on the topology tree according to subnet. Users can drill down to see all the subnets in the network, and all of the sub-elements of on that subnet. PolyView operates in a hierarchical manner. Most operations apply to the selected network elements, including all the sub-elements in the selection. PolyView supports up to seven levels of hierarchy.
Page 20 of 42
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, subnet, network element, or for the entire network. In terms of functionality, the alarm lists are similar to the network element EMS reports. Users can view, filter, print, and save the current alarms, alarm triggers, and the alarm history logs.
PolyViews alarms interface

The alarms interface provides details of each alarm, including the alarm type and severity, raise and clear time, probable causes, and corrective actions. The alarms interface provides details of each alarm, including the alarm type and severity, raise and clear time, probable causes, and corrective actions. After viewing an alarms details, an NMS user may: Acknowledge the alarm, or to perform a collective acknowledgement for a selection of alarms. Add a note to the alarm, without acknowledging the alarm. Reset an acknowledged alarm to unacknowledged. Set the alarm to hidden so that it will no longer appear in the alarm lists. Users will be prompted to add a note about the hidden alarm. Show hidden alarms, or remove hidden status from an alarm. The acknowledge state of an alarm, alarm descriptions, and alarm messages can all be used to help find the alarm when viewing the alarm or user actions logs.
Viewing top most alarm severity

Additionally, all map entities, including network elements, links, trails, and services, are color coded, with the color indicating the status of the top most current alarm.
Viewing alarm history

The list of current alarms helps users to identify which items require immediate action, for example, recurring events that may require preventative measures. Network administrators can specify how long to keep alarm log information, with the exception of raised alarms which are kept in the alarm history log until they are cleared.
Page 21 of 42
Network management alarms

Management alarms keep users informed about the state of their networks. For example, network management alarms will forward a trap if the NMS loses connectivity with a network element, if the network is unable to switch to a standby server, if the server is running low on disk space, or if a license is about to expire.
Alarm triggers
Alarm triggers and trap generation complement scheduled polling intervals, providing real time alerts about loss of radio frames, surpassing capacity thresholds and network element level issues that affect network services. Trigger configuration allows users to define activation conditions and activation operations for raising alarms. Activation conditions can be based on alarm severity, alarm type, alarm description, or acknowledged status. For example, 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. Activation operations include displaying messages, sound alarms, sending email, forwarding traps, and customized executables.
Configuration management
PolyView simplifies management of network elements by enabling global administration of network element configuration. PolyView simplifies network elements configuration management, with centralized configuration file backup and rollback. PolyViews 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. Network administrators can use these files to restore network elements to the latest functioned configuration.
Mass configuration broadcast

PolyViews broadcast configuration and software download utilities help the NMS user to manage groups of network elements. PolyViews broadcast configuration utility allows users to set attributes or modify configuration parameters for selections of network elements according to type of element, subnet, or other common feature.
Page 22 of 42
Mass software downloads

PolyViews smart software download utility allows users to perform simultaneous upgrades of multiple units. As with mass configuration broadcast, if a selection includes sub-elements, the download will apply to all the sub-elements as well. PolyView uses a customized version of its software download utility to provide automatic client upgrades.
NMS client auto upgrade

When upgrading from N6.7 or higher, PolyViews smart upgrade utility will find all CeraMap clients on the network, and will perform automatic upgrades from the previous two releases, for clients running versions N6.7 and higher.
Traffic services management

PolyView includes a service management GUI for provisioning, configuration, monitoring and management of Ethernet service and TDM trails. Service view provides Wizard based provisioning, service topology maps, and GUI driven configuration of service paths and 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. Ethernet level connectivity must be preconfigured manually; otherwise PolyView will not recognize the Ethernet ports neighbors. Additionally, ports must be enabled and configured for all the network elements for the target service. PolyViews end to end Ethernet service management is available for IP-10 release I6.7 and above. GUI based service management The Ethernet services GUI simplifies configuration and management of Ethernet service paths. Service view provides GUI based access to all service attributes: Provision and configure new Ethernet services. Edit service access points and service network point parameters. Repair services whose operational status is unknown, broken, or partially configured. Update service status. Poll a service to update the service topology map with the current status and alarms. View and manage service related alarms for network elements along the service path. View real time operational status of xSTP rings. Remove services.
Page 23 of 42
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. PolyViews 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. Spanning Tree allows a network design to include spare (redundant) links for automatic backup paths, needed for cases in which an active link fails. The backup paths can be included with no danger of bridge loops, or the need for manual enabling/disabling of the backup links. Bridge loops must be avoided since they result in network flooding. Users can choose between the Fast Ring RSTP and the standard RSTP protocols as defined in IEEE 802.1D. RSTP and Ring RSTP algorithms are designed to create loop-free topologies in any network design, which makes it sub-optimal to ring topologies.
End-to-end TDM trail management

PolyViews end-to-end trail management allows comprehensive trail definitions and configuration of trail properties and status information such as alarms, operational status and performance monitoring. GUI based TDM trail management The TDM trail GUI simplifies configuration and management of TDM trails, providing access to all trail parameters: Add trail protection to an unprotected trail. 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, or schedule recurring reports using PolyViews command line report interface. View trail related alarms. Poll trails to update the trail map with current availability and alarm status data.
Page 24 of 42
Automatic provisioning of TDM trails Wizard based provisioning wizard automates configuration of TDM trails. PolyViews auto discovery searches for the most efficient trail between two selected end points. PolyView calculates the trail path using information from the network elements. Links between network elements along the target trail must be discovered and TDM enabled for the system to automatically provision a TDM trail.
Performance management
Scheduled polling allows users to store historical data and to monitor network level activity in near real time. CeraMap reporting interface is designed to help users identify activity patterns and anticipate problems before they occur. Report specific filters allow for customized report generation. Inventory and performance reports can be generated for the entire network, or for a selected subnet, group, trail, or service. In addition to the built-in reports, the Service view reporting interface displays Ethernet service and TDM trail status information.
Inventory management
PolyView retrieves inventory information from all managed network elements. Inventory data is available to users via 14 built-in predefined reports. Inventory reports provide information about Ceragon interfaces and links in the system.
Performance monitoring
Comprehensive PMs for network entities are available via the built in Performance reports. Performance reports provide information about radio, interface, and trail performance.
Security
PolyView is a secure system that enables administrators to control who uses the system, and which parts of the system can be accessed. Security is maintained by a combination of user access control features, audit logging, and secured interfaces. Permissions are assigned to groups on a feature by feature basis. User access rights determine which parts of the network a user can view, and which operations users can perform for each subnet.
Page 25 of 42
User access control

User access configuration determines which parts of the network a user can view, and which operations users can perform for each subnet. In effect, user access rights create a personalized view of the network for each user. Personalize view per user Network topology and service maps are saved in the database per user. When network operators open their clients, they see only the map for the network where theyve been granted access. Discovery and configuration scope, alarm lists, traffic service management, and reports are all limited to the IP range and subnets where users have access rights. For example, 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. 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. Users are assigned to one group per subnet; however, they may be assigned to a different group with different permissions for each subnet. Permissions are configured on a feature by feature basis for each group. Password security configuration Administrators can enforce password security by enabling minimum password length, password complexity, and password aging. By default, passwords must be at least eight characters long and must include a mix of alphanumeric characters and case. The default interval for password expiry is one month. New passwords cannot repeat any of the previous five passwords. Password compliance is enforced. PolyView will not accept a user password that does not meet all the configured restrictions. Password rule settings can be modified by an Admin network administrator. Passwords information is encrypted on the database.
Page 26 of 42
Single sign-on to EMS web clients PolyView supports single sign-on with IP-10 CeraWeb EMS. User name and password for single sign-on are assigned to groups. Login information to EMS users is assigned to groups that define which operations users will be able to perform on managed network elements. For single sign-on with network elements, users must be granted access rights to the subnet where the network element is located, as a user of a group with silent login privileges. Remote user authentication PolyView uses RADIUS protocol for remote user authentication. When enabled, users must be authenticated by RADIUS server by using the embedded RADIUS client on the PolyView server.
Audit logging
Monitoring and managing connected NMS users Admin users can view actions performed by connected users. The connected users report displays the user name, the IP address of network element on which an action is being performed, 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. The log records details about each operation performed by every system user. The User action log displays the username, location, and details about the operation that was performed. When CeraWeb is connected to the network elements via PolyView, CeraWeb operations will be included in the user action log.
System administration
Task scheduler
PolyViews task scheduler allows network administrators to set up recurring tasks such as database checks and automatic database backup. While PolyViews command line interface only allows specific, PolyView supported executables, CeraMaps task schedule allows users to set up customized executables as recurring tasks. Ceragon recommends adding database and configuration backup as daily tasks. Database backup and repair can also be performed using PolyViews command line interface.
Database management
PolyView stores performance monitoring data, network element inventory, alarm and user action history, map topology, user definitions, and configuration backups for all network entities. The system is preconfigured with recommended but customizable - log limits. Polling data, alarm history and user action logs are stored for a userspecified period of time in the server database. Configuration backup saves the four most recent snapshots. Network map topology, alarm triggers, and scheduled tasks are saved per user.
Server redundancy and synchronization

PolyView has built-in support for server redundancy. When redundancy is enabled, network operators can configure redundancy thresholds and synchronization options. By default, data is synchronized from the primary to the secondary server. The administrator can also set the synchronization for both ways, or disable it altogether.
System specifications
Minimum hardware requirements
Component
Hardware type Processor Memory (RAM) Available drive space Operating system Ethernet ports
Windows requirements
Any type Core 2, 2.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
Page 28 of 42
Hardware capacity recommendations

Number of managed network elements
Up to 5,000 network elements Up to 7,000 network elements Up to 7,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, Oracle (Sun) SPARC server Client only support Windows 7
Supported protocols
SNMP V1 / V2C / V3 CLI / SSH-2 HTTP / HTTPS FTP / SFTP
Page 29 of 42
Supported network elements

IP-10
Marketing version
I6.0 I6.1 I6.2 I6.2.5 I6.2.6 I6.3 I6.3.1
Software version
1.4.5.2 2.7.12 2.8.25 2.8.32 2.8.33.0 2.9.6 2.9.9
Remarks
Upgrade only.
IP-10G
Marketing version
I6.5ca1 I6.5ca1 I6.6ca1 I6.6ca1 I6.6ga I6.6.1 I6.6.2 I6.7
Software 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 6.7.0.0.0.93
Remarks
Upgrade only Upgrade only
IP-10E
Marketing version
I6.7
Software version
6.7.0.0.0.93
Remarks
Page 30 of 42
FibeAir 1500 family

Product
1500 1528 1500A 1500AL 1528A 1500P (I5, S5, G5) 1500P (I5, S5, S5 Quad G5) 1500R 1500R 1500R 1500R Quad 3200T 640P 4.95 5.10 S6.0 S6.5 S6.6 S6.6 T5.0 4.95s19 5.10n1 SFD_6.00c3.sfd SFD_6.50e2.sfd SFD_6.60c3.sfd SFD_6.60c3.sfd SFD_5.00a71a I5.28 I-528f
Marketing version
Software version
FibeAir 2000/4800 family

Product
FA2000 FA4800
Marketing version
2.5 1.9.35
Software version
2.5.00_b2650 1.9.35_b1845
3rd party supported elements

Manufacturer Product
ECI BG-20B
Software version
V12.0.45
Page 31 of 42
License requirements
Description
PolyView Software + License for 20 network elements License for 21-100 network elements, per NE License for 101-500 network elements: per NE License for redundant PolyView support mySQL Enterprise Server 5.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
Page 32 of 42
Appendix A PolyViews server redundancy

PolyViews redundant server configuration
PolyView has built-in support for redundancy configuration. A redundant configuration includes two PolyView servers: a primary server, which is generally active, and a secondary server, which is generally located at a geographically remote site and is in standby mode.
Synchronizing server databases

Redundancy requires that databases in both servers remain synchronized: topology changes, including adding and deleting network elements, must be synchronized across both databases. By default, data is synchronized from the primary to the secondary server. The administrator can also set the synchronization for both ways, or disable it altogether.
Activation conditions for a standby server

If the main server is down, the standby server can be configured to automatically take over. The standby server becomes active when the main server crosses user specified thresholds, or if it loses connectivity with the main server. When the main server starts again after a failure, the secondary server returns to standby mode. Lost connectivity between the two servers could mean that the main server is unavailable, but it could also create a situation where both will become active. If the synchronization mode is both ways, when connectivity is restored, the main server will get the current topology map from the standby server. When the synchronization mode is from main to standby, no synchronization action will be performed when the main server becomes active again. In all cases, switching to the standby server raises an alarm, and gives users the option to switch back to the primary server.
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, the secondary (standby) server becomes active, and will: Start sending traps and triggers. Start accepting client connections. Raise the management alarm No Connection with Main Server. Start polling network elements.
Page 33 of 42
When the connection is resumed and is stable: The main server clears the No Connection with Standby Server alarm. If in Auto mode, the secondary (standby) server will go to standby mode, and will: Clear the management alarm No Connection with Main Server Notify about new client connections, and send the message Main server (IP) is active to connected clients. Stop sending traps and triggers. Resume limited polling (by default, in standby mode, the secondary server polls only alarms). When a security file is updated, the standby server reloads the file, and immediately begins to use it. Network elements should be configured to send traps to both servers.
Page 34 of 42
Appendix B PolyView predefined report types

Performance reports
Interface performance reports
Shows performance parameters for line (E1 / DS1/ STM-1 / OC-3) interfaces.
Radio Ethernet performance report

Displays Ethernet service performance parameters.
Page 35 of 42
TDM trail performance reports

Displays performance data for TDM trails. If TDM trail path protection is enabled, the system performs measurement on both the primary and secondary paths.
Inventory reports
Available interfaces for PM report
Shows which network element interfaces are enabled for performance monitoring.
Page 36 of 42
In-band report
In-band status is a way to manage the network.
Interface report
Displays information about all the interfaces on the unit.
Page 37 of 42
Interface availability report

Shows which network element interfaces are enabled.
Licensing report
Provides data about which licenses are enabled for each network element.
Page 38 of 42
Link report
Provides data about links, such as transmit and receive frequencies and slot number locations.
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.
Page 39 of 42
Protection report
Provides data about protected configurations in the network.
Radio report
Provides status information of outdoor units.
Page 40 of 42
Serial numbers report

Shows the serial number for each network element.
Slot population report

Reports which IDUs are inserted in each slot.
Page 41 of 42
Versions report
Provides data about which software versions are installed on network elements.
xSTP report
Provides data about active and inactive xSTP paths.
Page 42 of 42

PolyView Technical Description N6 7 (Rev A)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PolyView Technical Description N6 7 (Rev A)

Uploaded by

Copyright:

Available Formats

PolyView system N6.7.0.0.

Rev A 14 June 2011

PolyView system N6.7.0.0.0

Open source statement

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

System architecture .......................................................................................... 15

PolyView system N6.7.0.0.0

System specifications ....................................................................................... 28

Appendix A PolyViews server redundancy ................................................... 33

Appendix B PolyView predefined report types .............................................. 35

PolyView system N6.7.0.0.0

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

PolyView Network Management System (NMS) System overview

PolyView system N6.7.0.0.0

PolyView features overview

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Global fault management

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Network element configuration management

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Network performance management

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

End-to-End Ethernet services management

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

End-to-End TDM trail management

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Network security management

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

PolyView System network integration

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

PolyView server components

FTP/ TFTP server

XML & HTTP proxy

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

CeraMap client GUI

Network topology maps

Navigator panel topology tree

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

CLI report interface

SNMP southbound interface

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Adding network elements to a network topology map

Network auto discovery

Ceragon Proprietary and Confidential

PolyView system N6.7.0.0.0

Grouping and linking network elements

Network hierarchy and the Navigator topology tree

Ceragon Proprietary and Confidential