PolyView User Guide N6.8

PolyView N6.
8
NMS User Guide
DOC-00008492 (Rev A) March 2012
Copyright 2012 Ceragon Networks Ltd. All rights reserved.
www.ceragon.com
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 opera te the equipment and the warranty for such equipment.
Contents
1 2 PolyView system overview ..................................................................................................1 Getting started ......................................................................................................................2 2.1 Logging in to the NMS ........................................................................................... 2 2.2 Launching CeraMap .............................................................................................. 2 2.3 Preparing the network for system management .................................................... 3 Designing network topology maps ...................................................................................36 3.1 Configuring map display settings ......................................................................... 36 3.2 Adding network elements .................................................................................... 38 3.3 Adding symbols to network topology maps .......................................................... 48 3.4 Adding labels to network elements ...................................................................... 50 3.5 Creating groups of network elements .................................................................. 51 3.6 Creating links between map entities .................................................................... 53 3.7 Moving network elements .................................................................................... 55 3.8 Modifying map entities ......................................................................................... 55 3.9 Deleting map entities ........................................................................................... 56 3.10 Backing up network topology data ....................................................................... 56 Managing mapped devices ................................................................................................58 4.1 Global administration of network elements .......................................................... 58 4.2 Topology tree ....................................................................................................... 58 4.3 Discover node ...................................................................................................... 58 4.4 Poll node.............................................................................................................. 59 4.5 Testing for connectivity to network elements ....................................................... 61 4.6 Finding network elements .................................................................................... 62 4.7 Launching a network elements EMS ................................................................... 62 4.8 Working with multi-radio network elements ......................................................... 63 Fault management..............................................................................................................64 5.1 Configuring alarm settings ................................................................................... 64 5.2 Viewing alarms .................................................................................................... 65 5.3 Managing alarms ................................................................................................. 69 5.4 Configuring alarm triggers ................................................................................... 72 5.5 Trap forwarding.................................................................................................... 86 Configuration management ...............................................................................................91 6.1 Broadcasting network element configurations ..................................................... 91 6.2 Software and configuration archive file locations ............................................... 116 6.3 Backing up and restoring configuration archive files .......................................... 116 6.4 Downloading and installing software versions ................................................... 119 Performance management ..............................................................................................121 7.1 Configuring report settings ................................................................................. 121 7.2 Generating performance reports ........................................................................ 123 7.3 Performance report examples ........................................................................... 125 7.4 Generating inventory reports ............................................................................. 134 7.5 Inventory report examples ................................................................................. 135 7.6 Link utilization report .......................................................................................... 142 7.7 Customizing report data presentation ................................................................ 143 End-to-end traffic service management .........................................................................149 8.1 8.2 Service view ...................................................................................................... 149 End-to-end Ethernet service management ........................................................ 149
9 10
8.3 End-to-end TDM trail management.................................................................... 169 Security management ......................................................................................................186 9.1 Monitoring and managing user actions .............................................................. 186 System administration .....................................................................................................189 10.1 Scheduling tasks................................................................................................ 189 10.2 Database management ..................................................................................... 190 10.3 System maintenance ......................................................................................... 192 Reference ..........................................................................................................................202 11.1 11.2 11.3 11.4 11.5 11.6 11.7 11.8 11.9 CeraMap keyboard shortcuts ............................................................................. 202 Alarms ............................................................................................................... 202 Command line interface (CLI) ............................................................................ 211 CLI report interface ............................................................................................ 212 PolyView northbound interface .......................................................................... 223 Server redundancy ............................................................................................ 230 SNMP MIB support ............................................................................................ 236 PolyView support for floating IP addresses ....................................................... 239 Reports .............................................................................................................. 242
11
NMS User Guide PolyView N6.8
PolyView system overview
PolyView 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. CeraMap, PolyViews client interface 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 services and TDM trails. Service view provides Wizard based provisioning, service topology maps, and GUI driven configuration of service paths. 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, TDM trails, and Ethernet services, are color coded, with the color indicating the status of the most severe current alarm. Configuration management PolyView simplifies network elements configuration management, with centralized configuration file backup and rollback. PolyViews configuration broadcast 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 network element 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.
Page 1 of 271
Getting started
2
2.1
Getting started
Logging in to the NMS
To start PolyView :
Change to the PolyView directory and run pvstart.
2.2
Launching CeraMap
To launch CeraMap:
1. Run pvmap, select Start > Programs > PolyView > CeraMap or double click the desktop's CeraMap icon. 2. Enter your user name and password, and click OK to login.
Page 2 of 271
Getting started
2.3
2.3.1
Preparing the network for system management

Server configuration
2.3.1.1
Configuring server memory usage
To configure server memory usage:

1. Open the PolyView server config application. Select Start > Programs > PolyView > PolyView Server Config or in CeraMap, select Settings > Server configuration from the CeraMap menu.
2. Select the Advanced tab.
Page 3 of 271
Getting started
3. Specify the maximum number of network element polling tasks that the server can run simultaneously. In the Max concurrent tasks field, specify between 6-100 simultaneous tasks.
4. Specify the maximum amount of memory the application can allocate. In the Max memory allocation field, specify how many MB of memory to allocate to the application. The minimum is 256 MB, the maximum is 8192 MB. For large scale networks, increase the Max Memory Allocation size to ~1/3 the total memory in the computer. For example, if the computer is fitted with 2GB memory, set this value to around 700MB.
5. Specify the minimal amount of free disk space. In the Threshold of free disk space field, specify the low disk space threshold below which an alarm will be generated.
6. Specify the system load threshold. In the Threshold of average CPU load field, allow up to 100 processes to be waiting for CPU before generating an alarm.
7. Click Apply. 8. Click Close to exit the PolyView server config utility.
2.3.1.2
Configuring the SMTP mail server
To configure the SMTP mail server:

Page 4 of 271
Getting started
2. Select the General tab.
3. Specify the IP address or hostname of the email server. In the SMTP (email) server address field, specify the mail servers IP address.
2.3.1.3
Configuring the server time zone
To configure the application time zone:

Page 5 of 271
Getting started
3. Specify the time zone to be used. 4. In the Application time zone field, specify the servers time zone. You only need to specify the zone if the application time is not calculated correctly. If the time zone is already configured correctly, you can leave this field empty. The format is GMT+/-<offset> with no spaces between the parameters, for example: GMT+2.
5. Click Apply to save changes. 6. Click Close to exit the PolyView Server config utility.
2.3.1.4
Restoring server configuration defaults
To restore PolyView server defaults:

1. Open the PolyView server config application. Run pvconfig, select Start > Programs > PolyView > PolyView Server Config or in CeraMap, select Settings > Server configuration from the CeraMap menu.
2. Click Restore defaults to reset configuration parameters to their original values. 3. Click Apply to save changes. 4. Click Close to exit the PolyView server config utility.
Page 6 of 271
Getting started
2.3.2
2.3.2.1
Proxy configuration
Configuring ENM and HTTP proxy settings
To configure the ENM and HTTP proxy settings:

3. Allow the NMS to act as a proxy server when the ENM doesn't have direct access to a network element. In the Enable ENM proxy field, select True. Note that to enable this option, the ENM must be capable of working via a proxy.
4. Allow the NMS to act as a HTTPS proxy server when the web browser doesn't have direct access to a network element. In the Enable HTTP(S) proxy field, select True. Note that you must also configure your web browser to recognize PolyView as a proxy server.
Page 7 of 271
Getting started
2.3.2.2
Configuring client browser proxy settings
For each browser that will be used to manage network elements:

1. Open a browser window. 2. Select Internet options from the Tools menu. 3. Select the Connections tab. 4. Click LAN Settings. 5. In the Proxy Server area, select Use a proxy server for your LAN. 6. In the address area, specify the address of the machine on which the web proxy server is installed. 7. For Port, enter 8080 (or a different port number if configured otherwise in the web proxy server).
2.3.3
2.3.3.1
File transfer settings

Configuring FTP login information
To configure FTP login information:

2. Select the File Transfer tab.
Page 8 of 271
Getting started
3. Specify the IP address or hostname of the FTP server. In the FTP server address field, enter the IP address of the FTP server.
4. Specify the FTP server user name and password. In the FTP server username field, specify the FTP username to be used for communication with the PolyView server during automatic upgrade of the CeraMap client software.. In the FTP server password field, specify the FTP password to be used for communication with the PolyView server during automatic upgrade of the CeraMap client software.. Make sure that the user name and password match the login information on the FTP server.
NOTE:
2.3.3.2
Configuring the FTP protocol
To configure the FTP protocol

3. Specify the file transfer server protocol. In the FTP server protocol field, choose FTP or SFTP.
Page 9 of 271
Getting started
2.3.3.3
Configuring TFTP login information

Login information for the TFTP server must match TFTP login information in PolyView.
To configure TFTP login information:

3. Specify the IP address or hostname of the TFTP server. In the TFTP server address field, enter the IP address of the FTP server.
2.3.3.4
Configuring the TFTP files location
To configure the FTP protocol

Page 10 of 271
Getting started
3. Specify the path to network element software files. In the TFTP files location field specify a relative or absolute path to network element software files.
The folder name cannot contain spaces.
2.3.3.5
Configuring TFTP retries and timeout
To configure TFTP login retries and timeout:

Page 11 of 271
Getting started
3. Specify how long to block users after reaching the maximum number of failed login attempts. In the TFTP timeout field, specify how many seconds to wait before allowing blocked users to login again.
4. Specify the maximum number of allowed retries before initiating a TFTP timeout. In the TFTP retries field, specify between 2-7 allowed login attempts before timing out the user.
2.3.4
2.3.4.1
Port settings
Configuring the TCP port
To configure the servers TCP port:

Page 12 of 271
Getting started
3. Define which TCP port the server should use to listen to CeraMap clients. In the NMS server TCP port number field, specify the TCP port number.
To enable TCP communication in a redundant system:

1. Open the client configuration utility. Select Start > Programs > PolyView > CeraMap Client Config, or select Settings > Client configuration from the CeraMap menu.
Page 13 of 271
Getting started
2. Click the Remote Hosts tab.
3. Specify the TCP listening port of the primary server. In the Primary NMS server TCP port number field, specify the primary TCP listening port number. The value of this parameter should match the value configured for the NMS server TCP port number parameter on the primary server.
4. Specify the TCP listening port of the secondary server port. In the Secondary NMS server TCP port number field, specify the secondary TCP listening port number. The value of this parameter should match the value configured for the NMS server TCP port number parameter on the secondary server.
5. Click Apply. 6. Click Close to exit the CeraMap Client config utility.
2.3.4.2
Configuring the user actions logger port
To configure the user actions logger port:

Page 14 of 271
Getting started
3. Specify the port number for logging user actions. In the User actions logger port number field, specify which port to use for logging user actions.
2.3.4.3
Configuring the ENM proxy port
To configure the ENM proxy port:

Page 15 of 271
Getting started
3. Specify which PolyView port to use for receiving proxy requests. In the ENM proxy port number field, specify the ENM proxy port number.
2.3.4.4
Configuring the HTTP proxy port
To configure the HTTP proxy port:

Page 16 of 271
Getting started
3. Specify which PolyView port to use for receiving HTTP proxy requests. In the HTTP proxy port number field, specify the HTTP proxy port number.
2.3.4.5
Configuring the trap listening port
To configure the trap listening port:

1. Open the PolyView trap forwarding utility. Select Start > Programs > PolyView > Trap forwarding config, or select Settings > Trap forwarding options from the CeraMap menu.
Page 17 of 271
Getting started
3. Specify the trap listening port. In the Trap listening port field, specify which port to use for listening to network element traps. The standard port is 162. Change this number if it is already being used by another SNMP service.
4. Click Apply to save changes. 5. Click Close to exit the Trap forwarding config utility.
2.3.4.6
Configuring the management alarms port
To configure the management alarms port:

Page 18 of 271
Getting started
3. Configure the management alarms port. In the Management alarms port field, specify which port to use for sending management alarms to the trap forwarding hosts.
2.3.5
2.3.5.1
Database configuration
Configuring access to the MySQL database
The Server works with the MySQL database, which requires a user name and password. This procedure enables you to define and modify the user name and password to access the database.
To specify database login parameters:

1. Open the PolyView server security application. Select Start > Programs > PolyView > PolyView Security or in CeraMap, select Settings > Security settings.
2. Click the Database parameters tab.
3. Provide a user name and password for access to the database, and click Apply.
2.3.5.2
User action log settings
To configure the User Actions log:

Page 19 of 271
Getting started
3. Specify how long to keep user action history records. In the Keep actions history field, configure the server to store user actions for 5365 days.
2.3.5.3
PM history settings
To configure the PM history levels:

Page 20 of 271
Getting started
2. Select the Polling tab.
3. Specify how long to keep performance monitoring reports data in the database. In the Keep PM history field, configure the server to keep performance monitoring data for up to 366 days.
2.3.5.4
Alarms history settings
To configure the alarms history levels:

2. Select the Alarms tab.
Page 21 of 271
Getting started
3. Specify how long to keep alarm log history data in the database. In the Keep alarms history field, configure the server to keep alarm log history for between 5-365 days. Note that alarms that are open (raised) will be kept until they are closed, regardless of the value you set for this option.
2.3.6
Defining users and groups To configure users and groups:

2. Right click the Users item to add a new user. You can also copy or import existing user definitions. 3. Right click the Groups item to add a new group. 4. Open a group and double click the Features item for that group to grant feature by feature permissions to the group. 5. Configure user password settings. 6. Configure user access rights by assigning users to a specific group for each allowed subnet. 7. Save user definitions or update user configurations to the server.
2.3.6.1
Adding users
There are three ways to add users to the system: you can add users individually, copy an existing user configuration, or import user definitions.
To add a new user:

2. Select Edit > Add user or right click the Users item and choose Add user from the context menu. 3. Enter the new users name and password in the fields at the top of the window. 4. In the Access by subnet area, assign permissions to the user. 5. Click OK to add the new user.
Page 22 of 271
Getting started
2.3.6.2
Importing user definitions
To import user definitions:

2. Select File > Import users to import existing user definitions from a file.
2.3.6.3
Copying an existing user
To copy user definitions:

2. Expand the Users list. 3. Right click the user you wish to copy and select Copy User from the context menu.
4. Enter the new users name and password, and click OK. A new user will be created with the same access rights as the user you chose to copy.
2.3.6.4
Deleting users
To delete a user:
2. Expand the Users list, and right click the name of a user you want to work with. 3. Select Edit > Delete user or right click the user and select Delete user from the context menu. Note that you cannot delete the Admin user.
2.3.6.5
Exporting user definitions

You can export your user configuration for EMS applications or for different PolyView session.
Page 23 of 271
Getting started
To export user definitions:

1. Open the PolyView server security application.
Select Start > Programs > PolyView > PolyView Security or in CeraMap, select Settings > Security Settings.
2. Select File > Export users to save user definitions to a file.
2.3.6.6
Adding groups
To add a group: 1. Open the PolyView server security application. Select Start > Programs > PolyView > PolyView Security or in CeraMap, select Settings > Security settings.
2. Right click the Groups item and choose either Add read-only group or Add readwrite group from the context menu. 3. In the Enter group name window, enter a name for the new group, and click OK to add the group.
2.3.6.7
Copying groups
To copy group definitions:

2. Open the Groups item and select a group. 3. Select Edit > Copy group or right click the group instead and chose Copy group from the context menu. 4. Enter the groups name, and click OK. A new group will be created with the same permissions as the group you chose to copy.
2.3.6.8
Renaming groups
To rename a group:
2. Open the Groups item and select a group. 3. Select Edit > Configure group or right click the group and chose Configure group from the context menu. 4. Rename the group and click OK. Note that you cannot rename the Admin group.
Page 24 of 271
Getting started
2.3.6.9
Deleting groups
To delete a group:
2. Open the Group item and select a group. 3. Select Edit > Delete or right click the group and select Delete group from the context menu. Note that you cannot delete the Admin group.
2.3.7
Configuring user access

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 using a combination of user access control features, audit logging, and secured interfaces. PolyView's security configuration utility allows you to create customized views of the network for each user. User access rights determine which parts of the network a user can view, and which operations users can perform.
Permissions are defined for each group. User access is defined by subnet for a specific group.
To configure user access control:

1. Grant or deny access to groups on a feature by feature basis. .By default, access to all features is specifically denied, unless changed by the system administrator.
2. Grant users access to specified subnets. Access to all UNIX shell level commands from the NMS application will be restricted according to user and group access rights.
2.3.7.1
Configuring user password settings
To configure user password settings:

2. Select File > Setting to open the password settings configuration window.
Page 25 of 271
Getting started
3. Check the Users can change their own passwords option to enable password configuration. If this setting is not enabled, only the server administrator can change user passwords. When this setting is enabled, a Change user password option will be added to the menus.
4. Check the Users must enter passwords on their first login field to force users to create a new password when logging in for the first time. Clear the checkbox to disable this feature. A password cannot be repeated within the past 5 password changes.
5. In the Password expire time field, specify how often users will be required to change their passwords. The default password aging interval is 30 days. This can be changed to anywhere between 20 and 90 days, or may be disabled.
6. In the Minimum password length field, specify the minimum number of characters for user passwords. By default, passwords must be at least 8 characters long.
7. Check the Password must contain at least one non alphabetic character to enforce password complexity. New passwords will be checked for strength compliance.
8. Click Apply to save your settings.
2.3.7.2
Changing user passwords

If the PolyView administer has allowed users to change their passwords, the system will prompt users to change expired passwords.
To change a user password:

2. Select File > Change user password.

Page 26 of 271
Getting started
3. Enter and confirm the new password. 4. Click Apply to change the password. PolyView will also try to change the password for the user's allowed element managers. Note that for this to work, the Users can change their passwords option must also be enabled in the element manager's security application.
2.3.7.3
Assigning access rights to users

User access rights are determined by both group permissions and subnet. To assign access rights to users, first create groups with the permissions that you wish to allow. Then allow the user access to subnets, as users for a specific group.
To assign access rights to a user:

2. Create a group with the permissions that you wish to enable. 3. Open the Users item and select a user. 4. Select Edit > Configure user or right click the user and choose Configure user from the context menu.
5. In the Access by subnet area, select the subnet that you wish to enable for single sign-on and click Edit to open the User configuration window.
Page 27 of 271
Getting started
You cannot enter the same subnet twice for the same user. If none of the subnets you entered match an IP the user tries to connect to, the user will be denied access to that IP. If more than one subnet matches an IP the user tries to connect to, the group that belongs to the subnet that matches the IP the closest will be used for the IP access. For example, you created the user Joe with the following rights: 172.24.0.0 : Observer, and 172.24.30.0 : Administrator. If Joe requests access to 172.24.30.5, he will be granted Administrator rights for that IP. Even though both subnets you assigned to Joe match the IP he requested, the subnet 172.24.30.0 is closer to the IP than the other one. To obtain default Observer rights for IP addresses that do not match any of the subnets in the list, you need to assign the subnet 0.0.0.0 : Observer to the user, and the subnet mask must also be 0.0.0.0. Whenever a user performs an operation that is not applicable to a specific network element (such as changing the security configuration) access permissions will be calculated by the "Default Access" line (which contains the Subnet IP and Mask equal to 0.0.0.0). If a "Default Access" line does not exist for a user, that user will not be able to access general network features.
6. Assign the user to a group. 7. Click OK to save your settings, and OK again to close the main User configuration window.
2.3.7.4
Granting permissions to groups

When assigning users to groups, you can use one of PolyView's preconfigured groups, or define your own group with customized group access rights.
To configure group permissions:

2. Open the Group item, and then open the group that you wish to configure. 3. Select the group's Features item and choose Edit > Configure permissions or double click the Features item to configure permissions for the group.
Page 28 of 271
Getting started
4. Check components to enable group access to that feature. Clear any checked components to disable group access to that feature.
5. Click OK to save your changes and close the Features window.
Page 29 of 271
Getting started
2.3.7.5
Blocking users after unsuccessful login attempts

You can block users after unsuccessful login attempts to the PolyView and TFTP servers.
Use the PolyView server configuration utility to specify the allowed number of login requests and the timeout period between failed logins. By default, after 4 failed logins, users will be blocked for 5 minutes.
To specify server retries and timeout:

1. Open the PolyView server configuration utility. 2. Select the Security tab.
3. In the Allowed consecutive failed logins field, specify the number of times a user can attempt to login before being blocked. a) After the specified number of login attempts, a management trap will be issued, and the user will not be able to log in again for the amount of time specified by the Block user period. b) Setting this value to 0 will allow an infinite number of login attempts. 4. In the Block user period field, specify the number of minutes to block a user from logging in after reaching the maximum number of failed login attempts. Setting this value to 0 will disable this feature.
5. Click Apply to change the settings. 6. Click Close to close the PolyView server configuration utility.
Page 30 of 271
Getting started
To specify TFTP server retries and timeout:

1. Open the PolyView server configuration utility. 2. Select the File transfer tab.
3. In the TFTP timeout field, specify how many seconds to wait for the TFTP server response before considering a TFTP request as timed-out. 4. In the TFTP retries field, specify the maximum number of allowed login attempts before initiating a TFTP timeout. 5. Click Apply to change the settings. 6. Click Close to close the PolyView server configuration utility.
2.3.7.6
Enabling single sign-on with network element management clients

Synchronize login information with network element EMS to enable single sign on.
To enable single sign-on:

2. Define a group with the permissions that you wish to enable. 3. Open the Users item and select a user. 4. Select Edit > Configure user or right click the user and choose Configure user from the context menu. 5. In the Access by subnet area, select the subnet that you wish to enable for single sign-on and click Edit to open the User configuration window.
Page 31 of 271
Getting started
6. Assign the user to the group that you defined. 7. Enter the user name and password to the web EMS and click OK. Note that the login information must be the same for both the NMS and the EMS.
2.3.7.7
Enabling remote user authentication

Enable remote authentication or restrict all users to local access via security settings in the PolyView configuration utility. PolyView uses the RADIUS server protocol to enable secure, remote authentication. When Radius authentication is enabled:
If the Radius server is available, users will be authenticated by both the local and Radius servers. Note that users must be added to both servers, and the password must be the same on both servers to allow single sign on.
NOTE:
When Radius authentication is disabled:
Users will be authenticated only by the local server.
To enable remote authentication:

Page 32 of 271
Getting started
3. In the Radius authentication time field, select Enable. 4. In the Radius server host field, specify the IP address or hostname of the Radius authentication server. 5. In the Radius server login retry timeout field, specify how many seconds to wait before allowing users to login after reaching the maximum number of failed login attempts. 6. In the Radius server number of login retries field, specify the maximum number of allowed login attempts to the Radius server. 7. In the Radius server secret field, specify the shared secret for external authentication. 8. Click Apply to change the settings. 9. Click Close to close the PolyView server configuration utility.
2.3.7.8
Suspending inactive users

You can protect management channels by configuring the server to suspend inactive users.
To suspend inactive users:

3. In the Inactive client disconnect time field, specify the number of minutes the server should wait before disconnecting an inactive client. Setting this value to 0 will allow inactive clients to remain connected indefinitely. The maximum value is 30,000 minutes.
Page 33 of 271
Getting started
4. Click Apply to change the settings. 5. Click Close to exit the PolyView server configuration utility.
2.3.7.9
Enforcing secured client server connections

You can enhance network security by configuring the server to use only secure connections with clients.
To reject non-secure connections:

3. Set Secured client connection to True. 4. Click Apply to change the settings. 5. Click Close to close the PolyView server configuration utility.
2.3.7.10
Updating user settings
To update the PolyView after configuration changes:

2. Open the Users item and select a user. 3. Select Edit > Configure user or right click the user and choose Configure user from the context menu.
Page 34 of 271
Getting started
4. When you are done, select File > Update NMS server. to update the server with your changes. Note that changing the settings will not affect operations that were already defined before a security change was made.
Page 35 of 271
Designing network topology maps
3
3.1

Configuring map display settings
To specify topology map display settings:
2. Click the General tab.
3. Specify how to display network elements on the topology map. In the Displayed entity name format field, select the format for the element label: name only, IP address only, or both name and IP address.
4. Specify whether or not to display link names on the map. Select Hide Link Name or Show Link Name from the Display link name on map field drop down list
When hidden, you can view the link names via their tooltips.
5. Specify the default width of lines representing links between network elements in the topology map. In the Default link width field, specify between 1-10 pixels as the default width for map links.
6. Specify the color for the map background. In the Map background color field, select the color for the map background through a color choose pallet, specifying HSB values, or specifying RGB values.
7. Click Apply to save changes.

