Professional Documents
Culture Documents
End-to-End
Network
Management
Product Description
Registered TradeMarks
Ceragon Networks®, FibeAir®, and CeraView® are registered trademarks of Ceragon
Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
TradeMarks
CeraMapTM, ConfigAirTM, PolyViewTM, EncryptAirTM, CeraMonTM, EtherAirTM, and MicroWave
FiberTM, are trademarks of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
Statement of Conditions
The information contained in this document is subject to change without notice.
Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or
consequential damage in connection with the furnishing, performance, or use of this
document or equipment supplied with it.
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer
could void the user’s authority to operate the equipment and the warranty for such equipment.
Management Reports..................................................................................................9
Security ......................................................................................................................11
PolyView - Total Network Management
PolyView is Ceragon’s powerful yet user-friendly NMS (Network Management System) that can be used in
systems that do not have an NMS. It can also integrate with other NMS platforms (HP OpenView, SNMPc).
PolyView provides management functions for Ceragon’s FibeAir systems at the network level, as well as at
the individual network element level.
PolyView configuration and monitoring operations include:
! Performance Reporting
! Inventory Reporting
! Software Download
! Configuration Management
! Trail Management
! Viewing Current Alarms (with alarm synchronization)
! Viewing Alarm Logs
! Creating Alarm Triggers
Features
! Integrates with other NMS platforms (such as HP OpenView), and the OS on which the NMS system
runs
● PolyView framework - the foundation on which all PolyView applications and services run
● PolyView database - a centralized SQL-based database
● NMS plugable API interface - the connection between PolyView and the NMS
● PolyView applications
PolyView integrates with other NMS platforms (such as HP OpenView), and can also operate in systems that
do not use an NMS platform.
The following illustration shows the PolyView system and how it integrates with other NMS platforms in the
network.
A set of APIs are used to communicate with the host NMS platform, to provide iconic map functions and
alarm browsing.
In host NMS environments PolyView is launched whenever a Ceragon equipment element in the map is
selected. In systems without an NMS platform, PolyView is launched independently from a command line.
To obtain up-to-date information about Ceragon elements in the network, PolyView uses a Data Collector,
which polls the elements periodically and updates the database whenever necessary.
Root
A B
A1 A2 B1 B2
If the Root is selected, for some operations (such as software download), all relevant Ceragon elements in the
system will be affected by the specified operation.
If element A is selected, the operation will apply to A, A1, and A2. It will not apply to B, B1, and B2. For
the operation to apply to B and its sub-elements, both A and B must be selected.
If A1 or B1 are selected, the operation will include only A1 or B1 and all sub-elements related to them.
When you select a network element and invoke the PolyView or CeraMap Configuration Utility, you can set
different parameter values that will affect the element you choose and its sub-elements.
The parameters you can configure include historical user action storage time, polling intervals, redundancy
settings, and many others.
Different design windows enable you to define elements, link them, and group them.
If an element you selected for software or configuration download includes sub-elements, the download will
apply to all the sub-elements as well.
By default, data required for proper server operation (such as topology and security information) is
synchronized from the primary to the secondary server.The administrator can also set the synchronization for
both ways, or disable it altogether.
Security is obtained by creating users and user groups with designated access rights to the different
PolyView components.