Page 36 of 271
3.1.1
Configuring client user interface language To specify the language used for the application interface:
2. Click the Advanced tab.
3. Select the user interface language for CeraMap. Select English or German from the Select interface language field drop down list
Note that additional languages require a separate software license.
4. Click Apply to save changes. 5. Click Close to exit the CeraMap Client config utility.
3.1.2
Configuring the client time zone To configure the application time zone:
2. Click the Advanced tab.
Page 37 of 271
3. Specify the application time zone. In the Application time zone field, specify the time zone only if the application time is not calculated correctly. If the time zone is already configured correctly, you can leave this field empty.
The format is GMT+/-<offset> with no spaces between the parameters, for example: GMT+2.
3.1.3
Restoring client configuration defaults To restore CeraMap defaults:

2. Click Restore defaults to reset configuration parameters to their original values. 3. Click Apply to save changes. 4. Click Close to exit the CeraMap Client config utility.
3.2
Adding network elements

There are four ways to add network elements to a network topology map: Each method is appropriate for different stages of network management.
Manually adding network elements You 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.
Page 38 of 271
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 your network topology map. Importing map data You can also import saved network topology. Note that importing map data will overwrite any changes that you made after exporting the map data. Using the Auto Add Network Element feature Upon receiving the first trap from an element, PolyView adds it to the map. The element will be added to the root without any link. Note that the element must be configured manually to send traps to PolyView.
NOTE:
3.2.1
Network auto discovery

CeraMap provides auto discovery of network entities, including network elements, subnets, multi-line, multi radio, and protected links. Flexible discovery configuration options allow you to poll a specific subnet, range of IP addresses, or type of protocol.
To start scanning:
1. In the Topology tree, select a group to which all newly discovered elements will be added. 2. Select File > Network auto discovery.
Page 39 of 271
3. Click Add to open the Scope settings window to define the scope of the discovery. 4. Click Discover to start the discovery process.
3.2.1.1
Scope settings
To configure auto discovery scope settings:

1. Select the type of scope you want: IP range or Subnet. For IP range: Specify a range of IP addresses to which the network scan will apply.
For Subnet: Specify the subnets IP address and mask.
In the SNMP parameters tab: 1. Select which SNMP version to use for the discovery scan.
Page 40 of 271
In the Version field, select V1, V2c, or V3.
2. Specify which ports to scan. In the Port field, use the up/down buttons to select the port number of the element you want to include in the scan.
3. Specify the maximum number of login retries. In the Retries field, specify the number of allowed login retries before timing out SNMP requests.
4. Specify the length of the timeout after reaching the login retries threshold. In the Timeout field, specify how many minutes to wait after timing out before allowing a new SNMP request.
For V1 and V2c:
Specify the login information. In the Read community field, specify the login password for the Read community. In the Write community field, specify the login password for the Read community.
Page 41 of 271
For V3:
1. Configure the login information. In the User name field, specify the SNMPv3 user name. In the Password field, specify the SNMPv3 password with at least eight characters.
2. Specify the authentication algorithm. In the Authentication field, select MD5 or SHA. Select None to disable SNMP authentication.
3. Specify the security mode. In the Privacy field, select DES to enable privacy. Select None to disable SNMP privacy mode.
In the HTTP parameters tab: Specify the preferred communication protocol: HTTP or HTTPS.
Page 42 of 271
3.2.1.2
The auto discovery process

The Discovery status area shows the progress of the scan.
To view information about errors that may have been detected during the scan, click the Error log tab. The duration of the discovery process depends on the network size and the connection speed. The time may vary from several minutes to several hours. Newly discovered elements will be added to the group you selected. If a discovered element already exists in the target group or in one of its sub-groups, the original element will be retained, and the discovered one will not be added.
Page 43 of 271
During the process, PolyView will also search for connectivity between elements. Links will automatically be generated for any connected entities that PolyView discovers. If more than two elements are found to be linked, PolyView will create a sub-group for them, and all the linked elements will be moved to that sub-group. You can add more than one range or subnet, by clicking the Add button in the Network auto discovery window.
3.2.2
Adding network elements manually To manually add a network element to a map:

Select Edit > Add network element, press Insert, or right click a group icon in the topology tree or on the map and choose Add network element from the context menu.
Page 44 of 271
In the Add Network Element window: 1. Specify the IP address. In the IP address field, specify the IP address of the element you want to add.
2. Define a network name for the network element. Check the User defined name field, and enter a name for the network element.
3. Choose an icon to represent the map element from the Network elements icon gallery. The element type is determined from the icon that you choose, after investigating the element the icon will be according to the correct type of the element.
4. Configure the SNMP and HTTP settings. 5. Click OK to add the new network element to the map. The new element will also appear in the topology tree on the left. In the SNMP parameters tab: 1. Select which SNMP version to use for the discovery scan. In the Version field, select V1, V2c, or V3.
2. Specify which ports to scan. In the Port field, use the up/down buttons to select the port number of the element you want to include in the scan.
3. Specify the maximum number of login retries. In the Retries field, specify the number of allowed login retries before timing out SNMP requests.
4. Specify the length of the timeout after reaching the login retries threshold. In the Timeout field, specify how many minutes to wait after timing out before allowing a new SNMP request.
For V1 and V2c: Specify the login information. In the Read community field, specify the login password for the Read community. In the Write community field, specify the login password for the Read community.
Page 45 of 271
For V3:
1. Configure the login information. In the User name field, specify the SNMPv3 user name. In the Password field, specify the SNMPv3 password with at least eight characters. In the Authentication field, select MD5 or SHA. Select None to disable SNMP authentication. In the Privacy field, select DES to enable privacy. Select None to disable SNMP privacy mode.
2. Specify the authentication algorithm.
3. Specify the security mode.
Page 46 of 271
In the HTTP parameters tab: Specify the preferred communication protocol: HTTP or HTTPS.
3.2.3
Importing map data To import saved network topology data:

Select File > Import data.
The data will be imported under the currently selected group. If you import an entity that already exists - a network element with the same IP, or a group with the same name, PolyView updates the element attributes from the imported file.
3.2.4
Automatically adding network elements To automatically add network elements that forward traps to the server:
Page 47 of 271
3. Enable or disable automatically adding a new network element to the map as soon as it forwards a trap from an unknown IP address. Select Enable or Disable from the Auto add network element field drop down list.
3.3
Adding symbols to network topology maps

Symbols are icons that represent various network devices, but are not treated as network elements by PolyView.
No polling is performed for symbols. Links can be defined between symbols and other symbols or network elements. You can delete and move symbols the same as with other elements in the map.
To add symbols to a network map:

Select Edit > Add symbol, press Ctrl + S, or right click the map and choose Add symbol from the context menu.
Page 48 of 271
In the Add Symbol window: 1. In the Name field, specify a name for the symbol in the Name field. 2. Check the Show name on map checkbox if you want the name you specified to appear on the map under the symbol. 3. Select a symbol from the Select a symbol icon gallery and click OK. If you want to add a symbol that does not appear in the window, you must copy the graphic file to the symbol folder in PolyView/image/symbols. Only GIF and JPG formats are supported. Symbol files can be grouped in sub-folders in the symbols directory. Symbol file and sub-folder names cannot include spaces. If you want to include spaces in symbol file or sub-folder names, use underscores (_). For example, the file Ethernet_Bridge.gif, will appear as "Ethernet Bridge". Add symbol files only to PolyView. Media files are automatically copied to all PolyView clients.
Page 49 of 271
3.4
Adding labels to network elements

Labels are customizable text strings of up to 80 characters that you can use to document your map.
To add labels to a network element:

Select Edit > Add Text, press Ctrl + T, or right click the map and choose Add text from the context menu.
In the Add Text window: 1. In the Text field, enter the text you want to appear in the map. Each element can include up to 80 symbols. 2. Define the font, color, border, and background options, and click OK. Note that the Sample area may display only part of the actual text. The level of opacity is not shown in the sample, and for border size, only the simple border style will be displayed.
Page 50 of 271
3.5
Creating groups of network elements

Network entities will automatically be arranged on the topology tree according to subnet. For large networks, it is helpful to create additional hierarchy by organizing network entities into groups.
PolyView operates in a hierarchical manner. Most operations apply to the selected network elements, including all the sub-elements in the selection. You can establish visual differentiation between groups by establishing logical naming conventions, choosing different icons for each group, and by defining group backgrounds. You can create an unlimited number of levels in the map by grouping network elements. Groups that you add to the map will also be added to the topology panel on the left. The color of the group element is determined by the alarm severity level of network elements in the group.
To group map elements:

Select Edit > Add group, press Ctrl + G, or right click a group icon in the topology panel or on the map and choose Add group from the context menu.
Page 51 of 271
In the Add Group window: 1. In the Name field, enter a name for the group Group names can be alphanumeric strings, and may contain spaces.
2. In the Select a group icon area, choose an icon to represent the group. 3. Define the background color for the group. a) Check the Define background option.
Page 52 of 271
b) Click the Select... button to browse for a background image. c) Specify the Opacity level of the background image. 4. Click OK to add the new group to the map. The new group will also appear in the topology list in the left panel.
3.6
Creating links between map entities

Links in the map show how elements and groups are connected in the network.
To manually create a link:

Select two elements or groups and press Ctrl +L, select Edit > Add link from the menu, or right click the selection on the map and choose Add link from the context menu.
Page 53 of 271
In the Add Link window: 1. Specify the link end points. Specify the system ID or IP addresses for the linked elements in the End points field.
2. Name the link. Enter a name for the link in the Name field.
Unless you changed the default Display link name on map setting, the link name will be displayed as a tooltip, when you mouseover the link.
3. Define the link width The default width of map links is determined by the settings you defined in the Client configuration utility.
The color of the link will be determined by its alarm severity.

Page 54 of 271
4. Specify the type of link connection and click OK. In the Connections list area, specify the type of link: Radio, Multi radio, Line, Multi line, Protected, or Generic.
3.7
Moving network elements

You can move selected network entities to another group or subnet, by dragging them to a new location on the map or in the topology tree.
To move network elements to a different group:

1. Select the elements to be moved. 2. Select Edit > Move, or right click the element in the topology panel or on the map and choose Move from the context menu.
To select multiple elements, press the Ctrl key while you select.
3. Select a new parent group, and click OK. You can also drag & drop selected elements to a new location. If the elements you want to move have links between them, the links will be moved as well. If the elements have links to other elements that are not to be moved, the links will be deleted.
3.8
Modifying map entities

To view or modify properties of a map element:
Select the element and press Ctrl + Enter, choose Edit > Properties from the menu, or right click map entities and select Properties from the context menu.
For network elements, you can modify: The system name, location, and contact person. The user defined name. The SNMP or HTTP access. Change elements properties
Page 55 of 271
Changing SNMP or HTTP settings will affect only the PolyView database; it doesnt write the change to the element itself. To change a network elements access settings: Broadcast the configuration change. Change elements properties Perform a Poll node operation to update the elements properties.
For groups, you can modify: The name, icon or background color.
For links, you can modify: The link name and IP address of the link end points. Link display parameters such as line width and link type.
For labels, you can modify: The label text, font, color, border, and background options.
For symbols, you can modify: The symbol name and icon. You can delete any map entity except for the root element or the element that represents the PolyView server.
3.9
Deleting map entities

To delete map entities:
1. Select the element you wish to delete and select Edit > Delete, or right click the element and choose Delete from the context menu. To select multiple elements, press the Ctrl key while you select.
2. Click Yes to confirm.
3.10
Backing up network topology data

Map topology can be saved - either to the database or to a file. PolyView stores network topology data in the NMS database, and raises an event alarm to notify you of changes to the configuration. Note that if you use CeraMap to design a network, export the data, running a Discover operation will overwrite any links that you added to your design.
To export network topology data to an external file:

1. Use the topology tree to select which part of the network data to export. Select the root to export the entire network. To save topology data for a specific subnet, select the subnet before performing exporting the data.
2. Select File > Export data to open the Export data window.
Page 56 of 271
3. In the Data types area, clear the checkboxes of any data types you wish to exclude from the export. 4. In the File area, click the Ellipsis button to specify the output destination path and filename. 5. Click OK to export the topology data.
Page 57 of 271
Managing mapped devices
4
4.1

Global administration of network elements
The CeraMap GUI enables centralized administration of all discovered network elements.
View and manage network elements alarms filter network element alarm lists by alarm type, duration, severity, or raise/clear status for any selection of network elements. Perform global configuration operations such as configuration broadcasts and software and configuration downloads. Monitor network element status and performance. Define customized, feature-based access to network elements. Manage TDM trails and End-to-End Ethernet services.
4.2
Topology tree
CeraMaps topology tree provides a logical view of network topology. NMS users can drill down to see and open all the subnets in their view of network, and all of the elements in each subnet.
Selecting a network element in the topology tree highlights the network element on the topology map. Double clicking a network element in the topology tree opens its EMS. Double clicking a subnet in the topology tree opens the subnet topology map.
4.3
Discover node
When an element is first added to the map, PolyView automatically reads the elements information. If you change this information, you can perform a Discover node operation to write the element's most updated properties to the PolyView database. A Discover node operation removes all existing information, including stored reports, with the new data. Discover node operations can be performed only on a single element.
To update a network elements configuration and inventory information:

1. Select the element. 2. Select Tools > Discover node.
Page 58 of 271
3. In the Discover node window, click Apply to rediscover the network element. Poll node retrieves real time performance data for the network element, such as current alarms and network element availability.
4.4
Poll node
You can poll a selection of sub groups or network elements to retrieve current performance and inventory status. PolyView automatically polls all elements every few hours according to user configured polling intervals.
4.4.1
Retrieving network element inventory information

Executing a Poll node operation overwrites previous element inventory information with updated element status adds new alarms and performance monitoring information to the PolyView database.
To force PolyView to retrieve updated information from network elements:

1. Select one or more target elements and select Tools > Poll node. 2. In the Poll Node window, click Apply.
To update the map without polling:

Select File > Refresh or click the toolbars Refresh icon.
Page 59 of 271
4.4.2
Configuring polling intervals To configure polling intervals:

In the Polling tab: 1. Specify how often the server should poll network elements for dynamic inventory data. In the Dynamic polling interval field, specify the number of hours: minutes between dynamic data polling.
2. Specify how often the server should poll network elements for performance monitoring data. In the Reports polling interval field, specify the number of hours: minutes between PM data polling.
3. Specify how often the server should backup configuration files from network elements. In the Config upload interval field, specify the number of hours: minutes between uploading configuration files.
4. Specify how often the server should poll network elements for current alarm data. In the Alarms polling interval field, specify the number of hours: minutes between alarm data polling.
Page 60 of 271
4.5
Testing for connectivity to network elements

Ping and trace route are used to test connectivity between the PolyView server and the network element.
The Ping window lists the attempts made by the server to connect with the element, and other connectivity information, such as the connection speed. The Trace route window displays the routing connectivity to the element (the path the packet takes on its way to the element).
To start a ping operation:

Select an element in CeraMap, and then select Tools > Ping.
To start a trace route operation:

Select an element in CeraMap, and then select Tools > Trace route.
Page 61 of 271
4.6
Finding network elements

CeraMap's Navigator panel displays a hierarchical view of your network topology. You can drill down to see all the subnets in your network, and all of the sub-elements of on that subnet.
To find a network element:

1. Select Edit > Find.
2. Enter the search terms in the Text box. 3. Specify the scope of the search and click Find.
4.7
Launching a network elements EMS

The EMS that opens for a unit depends on the type of unit. IP-10 units open CeraWeb, a browser based EMS. Older units, such as the x1500 series, open the CeraView desktop SNMP EMS. 3rd party units open their proprietary EMS applications.
CeraMap also provides centralized access to network element EMS clients. When single signon is enabled, you can open the EMS for a selected network element from any network topology map, any list of alarms, or any type of report.
To launch an element manager from a report:

Select a report record, and select Actions > Launch element manager, or right click a record and select Launch element manager from the context menu.
To launch an element manager from an alarm:

Select an alarm from the list, and select Actions > Launch element manager, or right click an alarm and select Launch element manager from the context menu.
Page 62 of 271
To launch an element manager from a network topology map:

Double click a network element to launch its element manager, or right click a network element and select Open. Note that double clicking a group opens the group.
4.8
Working with multi-radio network elements

Use discover node to find new (multi radio) network elements and links.
1. Perform Poll node on discovered network elements. 2. Use Ping to verify connectivity.
To add a multi-radio link to two network elements

1. Choose two network elements on a map. 2. Right click and choose Add link to add a link between the selected elements.
To generate an inventory report on network elements with multi-radio links:

1. Select Reports > Inventory reports or click the Inventory reports icon to open the Inventory reports selection dialog. 2. Select Radio report from the drop down list, and click OK to generate the report. 3. Select Report > Filter > Show/hide columns or click the Filter icon and select Show/hide columns from the context menu to open the Filter report by columns value window. 4. Ensure that the Multi RadioAdmin column is set to visible. Check the Multi RadioAdmin checkbox and click OK.
5. Select Report > Filter > Filter by values or click the Filter icon and select Filter by values from the context menu to open the Filter report by columns value dialog. 6. Select Multi RadioAdmin from the Field drop down list.
Page 63 of 271
Fault management
5
5.1
Fault management
Configuring alarm settings
To configure alarm settings:
3. Specify how often the server should poll network elements for current alarm data. In the Alarms polling interval field, specify how often the server should poll network elements for current alarm data.
4. Click Apply. 5. Select the Alarms tab.
Page 64 of 271
Fault management
6. Specify how long to keep alarm log history data in the database. In the Keep alarms history field, configure the server to keep alarm log history for between 5-365 days. Note that alarms that are open (raised) will be kept until they are closed, regardless of the value you set for this option.
7. Select the format you want for email messages triggered by alarms. In the Email format field, select HTML or Plain text.
If you select, HTML, you can use HTML tags to control the way the messages appear.
8. Specify the maximum number of alarms to show in the alarm logs window. In the Max number of initial alarms field, specify between 1000 and 50,000 initial alarms.
Note that while the window is open, new alarms will be added to the alarms log as they are received.
9. Specify whether to acknowledge or ignore the heartbeat traps received from the network elements In the Ignore heartbeat field, select Enable or Disable.
Disable this trap to prevent them from being included with the rest of the forwarded traps.
5.2
5.2.1
Viewing alarms
Viewing current alarms
You can view current alarms or alarm history for the entire network, or for group, subnet, or selection of network entities.
To view current alarms:

1. Select the target network elements from the network topology map or the Navigator topology tree. 2. Select Reports > Current alarms, press ALT + A, click the Current alarms icon, or right click and select Current alarms from the context menu.
Page 65 of 271
Fault management
5.2.2
Viewing top most alarm severity

Alarm severity status is built into the topology GUI. Map entities are color coded according to alarm severity, and are displayed using the color of their top-most alarm. If there is more than one alarm configured for a network entity, the map displays the color of the most severe alarm.
Severity Critical Major Minor Warning Event Normal Unknown / not responding Color Red Orange Light orange Yellow Blue Green Grey
For example, green means that the element is operating with no alarms; while red means that the element is operating with one or more major alarms. Icons in the topology tree also reflect alarm status. The color of upper level groups and the root level will always be the color of the element in the list with the most severe alarm. If a network element is unreachable, it will appear on the map with a line across it.
5.2.3
Viewing alarm details

The Alarm details window provides comprehensive information about a selected alarm.
To view the details of a particular alarm:

1. Open the Current alarms report.
Page 66 of 271
Fault management
Select Reports > Current alarms, press ALT + A, click the Current alarms icon, or right click and select Current alarms from the context menu.
2. Double click an alarm to open its details. The General tab displays the location, description, severity, and status of the selected alarm. When available, the General tab will also provide probable causes and corrective actions to help you clear the alarm.
The User actions history tab displays which actions have been performed on the selected alarm, and by which user. For example, you can see if an alarm has been acknowledged or cleared, or if the user added any messages to the alarm.
The Advanced tab provides additional details to help you resolve the alarm, such as the alarm, trap, and object IDs.
Page 67 of 271
Fault management
5.2.4
Viewing alarm history

The list of current alarms helps identify which items require immediate action. The alarms log helps identify recurring events that may require preventative measures.
To view the alarm log:

1. Select the target network elements from the network topology map or the Navigator topology tree. 2. Select Reports > Alarm log, press ALT + L , click the Alarm log icon, or right click and select Alarm log from the context menu. 3. Specify the start and end dates of the report, and click OK.
Apply relevant filters to help identify recurring patterns or problematic areas of the network. By default, the alarm log is a logical view, meaning that Raise and Clear commands generate a single alarm, and are shown on the same line.
Page 68 of 271
Fault management
At times, it may be easier to view the Alarm Log in a chronological view, with Raise and Clear generated alarms on different lines.
To view the alarm log in chronological order:

1. Open the Alarm log window. Select Reports > Alarm log, press ALT + L , click the Alarm log icon, or right click and select Alarm log from the context menu. Specify the start and end dates of the report, and click OK.
2. Select Actions > Filter > Chronological view.
5.3
5.3.1
Managing alarms
Hiding alarms
Use the Hide button below the list of alarms to hide less critical alarms from the list.
To hide selected alarms:

1. Open the Current alarms report. Select Reports > Current alarms, press ALT + A, click the Current alarms icon, or right click and select Current alarms from the context menu.
2. Select the alarms that you wish to hide and select Actions > Hide or click the Hide icon.
5.3.2
Viewing hidden alarms To view hidden alarms:

2. Select Action > Show hidden to display all alarms that are normally hidden.
Page 69 of 271
Fault management
5.3.3
Acknowledging alarms
Use the Acknowledge and Note buttons below the list of alarms to acknowledge and add messages to an alarm. You can also add notes to alarms that you acknowledge.
To acknowledge an alarm:
2. Select the alarm that you wish to acknowledge. To perform a multiple acknowledgement, select all the alarms that you wish to include.
3. Select Actions > Acknowledge, click the Acknowledge icon, or right click an alarm and select Acknowledge from the context menu.
4. Add a message about the acknowledgement, and click OK to acknowledge the alarm.
5.3.4
Adding notes to alarms To add a message to an alarm:

2. Select an alarm. To add the note to multiple alarms, select all the alarms that you wish to include.
3. Select Actions > Add note, click the Add note icon, or right click an alarm and select Add note from the context menu.
4. Add a message to the alarm, or alarms, and click OK.
Page 70 of 271
Fault management
5.3.5
Filtering the list of alarms

You can filter the list of alarms by hiding entire columns from view, or by defining an explicit filter for a column.
To hide alarm report columns from view:

1. Open the list of alarms that you wish to view. To open the list of current alarms, select Reports > Current alarms, press ALT + A, click the Current alarms icon, or right click and select Current alarms from the context menu. To open the alarm log, select Reports > Alarm log, press ALT + L , click the Alarm log icon, or right click and select Alarm log from the context menu.
2. Select Report > Filter > Show/hide columns.
3. Clear the checkbox of any columns that you wish to hide, and click OK to filter the alarms list.
To filter the list of current alarms or the alarms log:

1. Open the list of alarms that you wish to view. To open the list of current alarms, select Reports > Current alarms, press ALT + A, click the Current alarms icon, or right click and select Current alarms from the context menu. To open the alarm log, select Reports > Alarm log, press ALT + L , click the Alarm log icon, or right click and select Alarm log from the context menu.
2. Select Report > Filter > Filter by value to open the Filter report by column values window. 3. Click Add to define a filter for the list of alarms.
Page 71 of 271
Fault management
4. Specify the Field, the Operator, and Value parameters, and click OK.
To edit a filter you defined:

Select the filter and click Edit.
To delete a filter you defined:

Select the filter and click Delete.
5.4
5.4.1
Configuring alarm triggers

Adding alarm triggers To add an alarm trigger:
1. Select Tools > Trigger configuration. 2. Select Actions > Add or click the Add trigger icon.
Page 72 of 271
Fault management
3. In the Trigger name field, enter a name for the trigger you want to define. 4. Specify the trigger Activation conditions. 5. Specify the trigger Activation operation. 6. Click OK.
5.4.2
Trigger activation conditions

In the Activation conditions section, specify which event will activate the trigger.
5.4.2.1
Trigger events based on NMS management alarms
To trigger events based on NMS management alarms:

Open the trigger configuration utility and add a new trigger. Select Tools > Trigger configuration. Select Actions > Add or click the Add trigger icon.
Page 73 of 271
Fault management
In the Activation conditions section 1. Click Trap Name. 2. Check NMS to filter the list of traps to select a PolyView management trap. 3. Select a trap by name from the Trap name drop down list.
5.4.2.2
Trigger events based on IP-10 generated alarms
To trigger events based on IP-10 generated alarms:

Page 74 of 271
Fault management
In the Activation conditions section: 1. Click Trap Name. 2. Check IP-10 to filter the list of traps to select a network element trap. 3. Select a trap by name from the Trap name drop down list.
5.4.2.3
Trigger events based alarm severity
To trigger events based on alarm severity:

Page 75 of 271
Fault management
In the Activation conditions section: 1. Click Severity. 2. Enable a Severity trigger, by checking the checkboxes for each alarm severity that you wish to include.
5.4.2.4
Trigger events based on specific text in the alarm description
To trigger events when specific characters are detected in the alarm text:
Page 76 of 271
Fault management
In the Activation conditions section: 1. Click Description. 2. Enter the text in the Description field.
5.4.2.5
Trigger events for alarms that remain unacknowledged
To trigger events for alarms that remain unacknowledged:

Page 77 of 271
Fault management
In the Activation conditions section: 1. Check the If was not acknowledged in option to establish a time threshold for alarms that havent yet been acknowledged. 2. In the Minutes text box, specify the number of minutes to wait before triggering the activation operation.
5.4.3
Trigger activation operations

In the Activated operation area, select the operation you want to activate when the alarm occurs.
5.4.3.1
Display a message when an alarm is triggered
To display a message when an alarm is triggered:

Page 78 of 271
Fault management
Specify the activation conditions.
In the Activated operation area: 1. Select Display message from the Operation type drop down list to display a pop up message when the alarm is triggered. 2. In the Sound field, specify the sound to play when the alarm is raised. 3. Click the Ellipsis button next to the Content field to select predefined variables to insert in the text.
Page 79 of 271
Fault management
5.4.3.2
Send email when an alarm is triggered
To send email when an alarm is triggered:

Open the trigger configuration utility and add a new trigger. Select Tools > Trigger configuration. Select Actions > Add or click the Add trigger icon. Specify the activation conditions.
Page 80 of 271
Fault management
In the Activated operation area: 1. Select Send email from the Operation type drop down list. Make sure that the SMTP (email) server address is defined (PolyView server configuration utility, under the General tab).
2. In the Address field, specify the address to which the mail will be sent. 3. Click the Ellipsis button next to the Subject field to select predefined variables to insert in the subject text. 4. Click the Ellipsis button next to the Content field to select predefined variables to insert in the message text. NOTE: To send emails using HTML markup, make sure that in the alarm tab of PolyView configuration utility, the Email format option is set to HTML.
Page 81 of 271
Fault management
5.4.3.3
Run an executable when an alarm is triggered
To run an executable when an alarm is triggered:

In the Activated operation area: 1. Select Run executable from the Operation type drop down list. 2. In the Executable field, specify the path of the executable file you want to run whenever the alarm occurs. 3. In the Parameters field, click the Ellipses button to select parameters to pass to the specified executable.
Page 82 of 271
Fault management
4. In the Execute on field, specify the targets of the operation: NMS server or the system's Connected clients.
5.4.3.4
Auto hide triggered alarms

Note that hiding an alarm from view will not prevent it from being generated and forwarded.
To hide automatically hide specific alarms:

In the Activated operation area: Select Auto hide from the Operation type drop down list.
5.4.3.5
Auto delete triggered alarms
To hide automatically delete specific alarms:

Open the trigger configuration utility and add a new trigger. Select Tools > Trigger configuration.
Page 83 of 271
Fault management
Select Actions > Add or click the Add trigger icon. Specify the activation conditions.
In the Activated operation area: Select Auto delete from the Operation type drop down list.
5.4.3.6
Trigger a trap forwarding filter
To filter the alarms to be forwarded:

Page 84 of 271
Fault management
In the Activated operation area: 1. Select Forward Trap from the Operation type drop down list. 2. Specify all the servers to which the traps will be sent, in the format <host IP>:<port> with a space between each entry.
5.4.4
Managing trigger data To delete an existing trigger:

Select the trigger and click Delete.
To save the trigger list in a file:

Select File > Save as.
To edit an existing trigger:

Select the trigger and click Edit.
Page 85 of 271
Fault management
5.4.5
Configuring trigger message display To specify trigger message display settings:

3. Specify the maximum number of trigger messages to be displayed for the user. 4. In the Max number of trigger messages field, specify between 100 and 5000 the maximum number of trigger messages to be displayed for the user. When the number of triggers exceeds this number, older messages will be deleted. To optimize performance, lines are deleted in batches instead of one by one. Inbetween batch deletions, the actual number of displayed messages may exceed the specified threshold.
Click Apply to save changes. Click Close to exit the CeraMap Client config utility.
5.5
Trap forwarding
PV can forward NMS specific management traps and SNMP traps that arrive from the devices to one or more OSS. Trap forwarding parameters determine how PolyView will work with traps. NOTE: For security purposes, trap forwarding must be configured locally on the PolyView server.
Page 86 of 271
Fault management
To configure trap forwarding:

1. Open the PolyView trap forwarding utility.
Select Start > Programs > PolyView > Trap forwarding config, or select Settings > Trap forwarding options from the CeraMap menu.
2. Specify the trap forwarding parameters. 3. Click Restore defaults to reset configuration parameters to their original values.
Click Reload
4. Click Apply to save changes. 5. Click Close to exit the Trap forwarding config utility. In addition, remember to configure the network elements to send traps to the listening port that you specify here.
5.5.1
Configuring the trap forwarding mode To configure the trap forwarding mode:
3. Specify the trap forwarding mode. In the Trap forwarding mode field, select:
Off to disable trap forwarding. Regular to forward the trap exactly as it was received. NSN to translate the trap for NSNs NetAct application. NSN alarm synchronization to support incoming alarm translation and NSN's NE3S agent.
Page 87 of 271
Fault management
Note: If the mode is set to Regular, NSN, or NSN alarm synchronization, all network elements must send the traps to the port specified in the Trap listening port field. If the mode is set to Off, all network elements must send traps directly to the Management alarms port that you specified in the Advanced configuration tab.
5.5.2
Configuring trap forwarding hosts To configure the trap forwarding hosts:

3. Specify the local host. In the Local host address field, specify the IP address or hostname of the local host. Leave the value 0.0.0.0 to bind all IP addresses.
4. Specify where to forward the traps. In the Forward traps to host field, specify the list of host names and port numbers to which traps will be forwarded. Use the format <host IP>:<port>.
Page 88 of 271
Fault management
5.5.3
Configuring the heartbeat trap interval To configure the heartbeat trap interval:
3. Specify the heartbeat interval. In the Heartbeat interval field, specify the number of minutes between forwarding heartbeat traps from network elements to remote hosts. Setting this value to 0 will disable heartbeat trap forwarding.
5.5.4
Configuring trap severity thresholds To configure the trap forwarding hosts:

Page 89 of 271
Fault management
3. Enable or disable sending cleared traps with zero severity. In the Send cleared traps with zero severity field, select Enable or Disable.
This setting will not affect cleared traps that are forwarded directly from network elements to the trap forwarding hosts.
Click Apply to save changes. Click Close to exit the Trap forwarding config utility.
Page 90 of 271
Configuration management
6
6.1
Broadcasting network element configurations
The broadcast configuration utility allows you to set attributes or modify configuration parameters for selections of network elements according to type of element, subnet, or other common feature.
To configure a network broadcast:

1. Select one or more target and choose Tools > Configuration broadcast or click the Configuration broadcast icon to open the Configuration broadcast utility. 2. Select which product type to configure. Select IP-10 for Ceragon elements. Select x1500 for older Ceragon units. Selecting General applies to all selected network elements.
3. Select what to configure from the Configuration navigation options on the left, or click the Load button at the bottom of the window to load an existing configuration file. 4. Select an action to perform using one of the action buttons at the bottom of the windows. Click Set to implement the settings for the network elements and display the results of your operation. Click Abort to cancel a configuration process that is already in progress. Click Save to save the current configuration to a file.
6.1.1
6.1.1.1
Broadcasting network element configurations for selected devices

Set the current date and time
To set the time and date for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select General. 3. Expand the General group. 4. Check the Current Time checkbox.
Page 91 of 271
In the Current Time section of the Configuration pane: 1. Specify the current date and time. 2. Click Set.
6.1.1.2
Configure alarm thresholds
To set excessive error and signal degrade thresholds:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select General. 3. Expand the Thresholds group. 4. Check the Radio checkbox to specify radio thresholds or the STM1/OC3 checkbox to specify interface thresholds.
Page 92 of 271
In the Radio section of the Configuration pane: 1. Select the level above which an excessive BER alarm is issued for errors detected over the radio link. In the Excessive Error field, select a threshold value from the drop down list.
2. Select the level above which a Signal Degrade alarm is issued for errors detected over the link. In the Signal degrade field, select a threshold value from the drop down list.
3. Click Set. In the STM1/OC3 section of the Configuration pane: 1. Select the level above which an alarm is issued for errors detected over the interface link. In the Excessive Error field, select a threshold value from the drop down list.
2. Select the level above which a Signal Degrade alarm is issued for errors detected over the link. In the Signal degrade field, select a threshold value from the drop down list.
3. Click Set.
6.1.1.3
Configure the trap manager IP address
To configure trap forwarding from selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select General. 3. Expand the Traps group. 4. Check the Managers IP Address checkbox.
In the Managers IP Address section of the Configuration pane: Specify the IP address to which traps will be sent.
Page 93 of 271
Enter the destination IP address for each trap manager that you wish to configure.
6.1.1.4
Specify the trap port

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select General. 3. Expand the Traps group.
In the Trap Port section of the Configuration pane: Specify the sending port. In the Trap port field, specify the port on the trap manager to which the element sends traps.
6.1.2
Broadcasting configuration settings for IP-10 series network elements

Enable NTP
6.1.2.1
To enable or disable NTP for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Network group. 4. Check the NTP checkbox.
Page 94 of 271
In the NTP section of the Configuration pane: 1. Enable NTP. Check the Enable NTP checkbox.
2. Specify the NTP server. In the NTP Server IP field, enter the IP address of the NTP server.
6.1.2.2

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Network group. 4. Check the GMT Time Zone checkbox.
Page 95 of 271
In the GMT Time Zone section of the Configuration pane: 1. Specify the hours and minutes offset from GMT. Offset from GMT is the Hours and Minutes offset of the time of day from Greenwich Mean Time (GMT).
2. Click Set. In the Daylight Saving Time section of the Configuration pane: 1. In the Start Date field, click the calendar to set the date when daylight saving time will automatically be activated. 2. In the End Date field, click the calendar to set the date when daylight saving time will automatically be terminated. 3. In the Offset field, specify the offset time, in hours, from GMT. 4. Click Set.
6.1.2.3
Set alarm thresholds
To set excessive error and signal degrade thresholds for selected E1/DS1 interfaces:
1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Thresholds group. 4. Check the E1/DS1 checkbox.
Page 96 of 271
In the E1/DS1 section of the Configuration pane: 1. Select the level above which an excessive BER alarm is issued for errors detected over the radio link. In the Excessive BER threshold field, select a value from the drop down list.
2. Select the level above which a Signal Degrade alarm is issued for errors detected over the link. In the Signal degrade threshold field, select a value from the drop down list.
3. Click Set.
6.1.2.4
Specify the web protocol
To specify the web protocol for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Security group. 4. Check the Security Parameters checkbox.
Page 97 of 271
In the Security Parameters section of the Configuration pane: 1. In the Web Protocol field, select HTTP or HTTPS. 2. Check or clear the Enable Telnet Protocol checkbox to enable or disable Telnet. 3. Click Set.
6.1.2.5
Apply SNMP settings
To specify the SNMP parameters for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Security group. 4. Check the SNMP Parameters checkbox.
Page 98 of 271
In the SNMP Parameters section of the Configuration pane: Specify the SNMP version. Select V1, V2c, or V3 from the Version drop down list.
For SNMP V1 and V2c: 1. Specify the read and write communities. In the Read Community field, enter the password for the SNMP read community. In the write Community field, enter the password for the SNMP write community.
2. Click Set.
Page 99 of 271
For SNMP V3:
1. Specify the user name and password. 2. Specify the authentication algorithm. In the Authentication field, select MDS, SHA, or None. This field is only configurable if security mode is not set to None.
3. Specify the security mode. In the Privacy field, select
None Authentication (default) Authentication privacy
4. Click Set.
6.1.2.6
Configure login parameters
To specify the login parameters for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Security group. 4. Check the Login Parameters checkbox.
Page 100 of 271
In the Login Parameters section of the Configuration pane: 1. Configure user login settings. Check or clear the Force user to change password upon first login checkbox.
2. Click Set.
6.1.2.7
Reset counters for selected ports
To reset RMON counters for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the PMs and Counters group. 4. Check the RMON Counters checkbox.
Page 101 of 271
In the RMON Counters section of the Configuration pane: Specify which counters to reset. To reset all counters, select Reset counters for all ports. To reset counters for specific ports, select Reset counters for ports, and check the checkbox for each port that you wish to reset.

6.1.2.8
Note that you cannot reset counters for individual ports that are members of a LAG port. The only way to rest counters for LAG port members is to reset counters for all ports. For IP-10C, you can select Ports 1, 2, 3, and 5. For IP-10Q, you can select Ports 1, 2, 3, 4, and 5.
Add users to selected network elements
To add users to selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Users group. 4. Check the Add / Delete User checkbox.
Page 102 of 271
In the Configuration pane: 1. Select Add User. 2. Specify the user privilege level. Select a group from the User privilege drop down list:
Viewer -This user cannot configure parameters, but only view them. Operator-This user can configure all parameters in the system, except for security-related parameters (such as adding privilege groups). Admin-This user has all Operator privileges, as well as the ability to add new users. Tech (technician) - Has all Admin privileges, as well as access to the Linux OS shell.
3. Specify how often the user password should be changed. In the Password aging field, specify the number of days until the user must choose a new password.
4. Specify how long to store the user account on the selected network elements. In the Account Expired field, specify how long to store the user information.
Check the Never Expired checkbox to disable user account expiration.
5. Click Set.
6.1.2.9
Delete users from selected network elements
To delete users from selected network elements:

1. Open the Configuration broadcast utility.
Page 103 of 271
2. In the Navigation panes Select field, select IP-10. 3. Expand the Users group. 4. Check the Add / Delete User checkbox.
In the Configuration pane: 1. Select Delete User. 2. In the User Name field, enter the user name of the user to be deleted from the selected network elements. 3. Click Set.
6.1.2.10
Forward traps from selected network according to alarm type

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Traps group. 4. Check the Send traps for alarms with severity checkbox.
6.1.2.11
Forward only traps with changed operational status

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select IP-10. 3. Expand the Traps group. 4. Check the Trap options checkbox.
Page 104 of 271
In the Trap Options section of the Configuration pane: Select the Send traps on operational status change only option if you want traps to be sent only when the system status changes. In the Trap Options section of the Configuration pane: In the Send traps for alarms with severity area, check the alarm severity levels to include for each manager.
6.1.3
6.1.3.1
Broadcasting network element configurations for older units

Enable NTP
To enable or disable NTP for selected network elements:

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select x1500. 3. Expand the Network group. 4. Check the NTP checkbox.
Page 105 of 271
In the NTP section of the Configuration pane: 1. Enable NTP. Check the Enable NTP checkbox.
2. Specify the NTP server. In the NTP Server IP field, enter the IP address of the NTP server.
6.1.3.2

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select x1500. 3. Expand the Network group. 4. Check the GMT Time Zone checkbox.
Page 106 of 271
In the GMT Time Zone section of the Configuration pane: 1. Specify the hours and minutes offset from GMT. Offset from GMT is the Hours and Minutes offset of the time of day from Greenwich Mean Time (GMT).
2. Click Set. In the Daylight Saving Time section of the Configuration pane: 1. In the Start Date field, click the calendar to set the date when daylight saving time will automatically be activated. 2. In the End Date field, click the calendar to set the date when daylight saving time will automatically be terminated. 3. In the Offset field, specify the offset time, in hours, from GMT. 4. Click Set.
6.1.3.3
Set alarm thresholds
To set excessive error and signal degrade thresholds for selected E1/DS1 interfaces:
1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select x1500. 3. Expand the Thresholds group. 4. Check the checkbox of the interfaces for which you wish to configure threshold levels.
Page 107 of 271
For each section of the Configuration pane: 1. Select the level above which an alarm is issued for errors detected over the interface link. In the Excessive BER threshold field, select a value from the drop down list.
2. Select the level above which a Signal Degrade alarm is issued for errors detected over the link. In the Signal degrade threshold field, select a value from the drop down list.
3. Click Set.
6.1.3.4
Forward traps with specific alarm severity

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select x1500. 3. Expand the Traps group. 4. Check the Send Trap for alarm with severity checkbox.
Page 108 of 271
In the Trap Options section of the Configuration pane: 1. Determine which alarms will be sent as SNMP traps to each manager. In the Send traps for alarms of group list, check each alarm type that you wish the manager to receive.
2. Specify the trap options: Select Standard traps include serial number if you want trap messages to include the IDU serial number. Select Report traps of far end IDU if you want remote IDU trap messages to be reported locally. Select Use different trap ID for each alarm type if you want each alarm type to be reported with a unique ID. Enable Send clear traps with zero severity to send Clear traps with a severity of 0. Disable this option to send Clear traps with the same severity as the equivalent Raised trap. Select Send traps with extended alarm information to include additional alarm details, such as alarm ID, to be added to the end of each radio-related trap.
3. Specify the number of minutes between generating Heartbeat traps from x1500 units to inform the server that the trap mechanism is working. Set this value to 0 to disable heartbeat trap generation. 4. Specify the alarm severity levels of SNMP traps for each manager. In the Send traps for alarms with severity area, check the alarm severity levels you want to include for each manager.
Page 109 of 271
6.1.3.5
Forward traps according to alarm type

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select x1500. 3. Expand the Traps group. 4. Check the Trap Options checkbox.
In the Trap Options section of the Configuration pane: 1. Determine which alarms will be sent as SNMP traps to each manager. In the Send traps for alarms of group list, check each alarm type that you wish the manager to receive.
2. Specify the trap options: Select Standard traps include serial number if you want trap messages to include the IDU serial number. Select Report traps of far end IDU if you want remote IDU trap messages to be reported locally. Select Use different trap ID for each alarm type if you want each alarm type to be reported with a unique ID. Enable Send clear traps with zero severity to send Clear traps with a severity of 0. Disable this option to send Clear traps with the same severity as the equivalent Raised trap. Select Send traps with extended alarm information to include additional alarm details, such as alarm ID, to be added to the end of each radio-related trap.
3. Specify the number of minutes between generating Heartbeat traps from x1500 units to inform the server that the trap mechanism is working. Set this value to 0 to disable heartbeat trap generation.
Page 110 of 271
4. Specify the alarm severity levels of SNMP traps for each manager. In the Send traps for alarms with severity area, check the alarm severity levels you want to include for each manager.
6.1.3.6
Include the serial number in forwarded traps

1. Open the Configuration broadcast utility. 2. In the Navigation panes Select field, select x1500. 3. Expand the Traps group. 4. Check the Trap options checkbox.
In the Trap Options section of the Configuration pane: Select Standard traps include serial number if you want trap messages to include the IDU serial number. Select Report traps of far end IDU if you want remote IDU trap messages to be reported locally. Select Use different trap ID for each alarm type if you want each alarm type to be reported with a unique ID. Enable Send clear traps with zero severity to send Clear traps with a severity of 0. Disable this option to send Clear traps with the same severity as the equivalent Raised trap. Select Send traps with extended alarm information to include additional alarm details, such as alarm ID, to be added to the end of each radio-related trap.
Specify the number of minutes between generating Heartbeat traps from x1500 units to inform the server that the trap mechanism is working. Set this value to 0 to disable heartbeat trap generation.
Page 111 of 271
6.1.3.7
Forward traps for remote IDUs

In the Trap Options section of the Configuration pane: Select Standard traps include serial number if you want trap messages to include the IDU serial number. Select Report traps of far end IDU if you want remote IDU trap messages to be reported locally. Select Use different trap ID for each alarm type if you want each alarm type to be reported with a unique ID. Enable Send clear traps with zero severit y to send Clear traps with a severity of 0. Disable this option to send Clear traps with the same severity as the equivalent Raised trap. Select Send traps with extended alarm information to include additional alarm details, such as alarm ID, to be added to the end of each radio-related trap.
Page 112 of 271
6.1.3.8
Enable unique trap IDs for each type of alarm

Page 113 of 271
6.1.3.9
Forward cleared traps with zero severity

Page 114 of 271
6.1.3.10
Forward traps with extended alarm information

Page 115 of 271
6.2
Software and configuration archive file locations

The software is located in the following directories:
<polyview installation folder>/data <polyview installation folder>/polyview/data/IDU <polyview installation folder>/polyview/data/IDU-G
The files are downloaded to the following directories: For IP-10 products .\polyview\data\<IDU | IDU-G | IDU-Q | IDU-C>, and the name of the file will be the same as the IP of the network element. Configuration files for other products will be in the \polyview\data directory and will have the suffix cfg.
Note that configuration upload from an IP-10G series network element is done per slot. Verify that the following parameters are defined in the PolyView configuration utility:
The TFTP server address should contain the IP address of the PolyView server. Network elements should have access to this IP. You should be able to ping from the network element to the server using this address. Specify the folder name that contains the files to be downloaded. Note that the name can be a specific path, or a path relative to the PolyView installation directory. The default software file folder is PolyView installation folder/data. Remember, the TFTP folder name and path cannot contain spaces.
6.3
6.3.1
Backing up and restoring configuration archive files

Backing up configuration data
PolyView's configuration log registers all changes in system configuration made by users. By default, configuration information is polled from network elements every 24 hours. Both this setting and the size of the log file can be changed in PolyView's configuration utility. Up to four configuration files are stored in PolyView for each network element. The newest configuration file will replace the oldest, however PolyView will not replace a configuration file unless it differs from the ones already stored in the database. <element IP>.cfg and are stored in the folder <polyview installation path>/data.
6.3.2
Scheduling configuration backup for selected network elements To schedule configuration backup:
1. Open the task configuration utility. Select Tools > Schedule task configuration.
Page 116 of 271
2. Add a configuration backup task. Select Actions > Add > Conf Backup, or click the Add icon and choose Conf Backup from the context menu.
3. Add a task identifier. In the Name field, enter unique name for the task.
4. Specify the task recurrence. For Daily, specify the time of day you want the report to be generated. For Weekly, specify if the report is to be generated each week, every two weeks, etc. In addition, specify which days of the week, and the time during the day. For Monthly, specify the day of the month, and the time during the day.
5. Specify the path and location of the task output report. Specify the path of the file. Specify the FTP server address. Enter your user name and password, and specify where files will be stored on the FTP server.
6. Click OK.
6.3.3
Restoring configuration files to selected network elements

Downloading configuration archive files will overwrite the existing configuration settings for the selected units.
To download a saved configuration to a network element:

1. Select the target network elements and select Tools > Configuration download to open the Configuration download utility.
Page 117 of 271
In the Download configuration file window:
Click Download All to restore the most current configuration archive. By default, the last configuration file that was stored in the database will be the one that will be restored to the unit.
Click Select file to choose which configuration file to restore. The Select file option will only be enabled if the available configuration file for all selected elements is the same.
Click Remove to exclude specific network elements from the scheduled rollback. Click Download all to begin the process.
Configuration files will be in the \polyview\data directory and will have the suffix cfg. Note that configuration upload from IP-10G, IP-10E, and IP-10Q series network elements is performed per slot.
6.3.4
Viewing configuration archive download status To view configuration archive download status:
1. Open the Download configuration file window: Select Tools > Configuration download to open the Configuration download utility.
2. Initiate the configuration download. During the process, the Download status column displays the status of the operation.
To terminate a configuration rollback after it has been started, click Abort All.
Page 118 of 271
6.4
Downloading and installing software versions

PolyView supports the ability to download software for all supported network elements using the file transfer server. You can download the files to a single element or a group of elements. As with network broadcasts. if a selection includes sub-elements, the download will apply to all the subelements as well. You can view the download progress in a separate window.
6.4.1
Configuring software downloads To download software to selected network elements:

Select the target elements and select Tools > Software download to open the Software download configuration window. If the selected target elements include a mix of product types, tabs appear at the top of the window for group of products.
In the Software download window: 1. For selections of more than one type of element, select the element type tab. 2. Select which versions to download to the selected elements and click Apply. For IP-10 units, check Internal RFU download if the destination is the RFU. For x1500 elements, in the Perform ODC internal download for field, select Left shelf, the Right shelf, or Both.
3. Specify the Download time. Select Now if you want the download to occur immediately. Click Date config to specify a different time and date.
Page 119 of 271
4. Select Enable if you want the system to perform a reset. Select After download to perform a reset after the software download ends and click Date config to specify the upgrade time and date. When downloading software to an IP-10 unit, the Upgrade command automatically initiates a Reset immediately after the download is complete.
5. Click Apply. 6. Click the Status log button to view the download status, or Close to finish.
6.4.2
Viewing software download status

The software downloads window lists information such as the IP addresses of the elements that were configured for software download, the names of the elements, the software file versions to be downloaded (whether or not the elements are scheduled for reset), and the current status of the downloads.
To view the software download status:

In the Software download configuration window, select Tools > Software download status, or click Status log icon.
Note that software will be downloaded in this order: first IDU, then MUX, and then ODU. If you chose all three and the IDU software download fails, the other downloads will be cancelled.
Page 120 of 271
Performance management
7
7.1
Configuring report settings
PolyViews customizable reporting GUI allows you to generate inventory and performance reports for the entire network, or for a selected subnet, group, trail, or service. PolyView reports include inventory and performance reports. Inventory reports provide information about elements interfaces and links in the system. Performance reports provide information about elements radio and Ethernet performance.
To configure report settings:

3. Configure the email address of report recipients. In the Sent by email address field, specify the email addresses to be used when the server sends reports by email.
4. Click Apply. 5. Select the Polling tab.

Page 121 of 271
6. Configure the polling intervals. In the Dynamic polling interval field, specify how often the server should poll network elements for dynamic inventory data. In the Reports polling interval field, specify how often the server should poll network elements for static inventory data.
Polling values will be rounded out to the nearest quarter of an hour.
7. Click Apply. 8. Click Close to exit the PolyView server config utility. 9. Open the client configuration utility. Select Start > Programs > PolyView > CeraMap client config, or select Settings > Client configuration from the CeraMap menu.
Page 122 of 271
11. Specify the maximum number of entries to retrieve when a performance monitoring report is requested. 12. In the Max PM report lines field, specify the number of PM entries to display. 13. Click Apply to save changes. 14. Click Close to exit the CeraMap Client config utility.
7.2
Generating performance reports

To generate a performance report:
1. Select one or more target elements and select Reports > Performance reports or click the Performance reports icon. 2. Define the date range. 3. Select the interfaces for which you want performance data. Check the checkbox for each interface that you wish to include in the report. Check the root checkbox to select all interfaces in the system.
4. Select Actions > Get report or click the Get report icon to obtain data for the interfaces you selected.
7.2.1
Specifying the performance monitoring interval to display

Performance data can be displayed in one of four pre-defined intervals: 15 minutes, daily, weekly, or monthly.
To specify which PM interval to use when displaying performance data:

1. Select Reports > Performance reports. 2. Select Actions and choose one of the predefined reporting formats:
7.2.2
15 minute report Daily report Weekly report Monthly report Missing intervals report
Modifying the date range for a performance report To modify the date range of a performance report:
1. Select Reports > Performance reports. 2. Select Actions > Report date range or click the Calendar icon to open the Report date range dialog.
Page 123 of 271
3. Click the Date config buttons to specify the start and end dates of your report.
4. Press OK to close the Date config window. 5. Press OK to close the Date range window. When you modify the date range, CeraMap automatically retrieves the specified data from the server, so that you do not need to click the Get report icon.
Page 124 of 271
7.3
7.3.1
Performance report examples

E1 performance
Page 125 of 271
7.3.2
DS1 performance
7.3.3
STM-1 performance
Page 126 of 271
7.3.4
Radio performance
7.3.5
Radio ACM performance
Page 127 of 271
7.3.6
Radio channel performance
Page 128 of 271
7.3.7
Radio MSE performance
Page 129 of 271
7.3.8
Radio RSL performance
Page 130 of 271
7.3.9
Radio TSL performance
7.3.10
Radio XPI performance
Page 131 of 271
7.3.11
Radio Ethernet frame error rate
7.3.12
Radio Ethernet capacity statistics
Page 132 of 271
7.3.13
Radio Ethernet throughput statistics
7.3.14
Radio Ethernet utilization statistics
Page 133 of 271
7.3.15
TDM trail performance
7.4
Generating inventory reports

To generate an inventory report:
1. Select the target elements and press Alt +I, select Reports > Inventory reports or click the Inventory reports icon. 2. Select which type of report to generate.
3. Click OK to view the selected report.

Page 134 of 271
7.5
7.5.1
Inventory report examples

In-band report
The In-band report shows in-band status parameters.
7.5.2
Interface report
The Interface report displays information about all the interfaces on the unit.
Page 135 of 271
7.5.3
Interface availability report

The Interface availability report shows which network element interfaces are enabled.
7.5.4
Available interfaces for PM report

The Available interfaces report shows which network element interfaces are enabled for performance monitoring.
Page 136 of 271
7.5.5
Licensing report
The Licensing report provides data about which licenses are enabled for each network element.
7.5.6
Link report
The Link report provides data about links, such as transmit and receive frequencies and slot number locations.
Page 137 of 271
7.5.7
Neighbors report
The Neighbors report provides data about the IP addresses of the units on a link.
7.5.8
Network element report

The Network element report provides status information and data about indoor units.
Page 138 of 271
7.5.9
Protection report
The Protection report provides data about protected configurations in the network.
7.5.10
Radio report
The Radio report provides status information of outdoor units.
Page 139 of 271
7.5.11
Serial numbers report

The Serial numbers report displays the serial number for each network element.
Page 140 of 271
7.5.12
Slot population report

The Slot population report shows which IDUs are inserted in each slot.
7.5.13
Versions report
The Versions report provides data about which software versions are installed on network elements.
Page 141 of 271
7.5.14
xSTP report
The xSTP report provides data about active and inactive xSTP paths.
7.5.15
Ethernet ports state report
7.6
Link utilization report

The link utilization report shows an aggregated measurement of radio link traffic capacity and utilization. The report is available by right clicking on a link from the topology map. In order to generate this report, PolyView automatically aggregates the performance monitoring data as measured by each IP-10 in the relevant link for the last 24 hours, and presents the following results: Maximum Throughput: Maximum amount of Ethernet traffic received through the link during any 15-minute interval of the latest 24 hour period.
Page 142 of 271
Average Throughput: Average amount of Ethernet traffic received through the link during the latest 24 hour period. Maximum Utilization: Maximum percentage of the total radio capacity (amount of traffic passed divided by total capacity of the radio link) used by Ethernet and TDM traffic during any 15-minute interval of the latest 24 hour period. Average Throughput: Average percentage of the total radio capacity (amount of traffic passed divided by total capacity of the radio link) used by Ethernet and TDM traffic during the latest 24 hour period.
7.7
7.7.1
Customizing report data presentation

Sorting report data
In a report generated by PolyView, you can sort the data in a column by clicking the column title. This is useful when it is important to group the data according to type or date.
Page 143 of 271
Clicking the column title sorts the table according to that column:
7.7.2
Alphabetically for string value columns Numerically for number value columns Chronologically for date value columns By IP address for columns with IP address values
Filtering column display

Not all reports display all columns by default, however, all reports let you control which columns to display.
To filter columns from view:

1. Open a report. 2. Click the Filter icon or select Reports > Filter... > Show/hide columns. 3. Clear the checkbox of any columns that you wish to hide. 4. Check the checkbox of any hidden columns that you wish to display.
5. Click OK to refresh the report presentation.
Page 144 of 271
7.7.3
Filtering reports by values

Report specific filters allow you to define thresholds to determine which data is displayed for each column. Sophisticated filtering of report data can help you identify activity patterns and anticipate network bottlenecks. For example, identifying which elements are consistently passing capacity thresholds can help you anticipate network bottlenecks.
7.7.3.1
Adding column filters
To filter a report by values:

1. Select or generate a report. 2. Click the Filter icon or select Reports > Filter... > Filter by values.
For each filter that you wish to add: 1. Click Add to open the Add filter window. 2. Specify which column to filter. Select a column from the Field drop-down list.
Page 145 of 271
Select a filter operation from the Op drop down list.
The available operators depend on the field type. >, >=, <, <=, =, or <>.
Enter allowed values in the Filter Value column.
3. Click OK to apply the filter.
7.7.3.2
Modifying column filters
To modify a filter:
1. Select a row and click Edit. 2. Make changes to one or more filter values. If you select a different Field option, make sure that the Op and Value field are valid for the selected column field.
3. Click OK to apply your changes.

Page 146 of 271
7.7.3.3
Deleting column filters
To delete a filter:
1. Click the Filter icon or select Reports > Filter... > Filter by values. 2. Select a row and click Delete.
7.7.4
Modifying the date range for a performance report To modify the date range of a performance report:
1. Select Reports > Performance reports. 2. Select Actions > Report date range or click the Calendar icon to open the Report date range dialog.
3. Click the Date config buttons to specify the start and end dates of your report.
4. Press OK to close the Date config window. 5. Press OK to close the Date range window. When you modify the date range, CeraMap automatically retrieves the specified data from the server, so that you do not need to click the Get report icon.
Page 147 of 271
7.7.5
Saving and printing reports

You can export customized views of your data to CSV for further data manipulation, such as creating charts and graphs, or for integration with an OSS level network management system.
To export the report data to a text (.txt) file or Excel (.csv) file:
1. Open a report. 2. Select File > Save as.
To print a report:
1. Open a report. 2. Select File > Print from the menu.
Page 148 of 271
End-to-end traffic service management
8
8.1

Service view
Service view provides access to traffic services topology maps, where you can configure, monitor, and manage TDM trail and Ethernet service connectivity. The Service management interface provides GUI based access to all TDM trail and Ethernet service attributes.
The Ethernet services wizard automates provisioning of E-LINE and E-LAN services. Instead of configuring each port manually along the service, you just specify two service access points and PolyView returns all possible paths between them. Trails can be provisioned automatically or manually, based on user-defined trail endpoints. With automatic trail provisioning, PolyView will suggest the most efficient trail between them; you can accept the suggested path or manually configure the trail.
8.2
8.2.1
End-to-end Ethernet service management

Configuring Ethernet services display settings To configure Ethernet services display settings:
Page 149 of 271
3. Specify the maximum number Ethernet services to display in Service views EVC list. In the Max number of Ethernet services to display field, enter a number between 100 and 1000.
4. Enable or disable allowing the NMS server to collect Ethernet services information from the network elements. In the Enable Ethernet service field, select True to allow service related polling of network elements.
8.2.2
8.2.2.1
Provisioning and configuring new Ethernet services

Adding a new Ethernet service
To provision an Ethernet service:

1. Follow instructions in the Installation and Configuration Guide to pre-configure the IP tables of the target SAPs, or enable LLDP on all ports. LLDP is available for network elements running version I6.8 or higher.
2. Enable ports for all target SNPs.

Page 150 of 271
3. Open Service view and select Ethernet services. 4. Select Services > Add EVC or click the Add icon at the bottom of the EVC list pane to open the Create EVC wizard.
8.2.2.2
Specify service parameters and attributes

In the General page of the Create EVC wizard, specify service settings and parameters.
In the General page of the Create EVC wizard: 1. Specify a unique ID for the transport VLAN used to carry traffic in network. In the Transport VLAN field, enter a user-defined value between 1-4090.
You may specify an occupied VLAN ID, as long as its unique in the service.
2. Specify a unique ID to identify the target service. In the ID field, define the EVC ID using an alphanumeric string of up to 15 characters.
By default, PolyView populates the EVC ID with the evc prefix and the transport VLAN ID.
3. Provide a short description of the service. In the Description field, describe the service using an alphanumeric string of up to 40 characters.
Page 151 of 271
By default, PolyView populates the description field with the evc prefix and the transport VLAN ID.
4. Specify the transport VLAN type. Select C-VLAN or S-VLAN from the Transport VLAN type field drop down list.
Ensure that network elements along the target service are all configured with the same switch mode. Mixing C-VLAN and S-VLAN types is not allowed. The transport VLAN type for Managed switch should be set to C-VLAN. The transport VLAN type for Metro switch should be configured as S-VLAN.
5. Specify the type of service to create: E-LINE, for services with only two Service Access Points (SAPs) or E-LAN, for services with more than two SAPs. Select E-LINE or E-LAN from the Type field drop down list.
When a service has less than two SAPS, for example, if one of the SAPs is unreachable, the service type will change to Unknown.
6. Enable or disable the service. Select Enabled or Disabled from the Admin state field drop down list.
Services are enabled by default.
7. Click Next to configure the service access points.
Page 152 of 271
8.2.2.3
Select service SAPs

In the Service Access Points page, configure service SAPs.
In the Service Access Points page of the Create EVC wizard: 1. Click Add to add a new service access point. 2. Specify the IP addresses of the target SAPs. In the IP address column, select the IP address of the network element. The Name field should populate automatically based on the IP address that you specified.
3. Specify which slot to use as the SAP. Select an available slot from the Slot field.
4. Specify the target port, for example, ETH-1, ETH-2 ETH-8. Ports in use as Service Network Points in other services will not be available. Only ports with no existing services will be displayed in the drop down list.
Page 153 of 271
5. Specify the VLAN encapsulation type. The VLAN encapsulation for a Managed switch can be either C-VID or Untagged.
Untagged encapsulation will not be available if there is already an existing service on the target port but only if it is access port. If it is trunk, untagged is not allowed.
The VLAN encapsulation for a Metro switch can be All-to-one or S-VID.
All-to-one and S-VID encapsulation options will not be available for if there is already an existing service on the target port, and the port type is configured as CN. All-to-one is available only in CN; S-VID is available only if PN.
6. Click Next to configure the service path.
8.2.2.4
Configure the service path

In the EVC path page, the service provisioning wizard displays all possible service paths. Use the drawing tools to configure the visual representation of the path.
Page 154 of 271
In the EVC path page of the Create EVC wizard: 1. Click Start redraw to enable editing of the service path. Use the Zooming buttons to enlarge or reduce the view of the elements in the service you are defining. Reposition the service elements, and load new element locations in the service.
2. Click Save to save the latest changes you made to the element positions in the service. 3. Click Load to load new element locations in the service. 4. Click Next to confirm your configuration settings.
8.2.2.5
Confirm the settings of the target service

In the Confirmation page, confirm the service settings.
In the Confirmation page: Confirm the service settings and click Create to view the service provisioning report.
Page 155 of 271
8.2.2.6
View the service provisioning report

In the Report page, the Create EVC wizard lets you know whether the service was added successfully.
In the Report page of the Create EVC wizard: Click Close to return to the services list. If PolyView is unable to configure a service for all the slots for all the network elements in the service path, the service will still be added to the list, but the admin status will be listed as partially configured.
8.2.3
Managing Ethernet services

Service view provides GUI based management of services and service attributes:
Provision and configure new Ethernet services. Modify configuration settings of existing services. View service alarms Repair services whose operational status is unknown, broken, or partially configured. Update service status. Remove services.
Page 156 of 271
8.2.4
Viewing service properties

The Ethernet services GUI simplifies monitoring of service paths, by providing a visual map of provisioned services. Service view displays all the network elements with at least one configured metro or managed switch along the service.
To view service properties:

1. Open Service view and select Ethernet services. 2. Select a service from the EVC list.
Page 157 of 271
General properties
Transport VLAN ID User defined value between 1-4090. The ID of the transport VLAN used to carry traffic in network.
EVC ID: User defined alphanumeric string of up to 15 characters. By default, PolyView populates the EVC ID with the evc prefix and the transport VLAN ID.
EVC description: User defined text string of up to 40 characters. By default, PolyView populates the description field with the evc prefix and the transport VLAN ID.
Transport VLAN type: C-VLAN or S-VLAN Ensure that network elements along the target service are all configured with the same switch mode. Mixing C-VLAN and S-VLAN types is not allowed. For IP-10 -G, the transport VLAN type for Managed switch should be set to CVLAN. The transport VLAN type for Metro switch should be configured as SVLAN.
EVC type: E-LINE or E-LAN E-LINE is a point to point service type, for services with only two Service Access Points (SAPs). Select E-LAN for services with more than two SAPs. When a service has less than two SAPS, for example, if one of the SAPs is unreachable, the service type will change to Unknown.
Admin state The admin state of the service (enabled / disabled)
Operational state Indicates the most severe alarm in the service.
Configuration status Completed indicates connectivity between the service endpoints and all service points are configured properly Unknown The operational state will be changed to Unknown if any of the network elements along the service become unreachable by the NMS. Up The service operational state will be Up if there is a connection between the SAP, all service ports are Enabled (admin state) and the VLAN is configured correctly for all the ports along the service. Up unprotected When there is more than one path available between two SAPs and the service is configured on an RSTP ring, the configuration status of the service will be Unknown when there is only one path available for the service. Down If the operational state of any of the service ports is Down and causes a lack of connection between two or more SAPs, the operational state of the service will also be down. Partially down In an E-LAN service, if there is no connection between a pair of 2 SAPs, but some of the SAPs are still connected, the configuration status of the service will be Partially down.
Page 158 of 271
Broken service If the NMS finds the same service ID in two subnets that are not connected, the configuration status of the service will be Broken service. Partially configured A service can be set to only Partially configured if the Service succeeded, but with specific fail points.
8.2.4.1
Viewing SAP properties
To view service access point properties:

1. Open Service view and select Ethernet services. 2. Select a service from the EVC list. 3. Click the SAP properties icon in the Properties pane toolbar.
Page 159 of 271
8.2.4.2
Viewing SNP properties
To view service access point properties:

1. Open Service view and select Ethernet services. 2. Select a service from the EVC list. 3. Click the SNP properties icon in the Properties pane toolbar.
Page 160 of 271
8.2.4.3
Hiding service properties columns
To filter service property data:

1. Open Service view and select Ethernet services. 2. Select a service. 3. Select one of the Properties panes. 4. Click the Filter by columns icon at the right end of the Properties toolbar. 5. Clear the checkbox for each column that you wish to remove from the selected set of properties.
8.2.4.4
Editing an existing Ethernet service

Use the Edit EVC feature to modify and configure service attributes.
To modify an existing Ethernet service:

1. Open Service view and select Ethernet services. 2. Select a service from the EVC list. 3. Select Services > Edit EVC or click the Edit icon at the bottom of the EVC list pane.
8.2.4.5
Modify service parameters and attributes
Page 161 of 271
In the General page of the Edit EVC wizard: 1. Specify a unique ID for the transport VLAN used to carry traffic in network. In the Transport VLAN field, enter a user-defined value between 1-4090.
2. Specify a unique ID to identify the target service. In the ID field, define the EVC ID using an alphanumeric string of up to 15 characters.
By default, PolyView populates the EVC ID with the evc prefix and the transport VLAN ID.
3. Provide a short description of the service. In the Description field, describe the service using an alphanumeric string of up to 40 characters.
By default, PolyView populates the description field with the evc prefix and the transport VLAN ID.
4. Specify the transport VLAN type. Select C-VLAN or S-VLAN from the Transport VLAN type field drop down list.
Ensure that network elements along the target service are all configured with the same switch mode. Mixing C-VLAN and S-VLAN types is not allowed. The transport VLAN type for Managed switch should be set to C-VLAN. The transport VLAN type for Metro switch should be configured as S-VLAN.
5. Specify the type of service to create: E-LINE, for services with only two Service Access Points (SAPs) or E-LAN, for services with more than two SAPs. Select E-LINE or E-LAN from the Type field drop down list.
When a service has less than two SAPS, for example, if one of the SAPs is unreachable, the service type will change to Unknown.
6. Enable or disable the service. Select Enabled or Disabled from the Admin state field drop down list.
Services are enabled by default.
Click Next to modify the service access points.
Page 162 of 271
8.2.4.6
Modify service SAPs

In the Service Access Points page, you can modify the service SAPs.
In the Service Access Points page of the Edit EVC wizard: 1. Click Add to add a new service access point. 2. Specify the IP addresses of the target SAPs. In the IP address column, select the IP address of the network element. The Name field should populate automatically based on the IP address that you specified.
3. Specify which slot to use as the SAP. Select an available slot from the Slot field.
4. Specify the target port, for example, ETH-1, ETH-2 ETH-8. Ports in use as Service Network Points in other services will not be available. Only ports with no existing services will be displayed in the drop down list.
Page 163 of 271
5. Specify the VLAN encapsulation type. The VLAN encapsulation for a Managed switch can be either C-VID or Untagged.
Untagged encapsulation will not be available if there is already an existing service on the target port but only if it is access port. If it is trunk, untagged is not allowed.
The VLAN encapsulation for a Metro switch can be All-to-one or S-VID.
All-to-one and S-VID encapsulation options will not be available for if there is already an existing service on the target port, and the port type is configured as CN. All-to-one is available only in CN; S-VID is available only if PN.
6. Click Next to modify the service path.
8.2.4.7
Modify the service path

In the EVC path page, use the drawing tools to modify the current service path.
Page 164 of 271
In the EVC path page of the Edit EVC wizard: 1. Click Start redraw to enable editing of the service path. Use the Zooming buttons to enlarge or reduce the view of the elements in the service you are defining. Reposition the service elements, and load new element locations in the service.
2. Click Save to save the latest changes you made to the element positions in the service. 3. Click Load to load new element locations in the service. 4. Click Next to confirm your configuration changes.
8.2.4.8
Confirm service configuration changes

In the Confirmation page, confirm the service configuration changes.
In the Confirmation page of the Edit EVC wizard: Confirm the service settings and click Update to view the service configuration report.
Page 165 of 271
8.2.4.9
View the service update report

In the Report page, the Edit EVC wizard lets you know whether the configuration changes were implemented successfully.
In the Report page of the Edit EVC wizard: Click Close to return to the services list.
8.2.4.10
Managing service alarms

You can view and manage service level alarms for network elements along the service path in the Alarms properties pane. Operational status of a service may be affected by:
Specific network element alarms. Management level alarms that affect the service.
To view Ethernet service alarms:

1. Open Service view and select Ethernet services. 2. Select a service from the EVC list. 3. Click the Alarm icon in the Properties pane toolbar.
Page 166 of 271
4. Double click an alarm to view its details.
8.2.5
Removing a service To delete a service:

1. Open Service view and select Ethernet services. 2. Select a service and choose Services > Remove EVC or click the Remove EVC icon at the bottom of the EVC list pane.
Page 167 of 271
8.2.6
Polling service performance

Refresh service performs an automatic poll of the service and updates the service topology map with the current service status and alarms.
To refresh a service:
1. Open Service view and select Ethernet services. 2. Select a service and choose Services > Refresh EVC or click the Refresh icon at the bottom of the EVC list pane.
8.2.7
Viewing xSTP map status

RSTP and Ring RSTP algorithms are designed to create loop-free topologies in any network design, which makes it sub-optimal to ring topologies. 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.
Page 168 of 271
8.3
8.3.1
End-to-end TDM trail management

Provisioning TDM trails
PolyView provides automatic discovery of a TDM trail between two selected end points. Auto discovery searches for and selects optimal end-to-end primary and protection trails across complex network topologies. Trails can be built either automatically based on user-defined trail endpoints. After selecting the two end points, PolyView will suggest the most efficient trail between them. You can accept the suggested path or manually configure the trail.
Page 169 of 271
PolyView calculates the trail path using information from the network elements. Links between network elements along the target trail must be configured / discovered / known for the system to automatically provision a TDM trail.
8.3.1.1
Adding a new trail
To create a new TDM trail:

1. Open Service view, and select TDM trails. 2. Select Trails > Add trail, or click the Add trail icon.
8.3.1.2
Specify trail parameters and attributes

In the General page, add a trail description and a unique trail ID. Specify the type of trail (protected or unprotected), the operational state (active or inactive), and the ACM priority.
In the General page of the Create TDM wizard: 1. Specify a unique trail ID. In the ID field, specify a unique trail ID.
2. Add a short description to help identify the trail. In the Description field, add a short description to help identify the trail.
3. Specify the type of protection. NOTE: Protected trails allow traffic from two different paths. Dual ended protected trails have three end points, with outgoing traffic split between two alternative endpoints. In the Type field, specify the type of protection.
Select Unprotected to provision a point-to-point trail. Select Protected 1+1 to enable permanent use of bandwidth in both paths. In a protected 1+1 configuration, instead of a single IP address for both units,
Page 170 of 271
the node has two IP addresses, those of each of the main units. The IP address of the active main unit is used to manage the node.
Select Protected ABR to enable protection with dynamic allocation of bandwidth. Protected ABR is a unique network level method of dynamic capacity allocation for TDM and Ethernet flows. By using the bidirectional capabilities of the ring, TDM-based information is transmitted in one direction and unused protection capacity is allocated for Ethernet traffic, making better use of bandwidth and effectively doubling the capacity of wireless rings. Select Protected 1+1 DE to enable dual ended protection with permanent allocation of bandwidth. Select Protected ABR DE to enable dual ended protection with dynamic allocation of bandwidth.
4. Activate or reserve the target trail. In the Admin state field, select Operational to activate the trail, or Reserved if you want allocate bandwidth without activating the trail.
5. Specify the trail priority. NOTE: Priority determines which trails will be dropped first from radio links when bandwidth is reduced (in ACM) In the ACM priority field, select High or Low priority for the Adaptive Coding & Modulation (ACM).
6. Click Next to configure the trail end points.
8.3.1.3
Select trail end points

In the End points page, specify the IP address, slot, port and interface of the trail end points.
Page 171 of 271
In the End Points page of the Create TDM trail wizard: 1. Specify the target end points by name or IP address. In the IP address column, select the IP address of the network element. The Name field should populate automatically based on the IP address that you specified. In the Name column, select the IP address of the network element. The IP Address field should populate automatically based on the name that you selected.
2. Specify which slot to use as the trail end point. Select an available slot from the Slot field.
3. Specify the target port. You can only choose endpoints from TDM enabled interfaces that are not in use by other trails. Ports in use by other trails will not be available. The end-points must either be in different elements, or different IDUs, or different type of line interface. For protected trails, the end-point interfaces may be either line interfaces where traffic is added /dropped (E1/T1, STM-1 VC-11/12 only), or network protected line interfaces that provide entry points of a trail to a separate network. If two consecutive slots are both included in a protected trail, PolyView displays the main IP or name of the device instead of the individual slots. For dual ended protection trails, chose one user interface and two network protected interfaces.
4. Click Next to configure the service path.
Page 172 of 271
8.3.1.4
Configure the trail path

In the TDM trail path window, modify the graphical representation of the new trail.
In the Path page of the Create TDM trail wizard: 1. Click Icon positioning and then Start redraw to redraw the service path. Use the Zooming buttons to enlarge or reduce the view of the elements in the trail you are defining. Reposition the trail elements, and load new element locations in the service. Click Primary Path Selection to enable editing of the primary service path which is marked with regular line. Clicking an unmarked marked line will mark it and clicking on a marked line will unmark it. Click Secondary Path Selection to enable editing of the secondary service path which is marked with dashed line. Clicking an unmarked marked line will mark it and clicking on a marked line will unmark it.
2. Click Save to save the latest changes you made to the element positions in the service. 3. Click Load to load new element locations in the service. 4. Click Next to confirm your configuration settings.
Page 173 of 271
8.3.1.5
Confirm the settings of the target trail

In the Confirmation page, confirm the trail settings.
In the Confirmation page: Confirm the service settings and click Create to view the trail provisioning report.
8.3.1.6
View the trail provisioning report

In the Report page, the Create TDM trail wizard displays the trail provisioning results.
Page 174 of 271
In the Report page of the Create TDM trail wizard: Click Close to return to the trails list.
8.3.2
8.3.2.1
Managing TDM trails

Polling and refreshing trails
Refresh trail performs an automatic poll of the trail and updates the service map with the current status.
To refresh a trail:
1. Open Service view and select TDM trails. 2. Select a trail and choose Trails > Refresh trail from the menu or right click a trail and select Refresh trail from the context menu.
8.3.2.2
Editing TDM trails

Note that editing a trail affects the trail's traffic.
Modify trail parameters and attributes
To edit trail attributes:

1. Open Service view and select TDM trails. 2. Click the Edit icon below the trails list or right click a trail from the list and choose Edit trail from the context menu to open the Edit TDM trail wizard.
In the General page of the Edit TDM wizard: 1. Modify the trail ID, description type, operational state, and priority.
To modify the trail ID:

In the ID field, specify a new trail ID.
Page 175 of 271
To modify the trail description:

In the Description field, change the 40 character description used to identify the trail.
To modify the type of protection:

Select a different protection mode from the Type field drop down list.
Select Unprotected to provision a point-to-point trail. Select Protected 1+1 to enable permanent use of bandwidth in both paths. Select Protected ABR to enable protection with dynamic allocation of bandwidth. Select Protected 1+1 DE to enable dual ended protection with permanent allocation of bandwidth. Select Protected ABR DE to enable dual ended protection with dynamic allocation of bandwidth.
To modify the trails operational state:

In the Admin state field, select Operational to activate the trail, or Reserved if you want allocate bandwidth without activating the trail. Note that you can also manage trail operational state directly from the trails list. Right click a trail and choose Set trail admin state from the context menu.
To modify which trails will be dropped first from radio links when bandwidth is
reduced: In the ACM priority field, select High or Low priority for the Adaptive Coding & Modulation (ACM). 2. Click Next to modify the trail end points.
Modify trail end points
In the End Points page of the Edit TDM trail wizard: Configure the IP address, slot, port and interface of the trail end points, and click Next to modify the trail path.
Page 176 of 271
To change the trail end points:

Select new trail end points by name or IP address. Either select the IP address of the network element from the IP address column or select the network element by name from the Name column.
To modify which slot is participating in the trail:

Select an alternative available slot from the Slot field.
To modify port membership:

Select an alternative available port from the Port field. Ports in use by other trails will not be available.
Modify the trail path
In the Path page of the Edit TDM trail wizard: 1. Click Icon positioning and then Start redraw to redraw the service path. Use the Zooming buttons to enlarge or reduce the view of the elements in the trail you are defining. Reposition the trail elements, and load new element locations in the service. Click Primary Path Selection to enable editing of the primary service path which is marked with regular line. Clicking on an unmarked marked line will mark it and clicking on a marked line will unmark it. Click Secondary Path Selection to enable editing of the secondary service path which is marked with dashed line. Clicking on an unmarked marked line will mark it and clicking on a marked line will unmark it.
2. Click Save to save the latest changes you made to the element positions in the trail. 3. Click Load to load new element locations in the trail. 4. Click Next to confirm your configuration changes.
Page 177 of 271
Confirm the trail configuration changes

In the Confirmation page, confirm the trail settings.
In the Confirmation page of the Edit TDM trail wizard: Confirm the service settings and click Create to view the trail provisioning report.
View the trail provisioning report

In the Report page, the Edit TDM trail wizard displays the trail provisioning results.
In the Report page of the Edit TDM trail wizard: Click Close to return to the trails list.
Page 178 of 271
8.3.2.3
Activating and reserving trails
To modify the trail admin state:

1. Open Service view and select TDM trails. 2. Right click a trail and choose Set trail admin state from the context menu. Choose Operational to activate an inactive trail. Choose Reserved to allocate bandwidth for an inactive trail with no traffic and no performance monitoring.
8.3.2.4
Managing primary and secondary protected trail paths

By default, the shortest trail in a pair will be the primary (active) trail, while the secondary path should minimize the number of common network elements. The Force trail protection option lets you specify which will be the primary trail and which will be the secondary trail.
To specify a trail as either the primary and secondary path:

Right click a trail and select Force trail protection from the context menu. Choose Primary, Secondary, or None.
Primary the element with the SNCP will take the data received on the primary path, meaning in case the primary path is down, the user will need to switch protection manually to the secondary path. If primary and secondary paths exist for only a portion of the links between the end-points, the status of the trail will be partially protected. Secondary the element with the SNCP will take the data received on the secondary path, meaning in case the secondary path is down, the user will need to switch protection manually to the primary path. None the element with the SNCP will take the data received on either the primary or the secondary path, meaning the user won't need to switch protection manually in case one of the paths is down.
8.3.2.5
Removing trails
To delete a trail:
1. Open Service view and select TDM trails. 2. Select a trail and choose Trails > Remove trail from the menu or right click a trail and select Remove trail from the context menu.
8.3.2.6
Viewing trail properties

The Properties pane displays the properties for the selected trail:
Viewing trail details
To view trail details:

1. Open Service view and select TDM trails.
Page 179 of 271
2. Select a trail.
In the Details section of the Properties pane:
Trail ID and Trail description are trail identifiers. Most severe alarm indicated trail severity. Major and critical alarms should be resolved. Admin state indicates whether the selected trail is Operational or Reserved. Configuration status indicates if a trail is completed. Type indicates the type of trail protection. ACM priority indicates the priority for which trails will be dropped first from radio links when bandwidth is reduced.
Page 180 of 271
Viewing trail endpoint properties
To view trail endpoint properties:

1. Open Service view and select TDM trails. 2. Select a trail. 3. In the Properties pane, click the Endpoints icon.
In the End Points section of the Properties pane:
IP Address and Name identify the trail end points. Slot indicates the participating slot. Port indicates the participating port.
Page 181 of 271
Viewing trail protection
To view trail endpoint properties:

1. Open Service view and select TDM trails. 2. Select a trail. 3. In the Properties pane, click the SNCP icon.
In the SNCP section of the Properties pane:
IP Address and Name identify the trail end points. Slot indicates the participating slot. Port indicates the participating port. Active path indicates the active path. 'Primary' means the primary path, usually the shortest one. 'Secondary' means the secondary path. This setting can only be set on the create/edit trail wizard.
Page 182 of 271
Force protection indicates the primary and secondary paths. Primary the element with the SNCP will take the data received on the primary path, meaning in case the primary path is down, the user will need to switch protection manually to the secondary path. Secondary the element with the SNCP will take the data received on the secondary path, meaning in case the secondary path is down, the user will need to switch protection manually to the primary path. None - the element with the SNCP will take the data received on either the primary or the secondary path, meaning the user won't need to switch protection manually in case one of the paths is down.
Hiding trail properties details
To filter trail property data:

1. Open Service view and select TDM trails. 2. Select a trail. 3. Select one of the available views from the Properties pane. 4. Click the Filter by columns icon at the right end of the Properties toolbar. 5. Clear the checkbox for each column that you wish to remove from the selected set of properties.
8.3.2.7
Managing trail alarms

The Alarms properties pane displays the IP address, path, severity, and a short description of each alarm. Operational status of a trail may be affected by:
Specific network element alarms. Management level alarms that affect the trail.
Double click a trail alarm to view its details, probable causes, and corrective actions.
To view trail alarms:

1. Open Service view and select TDM trails. 2. Select a trail. 3. In the Properties pane, click the Alarms icon to view alarm details for the selected trail.
Page 183 of 271
In the Alarms section of the Properties pane:
IP Address indicates the location of the alarm. Path indicates the location of the fault. Severity indicates the severity of the fault. Description provides a short explanation about the alarm.
To view alarm details and corrective actions:

Click the + next to each alarm to for more information about the alarm.
Page 184 of 271
8.3.2.8
Monitoring trail performance

PolyView logs performance monitoring data collected for the trail termination points of each trail in the system. All performance monitoring information is stored in the PolyView database.
To view a trail's performance report:

1. Open Service view and select TDM trails. 2. Right click a trail and select Trail PMs from the context menu.
In the TDM performance report window: 1. Specify which PM interval to use when displaying performance data. Select Actions and choose one of the predefined reporting formats:
15 minute report Daily report Weekly report Monthly report Missing intervals report
2. Select the date range of a performance data to display. Select Actions > Report date range or click the Calendar icon to open the Report date range dialog.
3. Select Actions > Get report or click the Get report icon to view trail performance for the selected date range.
Page 185 of 271
Security management
9
9.1
9.1.1
Security management
Monitoring and managing user actions
Viewing connected users
An administrator can view users currently connected to the server, their computer IDs, and since when they were connected.
To view connected user information

Select File > Show connected users.
You can send a message to any connected user, disconnect a user, or view user actions for a specific user.
9.1.2
Sending messages to connected users To send a message to a user:

1. Open the Connected users window. Select File > Show connected users.
2. Select Actions > Send a message to user, click the Send a message to user icon or right click a user and choose Send a message to user from the context menu.
9.1.3
Disconnecting a connected user To disconnect a user:

1. Open the Connected users window. Select File > Show connected users.
2. Select Actions > Disconnect user, click the Disconnect user icon or right click a user and choose Disconnect user from the context menu.
Page 186 of 271
Security management
9.1.4
Viewing a users user action history To view user actions:

1. Select Reports > User action log to open the Users action log. You can also open the User actions log from the Connected users window. Select Actions > Show user actions, click the Show user actions icon or right click a user and choose Show user actions from the context menu.
2. Select the time range that you wish to view and click OK.
A user action log appears with a list of actions the user you selected performed within the last day.
9.1.5
Viewing user action details

Each action recorded in the database contains information about the user, the time the action was performed, the application name, and the name of the action.
To view details of a user action:

Select a user action record and select Actions > Show details, click the Show details icon, double click a record in the report, or right click a record and choose Show details from the context menu.
Page 187 of 271
Security management
If CeraWeb is connected to the network elements via PolyView (PolyView acts as a proxy), all user actions in CeraWeb are automatically recorded in the PolyView server database. If CeraWeb is not connected via PolyView, but the administrator nonetheless wants user actions to be logged, CeraWeb can be configured to route the actions to the PolyView server.
You can filter the information by selecting Report > Filter. Actions performed after the window was opened will automatically be added to the window.
Page 188 of 271
System administration
10
10.1
Scheduling tasks
PolyViews task scheduler takes on some of the system administration burden, by allowing you to set up recurring tasks such as database checks and automatic database backup. In addition to the database and configuration backup, PolyViews task scheduler allows you to set up customized recurring tasks.
To schedule a task:
1. Open the Schedule task configuration utility. 2. Select Tools > Schedule task configuration. 3. Select Actions > Add > Execute, or click the Add icon and choose Execute from the context menu.
4. In the Name field, enter unique name for the task. 5. In the Recurrence area, specify how often to run the configuration backup. For Daily, specify the time of day you want the report to be generated. For Weekly, specify if the report is to be generated each week, every two weeks, etc. In addition, specify which days of the week, and the time during the day. For Monthly, specify the day of the month, and the time during the day.
6. For Executable, specify any executable program you want to run (related or not related to PolyView). 7. For Parameters, specify parameters you want for the executable. 8. Click OK to schedule the task.
Page 189 of 271
10.2
10.2.1
Database management
Backing up the NMS database
It is highly recommended to perform regular backups to the database. Backup can be done using the tools provided with the database. However, to make this task easier, a backup script called pvdbbackup can be found in the directory in which PolyView was installed. Usage: pvdbbackup [backup / restore] [[target path name] / [target file name]] Note that a backup can be performed while PolyView is running (known as "hot backup"). However, before running a restore backup operation, PolyView must be terminated by typing pvstop in a command window.
To define an automatic backup for the PolyView database:

1. Select Tools > Schedule task configuration. Select Actions > Add > DB Backup or click the Add task icon and choose DB Backup from the context menu.
2. In the Name field, enter unique name for the task. 3. In the Recurrence area, specify how often to run the database backup. For Daily, specify the time of day you want the report to be generated. For Weekly, specify if the report is to be generated each week, every two weeks, etc. In addition, specify which days of the week, and the time during the day. For Monthly, specify the day of the month, and the time during the day.
Page 190 of 271
4. In the Output area, specify the name and location of the backup report. For File, enter the path of the file. For FTP, specify the IP address or hostname of the FTP server. Enter your user name and password, and where files should be stored on the FTP server.
10.2.2
Restoring the NMS database

In many cases, it may be possible to repair just the database index file instead of recreating the entire database. PolyView task scheduler allows you to restore your database to a previous version. Note that database repair process makes copies of the database tables. Make sure that you have enough free disk space available before running the task. Adding a database check task as a recurring task can help you monitor the integrity of your database tables.
To define an automatic check for the PolyView database:

1. Select Tools > Schedule task configuration. 2. Select Actions > Add > DB Check or click the Add icon and choose DB Check from the context menu.
3. In the Name field, enter unique name for the task. 4. In the Recurrence area, specify how often to run the database check. For Daily, specify the time of day you want the report to be generated. For Weekly, specify if the report is to be generated each week, every two weeks, etc. In addition, specify which days of the week, and the time during the day. For Monthly, specify the day of the month, and the time during the day.
10.2.3
Repairing tables with mysqlcheck

The mysqlcheck command can be used while the MySQL database server is running. Run the mysqlcheck command: mysqlcheck -uroot ppvroot PolyView
Page 191 of 271
10.2.4
Repairing tables with myisamchk

1. Before running this command, shut down the MySQL server: Run mysqladmin shutdown -uroot -ppvroot
2. Run the myisamchk command: Run myisamchk [options][tablenames]
Note that you must specify the full path of the database files. For example, for Windows systems the command may be: myisamchk -fr c:\mysql\data\PolyView\*.MYI
3. When the check is done, restart the server.
10.2.5
Creating a new MySQL database

If your system database becomes corrupted, and you prefer to rebuild your database rather than merely restoring it, you can use the command line interface to create a new database. Creating a new database clears the existing database, and creates new tables.
To create a new database:

1. Change to the PolyView directory. 2. Run createdb create. 3. When the command prompt asks if you wish to continue, enter Y to confirm and press Enter. TIP: If you know that a specific part of the database is causing the problem, you may be able to salvage some of your data by exporting a filtered data set before overwriting the database. Alternatively, if youve been backing up the database regularly, you can opt to overwrite the new database with a backup.
10.3
10.3.1
System maintenance
Daily maintenance routine
The two tasks that you must perform on a daily basis are to view and resolve all major and critical alarms. There are two ways to identify these alarms:
Apply a severity filter to the current list of alarms. Configure a trigger to provide real time alerts for any loss of radio frame communication.
Page 192 of 271
10.3.1.1
Filtering the list of current alarms

The list of current alarms is a context sensitive list. By default, you'll always see the full list of alarms for your current selection. If no entities are selected, the list displays current alarms for the entire network. You can also apply filters to the list of current alarms to view alarms for a specific range of IP addresses, alarms that haven't been acknowledged, text in the alarm key description, or other properties. For your daily maintenance routine, Ceragon recommends that you apply a severity filter to the full list of current alarms to identify alarms that need immediate attention.
To view just major and critical alarms:

1. Make sure that you are looking at the entire network. In the Navigator panel on the left, select root at the top of the topology tree.
2. Open the list of current alarms. Select Reports > Current alarms from the menu bar, press Alt + A, or click the toolbar's Current alarms icon.
3. Add a filter. Select Report > Filter... > Filter by values from the Current alarms menu or click the Filter icon and choose Filter by values from the submenu. Click Add to open the Add one field filter utility.
Page 193 of 271
4. Configure your alarm severity filter, and click OK.
Select Severity from the Field drop down list. Select < (less than) from the Op list of operations. Select Critical from the list of values.
5. Click OK to apply your filter to the current list of alarms.
Page 194 of 271
Applying the severity filter will filter the list of current alarms to display only major and critical alarms. These are the alarms that require immediate attention. You'll need to address and resolve each alarm individually.
To resolve alarms:
1. Open alarm details for each remaining alarm. Select Actions > Alarm details for each alarm or right click and choose Alarm details from the context menu.
2. Identify the alarm's location and cause and click Close. 3. Launch the element manager for the selected alarm. Select Actions > Launch element manager or right click and choose Launch element manager from the context menu.
When you are finished treating all of the alarms, close, reopen, and reapply the severity filter to the list of current alarm to ensure that there are no remaining major or critical alarms.
10.3.1.2
Configuring a loss of radio frame trigger
To configure a daily loss of radio frame trigger:

1. Add a new trigger. Select Tools > Trigger configuration. Select Actions > Add or click Add to open the Add trigger window.
2. Name the trigger.

Page 195 of 271
Enter a name for the new trigger in the Trigger name field.
3. Define the activation conditions. In the Trap name field, check the IP-10 option, and select radio-lof from the list of traps. In the Severity field, check the Major and Critical options. In the Description text box, add any text from alarm names, descriptions, or messages that should trigger the alarm. Check the If was not acknowledged in... option and specify the number of minutes to wait before triggering a trap for an unacknowledged alarm.
4. In the Activated operation section, select Send Email from the Operation type drop down list. 5. Specify the email address, subject line, content of the triggered email, and click OK. Enter the email addresses for the target recipients in the Address field. Click the Ellipsis button next to the Subject field to select predefined variables that you can insert in the text.
Page 196 of 271
Click the Ellipsis button next to the Content field to select predefined variables that you can insert in the text.
To send email with HTML markup, make sure that the email format for alarms is set to HTML.
Page 197 of 271
10.3.2
Weekly maintenance routine

Over time, a weekly maintenance routine can help reduce the number of daily alarms that are raised. Your weekly routine should include:

10.3.2.1
Reviewing the alarms log. Reviewing the performance reports.
Viewing the alarms log
To view a report of historical alarms:

1. Open the Alarm log. Select Reports > Alarm log from the menu, press Alt + L, or click CeraMaps Alarm log icon.
2. Specify the previous week as your start and end dates, and click OK. 3. Select Report > Filter > Chronological view to switch to chronological view.
By default, the alarm log is listed by alarm, with Raise and Clear times listed as attributes of the alarm. Chronological view lists raise clear alarms as separate events. Depending on how you sort or filter your view, chronological view should help you understand the effectiveness of your daily routine.
Page 198 of 271
10.3.2.2
Performance monitoring
While you could also use the command line interface to schedule a weekly performance reporting the, Ceragon recommends a weekly interactive session via the Reporting GUI, using real time filtering and sorting.
To generate a performance report:

1. Right click a group or subnet of your network, either from the map or from the topology tree, and select Performance reports from the context menu. 2. Specify the previous week as your start and end dates. Select Actions > Report date range or click the Report date range icon to specify the time interval, and click OK. For alternative views, you can also:
Select Report > Weekly report for a summarized version, based on the network selection and time interval. Select Report > Missing interval report to display the periods of time in which no activity was recorded. Select Report > Filter > Filter zeros to exclude all zero values from the table.
3. Check the box of each interface that you wish to include in the report. To select all the interfaces of a unit, check the box beside the top level unit. To select all interfaces in the system, check the root box.
4. Generate a report for the selected interfaces. Select Actions > Get report or click the Get report icon.
5. Filter the report to display only performance errors that lasted longer than one second. Select Report > Filter... > Filter by values from the Performance reports menu or click the Filter icon and choose Filter by values from the submenu. Click Add to open the Add one field filter utility.
6. Configure your ES filter, and click OK. Select ES from the Field drop down list. Select >= (greater than or equal to) from the list of operations. Enter 1 in the Value text box.
7. Click OK to apply your filter to the performance report.
Page 199 of 271
10.3.3
Troubleshooting alarms
If any errors remain after applying the filter, apply the recommended workarounds and use the troubleshooting intermittent ES errors flowchart to resolve any remaining errors.
10.3.3.1
ODU intermittent ES errors

Product Non- IDUs, x1500, all ODUs Probable Cause Unknown triggered by variable causes. Recommended workarounds
10.3.4
Verify you are using latest software versions as indicated in the release notes. Verify proper physical installation: check the units IF cables, grounding, waveguide, and OCB. For SD links, it helps to perform delay calibration. Check to see if the error correlates with RSL fading issues such as rain.
XPIC notes: Links should be confirmed error-free individually before enabling XPIC and bringing up the second link Alternatively, change the frequency of one of the links and work without XPIC Verify that the XPI is greater than 25dB.
Backup maintenance routine

1. Backup the PolyView database. 2. Backup the network topology map to /PolyView/<backup directory>.
For redundant systems, back up network topology for both servers separately. Backup to the standby server first, and then to the main server.
3. Backup network element configuration files to the /PolyView/data directory. 4. Backup user definitions to the /PolyView/config directory. 5. Update your emergency boot disks.
10.3.5
Connectivity verification routine

1. Perform Poll node on random selections of network elements to verify communication with the NMS server. 2. Select random network elements on a non-operational TDM path to simulate an alarm to verify that alarms are raised and logged.
Page 200 of 271
10.3.6
Database maintenance routine

Add a database check task via the task scheduler GUI or the command line interface.
10.3.7
Disk maintenance routine

1. Manually scan system folders to remove junk, temporary, and unnecessary system files. 2. Run the OS disk clean up utility. 3. Run the OS disk defragmenter utility. 4. San for corrupt file system data with CHKDSK or similar. 5. Scan for viruses.
10.3.8
Hardware maintenance routine

1. Check server power protection devices to ensure they are still protecting the system. 2. Check server power supply fan for ventilation and dirt buildup and clean if necessary. 3. Check processor temperature, inspect heat sink and fan to ensure they are working. 4. Check connection / visibility to all network elements.
10.3.9
Task verification routine

Verify that scheduled scripts are running.
Page 201 of 271
Reference
11
11.1
Reference
CeraMap keyboard shortcuts
Shortcut F5 Insert Delete Enter Alt + Enter Backspace Ctrl + D Ctrl + F Ctrl + G Ctrl + L Ctrl + M Ctrl + P Ctrl + S Ctrl + S Ctrl + T Ctrl + U Alt + A Alt + D Alt + E Alt + I Alt + L Alt + P Alt + S Alt + U Task Refresh map Add network element Delete selected Open selected View properties View previous level Perform network auto discovery Find selected network element Add group Add link Move selection Print list or report Export list or report Add symbol Add label Show connected users View current alarms View software download status Open tasks Get inventory report View alarms log Get performance report Software downloads View user action log Menu File > Refresh Edit > Add network element Edit > Delete Tools > Open Edit > Properties Edit > Map up one level File > Network auto discovery Edit > Find Edit > Add group Edit > Add link Edit > Move File > Print File > Save as Edit > Add symbol Edit > Add text File > Show connected users Reports > Current alarms Tools > Software download status Tools > Schedule task configuration Reports > Inventory reports Reports > Alarm log Reports > Performance reports Tools > Software download Reports > Users action log
11.2
11.2.1
Alarms
Network management alarms
PolyView generates several management alarms. Most of the alarms (in the current alarms and alarm log) can be viewed by selecting the icon representing the PolyView server in CeraMap. The server icon changes color in accordance with the top-most current management alarm severity. The only exception is the nmsNodeDown (unreachable element) and nmsNodeUp (element is reachable) alarms, which are generated by the PolyView server according to the connectivity
Page 202 of 271
Reference
to the network element. These alarms are raised on behalf of the network element itself (as if it was sent by the element). Note that all management alarms are forwarded to northbound systems (if PolyView is configured to forward alarms to the northbound OSS).
11.2.1.1
Management raise alarms

Alarm name nmsNodeDown Description Sent when the NMS loses connection with a network element. Sent if a user fails three sequential login attempts to the NMS system. Sent when a secondary standby server tries to connect to standalone server. Sent by a primary server when it loses connection to the secondary standby server. Sent by a main server when license file expires in less than two weeks. Sent by a main server when the license file has expired. Sent by a main server when the number of network elements exceeds the license limit. Sent by a main server when it fails to load a license file. Sent when TFTP port is bound by another process. Sent when a user is disconnected by another user. Sent when a secondary standby server tries to connect to a main server with a different NMS version. Sent when the server cannot communicate with ESYMAC services. Sent by a secondary standby server when it loses connection to the primary server. Sent when an enabled feature set is not licensed. Sent when the free disk space on the main disk is below the configured threshold. Sent when average system load is above the configured threshold. Page 203 of 271 ID 401 Severity Node down Event
nmsSecurityFailure
402
nmsPrimaryServerConfigMismatch
403
Major
nmsSecondaryServerNotConnected
404
Major
nmsLicenseExpiresInLessThanTwoWeeks
405
Warning
nmsLicenseExpired nmsNetworkElementNumExceedsLimit
406 407
Major Major
nmsFailedLoadingLicenseFile nmsTftpServerAlreadyRunning userDisconnected nmsPrimaryServerVerMismatch
408 409 410 411
Major Major Event Major
nmsEsymacNotConnected
412
Major
nmsPrimaryServerNotConnected
413
Major
nmsEnabledFeatureSetNotLicensed nmsFreeDiskSpaceTooLow
414 415
Major Major
nmsCpuLoadTooHigh
416
Major
Reference
Alarm name nmsProtectionSwitchOccurred
Description Sent when a protection switch occurs between the main slots in a network element Sent by a primary server (Main) and by the secondary server (Standby) when both servers are in active mode in case the percentage of unreachable NE in the main server crossed the configured threshold. The trap description includes the following format: 'Percentage of unreachable elements in main server is over threshold Raised'. Sent when a floating IP is added to a network element. The trap description includes the main (non floating) IP of the network element in the following format: 'Alarm from IP <IP>: Floating IP added'. Management trap: NMS configuration change event: For each configuration change, The description of the event shall be the same description that being logged in the Users Action Log concatenated with the three fields - Application - User name - Connected From - Description + Details (in { })
ID 417
Severity Major
nmsPrimaryAndSecondaryServersAreActive
418
Major
nmsFloatingIpAdded
419
Minor
nmsConfigurationChange
421
Warning
11.2.1.2
Management clear alarms

Alarm name nmsNodeUp Description Sent when the NMS resumes connection with a previously disconnected network element. Sent when a secondary standby server connects to a main server Sent by a primary server when it reconnects to the secondary standby server Sent by a main server when license file expires in more than two weeks. Sent by a main server when license file does not expire. Sent by a main server when the number of network elements is back within the license limit. Sent by a main server after successfully loading the license file. ID 501
nmsPrimaryServerConfigOK nmsSecondaryServerConnected
503 504
nmsLicenseExpiresInMoreThanTwoWeeks nmsLicenseDoesNotExpire nmsNetworkElementNumWithinLimit
505 506 507
nmsSuccededLoadingLicenseFile
508
Page 204 of 271
Reference
Alarm name nmsTftpServerStartRunning nmsPrimaryServerVerMismatchOK nmsEsymacConnected nmsPrimaryServerConnected nmsLicenseConfigurationMismatchRemoved nmsFreeDiskSpaceOK
Description Sent when the TFTP server successfully binds the TFTP port. Sent when a secondary standby server connects to a main server. Sent when server can communicate with ESYMAC services. Sent by a secondary standby server when it reconnects to the primary server. Sent when a license configuration mismatch is resolved. Clears the free disk space alert. It is sent when the free disk space of the main disk is back above the configured threshold. Clears the high CPU load alert. It is sent when the average system load is back to below the configured threshold. Sent by a primary server (Main) and by the secondary server (Standby) when both servers are no longer both in active mode. Clears the alert that was sent when a floating IP was added to a network element. Clears the alert that was sent when no trusted certificate was found for a network element.
ID 509 511 512 513 514 515
nmsCpuLoadOK
516
nmsPrimaryAndSecondaryServersAreNotActive
518
nmsFloatingIpCleared
519
nmsTrustedCertificateFound
520
11.2.2
Ethernet service related alarms

Common service misconfiguration alarms
Description Transport VLAN is not correlated Severity Major Raise condition There are at least two network elements with the same service ID, but different VLAN types. Clear condition All the network elements in a service must be configured with the same service ID and transport VLAN type. All the SNPs in a service must be enabled for transporting service traffic. Corrective actions Reconfigure the service path with a single transport VLAN type.
The SNP is not configured to carry the transport VLAN ID
Major
The SNP for one of the network elements on the service is misconfigured with the wrong VLAN type. Mismatch between the switch and VLAN types.
Enable VLAN transport for all of the target network elements.
VLAN type is not correlated
Major
Each network element along the service has the correct correlation between its VLAN type and switch type.
Set the correct VLAN type for the enabled switch.
Page 205 of 271
Reference
Description Less than two SAPs were found on the service
Severity Major
Raise condition One of the service access points is unreachable.
Clear condition A service needs at least two service access points.
Corrective actions Ensure that both access points are reachable. Clear any major or critical alarms. Refresh the service. Perform repair action and set the correct description for the EVC. Reconfigure the furthest SNP as one of the service SAPs. Reconfigure the SNP on the edge of the service as one of the service SAPs, or change the service type from E-LINE to ELAN, and add the SNP as an additional SAP.
The description for some of the network elements varies SAP was found not in the edge of the EVC
Minor
The descriptions for at least two of the network elements along the service are not correlated. One of the service access points no longer at the end of the service path. One of the network elements is outside of the specified service path.
The description for all network elements on a service must be identical. The service finds at least one path between two service access points. E-LINE service between two SAPs, or E-LAN service with more than two SAPs.
Minor
SNP was found in the edge of the EVC
Minor
Service related network element alarms

Alarm description Mute FE Loss of carrier on port #n (n = 3,4,5,6,7) Ethernet gigabit loss of carrier (port 1 or 2) SFP is not inserted (port1 or 2) SFP malfunction (port 1 or 2) GBE TX mute override Loss of frame on radio IF loopback RF loopback ODU TX mute Alarm ID 410 401 403 404 405 406 603 1601 1722 1735
Ethernet service related management alarms

Alarm name nmsNodeDown nmsNodeUp Description Sent when the NMS loses connection with a network element. Sent when the NMS resumes connection with a previously disconnected network element. ID 401 501
Page 206 of 271
Reference
11.2.3
Trail alarms
Name lvdsbackplaneerror-main ID 728 Description Errors in TDM backplane channel for slot # %1. Errors in TDM backplane channel in connection with main. Errors in TDM channel in connection with T-card. Error in TDM drawer type detection Severity Major Origin IDU Probable Cause Extension or main unit equipment failure. Backplane failure. Extension or main unit equipment failure. Backplane failure. IDU HW failure. T-card HW failure. Corrective Action Reinsert unit. Power-cycle unit. Replace unit. Check backplane. Reinsert unit. Power-cycle unit. Replace unit. Check backplane. Reinsert unit. Power-cycle unit. Replace T-card. Replace IDU. Make sure drawer is properly inserted. Power cycle the system. Replace drawer Reinsert unit. Power-cycle unit. Check backplane.
lvdsbackplaneerror-extn
729
Major
IDU
lvds-db-error
730
Major
IDU
eepromaccessfailure
2201
Major
IDU
Inserted drawer not supported. Hardware error.
bp-lof-alarm
2301
TDM backplane LOF for slot #%1.
Critical
IDU
Extension or main unit equipment failure. Backplane failure. IDU with TDM trails mapped to it was extracted from shelf. Extension or main unit equipment failure. Backplane failure. Network TDM trail configuration error. Signal failure in TDM trail - this may be due to equipment failure or AIS at the line input. Excessive BER in TDM trail. Signal degrade in TDM trail.
idupresencenot-detected extensionbp-lof
2304
IDU #%1 presence not detected. TDM backplane LOF in connection with main. Failure in one or more TDM trails.
Minor
IDU
Insert IDU in shelf. Delete relevant TDM trails Re-insert unit. Power-cycle unit. Check backplane
2402
Critical
IDU
failure-inone-ormore-tdmtrails
2403
Warning
IDU
Check TDM trails status.
Page 207 of 271
Reference
Name invalid-trailstatuschange
ID 2406
Description Invalid trail status change %1 in trail %2.
Severity Major
Origin IDU
Probable Cause Trail end-point failure detected for one or more trails. Trail end-point failure cleared for one or more trails. Trail excessive BER detected for one or more trails. Trail excessive BER cleared for one or more trails. Trail ID spelling difference between trail ends. Network TDM trail configuration error. Errors in incoming signal.
Corrective Action Perform reset in end-point IDU if exists. Replace endpoint IDU.
trailexcessiveBER-change
2407
Trail excessive BER status change %1 in trail %2.
Major
IDU
Check links and equipment alarms along the TDM trail.
trail-idmismatch
2408
Trail ID mismatch in at least one trail.
Warning
IDU
Check trail ID at both ends of the trail. Check network trail configuration. Check trail performance (BER) along the trail path and fix errored links if needed. Check trail ID at both ends of the trail. Check network trail configuration.
trail-idmismatchchange
2409
Trail ID mismatch status change %1 in trail %2.
Warning
IDU
Trail ID mismatch detected for one or more trails. Trail ID mismatch cleared for one or more trails. User command force active.
trailprotectedforced-active trailprotectedswitch
2410
Trail ID: %1, path: %2 forced active. Trail protection switch performed in trail %1 due to %2. Trail signal degrade status change %1 in trail %2.
Warning
IDU
Set force active to "none" for this trail. NA
2411
Warning
IDU
Signal failure along the active trail's path. User issued force active command to stand-by path. Trail signal degrade detected for one or more trails. Trail signal degrade cleared for one or more trails.
trail-signaldegradechange
2412
Minor
IDU
Check links and equipment alarms along the TDM trail.
Page 208 of 271
Reference
Name trailsmapped-toinexistentinterfaces
ID 2413
Description Trails mapped to inexistent interfaces in IDU #%1.
Severity Warning
Origin IDU
Probable Cause One or more components were extracted from the system since trails were defined. Radio scripts have been replaced by narrower scripts since trails were defined. (1) Fade in a link along the trail. (2) Equipment failure in a network element along the trail. (3) Trail not properly provisioned along the path. Protection was enabled in pair of IDUs between which trails were previously configured. Clock source configured from wrong VC. Radio LOF or equipment failure along the path of the synchronization trail. LOS or AIS at the synchronization source interface in the far end of the trail.
Corrective Action Replace missing components (IDUs, T-cards). Make sure radio scripts support required number of E1/DS1 trails through radio. Delete relevant trails.
trail-signalfailurechange
2414
Trail signal failure status change %1 in trail %2.
Warning
IDU
Check links, equipment alarms and trail configuration along the TDM trail.
illegal-trailconfiguration
2415
Conflicting trails are configured in protected IDUs %1 and %2. STM-1 clock source signal failure.
Warning
IDU
Erase relevant trails. Disable protection in pair.
stm1-syncclock-signalfailure
2613
Major
IDU
Make sure the configured VC is the end-point of the synchronization trail. Check status of synchronization trail. Check status of clock source interface.
Page 209 of 271
Reference
11.2.4
Configuring sound alarms

It is possible to configure a sound that will be played when triggered by an alarm. The sound will be played continuously until the user acknowledges the alarm. In the PolyView installation directory, an application called playsound enables you to configure the sound to be played. You can run playsound in a command window, using the format: playsound <sound file name> <message to the user> <severity> where: <sound file name> is the name of the file that contains the sound. The value can be a specific path, or a path relative to the PolyView installation folder. Several sound files were included with the PolyView installation in the sound directory in the installation folder. <message to the user> is a text message that will be displayed for the user in a window that opens. <severity> is used to organize the playing of sounds, according to their severity. If a sound with severity X is triggered by an alarm, and another sound is triggered by an alarm with severity Y, if Y's severity is greater than that of X (for example, Y is Major and X is Warning), Y will be played instead of the X. If Y is not greater than X, X will be played. PlaySound example An example of the usage of the playsound application would be to define different sounds for Major alarms and Critical alarms: 1. Create a trigger. 2. For Severity in the Activate conditions area, select Major. 3. In the Activation operation field, select Run Executable. Path: playsound Parameters: sound/bark.au %SEVERITY: %DESCR %#SEVERITY Execute On: Connected clients
4. Create an additional trigger. 5. For Severity in the Activate conditions area, select Critical. 6. In the Activation operation area, select Run Executable Path: playsound Parameters: sound/bong.au %SEVERITY: %DESCR %#SEVERITY Execute On: Connected clients
Page 210 of 271
Reference
11.3
Command line interface (CLI)

The CLI executable is a part of the PolyView installation (both client and server) and therefore the CLI can be activated from any machine on which PolyView client or server is installed. There are two common working modes.
CLI runs locally on the server. The report file is saved in the server machine under a known FTP directory. Assuming the FTP server is enabled on the PolyView server machine, a remote machine should fetch the file using an FTP/SFTP client.
Advantage: The file can be copied via a known protocol (FTP/SFTP) which is sometimes the only option when dealing with firewalls.
CLI runs on a remote machine CLI runs as a remote client towards the server. The report is saved on the remote machine and there is no need for FTP.
11.3.1
Advantages: No need for FTP, the client application copies the file.
CLI scheduling instructions For Windows, create a batch file containing the desired CLI command. Schedule it via
the Windows scheduler.
For Solaris, create a shell script containing the desired CLI command. Schedule it via the UNIX crontab application.
11.3.2
CLI commands
CLI command pvstop pvstart startpv pvmap pvconfig pvstatus Description Manually stops the NMS server Manually starts the server. Restarts the NMS server. Starts the NMS client. Opens the server configuration utility. Displays the current state of the NMS server. logger trapFD snmpServer pvman httpServer tftpServer pvSysTray Opens the client configuration utility. Clears the database, and creates empty tables. Warning: This command erases the existing data. Backup the MySQL database. Export network topology and trigger data. Import network topology and trigger data.
cmconfig createdb create pvdbbackup pvexport pvimport
Page 211 of 271
Reference
11.4
11.4.1
CLI report interface

CLI performance report format
pmreport -CLI -IP <IP list> -FFILTER <filter> -OFN <file name> -RT <report type> MAIL <target-email> -SD <date> ED <date> -FILTER <value> -USER <username> -PASSWORD <password>
For example:
pmreport CLI -IP 172.24.30.100 -FFILTER UAS>0,UAS<900,Max. RSL>-99 -OFN filename.txt -RT Radio Performance Report -USER reportUser -PASSWORD viewer Command -CLI IP Format CLI -IP <IP> <IP> Or -IP ALL -MAIL <email address> Description Command line input, tells pmreport to work in command line mode. List of element IP addresses: For example: -IP 172.24.30.100 172.24.30.101 Use ALL to generate a report for all elements in the database. Mail address of report recipients For example: -MAIL alex@mis.ca Outputs a summarized daily report. Outputs a summarized weekly report. Outputs a summarized monthly report. For example: -SD 05/17/11 12:00 For example: -SD 05/18/11 23:59 Only fields that exceed the specified value are presented. For example: -FILTER 0 - Dont show zero value fields. Filter the report by specified field value. The field name is the name as it appears in the report header: For example, UAS or Max. RSL. Allowed operators include: > >= < <= = <> User either | for OR or & for AND as boolean operators between expressions. Use a space or underscore for two word filters. For example: Min_RSL. Note: You cannot use both FILTER Page 212 of 271
MAIL
SDAY SWEEK SMONTH SD ED FILTER
-SDAY -SWEEK -SMONTH -SD dd/MM/yy HH:mm -ED dd/MM/yy HH:mm -FILTER <minimum threshold>
FFILTER
-FFILTER <field-name><operator><value> <boolean-op> <field-name><operator><value> <boolean op> ---
Reference
Command
Format
Description and FFILTER in the same command.
OFN
- OFN <filename.ext>
Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV format. The name of the user with read access to the target elements. The users password.
USER PASSWOR D -pm_type
The name of the user with read access to the target elements. The password of the user with read access to the target elements. -pm_type <pmType>
E1 T1 STM1 OC3 ETHERNET_RADIO <pmType> must be in upper-case.
11.4.1.1
CLI radio performance reports

Command RT Format -RT Radio Performance Description Report type
Radio performance report columns
Interface TSL Min TSL, Max TSL, TSL Thresh UAS, ES, SES, BBE, Integrity
RSL Min RSL, Max RSL, RSL Thresh 1, RSL Thresh 2
ACM Lowest ACM Profile, Highest ACM Profile, Lowest Bitrate, Highest Bitrate, Lowest Number of TDM Interfaces, Highest Number of TDM Interfaces
MSE Min MSE, Max MSE, MSE Threshold Exceeded,
General Date
Page 213 of 271
Reference
11.4.1.2
CLI interface performance reports

The CLI performance report utility can generate separate PMs for specific interfaces.
Command usage : pmreport -RT Interface Performance Report -pm_type <pmType>.
Note that if the RT option isnt used, the pm_type option will be ignored. Usage example:
pmreport -CLI -OFN C:\pmReport.txt -RT "Interface Performance Report" -USER admin -PASSWORD Ceragon -pm_type E1 Command RT pm-type Format -RT Interface Performance -pm_type <pmType> Description Report type <pmType> can be: E1, T1, STM1, OC3 or ETHERNET_RADIO The pmType must be upper-case.
Interface performance report columns
Interface UAS, ES, SES, BBE, Radio UAS
General Integrity, Date
11.4.1.3
CLI trail performance reports

Command RT Format -RT Trails Performance Report Description Report type
For example:
pmreport CLI -IP ALL -OFN C:\TrailPms.txt -RT Trails Performance Report -USER admin -PASSWORD reportUser
Trail performance report columns
11.4.2
Date, UAS, ES, SES, BBE, Number of switches, Active path count, Integrity The -col option is not supported for this report.
CLI inventory report format

inreport -CLI -IP <IP list> -OFN <file name> -RT <report type> MAIL <targetemail> -SD <start date> ED <end date> -USER <user-name> -PASSWORD <password>
For example:
inreport -CLI -IP 172.24.30.100 -OFN filename.txt -RT Network Element -USER reportUser -PASSWORD viewer
Page 214 of 271
Reference
Command CLI IP
Format CLI -IP <IP> <IP> Or -IP ALL -MAIL <email address>
Description Command line input, tells inreport to work in command line mode. List of element IP addresses: For example: -IP 172.24.30.100 172.24.30.101 Use ALL to generate a report for all elements in the database. Mail address of report recipients For example: -MAIL alex@mis.ca For example: -SD 05/17/11 12:00 For example: -SD 05/18/11 23:59 Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV format. The name of the user with read access to the target elements. The password of the user with read access to the target elements.
MAIL
SD ED OFN
-SD dd/MM/yy HH:mm -ED dd/MM/yy HH:mm - OFN <filename.ext>
USER PASSWORD
-USER <username> -PASSWORD <password>
11.4.2.1
CLI in-band reports

Command RT COL Format -RT In-band -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. In-band Report columns IP Address Name In-band Status Element Type Channel TTL Subnet Address Subnet Mask Network ID Ethernet Mask Default Router Address XC Slot Number
11.4.2.2
CLI interface reports

Command RT COL Format -RT Interface -COL <column_title> Description Report type Specify which report columns to Page 215 of 271
Reference
Command
Format
Description include in the report, and in which order they should appear. Interface report columns IP Address Name Slot Interface XC Slot Number
11.4.2.3
CLI interface availability reports

inreport -cli -ip <IP address> -OFN <filename> -rt " Interface Availability Report " -user <username> -password <password> -col <columns> Command RT COL Format -RT Interface -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Interface report columns IP Address Name Slot Interface XC Slot Number
11.4.2.4
CLI available interfaces reports

Command RT COL Format -RT Available Interfaces -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Available interfaces report columns IP Address Name Product Type Is Radio Interface Available Is Non-Radio Interface Available XC Slot Number
11.4.2.5
CLI license usage summary reports

inreport -CLI -IP <IP list> -OFN "<file name>" -RT <report type>" -MAIL <target-email> -SD <date> ED <date> -USER <user-name> -PASSWORD <password> Command RT Format -RT Link Description Report type
Page 216 of 271
Reference
Command COL
Format -COL <column_title>
Description Specify which report columns to include in the report, and in which order they should appear. Usage summary columns Number of licenses NE type Feature License Model Date and time
11.4.2.6
CLI link reports

Command RT COL Format -RT Link -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Link report columns IP Address Name Transmit Frequency (MHz) Receive Frequency (MHz) ATPC XC Slot Number
11.4.2.7
CLI neighbors reports

Command RT COL Format -RT Neighbors -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Neighbors report columns IP Address Name Interface IP Address Name XC Slot Number
11.4.2.8
CLI network elements reports

Command RT COL Format -RT Network element -COL <column_title> Description Report type Network element report columns IP Address Name System Name System Location Page 217 of 271
Reference
Command
Format
Description System Contact Product Type Wayside Channel
For example
inreport -CLI -IP ALL -OFN "C:\NetworkElements.txt" -RT "Network element" USER admin -PASSWORD reportUser -COL "ip,name,investigated"
11.4.2.9
CLI radio reports

Command RT COL Format -RT Radio -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Radio report columns: IP Address Name Slot ODU Type Modem Type Transmit Frequency (MHz) Receive Frequency (MHz) Min Transmit Frequency (MHz) Max Transmit Frequency (MHz) Channel Spacing (MHz) Transmit Level ATPC ATPC Reference Level Link ID XC Slot Number Multi RadioAdmin
11.4.2.10 CLI serial numbers reports

Command RT Format -RT Serial Numbers -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Serial numbers report columns IP address Name Slot Type Serial number XC Slot Number
Page 218 of 271
Reference
11.4.2.11 CLI slot population reports

Command RT COL Format -RT Slot Population -COL <column_title> Description Report type Slot population report columns Name Slot 1 to Slot 6
11.4.2.12 CLI versions reports

Command RT COL Format -RT Versions -COL <column_title> Description Report type Specify which report columns to include in the report, and in which order they should appear. Versions report columns IP Address Name Slot Type Version Post Reset Version XC Slot Number
11.4.3
11.4.3.1
CLI log reports

CLI alarms report format
alarmreport -CLI -IP <IP list> -OFN <file name> -RT <report type> MAIL <target-email> -SD <start date> ED <end date> -USER <user-name> -PASSWORD <password>
For example:
alarmreport -CLI -IP ALL -RT "Alarm Log" -OFN c:\temp\alarm.txt -user admin password admin Command CLI Format CLI Description Command line input, tells alarmreport to work in command line mode. List of element IP addresses: For example: -IP 172.24.30.100 172.24.30.101 Use ALL to generate a report for all elements in the database. Mail address of report recipients For example: -MAIL alex@mis.ca For example:
IP
-IP <IP> <IP> Or -IP ALL -MAIL <email address>
MAIL
SD
-SD dd/MM/yy HH:mm
Page 219 of 271
Reference
Command
Format
Description -SD 05/17/11 12:00
ED RT OFN
-ED dd/MM/yy HH:mm -RT <report type> - OFN <filename.ext>
For example: -SD 05/18/11 23:59 Report type Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV format. Only fields that exceed the specified value are presented. For example: -FILTER 0 - Dont show zero value fields.
FFILTER
-FFILTER <field-name><operator><value> <boolean-op> <field-name><operator><value> <boolean op> ---USER <username> -PASSWORD <password> -COL
USER PASSWORD COL
The name of the user with read access to the target elements. The password of the user with read access to the target elements. Ack Raise Time IP Slot ID Name Severity Module Description
11.4.3.2
CLI user action log report format

pvlog -CLI -IP <IP list> -OFN <file name> -RT <report type> MAIL <targetemail> -SD <start date> ED <end date> -USER <user-name> -PASSWORD <password>
For example:
pvlog -CLI -OFN "C:\UserActionlog.txt" -RT "User Action log" -USER admin PASSWORD reportUser Command CLI IP Format CLI -IP <IP> <IP> Or -IP ALL -MAIL <email address> Description Command line input, tells the pvlog to work in command line mode. List of element IP addresses: For example: -IP 172.24.30.100 172.24.30.101 Use ALL to generate a report for all elements in the database. Mail address of report recipients For example: -MAIL alex@mis.ca Start date For example: Page 220 of 271
MAIL
SD
-SD dd/MM/yy HH:mm
Reference
Command
Format
ED
-ED dd/MM/yy HH:mm
End date For example: -SD 05/18/11 23:59 Report type Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV format. The name of the user with read access to the target elements. The password of the user with read access to the target elements. User action columns Action time Application User name Connected from Description
RT OFN
-RT <User Action log > - OFN <filename.ext>
USER PASSWORD COL
-USER <username> -PASSWORD <password> -COL <Column title>
11.4.4
11.4.4.1
CLI data reports

CLI trail list report format
pvlog -CLI -IP <IP list> -OFN <file name> -RT <report type> MAIL <targetemail> -SD <start date> ED <end date> -USER <user-name> -PASSWORD <password>
NOTE:
The-col option is not supported for this report.
For example:
pvlog CLI IP ALL RT Trail List OFN C:\TrailsList.txt USER admin PASSWORD reportUser Command CLI IP Format CLI -IP <IP> <IP> Or -IP ALL -MAIL <email address> Description Command line input, tells pvlog to work in command line mode. List of element IP addresses: For example: -IP 172.24.30.100 172.24.30.101 Use ALL to generate a report for all elements in the database. Mail address of report recipients For example: -MAIL alex@mis.ca For example: -SD 05/17/11 12:00 For example:
MAIL
SD ED
-SD dd/MM/yy HH:mm -ED dd/MM/yy HH:mm
Page 221 of 271
Reference
Command
Format
OFN
Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV format. The name of the user with read access to the target elements. The password of the user with read access to the target elements. Report type Trail list columns ID Description Most severe alarm Admin state Operational status Type ACM priority
USER PASSWORD RT COL
-USER <username> -PASSWORD <password> -RT <Trail List> -COL <Column title>
11.4.4.2
CLI export data reports

pvexport -CLI -TYPE {TOPOLOGY | TRIGGERS | ALL} -GROUP <GROUP NAME> -OFN <TARGET FILE> -USER <user-name> -PASSWORD <password>
For example:
pvexport -CLI -TYPE ALL -GROUP root -OFN c:\pvdata.exp -USER admin -PASSWORD admin Command CLI TYPE Format CLI -TYPE TOPOLOGY -TYPE TRIGGERS -TYPE ALL -GROUP <group name> Description Command line input, tells inreport to work in command line mode. Type of data to export: TOPOLOGY will export only topology data, TRIGGERS will export only trigger data, ALL will export all data. The root group to start the export with. If there is more than one group with the specified name, the first one that will be found will be used. Output file name. If the extension is .txt, the file will be saved in textual format. If the extension is .csv, the file will be saved in CSV format. The name of the user with read access to the target elements. The password of the user with read access to the target elements.
GROUP
OFN
USER PASSWORD
-USER <username> -PASSWORD <password>
Page 222 of 271
Reference
11.4.4.3
CLI import data reports

Import data is used to import topology and/or trigger data from a file.
pvimport -CLI -TYPE {TOPOLOGY | TRIGGERS | ALL} -GROUP <GROUP NAME> -OFN <TARGET FILE> -USER <user-name> -PASSWORD <password>
For example:
pvimport -CLI -TYPE ALL -GROUP root -OFN c:\pvdata.exp -USER admin -PASSWORD admin Command CLI TYPE Format CLI -TYPE TOPOLOGY -TYPE TRIGGERS -TYPE ALL -GROUP <group name> Description Command line input, tells import to work in command line mode. Type of data to export: TOPOLOGY will export only topology data, TRIGGERS will export only trigger data, ALL will export all data. The root group to start the export with. If there is more than one group with the specified name, the first one that will be found will be used. An optional list of network element IPs in the format: <IP> <IP> For example: -IP 172.24.30.100 172.24.30.101 The entities in this list will be added to the topology under the group designated by the -GROUP parameter. Optional parameter. If set, the existing element will not be updated if the same element is imported. The name of the file from which the data will be imported. The name of the user with read access to the target elements. The password of the user with read access to the target elements.
GROUP
IP
-IP <IP> <IP>
NO_UPDATE
-NO_UPDATE
IFN USER PASSWORD
- IFN <filename.ext> -USER <username> -PASSWORD <password>
11.5
PolyView northbound interface

PolyView's flexible architecture allows it to be used either as a stand-alone network management system or as a supporting component for an OSS with an existing NMS.
11.5.1
PolyView northbound integration

PolyView supports all OSS for basic northbound communication, providing a deeper level of integration with the NSN open OAM. Via this interface, besides faults performance data is also sent to the northbound NSN Netact OSS.
Page 223 of 271
Reference
PolyViews trap forwarding utility allows integration with OSS network systems. PolyView can forward SNMP traps that arrive from the devices to one or more OSS network management systems. PolyView also includes an SNMP agent that provides a system-wide active alarm table, which the northbound OSS can poll when needed.
11.5.2
Northbound trap forwarding

PolyView can forward network element traps and events that arrive from network devices to one or more OSS network management systems. In addition, PolyView also forwards management alarms, such as security, license, and redundancy. Trap forwarding is a two-step process: network elements send traps to the trap forwarding utility. The trap forwarding utility forwards these traps to PolyView, encapsulates it, and sends it to the northbound traps destination. In the Internet protocol header, the sender IP of the forward trap will be the PolyView IP. In the SNMP trap header, the agent address (agent-addr) will contain the element IP address. PolyView forwards the same the SNMP version that it receives from the elements: V1, V2c, V3.
11.5.3
Configuring northbound trap forwarding

Set trap forwarding parameters specific to the OSS network management application.
To configure northbound trap forwarding settings:

2. Select the NetAct Specific tab.
3. SNMP agent address Specify the IP address. 4. SNMP agent port number Specify the agent port.
Page 224 of 271
Reference
5. NMS server ID Define a unique ID for the OSS NMS server. In the NMS server ID field, you may want to change the value When multiple NMS servers are connected to the same NSN server, make sure that each NMS server has a unique ID.
Page 225 of 271
Reference
11.5.3.1
Enabling PolyView for northbound trap forwarding

Northbound trap forwarding is configuring using PolyViews trap forwarding configuration utility.
To enable northbound forwarding, in the Trap Forwarding utility:

1. Set the Trap Forwarding mode to Regular. 2. Specify the host addresses of the target destinations. 3. Specify the listening port number for incoming traps. To avoid multiple traps being sent to the northbound OSS, network elements should only send traps to the PolyView traps receiver. Note that you can customize elements traps by setting the severity level for sending traps and enabling or disabling heartbeat traps. You can also modify the polling interval that PolyView uses to poll network elements.
11.5.4
Scheduling reports for the northbound NMS

Report Information: Using the PolyView CLI interface, you can generate different reports, such as Current alarms, Alarm log, Performance management, Inventory, and User actions. The reports can be forwarded to the northbound OSS automatically and periodically (in accordance with user preference) in plain text or CSV format.
11.5.5
Scheduling reports for the northbound NMS

Using the PolyView CLI interface, you can generate different reports, such as Current alarms, Alarm log, Performance management, Inventory, and User actions. The reports can either collected or forwarded to the northbound OSS automatically and periodically (in accordance with user preference), in plain text or CSV format.
11.5.6
Northbound trap synchronization

When a trap detected from the network element was not received, PolyView will generate the trap for the network element and send it to the northbound OSS. When a trap detected from the network element was not received, PolyView will generate the trap for the network element and send it to the northbound OSS. PolyView will raise node down trap (nmsNodeDown Alarm ID 63, trap ID 401) for the unreachable element. Upon resuming connection, PolyView will send a node up trap. (nmsNodeUp Alarm ID 63, trap ID 501).
To enable alarm synchronization:

1. Enable trap forwarding of the nmsAlarmLastChange event. The nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1) is a counter that advances every change of the current alarm table and compares it with the OSS alarms/traps counter.
2. Allow the OSS NMS access to the PolyView alarm table.
Page 226 of 271
Reference
If the value is not the same, the OSS must poll the current PolyView alarm table, nmsCurrentAlarmTable (which contains all IP-10, x1500, PolyView, and 3rd party current alarms). This will synchronize all alarms in the current alarm table.
11.5.7
Northbound alarm synchronization

For northbound interfaces, PolyView provides an alarm synchronization mechanism. PolyViews SNMP agent provides a system -wide active alarm table, which the northbound OSSs can poll when needed. An external OSS can poll the alarms counter and the current alarm table through SNMP. To enable alarm synchronization, allow the OSS NMS access to the PolyView alarm table and enable trap forwarding of the nmsAlarmLastChange event. The nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1) is a counter that advances every change of the current alarm table and compares it with the OSS alarms/traps counter. If the value is not the same, the OSS must poll the current PolyView alarm table, nmsCurrentAlarmTable (which contains all IP-10, x1500, PolyView, and 3rd party current alarms). This will synchronize all alarms in the current alarm table.
11.5.8
Enabling network elements for northbound trap forwarding

Ceragon MIB objects to configure traps of network element of IP-10 series. genEquipTrapCfgMgrAdmin Enables/ disables a specific manager. When disabled - will not send traps to this trap manager. genEquipTrapCfgMgrIP Configures the managers IP address. genEquipTrapCfgMgrPort Configures the port that sends the trap for each manager. genEquipTrapCfgMgrName Configures the name of the manager that receives the traps. genEquipTrapCfgMgrCommunity Configures the trap manager community. genEquipTrapCfgMgrSeverityFilter Bit mask value for masking traps according to its severity. genEquipTrapCfgMgrStatusChangeFilter Enables or disables filtering alarms according to a change in the trap severity filter. genEquipTrapCfgMgrCLLI Configures the Common Language Location Identifier (CLLI), a user input that will be sent in a field in the trap varbind genEquipTrapCfgMgrHeartbeatPeriod Configures the minute interval between each heartbeat.
Page 227 of 271
Reference
Ceragon MIB objects to configure traps of network element of 1500 series gnAgnMgrId This value indicates an index of a specific manager.
gnAgnMgrIP This value indicates the managers IP address. An IP address of all zeroes (0.0.0.0) will remove the entry.
gnAgnMgrAlarmGroupMask bit mask .1 is 'send a trap' 0 is doesnt send any traps'. The list of alarms from MSB to LSB is: bit 1 = Power supply alarm bit 2 = Cable alarm bit 3 = Temperature alarm bit 4 = External alarm bit 5 = Radio alarm bit 6 = Modem alarm bit 7 = Line alarm bit 8 = SDH alarm bit 9 = BER alarm bit 10 = System fault alarm bit 11 = Maintenance alarm If this field is 0, only standard traps will be sent to the manager
gnAgnMgrSeverityFilter This is a bit mask value for masking traps according to their severity. There is a bit for each severity. If the relevant bit is on (1), then the Agent will send traps with this severity The list of bits from LSB to MSB: bit 1 (LSB) = Event.
Page 228 of 271
Reference
bit 2 = Warning. bit 3 = Minor. bit 4 = Major. bit 5 (MSB) = Critical.
gnAgnMgrTrapPort The port for sending the trap for each manager (possible values: 70-65535)
gnGenCfgCLLI Common Language Location Identifier (maximum length 30 characters). This string is added as a field in the trap.
gnGenCfgHeartbeatPeriod Configure the element to send heartbeat trap. The value is in minutes. Setting the value to 0 disables this feature.
gnGenCfgTrapOption This item defines various trap options. It is a bitmask: i.e., you can set multiple options, by doing bitwise OR between their values. Possible values are:
Standard traps include serial number. If selected, the unit serial number is added only to the standard traps such as "Link Down" Not supported for the 1500P family. Use different trap ID for each alarm type. This option normally should be set, otherwise, the traps are grouped together, and sent with trap ID 1 to 8. Send 'Cleared' traps with zero severity. Otherwise they will be sent with the same severity as the "Raised" trap.
gnGenAddAlarmExtToTraps If this entry enabled, extended information is added to each Ceragon trap. Those additional parameters are added after the last parameter of the trap, as defined in the MIB. Note that PolyView requires this option to be enabled.
Page 229 of 271
Reference
11.5.9
Northbound heartbeat trap mechanism

PolyView can be configured to forward heartbeat traps from network elements to a northbound OSS. When both IP-10 and PolyView are configured to send heartbeat traps to northbound. 1. IP-10 sends heartbeat traps with ID (specific trap) 1003 to PolyView. 2. PolyView receives the traps encapsulates it and sends it as is to northbound. 3. Northbound receives heartbeat traps from PolyView with agent address of IP-10 and with ID 1003. 4. PolyView sends heartbeat traps with ID (specific trap) 49 to northbound. 5. Northbound receives heartbeat traps from PolyView with ID 49. Since PolyView forwards traps to northbound without analyzing the trap type, alarms will not be raised for missing or resumed heartbeats. PolyView is notified about unreachable network elements only if the network element is still down during the next polling cycle. The way to stop heartbeat trap forwarding is to either disable trap forwarding from PolyView or to disable forwarding of heartbeat traps from the network elements.
11.6
Server redundancy
PolyView has built-in support for redundancy configuration. This 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.
PolyView redundancy schema
Page 230 of 271
Reference
11.6.1
The role of the secondary server

While a secondary server is on standby, its server duties are usually limited to polling network elements. By default, a secondary server will poll only for alarms, but network administrators can configure the secondary to poll also for inventory information and PMs. Administrators who are concerned about the toll of two servers polling the network can also configure the secondary server to not do any polling at all. When a secondary server becomes active, it immediately takes over all the defined tasks of the main server. It immediately begins polling the network, activating triggers, and forwarding traps.
A secondary server takes over automatically when: It loses connection with the main server. The main server loses connection to PolyView clients. The network administrator forces the secondary server to be active mode. A secondary server resumes standby mode when: When the main server is active. 11.6.2 Synchronizing network data over redundant servers
In a redundant server configuration, data that is imperative for the well functioning of the servers, such as topology and security information, is usually synchronized from the primary to the secondary server. Administrators can also set synchronization to work in both directions, or disable it altogether.
Topology data, trigger definitions, and security settings are included in the synchronization. Configuration settings may differ between servers and are not included in the synchronization process.
11.6.3
Configuring the main server To configure the main server for a redundant system:
2. Select the Redundancy tab.
Page 231 of 271
Reference
3. For Server role, choose Main server. 4. In the Connection timeout to standby server field, specify the number of minutes before generating an alarm after losing connection with the standby server. 5. Click Apply to save these settings. 6. Click Close to close the PolyView server config utility. 7. Restart the main server.
11.6.4
Configuring the secondary server To configure the secondary server for a redundant system:
2. Select the Redundancy tab.
Page 232 of 271
Reference
3. Choose Standby-Auto-switch as the Server role. 4. Enter the details of the primary server: In the Main server host address field, specify the IP address of the main PolyView server.
5. Specify activation and deactivation settings: In the Standby activate time field, specify the number of minutes after which the standby server will be active when the connection to the main server is down. In the Standby deactivate time field, specify the number of minutes after which the standby server will be muted when the main server resumes operation. In the Main server management threshold field, specify the percentage of unreachable network elements that will force a switch to the standby server.
Note that the standby server will switch to Active state only if the standby server management threshold has not been crossed.
In the Standby server management threshold field, specify the percentage of unreachable network elements that will mute the standby server.
Note that the standby server will switch to Mute state only if the main server management threshold has not been crossed.
6. Define synchronization preferences. In the Main-standby synchronization field, choose a synchronization mode between the main and the standby servers.
Disabled disables the synchronization feature.

Page 233 of 271
Reference
Full causes changes in one server (main or standby) to be made in the other server as well. Only from main to standby - (recommended setting) causes changes in the main server to be made in the standby server as well, but not vice versa. Only from standby to main - causes changes in the standby server to be made in the main server as well, but not vice versa.
In the Sync interval field, specify the number of minutes between synchronization updates between the main and standby servers.
7. In the Mute standby server poll mode field, specify the level of polling activity for the secondary server to perform while its in standby mode. No data polled - When the secondary server is in standby mode, polling of data from network elements will be disabled. When the server becomes active, polling will resume. Poll only alarms - This is the recommended and default setting. When the secondary server is in standby mode, only alarm information will be polled from network elements. Poll alarms and inventory - When the secondary server is in standby mode, only alarm and inventory information will be polled from network elements. Poll all data - When the secondary server is in standby mode, all data will be polled by both the primary and the secondary servers.
8. Mirror any proxy settings that you enabled in the main server. Click the General tab to configure proxy settings.
Note that for HTTP and HTTPS proxy, youll also need to change your browser settings to recognize both the main and standby PolyView servers as proxies..
9. Click Apply to save these settings. 10. Click Close to close the PolyView server config utility. 11. Restart the secondary server.
11.6.5
Configuring primary and secondary server host addresses

When working with redundant servers, NMS users must specify the addresses of both the primary and secondary servers in the CeraMap config utility. If an active client fails to connect to the primary server, it will try connecting to the secondary server that was configured.
To specify primary and secondary server host addresses:

2. Click the Remote Hosts tab.
Page 234 of 271
Reference
3. Primary NMS server host address Specify the IP address or hostname of the primary server. 4. Secondary NMS server host address Specify the IP address or hostname of the secondary server. 5. Click Apply to save changes. 6. Click Close to exit the CeraMap Client config utility.
11.6.6
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.
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).
Page 235 of 271
Reference
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.
11.7
SNMP MIB support

Ceragon NMS-MIB functionalities PolyView supports Ceragons proprietary NMS-MIB. The main functionality of the MIB for HighCapNMS is the current alarm table. PolyView MIB uses the current alarm as defined in the Ceragon MIB. The current alarm table includes: NMS server alarms All network element alarms, including alarms for the IP-10 and the x1500. In addition to the current alarms there are two scalars: nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1 ) a counter that advance every
change of the current alarm table.
nmsMostSevereAlarm (1.3.6.1.4.1.2281.2.2.15.1.3( - the most severe alarm within the current alarm table.
Note the following: Only SNMP V.1 is supported. The default Server SNMP port number is 1610 (configurable). The community string for Read only is public. There are no write permissions for the MIB. 11.7.1
11.7.1.1
NMS current alarm table (nmsCurrentAlarmTable)

NMS current alarm table columns
nmsCurrentAlarmCounter - A running counter of open alarm, the counter is incremented on every new RAISED trap. It is cleared after reset. nmsIpAddress The IP address of the NE that the alarm is raised upon. It could be the NMS servers IP for NMS alarms, or a NE IP for any NE alarm. nmsCurrentAlarmSeverity The severity of the alarm. The following severities can be for the alarms
event (1) warning (3) minor (7) major (15)

Page 236 of 271
Reference
critical (31) node down (63) - this is for unreachable NEs raised by the NMS server only.
nmsCurrentAlarmId - Alarm Identifier (contains alarm type and interface). Same AlarmId for raise and clear alarms. nmsCurrentAlarmIfIndex- Interface Index where the alarm occurred, alarms that are not associated with specific interface will have the following value (for example, for the x1500):
For IDC related alarms the value is: 65001 For drawer1 related alarms the value is: 65003 For drawer2 related alarms the value is: 65004 If Alarm's origin is bigger than 256, it will be 65000 + the origin
nmsCurrentAlarmOrigin- The origin drawer of the alarm (if applicable, otherwise it will be idc(2)) other possible values are based on gnAgnCurrentAlarmOrigin:
Interfaces(1), idc(2), drawer1(3), drawer2(4), unknown(5), tIdc1(257), tIdc2(258), tIdc3(259), tIdc4(260), tIdc5(261), tIdc6(262), tIdc7(263), tIdc8(264), tIdc9(265), tDrawer1(513), tDrawer2(514), tDrawer3(515), tDrawer4(516), tDrawer5(517), tDrawer6(518), tDrawer7(519), tDrawer8(520), tDrawer9(521), tDrawer10(522), tDrawer11(523), tDrawer12(524), tDrawer13(525), tDrawer14(526), tDrawer15(527), tXC1(769), tXC2(770), tXC3(771), tXC4(772), tXC5(773), tXC6(774)
nmsCurrentAlarmUnit- The unit of the alarm, possible values are:

11.7.1.2
idc(2), odu(3), mux(4), modem(5), drawer(6), unknown(7), xc(9) ODU (101)
nmsCurrentAlarmTrapID- The trap ID of the RAISED trap that was sent when this alarm was raised. nmsCurrentAlarmTimeT Timestamp of this alarm, this number is the seconds from midnight 1.1.1970 nmsCurrentAlarmText- The alarm display text (same as the text in the sent trap).
IP-10/ IP-10G current alarm mapping to the NMS current alarms

Var-bind mapping IP-10 to NMS current alarms IP-10 trap VarBind/Current Alarm Column Trap var-bind & current alarm column
IP-10 Var-Bind
NMS Var-Bind
Comments
genEquipCurrentAlarmCounter
nmsCurrentAlarmCounter
No mapping. The NMS counter is different from the NE counter. Mapping 1:1
Trap var-bind & current alarm column
genEquipCurrentAlarmRaisedTi meT
nmsCurrentAlarmTimeT
Page 237 of 271
Reference
IP-10 trap VarBind/Current Alarm Column Trap var-bind & current alarm column Trap var-bind & current alarm column Trap var-bind & current alarm column Trap var-bind & current alarm column Trap var-bind & current alarm column Trap var-bind & current alarm column Trap var-bind only Trap var-bind only Trap var-bind & current alarm column
IP-10 Var-Bind
NMS Var-Bind
Comments
genEquipCurrentAlarmId
nmsCurrentAlarmId
Mapping 1:1
genEquipCurrentAlarmInstance
NA
No mapping
genEquipCurrentAlarmSeverity
nmsCurrentAlarmSeverity
Mapping 1:1
genEquipCurrentAlarmIfIndex
nmsCurrentAlarmIfIndex
Mapping 1:1
genEquipCurrentAlarmModule
nmsCurrentAlarmUnit
Mapping IDU : 101 ODU : 3 (odu) Mapping 1:1
genEquipCurrentAlarmDesc
nmsCurrentAlarmText
genEquipMostSevereAlarm genEquipNetworkAgentIp genEquipCurrentAlarmState
NA nmsIpAddress NA
No mapping Mapping 1:1 No mapping (no need, as only the raised traps will be in the table) No mapping The trap ID of the alarm (SNMP v.1) No mapping
Trap var-bind only Trap id
genEquipTrapCfgMgrCLLI NA
NA nmsCurrentAlarmTrapID
Current alarm column only
genEquipCurrentAlarmName (the parameter and entity in the CLI) for example 'radio/framer/radio-lof') genEquipCurrentAlarmSlotId
NA
Trap var-bind & current alarm column
nmsCurrentAlarmSlotId
1000 SA IP-10 1001 IP-10G slot 1 1002 IP-10G slot 2 1003 IP-10G slot 3 1004 IP-10G slot 4 1005 IP-10G slot 5 1006 IP-10G slot 6
Current alarm column only
genEquipCurrentAlarmProbable Cause
nmsCurrentAlarmProbableCa Alarm Probable use Cause
Page 238 of 271
Reference
IP-10 trap VarBind/Current Alarm Column Current alarm column only
IP-10 Var-Bind
NMS Var-Bind
Comments
genEquipCurrentAlarmCorrective nmsCurrentAlarmCorrectiveA Alarm Corrective Actions ctions Actions
11.7.2
NMS traps
The list of NMS traps are defined in Ceragon NMS MIB, and in the alarm chapter.
NMS traps are sent with the following var-binds gnGenCfgTrapSeverity: gnGenCfgAlarmText: gnGenCfgCLLI: gnAgnCurrentAlarmOrigin: gnAgnCurrentAlarmUnit: gnAgnCurrentAlarmTimeT: gnAgnCurrentAlarmID: Severity of the trap (nmsCurrentAlarmSeverity) Alarm text (nmsCurrentAlarmText) Fixed empty string will be sent ("") - not supported 400 (fixed number) will be sent - not supported 400 (fixed number) will be sent - not supported Timestamp of this alarm, nmsCurrentAlarmTimeT will be sent. For event - 0 (integer), for alarm it will be equal to the trap ID of the raise alarm (400+).Trap-ids starting from 500 are always clearing raise alarms starting in 400. There is a difference of 100 between raise and clear alarms, for example, Trap 401 is a raise alarm, while 501 is the clear alarm for it.
11.8
PolyView support for floating IP addresses

The network element can be configured to enable a floating IP address in a 1+1 slot protection configuration. The Floating IP is an additional IP added to an element configured for 1+1 HSB (hot standby). The element has three IP addresses as follows: One IP for each unit (slot, altogether two) Another floating IP for the current active unit
11.8.1
Auto discovery
The network element can be found by one of its three IP addresses. PolyView can identify that it is the same network element (one icon). Note: IP-10G standalone does not support a floating IP.
Page 239 of 271
Reference
11.8.2
Add network element

Adding an element manually can be done while adding one of the IPs supported by the element (three options, including the floating IP). Note that PolyView does not support IP configuration or change in the element; it can only be discovered.
11.8.3
Inventory reports
In all inventory reports, the floating IP will be the main IP of the element (the IP address column).
11.8.4
Network element configuration

Any configuration of the element (that is using a floating IPwill be done via its floating IP. IP-10G specifically supports the ability to configure the active slot in a 1+1 configuration via the extensions.
11.8.5
Network element notifications

Traps (from active or standbywill be sent with the floating IP address. The slot number inside the trap will be the slot that was sending the trap. Alarms should be saved in the current alarm log as usual (with the floating IP). Events should be saved in the event log. Trail status events should be handled when they are sending via the floating IP.
11.8.6
Enable/Disable floating IP
NOTE: Enabling or disabling floating IP requires a new discover node of the element.
When polling inventory from the element, if PolyView understands that the element was configured with a floating IP, If the user did not discover the node after enabling or disabling, an alarm will be raised (Floating IP added, severity Minor). See the alarm table below. The alarm should be cleared after the discovered node process.
Trap name nmsFloatingIPAdded nmsFloatingIpCleared Description Floating IP added Floating IP cleared ID 419 519 Severity Minor Minor
Page 240 of 271
Reference
Disable floating IP procedure

1. When you disable a Floating IP in the element, do not use the floating IP in another element before discovering the node. 2. Perform discover node. NOTE: If discover node is run while the element does not have a slot 1 connection, the element will not be discovered. Disabling the floating IP in the element, will cause the element to be unreachable (if discover node was not done). If discover node was not done, and the PolyView polled the inventory, an alarm will be raised (as defined above).
NOTE:
NOTE:
Enable floating IP procedure

3. Enable Floating IP in the element. 4. Perform discover node.
11.8.7
Delete network element

Deleting an element and adding it again using a floating IP will cause the abandonment of the database of the old element, and the building of a new database for the new element. This option is not advised.
Page 241 of 271
Reference
11.9
11.9.1
11.9.1.1
Reports
Performance monitoring reports
Radio performance
Radio channels
Page 242 of 271
Reference
Radio MRMC performance
Radio MSE performance
Page 243 of 271
Reference
Radio RSL performance
Radio TSL performance
Page 244 of 271
Reference
Radio XPI performance
11.9.1.2
Radio Ethernet performance

The Radio Ethernet performance report displays Ethernet service performance parameters.
Frame error rate
Page 245 of 271
Reference
Frame Error Rate (%) is the number of received error frames measured by the radio Ethernet port, relative to all frames received by the radio Ethernet port. Integrity indicates whether the values received at that time and date are reliable. An x in the column indicates that the values are not reliable due to a possible power surge or power failure that occurred at that time.
Throughput
The Throughput parameters displays radio Ethernet throughput statistics (excluding TDM traffic), measured on the radio port.
Peak Throughput (bps) is the maximum throughput measured during the last interval. Average Throughput (bps) is the average throughput measured during the last interval. Throughput Exceed (Seconds) is the number of seconds the throughput exceeded the threshold (configured in the field below the table) during the last interval. Integrity indicates whether the values received at that time and date are reliable. An x in the column indicates that the values are not reliable due to a possible power surge or power failure that occurred at that time.
Page 246 of 271
Reference
Capacity
The Capacity parameters displays statistics of the Ethernet capacity (including Ethernet data and overhead bytes) measured on the radio port.
Peak Capacity (bps) is the maximum capacity measured during the last interval. Average Capacity (bps) is the average capacity measured during the last interval. Capacity Exceed (Seconds) is the number of seconds the throughput exceeded the threshold (configured in the field below the table) during the last interval. Integrity indicates whether the values received at that time and date are reliable. An x in the column indicates that the values are not reliable due to a possible power surge or power failure that occurred at that time.
Page 247 of 271
Reference
Utilization
The Utilization parameters display statistics of Ethernet utilization (%) measured on the radio port. Ethernet utilization is a measurement of actual Ethernet throughput, relative to the potential Ethernet throughput of the radio (excluding TDM channels). The Utilization threshold percentage is the utilization threshold percentage which was specified in the radio unit. Ethernet utilization during the last interval is displayed as one of five bins: 0-20%, 20-40%, 40-60%, 60-80%, 80-100%.
Range of Peak Utilization (%) is the maximum utilization measured during the last interval. Range of Average Utilization (%) is the average utilization measured during the last interval. Utilization Exceed (Seconds) is the number of seconds the value exceeded the threshold during the last interval. Integrity indicates whether the values received at that time and date are reliable. An x in the column indicates that the values are not reliable due to a possible power surge or power failure that occurred at that time.
Page 248 of 271
Reference
11.9.1.3
Interface performance reports

The Interface performance report shows performance measurements for line (E1 / DS1/ STM1 / OC-3) interfaces.
Date records the time that the data was polled. UAS is the Unavailable Seconds value of the current interval. The value can be between 0 and 900 seconds (15 minutes). ES is the number of seconds during which errors occurred. SES is the number of severely errored seconds. . Sever errors lasting longer than 10 seconds are recorded as Unavailable Seconds (UAS). BBE is the number of background block errors. The Integrity column indicates whether the values received at that time and date are reliable. An x in the column indicates that the values are not reliable due to a possible power surge or power failure that occurred at that time.
Page 249 of 271
Reference
11.9.1.4
TDM trail performance report

The TDM trail performance reports shows Bit Error Rate (BER) measurements for a trail. If TDM trail path protection is enabled, the system performs measurement on both the primary and secondary paths.
Date records the time that the data was polled. UAS is the Unavailable Seconds value of the current interval. The value can be between 0 and 900 seconds (15 minutes). ES is the number of seconds during which errors occurred. SES is the number of severely errored seconds. . Sever errors lasting longer than 10 seconds are recorded as Unavailable Seconds (UAS). BBE is the number of background block errors. Number of switches indicates the number of protected switches. Active path count indicates the number of active paths. The Integrity column indicates whether the values received at that time and date are reliable. An x in the column indicates that the values are not reliable due to a possible power surge or power failure that occurred at that time.
Page 250 of 271
Reference
11.9.2
11.9.2.1
Inventory reports
In-band reports
In-band management uses the network management software to send management packets through the same network it is managing.
IP address - displays the IP address of the network element. The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and it should be managed via the active unit. IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest
Slot number indicates the slot number of the interface.
Name indicates the slots system name. In-band status indicates the management type, either In-band or Out-of-band. Element type indicates the type of network element. Channel indicates user channel availability. TTL displays the Reply TTL hop number Subnet address displays the IP address of the subnet. Subnet mask Displays the subnet mask string describing the network and host addresses. Network ID shows the TCP/IP address used to identify the subnet.
Page 251 of 271
Reference
11.9.2.2
Interface reports
The Interface report presents data polled from network interfaces.
Name indicates the slots system name. Slot displays the number of enabled interfaces out of the total number of interfaces. Interfaces indicates the names of available interfaces. Wayside interface reports if the connector type is RJ-45. Wayside admin indicates whether the wayside channel is enabled or disabled.
Page 252 of 271
Reference
11.9.2.3
Available interfaces report

The Available interfaces report presents the location and availability of network element radio interfaces.
IP address - displays the IP address of the network element.
The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and it should be managed via the active unit.
IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest
Name indicates the slots system name. Product type indicates the network element type. Is radio interface available indicates whether or not radio interface is available. A radio interface is considered disabled if
The Radio Admin state is set to Disable A reset was performed, and the operational state is Down. The local-remote status is unavailable for the interface. A radio interface is considered enabled if The RadioAdmin state was set to Disable, but no reset was performed.
Is non-radio interface available indicates availability of non-radio interface.
Page 253 of 271
Reference
11.9.2.4
Interface availability reports
Name indicates the slots system name. Slot label Displays the name of the slot unit across the radio link. Radio Displays the number of enabled radio interfaces out of the total number available. E1/DS1 Displays the number of enabled E1 and DS1 interfaces out of the total number available. STM-1 / OC-3 Displays the number of enabled STM-1 and OC-3 interfaces out of the total number available. Optical GE Indicates the number of enabled optical GE interfaces out of the total number available. Electrical GE Indicates the number of enabled electrical GE interfaces out of the total number available. Combo GE Indicates the number of enabled combo GE interfaces out of the total number available. FE Indicates the number of enabled FE ports out of the total number available. UC Indicates the number of enabled UC interfaces out of the total number available. EoW Indicates the number of Engineering Order Wire (EoW) interfaces out of the total number available. WS Indicates the number of enabled wayside Ethernet interfaces out of the total number available.
Page 254 of 271
Reference
11.9.2.5
Licensing reports
The Licensing report provides data about which licenses are enabled for each network element.
IP address - displays the IP address of the network element. The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and it should be managed via the active unit.
Slot number indicates the slot number of the interface. IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest
License indicates the license status. License type indicates the license type. License code displays license validity code. License per usage indicates the capacity of the license feature. Demo admin indicates if the demo license is enabled or disabled. Demo timer indicates the remaining validity period of the license for trial or demo licenses. Feature indicates which feature set is enabled by the license. Usage configuration indicates if the feature is allowed or not allowed for the given license. License model indicates the license model for allowed features.
Page 255 of 271
Reference
11.9.2.6
Link reports
The Link report provides data about links, such as transmit and receive frequencies and slot number locations.
Link Name a text name given to the link by the user. IP address - displays the IP address of the network element. The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and it should be managed via the active unit. IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest
Name indicates the slots system name. Transmit frequency indicates the transmit frequency for that end of the link. Receive frequency indicates the receive frequency for that end of the link. ATPC indicates whether the link is using Ad hoc TCP.
Link reports are unavailable for disabled radio interfaces.
Page 256 of 271
Reference
11.9.2.7
Neighbors reports
The Neighbors report provides data about the IP addresses of the units on a link.
Name indicates the slots system name. Interface indicates the interface type and the port number. Neighbor IP address indicates the IP address of the neighboring interface. Neighbor name indicates the system name for the neighboring interface slot. Neighbor interface indicates the interface type and the port number for the neighboring interface. Neighbor slot number indicates the slot number of the neighboring interface, or the two slot numbers for a protected unit. Config manually indicates whether the link can be configured manually. This option is currently unavailable for Ethernet link types.
Neighbor reports are unavailable for disabled radio interfaces.
Page 257 of 271
Reference
11.9.2.8
Network element reports

The Network element report provides status information and data about indoor units.
Status indicates the availability of the network element: reachable, unreachable, or uninvestigated. Last reachable indicates the last reachable date and time of the network element. Applicable only for network elements with a status state of Reachable or Unreachable.
Name indicates the network elements User defined name. System name indicates the system name of the network element. System contact indicates the network user responsible for the network element. System location indicates the physical location of the network element. Product type indicates the type of network element.
Page 258 of 271
Reference
11.9.2.9
Protection reports
The Protection report provides data about protected configurations in the network. Note that for protected IP-10G series network elements PolyView presents alarms and report data for the IP address of the active slot. Only protected slots are included in the protection reports.
IP address - displays the IP address of the network element. The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and it should be managed via the active unit. The IP address of the network elements Slot 1, which acts as the primary IP address for a protected unit. The floating IP address for the network element, if it is using floating IP instead of a permanent IP address.
IP displays either:
Mate IP displays the IP address of the secondary slot. Slot number indicates the slot number of the interface. IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest For slots enabled with 2+2, protection, the slot number will be the slot of the primary slot (Slot 1, 3, or 5).
Type indicates the type of protection: 1+1 HSB, 2+2 HSB, or 2+0 HSB (Multi radio with line protection). Mode indicates the admin state of the protection, either Active or Standby.
Page 259 of 271
Reference
11.9.2.10 Radio reports

Radio reports display inventory information of outdoor units.
Name indicates the slots system name.

Page 260 of 271
Reference
ODU type displays the product type of the ODU. Modem type indicates the type of modem in use. Transmit frequency (MHz) indicates the transmit frequency measured during the interval. Receive frequency (MHz) indicates the receive frequency measured during the interval. Min transmit frequency (MHz) indicates the minimum received level measured during the interval. Max transmit frequency (MHz) indicates the maximum received level measured during the interval. Channel spacing (MHz) indicates the allocated bandwidth for the RF channel Transmit level indicates the average transmit level for the measured interval. ATPC indicates the Automatic Transmit Power Control status (enabled or disabled). ATPC reference level indicates the Received Signal Level value. Link ID displays the link ID. Admin state reports whether the radio interface is Enabled or Disabled. Operational status indicates whether the radio is operational. MultiRadio admin indicates the status of the multi- radio unit (enabled or disabled).
11.9.2.11 Serial number reports

The Serial numbers report shows the serial number for each network element.
Page 261 of 271
Reference
Name indicates the slots system name. Slot indicates the name of the slot across the unit. Type indicates the unit type: IDU or RFU. Serial# indicates the device ID. Part# indicates the part number of the interface.
11.9.2.12 Slot population reports

The Slot population report shows the IP address of each slot's IDU and its availability.
Name indicates the slots system name. Slot 1-6 indicates the availability status for each slot in the shelf. IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest
Page 262 of 271
Reference
11.9.2.13 Versions reports

The Versions report provides data about which software and firmware versions are installed on network elements. Double-clicking a line in a versions report opens a page with additional information about the version type.
Name indicates the slots system name. Slot indicates the name of the main slot. Type indicates the product type. Version indicates the installed software version on the unit. Post reset version indicates the updated version after a software upgrade.
Page 263 of 271
Reference
11.9.2.14 xSTP reports

The xSTP report provides data about active and inactive xSTP paths.
Name indicates the slots system name. Admin state indicates if the port is Enabled or Disabled. Bridge ID indicates the MAC address of the bridge in the active IDU. Is edge indicates whether the port is a service access point on the ring, or is functioning as one of the ring edges. Operational state indicates if the ports operational status is active (UP) or inactive (DOWN). Port number indicates which port has been enabled for RSTP traffic. Bridge priority indicates the specific (ACM?) priority for this interface. Designated path cost indicates the path cost for this port. The lower the value the more likely that port is used. Role indicates the role of the bridge: Root or Designated. Root ID - The MAC address of the root bridge. Root Path Cost - The cost of the path from the active IDU to the root bridge. State indicates whether the port state is Disable, Forwarding, Learning, or Blocking. xSTP protocol indicates which STP protocol is in use: standard RSTP or Ring RSTP. If RSTP has been configured but disabled, the xSTP protocol status will be Disabled.
Page 264 of 271
Reference
11.9.3
11.9.3.1
Logs
Alarm log
IP indicates the IP address of the unit where the alarm was raised Slot number indicates the slot number where the alarm was raised. Name indicates the system name of the unit where the alarm was raised. Severity indicates the severity of the alarm. Ack indicates whether the alarm has been acknowledged: True or False. Time indicates the raise time of the alarm. Status indicates the status of the alarm: Raised or Cleared. Module indicates the type of interface where the alarm was raised. Description provides a one sentence summary of the alarm. Details about each alarm, including its probable causes and suggested corrected actions, are available in a separate window.
Alarm severity
Alarm severity is classified into seven categories. Alarm severity is represented in the client GUI by colors that correspond to the alarm severity classes. The color of a map entity indicates its most severe alarm:
Clear 0 Green Event 1 Blue Warning 3 Yellow Minor 7 Orange Major 15 Dark orange Critical 31 Red Node down 63 Grey
Severity Weight Color
Page 265 of 271
Reference
11.9.3.2
User actions log
Action time indicates the date and time of the logged user action. Application indicates the application where the action was performed. User name indicates the username of the user who performed the action. Connected from indicates the IP address of the user who performed the action. Description describes the feature set of the logged action, using the system command name to describe which action was performed. For example, Topology, add network element. When available, the log will add details about the action. Using Add network element as an example, logged details could include the type of network element that was added and its IP address.
List of optional user actions for the users actions log report
Operation area Alarms Alarms Alarms Alarms Alarms Alarms Alarms Configuration Broadcast Configuration Download Connected Users Connected Users Details Acknowledge Delete alarm from current alarm Delete alarm from current alarm Delete Alarms Hide Note Show Run Run Disconnect User Display Message Page 266 of 271
Reference
Operation area Discover Node Dynamic Security Edit EVC Import Data Login Network Auto Discovery Topology Run Scheduled Task Software Download Software Download Software Download Software Download Topology Topology Topology Topology Topology Topology Topology Topology Topology Topology Topology Topology Topology Topology Trail Trail Trail Trail Trail Trail Trail Trail Triggers Logout
Details Run Configuration Configuration Run Login CeraMap Discover Remove NE Run Data Delete Scheduled Status Add Group Element Add Link Add Network Element Add Symbol Add Text Configure Group Configure Link Configure Network Element Configure Symbol Configure Text Delete Link Delete Topology Element Move Element Relocate Topology Element Advanced Trail Configuration Create Trail Delete Trail East West Validation Edit Trail Fix Trail LoopBack Switch Trail Active Path Configuration Logout CeraMap
Page 267 of 271
Reference
11.9.4
11.9.4.1
Service lists
Trail lists
Trail ID and Trail description are trail identifiers. Most severe alarm indicates the severity level of the most severe alarm on the trail. Admin state indicates whether the selected trail is Operational or Reserved. Operational state indicates whether the trails operational status is Operational or Reserved. ACM priority indicates High or Low priority for which trails will be dropped first from radio links when bandwidth is reduced. Type indicates the type of trail protection. Protected trails allow traffic from two different paths, with different methods of allocating bandwidth. Dual ended protected
Page 268 of 271
Reference
trails have three end points, with outgoing traffic is split between two alternative endpoints. Unprotected indicates a point-to-point trail. Protected 1+1 indicates permanent use of bandwidth for both paths. In a protected 1+1 configuration, instead of a single IP address for both units, the node has two IP addresses, those of each of the main units. The IP address of the active main unit is used to manage the node. Protected ABR indicates protection with dynamic allocation of bandwidth.
Protected ABR is a unique network level method of dynamic capacity allocation for TDM and Ethernet flows. By using the bidirectional capabilities of the ring, TDM-based information is transmitted in one direction and unused protection capacity is allocated for Ethernet traffic, making better use of bandwidth and effectively doubling the capacity of wireless rings.
Protected 1+1 DE indicates dual ended protection with permanent allocation of bandwidth. Protected ABR DE indicates dual ended protection with dynamic allocation of bandwidth.
End point parameters
Name indicates the slots system name. Slot indicates the name of the main slot.
Page 269 of 271
Reference
11.9.4.2
EVC lists
EVC ID and EVC description display are service identifiers. Transport VLAN type indicates whether the transport VLAN is configured with CVLAN or S-VLAN. EVC type: E-LINE or E-LAN E-LINE indicates a service with only two Service Access Points (SAPs). E-LAN indicates a service with more than two SAPs.
Admin state indicates whether the service is Enabled or Disabled. Operational state can be: Unknown The operational state will be changed to Unknown if any of the network elements along the service become unreachable by the NMS.
Page 270 of 271
Reference
Up The service operational state will be Up if there is a connection between the SAP, all service ports are Enabled (admin state) and UP (operational state), and the VLAN is configured correctly for all the ports along the service. Up unprotected When there is more than one path available between two SAPs and the service is configured on an RSTP ring, the Operational state of the service will be Unknown when there is only one path available for the service. Down If the operational state of any of the service ports is Down and causes a lack of connection between two or more SAPs, the operational state of the service will also be down. Partially down In an E-LAN service, if there is no connection between a pair of 2 SAPs, but some of the SAPs are still connected, the operational state of the service will be Partially down. Broken service If the NMS finds the same service ID in two subnets that are not connected, the operational state of the service will be Broken service. Partially configured A service can be set to only Partially configured if the Service succeeded, but with specific fail points.
SAP parameters
IP address - displays the IP address of the network element. The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and should be managed via the active unit. IDUs in such a shelf get each a slot ID indicating their position: slot 1 is the lowest IDU and 6 is the highest
Name indicates the slots system name. Slot indicates the name of the main slot. VLAN encapsulation type can be C-VID or Untagged for Managed switches, and All-to-one or S-VID for Metro switches.
Page 271 of 271

PolyView User Guide N6.8

Uploaded by

Document Information

Original Description:

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 User Guide N6.8

Uploaded by

Copyright:

Available Formats

PolyView N6.

Copyright 2012 Ceragon Networks Ltd. All rights reserved.

Open Source Statement

NMS User Guide PolyView N6.8

PolyView system overview

PolyView system overview

NMS User Guide PolyView N6.8

NMS User Guide PolyView N6.8

Preparing the network for system management

Configuring server memory usage

To configure server memory usage:

2. Select the Advanced tab.

NMS User Guide PolyView N6.8

Configuring the SMTP mail server

To configure the SMTP mail server:

NMS User Guide PolyView N6.8

2. Select the General tab.

Configuring the server time zone

To configure the application time zone:

NMS User Guide PolyView N6.8

2. Select the Advanced tab.

Restoring server configuration defaults

To restore PolyView server defaults:

NMS User Guide PolyView N6.8

To configure the ENM and HTTP proxy settings:

2. Select the General tab.

NMS User Guide PolyView N6.8

Configuring client browser proxy settings

For each browser that will be used to manage network elements:

File transfer settings

To configure FTP login information:

2. Select the File Transfer tab.

NMS User Guide PolyView N6.8

Configuring the FTP protocol

To configure the FTP protocol

2. Select the File Transfer tab.

NMS User Guide PolyView N6.8

Configuring TFTP login information

To configure TFTP login information:

2. Select the File Transfer tab.

Configuring the TFTP files location

To configure the FTP protocol

NMS User Guide PolyView N6.8

2. Select the File Transfer tab.

The folder name cannot contain spaces.

Configuring TFTP retries and timeout

To configure TFTP login retries and timeout:

NMS User Guide PolyView N6.8

2. Select the File Transfer tab.

To configure the servers TCP port:

NMS User Guide PolyView N6.8

2. Select the General tab.

To enable TCP communication in a redundant system:

NMS User Guide PolyView N6.8

2. Click the Remote Hosts tab.

Configuring the user actions logger port

To configure the user actions logger port:

NMS User Guide PolyView N6.8

2. Select the General tab.

Configuring the ENM proxy port

To configure the ENM proxy port:

NMS User Guide PolyView N6.8

2. Select the General tab.